COREN Registered Engineer common mistakes
COREN Registered Engineer · Understand the traps and how to avoid them.
Reciting a COREN Act section or decree number from memory when the question asks which body performs a function, and mixing up COREN with NUC, NSE or a federal ministry.
Study notes list legal instruments as isolated dates; under time pressure the brain retrieves the most familiar acronym rather than the statutory function.
What to do instead
Build a one-page function-to-instrument table covering registration, licensing, programme accreditation, discipline, standards and enforcement; for each function write the responsible body and instrument, then practise 'who acts' scenarios rather than 'what year' recall.
In an ethics scenario involving imminent public danger, selecting 'report to my supervisor and await instructions' instead of stopping the unsafe work and escalating.
Candidates import workplace deference into the exam and treat the chain of command as the highest duty, even when harm is foreseeable.
What to do instead
Rank obligations explicitly: public safety and life first, then law and regulation, then client or employer, then career. Ask 'who can be harmed if I wait?' and choose the action that prevents harm first, then document and escalate.
Assuming that passing the registration examination and having a name on the register automatically authorises indefinite sealing of drawings and independent practice.
Registration is studied as a one-off credential; the annual practice licence, CPD and renewal are treated as administrative afterthoughts.
What to do instead
Separate the concepts: registration establishes title and register entry; the practice licence is time-bound and tied to CPD and good standing. Verify current licence status before signing and track renewal dates.
In a project-delivery sequence question, placing site mobilisation and excavation before statutory approvals, environmental assessment and buildability review.
Schedules are memorised as activity lists, and political pressure to show early progress rewards starting work before approvals are complete.
What to do instead
Use a gated sequence: feasibility and site investigation, statutory approvals and permits, design freeze, constructability and safety review, then mobilisation. Eliminate any option that says 'start early and regularise later'.
Selecting PPE, such as respirators or ear defenders, as the primary control for a dust or noise hazard instead of engineering or substitution controls.
PPE is visible and cheap, and candidates equate 'safety answer' with 'wear protective equipment' rather than controlling the hazard at source.
What to do instead
Apply the hierarchy of controls in order: eliminate, substitute, engineer, administrate, then PPE. Choose the highest feasible control at source and treat PPE as the last line of defence, not the first.
Mixing units in calculations - kN with N, mm with m, MPa with N/mm² - and selecting an answer because the number 'looks right'.
Formulae are memorised without dimensional tracking, and exam pressure encourages skipping unit conversion.
What to do instead
Write units beside every substituted value, convert to one consistent system before calculating, and perform a final dimensional and order-of-magnitude check. If the result is a factor of 1000 off, suspect a unit conversion.
Applying a familiar code clause or edition without checking whether that code is adopted for the project, its national annex, or the clause's scope.
Textbooks and study notes usually rely on one code, so candidates treat that code as universal and ignore project-specific adoption.
What to do instead
Before calculating, identify the governing code, edition, national annex and clause scope. State assumptions in the answer; for a Nigerian project, verify adoption rather than defaulting to a foreign code.
Crashing a schedule by adding labour or equipment to every activity, including non-critical ones, and expecting the completion date to move earlier.
Activity duration is confused with project duration; 'more resources equals faster' is intuitive but false when applied off the critical path.
What to do instead
Calculate the critical path first, crash only critical activities, and re-run the network after each change because a new critical path can appear. Compare crash cost per day saved before selecting an option.
Continuing with a tender evaluation or design approval when a relative, former employer or financial interest is involved, or accepting a 'facilitation' payment, without written disclosure.
Conflict rules are memorised as phrases rather than applied, and small gifts are normalised as local hospitality.
What to do instead
Use a written declaration before engagement and recuse where a reasonable observer would doubt impartiality. Record gifts and hospitality in a register; if unsure, disclose and seek written guidance before acting.
Proceeding with a verbal instruction or client change on site without issuing or requesting written confirmation, and later sealing the as-built drawing.
Speed and deference to the client make paperwork feel like delay, so undocumented changes enter the permanent record.
What to do instead
Convert every instruction and change into a written site instruction, RFI or change order before execution; confirm scope, cost and safety impact and retain the record. Do not seal work that cannot be traced to an approved, documented instruction.