AMIE Section B Civil common mistakes
AMIE Section B Civil · Understand the traps and how to avoid them.
Writing the answer to a structural design question without stating the design code, load combination, and units being used, so the examiner cannot tell whether the calculation follows a recognised basis.
Candidates practise calculations in isolation and treat the code reference as optional preamble, then run out of time and drop the assumptions to save writing.
What to do instead
Open every structural answer with a short 'basis' block: code and edition, load case, material grades, and unit system. Draft this block first in the answer booklet before starting numbers so it is never sacrificed to time pressure.
Producing a numerical answer to a structural analysis problem with no free-body diagram, no sign convention, and no check that reactions satisfy equilibrium.
Under exam pressure candidates jump straight to formulas memorised from worked examples and skip the sketch, which is where most sign and direction errors would be caught.
What to do instead
Adopt a fixed routine: sketch the member, draw the free-body diagram, state the sign convention, then compute. Finish with a two-line equilibrium check (sum of vertical forces and moments) written out explicitly, and carry units through every line.
Describing a geotechnical site investigation or foundation choice in general terms without linking it to the soil parameters, groundwater conditions, or the specific limit states being checked.
Soil mechanics is often revised as vocabulary rather than as a design process, so candidates recall the names of tests but not how the results drive bearing capacity or settlement decisions.
What to do instead
For each foundation question, write the parameter table first (unit weight, cohesion, friction angle, groundwater level), then state which limit state each parameter feeds. Practise converting a boring log into a design decision in under five minutes.
Treating hydraulics and water-resources questions as pure formula recall, giving a Manning or Darcy answer without checking that the assumed flow regime, roughness, or units are consistent with the question.
These topics appear formula-light, so candidates memorise equations and skip the assumptions embedded in them, such as uniform flow or laminar conditions.
What to do instead
Before substituting, write the validity conditions of the formula being used and confirm each one against the data given. Keep a one-page sheet of variable definitions and standard units per formula and rehearse dimensional checks on every answer.
Answering construction-management questions with a list of activities but no sequence logic, no critical path, and no resource or duration figures, so the answer reads as a general essay.
Candidates underestimate how quantitative planning questions are and rely on descriptive knowledge of management theory instead of practising network and scheduling techniques.
What to do instead
Rehearse drawing activity-on-node networks from a written scenario, computing earliest and latest times, and identifying float. Always present a table of activities with durations and dependencies, then state the critical path explicitly.
Ignoring the second half of a two-part question, typically the 'state the limitations', 'discuss the alternatives', or 'recommend and justify' instruction that carries a large share of the marks.
The calculation or description consumes the available time, and candidates do not budget marks against minutes, so the discursive section is left blank or reduced to one line.
What to do instead
Before writing, split the marks in the margin and allocate minutes proportionally. Answer the discursive part in bullet form first if time is tight, then expand, so a structured skeleton exists even if the clock runs out.
Using vague qualitative language in place of engineering quantities, for example saying a material is 'strong enough' or a slope is 'safe' without a factor of safety, stress value, or permissible limit.
Candidates are more comfortable with description than with committing to a number, and fear that a stated figure will be marked wrong.
What to do instead
Train yourself to attach a number and a source to every judgement: state the computed value, the limiting value, and the resulting factor of safety. A defensible stated assumption scores better than an unquantified claim.
Presenting calculations with no intermediate steps, mixed or missing units, and final answers without a stated magnitude and unit, making partial credit impossible to award.
Candidates copy the compressed style of textbook solutions and assume the examiner can follow the arithmetic, while exam-time pressure encourages shortcuts.
What to do instead
Write one operation per line with units carried throughout, box the final answer with its unit, and add a one-sentence sanity comment on whether the magnitude is plausible for the structure or material involved.
Misreading the scope of a question, for example designing for the wrong limit state, answering for the wrong member, or using service loads where factored loads were requested.
Questions contain several qualifiers and candidates skim them, pattern-matching to a familiar past question rather than reading the specific wording.
What to do instead
Underline every qualifier in the question (limit state, member, loading, code, units) before starting, and restate the requirement in one sentence at the top of the answer. Re-read the question against your answer in the final two minutes.
Spending disproportionate time perfecting one long design calculation while leaving several shorter questions untouched, resulting in large blocks of zero marks.
Candidates invest emotionally in a calculation they have already started and dislike abandoning it, and they misjudge how long a full design check takes under exam conditions.
What to do instead
Do a timed first pass answering the questions you can complete quickly, mark hard questions for return, and set a hard stop time per question. In practice, rehearse full papers with a clock and a written time budget per mark.