PEC EPE Part-I common mistakes
PEC EPE Part-I · Understand the traps and how to avoid them.
Answering ethics items with personal opinion about what is 'right' instead of applying the code's defined obligations (e.g., duty to report, conflict-of-interest disclosure, competence limits) and the priority order of public safety, employer, and client.
Candidates study ethics as general good behaviour and never learn the operative clauses of the engineering code, so they reason from instinct and pick the answer that sounds most virtuous rather than the one the code mandates.
What to do instead
Build a one-page 'code map' of the clauses you will be tested on: paramountcy of public welfare, competence boundary, conflict of interest, confidentiality, reporting unsafe practice, and signing/sealing authority. For every practice question, cite the clause that drives the answer before selecting the option.
Treating 'notify the client/employer' and 'report to the regulator' as interchangeable, and choosing notification when the situation requires a formal report (or vice versa).
The two duties serve different purposes and have different triggers, and candidates rarely separate them in study. Under exam pressure they default to the softer, internal action.
What to do instead
Tabulate escalation paths: internal first (supervisor, then employer's responsible officer), external when the public is at risk or the internal route fails, regulator when there is a legal reporting duty or continuing unlicensed practice. Practise classifying scenarios by trigger, not by tone.
Ignoring units and dimensional consistency in design calculations, mixing kN and N, MPa and kPa, or mm and m, and then selecting an answer from the options that matches the arithmetic error.
Working quickly under time pressure, candidates substitute numbers into memorised formulas without carrying units through, and distractors are deliberately built from the common unit slips.
What to do instead
Carry units through every step and do a magnitude sanity check before looking at the options (e.g., a 300 mm beam is not 0.3 m deep in a span/deflection check unless the span is also converted). Where possible, estimate the answer order of magnitude first.
Applying a design formula outside its stated validity limits, for example using a simplified beam or column equation beyond its slenderness, span-to-depth, or material-strength range without checking applicability.
Revision compresses standards into a handful of formulas, and the conditions attached to them are the first thing dropped. Candidates recognise the formula and stop reading.
What to do instead
For each formula you revise, write the three conditions that must hold (geometry limits, material limits, load or support assumptions) alongside it. In the exam, state the check explicitly in your working so a wrong applicability call is at least visible and partially creditable.
Using the wrong load combination or the wrong load factors because the candidate applies a remembered combination rather than the one matching the limit state and structure type in the question.
Load combinations look similar across codes and editions, and candidates memorise one 'standard' combination instead of the set.
What to do instead
Memorise the combination families (ultimate versus serviceability, permanent plus leading variable plus accompanying variable, with and without wind or seismic) with their factors, and note which edition the exam syllabus cites. Read the question for the limit state keyword before choosing factors.
Answering code and standards questions from general engineering intuition rather than the specific clause, so answers reflect common practice instead of the mandatory requirement.
Experienced candidates rely on habit and site practice, which often exceeds or lags the code minimum, and the exam tests the minimum requirement as written.
What to do instead
Separate 'good practice' from 'code requirement' in your notes. For each topic, record the clause number and the exact obligation (shall versus should). When a question asks what is required, answer from the clause, not from what you would do on site.
Producing reports with no explicit structure: findings, analysis, and recommendations blended into one narrative, with no executive summary and no traceable basis for conclusions.
Candidates write reports as they would write an email, in chronological order of what they did, rather than in the order a reviewer needs to make a decision.
What to do instead
Use a fixed skeleton every time: purpose and scope, basis of assessment (codes, data, assumptions), findings with evidence, analysis and limitations, recommendations with owners, appendices. Draft the headings before writing a single sentence and check each section answers the question its heading promises.
Stating conclusions and recommendations without showing the supporting calculation, data source, or assumption, so the report asserts rather than demonstrates.
Candidates assume the reader shares their context and treat working as scratch paper rather than as part of the deliverable.
What to do instead
For every conclusion, include the number, the method, and the input it rests on, either inline or in a referenced appendix. Adopt the rule that no recommendation appears without an explicit basis sentence immediately before it.
Mismanaging time by spending disproportionate effort on one long calculation or one essay-style answer and leaving short factual items or the report section unanswered.
The paper mixes calculation, short answer, and extended writing, and candidates allocate time by interest rather than by marks per minute, often over-investing in the first heavy question.
What to do instead
Before starting, compute minutes per mark and write the target finish time for each section on the answer booklet. Set a hard stop per question, leave a marked gap if incomplete, and bank the easy marks first so no item is left blank.
Failing to answer the question actually asked: writing everything known about a topic instead of addressing the specific verb (compare, evaluate, justify, state two reasons) and the stated scope.
Under pressure, candidates dump recalled content as a safety strategy and hope markers find the answer, which wastes time and dilutes the credited points.
What to do instead
Underline the command verb and the scope limit in every question before answering. Structure the response to match the verb (a comparison needs both sides and a criterion; a justification needs reasons tied to evidence) and stop when the required points are covered.