CPE I common mistakes
CPE I · Understand the traps and how to avoid them.
Treating the exam as a pure recall test and memorizing formula sheets instead of practising problems that require selecting the correct governing relation, checking unit consistency, and sanity-checking the result.
Many candidates come from coursework where plugging numbers into a provided equation earned full marks, so they underestimate how often the exam tests judgement about which principle applies and whether an answer is physically plausible.
What to do instead
Work through mixed problem sets where you must first state the assumptions and the governing principle in one sentence, then solve, then verify magnitude and units. Time yourself and keep an error log of every problem where the method was right but the model choice was wrong.
Skipping the unit and dimensional check on numeric answers, submitting a result that is off by a factor of 1000 or in the wrong unit system.
Under time pressure, candidates jump from the last calculation step straight to the answer options and pattern-match the digits, ignoring prefixes such as milli, kilo, and mega or mixing gauge and absolute pressure.
What to do instead
Adopt a fixed habit: before looking at the options, write the final value with its unit and do a one-line dimensional check. Practise converting between SI and common engineering units until it is automatic, and deliberately include unit-conversion distractors in your practice.
Producing a design or analysis answer that jumps to a solution without stating requirements, constraints, assumptions, and the basis of design.
Candidates are used to textbook problems where everything needed is given, so they omit the framing step that the exam rewards, and then lose credit even when the final number is defensible.
What to do instead
Use a fixed template for every design or analysis item: objective, given data, assumptions, governing relations, calculation, check against constraints, conclusion. Practise writing the template in under two minutes so it becomes the default response pattern rather than an afterthought.
Failing to perform a sensitivity or reasonableness check on a calculated design value, accepting a result that is technically computed but outside practical engineering ranges.
Candidates focus on arithmetic correctness and forget that exam items often embed an answer that follows from the math but violates a physical or practical limit, such as a negative thickness or an efficiency above 100 percent.
What to do instead
After each calculation, ask three questions: is the sign sensible, is the order of magnitude plausible for this equipment, and does the result satisfy every stated constraint. Build a short list of typical ranges for common quantities and review it before the exam.
Building a schedule or plan that lists activities but ignores dependencies, resource limits, and float, then answering sequencing questions from intuition.
Candidates conflate a task list with a plan and have not practised forward and backward pass calculations enough to do them quickly and accurately under exam conditions.
What to do instead
Drill critical path method problems until forward pass, backward pass, total float, and free float are routine. For planning questions, explicitly identify the constraint being tested (logic, resource, or calendar) before choosing an answer, and practise crashing and fast-tracking trade-off questions.
Confusing monitoring and controlling with execution, or selecting a corrective action without first identifying the variance and its root cause.
Project-control terminology overlaps in everyday usage, and candidates answer from general management intuition rather than from the sequence of measure, compare, analyse, act that the exam expects.
What to do instead
Memorize the control loop as a sequence and apply it explicitly to scenario questions: what was measured, against what baseline, what is the deviation, what is the cause, what action follows. Practise earned value problems until variance and index interpretation is immediate.
Answering quality questions by naming a tool (fishbone, Pareto, control chart) without matching the tool to the phase of the problem, such as using a control chart to generate root-cause hypotheses.
Candidates memorize tool names from a list without linking each tool to its purpose, its inputs, and the type of data it handles, so they choose by familiarity rather than fitness.
What to do instead
Build a two-column table of quality tools with the question each one answers and the data type it requires. For each practice item, justify in one sentence why the chosen tool fits and why the strongest distractor does not.
Treating safety and regulatory items as common-sense questions, choosing the answer that seems most reasonable rather than the one consistent with the hierarchy of controls or the cited standard.
Candidates without field exposure rely on intuition, and intuition often favours administrative measures or personal protective equipment over elimination and engineering controls, which the exam ranks differently.
What to do instead
Learn the hierarchy of controls in order and apply it explicitly to every safety scenario. For regulatory items, identify which standard or jurisdiction is implied and answer from that framework, not from general practice. Flag any standard you cannot state confidently and review it.
Handling ethics scenarios by choosing the option that protects the employer or the client relationship instead of the option that protects public safety and discloses the conflict through the proper channel.
Candidates read ethics items as loyalty tests and worry that escalation looks disloyal, so they pick informal resolution or silence when the correct action is a documented, escalated disclosure.
What to do instead
Anchor every ethics answer on the primacy of public welfare, competence limits, and full disclosure. Practise a fixed decision sequence: identify the duty, identify who is at risk, identify the proper reporting channel, then choose the option that follows it. Rehearse confidential-reporting scenarios specifically.
Giving vague, hedged answers to communication and teamwork scenarios, or choosing to avoid the conversation rather than address the issue directly with the person concerned.
Candidates fear conflict and select the politest-sounding option, but exam items generally reward direct, timely, documented communication with the person involved before escalation.
What to do instead
Prefer answers that address the issue directly and early, use specific observable behaviour rather than character judgements, and escalate only after direct attempt or when safety or ethics requires it. Practise writing feedback in a behaviour-impact-request structure and apply that structure when evaluating answer options.