PEPT common mistakes
PEPT · Understand the traps and how to avoid them.
Treating a conflict-of-interest question as a pure ethics question and picking the 'most ethical-sounding' option, without first identifying the concrete duty owed (to employer, client, public, or regulator) and which duty is paramount.
Candidates memorise slogans such as 'public safety first' and apply them by feel; they do not map the scenario onto the hierarchy of obligations or notice when a secondary interest (gift, family tie, prior employment) is the actual trigger.
What to do instead
Before answering, write one line: who is the client, who is the employer, who is at risk, and what does the code require to be disclosed and to whom. Reject any option that resolves the conflict silently or defers disclosure until after the decision.
Answering regulatory questions from general engineering habit rather than from the specific statutory instrument, e.g. assuming a professional engineer's seal is required for all drawings, or that any competent person may certify a regulated activity.
Most candidates practise under one jurisdiction and generalise; exam items deliberately test the boundary of reserved practice, delegated authority, and statutory notification duties.
What to do instead
Build a one-page matrix per jurisdiction covered: reserved titles, reserved activities, who may certify, mandatory notifications to the regulator, and penalties. For each practice question, ask 'which instrument authorises this act?' before choosing.
Confusing the standard of care in negligence with strict liability or with contractual warranty, and concluding that because a design met code the engineer cannot be liable.
Code compliance is a floor, not a defence; candidates conflate 'I followed the standard' with 'I exercised reasonable skill and care', and miss fact patterns where a known risk was foreseeable.
What to do instead
For liability items, run three tests in order: was a duty owed, was it breached relative to what a reasonable peer would do with the same information, and was the loss within the scope of that duty? Treat code compliance as evidence of care, not proof of it.
Computing net present value, equivalent annual cost, or payback by mixing nominal cash flows with a real discount rate, or by discounting at the wrong point in the period.
Time-zero conventions and inflation treatment are the two most common arithmetic traps; candidates also forget to include salvage value, working capital release, or tax effects in incremental cash flow.
What to do instead
State the convention explicitly at the top of your working: 'all cash flows end-of-year, nominal, discounted at nominal rate'. Convert rates with (1+nominal)=(1+real)(1+inflation) before discounting, and reconcile the incremental cash flow table to the project's free cash flow.
Reading a network diagram and reporting the critical path by longest duration rather than by zero total float, then quoting a project duration that ignores a near-critical path with small float.
Candidates do forward and backward passes mentally and skip the float calculation; near-critical paths with one day of float are easily missed and change the risk answer.
What to do instead
Always tabulate early start, early finish, late start, late finish, and total float for every activity, however short the network. Identify the critical path as the chain with zero total float and separately list activities with float below a stated threshold as near-critical.
Treating a hierarchy of controls question as satisfied by any control that reduces exposure, e.g. accepting PPE or a warning sign where elimination, substitution, or engineering isolation was reasonably practicable.
Candidates answer from site experience where PPE is normal, and forget that the hierarchy is a legal and ethical ordering, not a menu of equal options.
What to do instead
Rank the proposed controls against the hierarchy explicitly: elimination, substitution, engineering, administrative, PPE. Choose the highest practicable level and justify why lower levels were not reasonably practicable, not merely inconvenient or costly.
Assuming a quality management system certificate proves product conformity, or that a nonconformity is closed once a corrective action is written rather than verified as effective.
Candidates conflate certification of a process with conformity of an output, and treat corrective action as paperwork rather than a loop requiring root-cause analysis and effectiveness review.
What to do instead
Separate the three questions: does the process conform, does the product conform, and was the corrective action effective? For nonconformity items, expect root cause, containment, corrective action, and verification of effectiveness as distinct steps.
Answering contract administration items by choosing the commercially fair outcome instead of the outcome the contract's notice, variation, and time-bar provisions actually produce.
Candidates reason from fairness and goodwill, and underestimate how strict notification deadlines, deemed acceptance, and payment provisions override the merits of a claim.
What to do instead
For every contract scenario, first identify the trigger event, the notice period, the required form of notice, and the consequence of missing it. Answer within the contract mechanism; note fairness only if the question asks about negotiation strategy.
Reducing sustainability questions to a single metric such as operational carbon or capital cost, ignoring whole-life carbon, embodied impacts, resource depletion, and distributional effects on affected communities.
Candidates reach for the metric they use at work and miss that exam items test lifecycle thinking and stakeholder impact, including the difference between efficiency gains and absolute reductions.
What to do instead
Structure the answer around lifecycle stages (materials, construction, operation, end of life) and impact categories (carbon, water, land, health, equity). Where a rebound effect or burden-shifting is plausible, name it explicitly before concluding.
In leadership and teamwork scenarios, choosing the option that avoids confrontation, such as escalating immediately or reassigning work quietly, instead of addressing the performance or conduct issue directly with the person concerned.
Candidates equate professionalism with harmony and fear that direct feedback is unprofessional; they also confuse delegation with abdication of accountability.
What to do instead
Apply a fixed sequence: raise the issue privately and specifically with the individual, agree an action and a review date, document it, then escalate only if the issue persists or risk is serious. Retain accountability for delegated work rather than transferring it.