MPPSC SES Civil common mistakes
MPPSC SES Civil · Understand the traps and how to avoid them.
Treating the paper as a single combined technical test and allocating study time evenly across all ten domains, so Structural Engineering and Geotechnical get the same hours as Surveying or Remote Sensing.
The syllabus lists many domains, which creates a false impression of equal weightage; candidates coming from a civil engineering degree default to revising their college strengths and neglect the state-specific and management portions entirely.
What to do instead
Build a weightage table from the official syllabus and past-paper topic frequency, then assign hours proportional to marks and to your personal gap. Reserve fixed weekly slots for the low-familiarity domains (Estimating, Remote Sensing, State GK) so they are never squeezed out by structural revision.
Solving numerical problems without writing the unit and dimension at each intermediate step, then carrying an unnoticed factor-of-1000 or kN-to-N error to the final answer.
Coaching material often shows only the final line, so candidates imitate the shortcut style; under time pressure the habit of tracking units collapses and the arithmetic looks plausible enough to be accepted uncritically.
What to do instead
Adopt a fixed solution template: state given data with units, state the formula symbolically, substitute with units, then box the answer with units and a sanity check (e.g. concrete strength in the 20-40 MPa band, soil bearing capacity in the 100-500 kPa band). Practise twenty problems using only this template until it is automatic.
Memorising IS code clause numbers and values as isolated facts without knowing which clause applies to which design situation, so a question framed as a scenario cannot be mapped to a provision.
Revision notes and MCQ compilations present codes as lists of numbers, which rewards rote recall; the exam increasingly frames questions as short design or site situations, and the mapping step is never practised.
What to do instead
For each frequently tested code (IS 456, IS 800, IS 1893, IS 1904, IS 10262), write a one-page decision map: situation to clause to governing limit. Then attempt scenario-style questions and justify the clause choice in writing before checking the answer.
Answering geotechnical questions from memory of typical values without checking whether the question specifies saturated, dry, or submerged conditions, or whether it asks for total or effective stress.
Effective stress, bearing capacity, and settlement formulas differ only by a few terms between drainage conditions, so the recalled formula feels correct; candidates rarely slow down to classify the drainage condition before substituting.
What to do instead
Before any soil mechanics calculation, write one line: drainage condition, total or effective, short-term or long-term. Solve every problem twice where possible, once by formula and once by a sketch of the stress or failure mechanism, and reconcile the two.
Treating hydrology and hydraulics as formula recall, so unit hydrograph ordinates, return period probability, and specific energy are computed with the right formula but the wrong basis (catchment area, duration, or datum).
These topics have compact formulas that look self-sufficient, and the conditions attached to them (unit duration, linearity assumption, critical depth definition) are stated in the textbook prose that candidates skip.
What to do instead
For each hydraulic and hydrologic formula, maintain a card listing assumptions, units of each variable, and one worked example with a diagram. Redo unit hydrograph conversion and specific energy curve problems from first principles at least twice before the exam.
Studying environmental engineering only as treatment-process descriptions, without being able to compute BOD dilution, population-equivalent flows, or the design parameters of a septic tank or trickling filter.
The descriptive parts of the syllabus (water quality standards, pollution control) dominate most study material, and numerical design questions appear less frequently in casual practice, so the calculational side is never drilled.
What to do instead
Work a fixed set of standard numericals: BOD/DO sag, population forecasting by three methods, design of a sedimentation tank and a trickling filter, chlorination dose, and sludge volume. Keep a one-page formula sheet with typical design values (e.g. per-capita demand, BOD of domestic sewage).
Skipping the geometric design numericals of transportation engineering (superelevation, transition curve length, sight distance, pavement thickness by CBR) in favour of descriptive highway material questions.
Transportation feels like a general-awareness topic about roads and codes, and the design formulas look like a small subset; candidates therefore under-invest and meet them cold in the exam.
What to do instead
Treat the geometric design chapter as a guaranteed numerical block: derive superelevation and extra widening, compute SSD and OSD for given speed and friction, and design a transition curve. Practise with the standard design speed and coefficient values so the constants are known without lookup.
Preparing surveying and remote sensing only at the level of instrument names and definitions, unable to solve a level-book reduction, a traverse adjustment, or a scale and resolution calculation.
These domains are perceived as 'light' topics suitable for quick reading, and the small numerical component is easy to postpone; when postponed to the last week it is never practised.
What to do instead
Allocate two dedicated sessions: one for level-book and theodolite traverse computations including closing error adjustment, and one for photogrammetry and remote sensing numericals (scale, flying height, relief displacement, resolution, NDVI-type index arithmetic). Solve one full numerical set from each before moving on.
Attempting estimating and project management questions without a mental model of a bar chart, CPM network, or rate analysis, so questions on critical path, float, and quantity take-off are answered by guesswork.
The domain is treated as clerical rather than analytical, and candidates from a design-oriented background have rarely drawn a network or prepared a rate analysis by hand.
What to do instead
Draw at least ten small networks by hand and compute ES, EF, LS, LF, total float, and critical path for each; prepare two full rate analyses and one detailed estimate (e.g. a single-storey building) with measurement sheets. This builds the pattern recognition the questions test.
Leaving Madhya Pradesh-specific general awareness, language, and reasoning to the final days, and revising them only through random quiz apps rather than a structured state-specific source.
The technical domains consume all available preparation time, and candidates assume general awareness is unpredictable; in practice the state portion is drawn from a bounded set of themes (geography, rivers, dams, forests, schemes, culture, current appointments).
What to do instead
Maintain a running one-page-per-theme state file from the start of preparation: physiography and river systems, major dams and irrigation projects, protected areas, state schemes, and current state appointments. Review it weekly and add a short reasoning and language practice set twice a week so these marks are secured rather than hoped for.