QETPP common mistakes
QETPP · Understand the traps and how to avoid them.
Memorising a procedure as a fixed sequence of steps and then answering ordering or 'which step may be omitted' items from that memorised order, without checking whether the published procedure makes a step conditional.
Step lists get compressed during study into a linear chant, so conditional, optional, and repeat-after-failure steps collapse into the same rank as mandatory ones; the question then tests a branch the candidate never encoded.
What to do instead
Rewrite each procedure as a decision tree, not a numbered list: for every step, record the entry condition, the exit condition, and what triggers a repeat or hold point. Before answering any sequence item, ask 'what would make this step not apply?'
Working a calculation in whatever unit the values arrived in, then picking the answer that matches the raw arithmetic instead of converting to the unit the answer options use (for example leaving a current in milliamps when options are in amps, or dropping a per-unit or percentage scaling).
Numeric distractors are usually the same number with a decimal or prefix error, so a plausible-looking match rewards the unconverted result; time pressure discourages a second pass on units.
What to do instead
Adopt a fixed three-line habit for every numeric item: write the target unit first, convert all inputs to base units, then compute. Sanity-check with an order-of-magnitude estimate before looking at options, and reject any option outside that band.
Treating normative wording as interchangeable - reading 'shall', 'should', 'may', and 'recommended' as the same strength of requirement, and selecting an answer that describes good practice when the stem asks what is required.
Study summaries and informal notes flatten modal verbs into plain instructions, so the candidate never learns that 'should' answers can be wrong when the stem asks for the mandatory minimum.
What to do instead
While reading source material, highlight every modal verb and tag it mandatory / advisory / permitted. Drill with paired items where the only difference is the modal verb, and in the exam underline the requirement-strength word in the stem before evaluating options.
Reading the stem, recognising a familiar topic, and selecting an option before finishing the sentence - missing a trailing qualifier such as 'EXCEPT', 'least appropriate', 'first action', or 'most cost-effective'.
Recognition memory fires on the topic keyword and produces a strong feeling of knowing, which short-circuits the slow work of parsing the actual ask; negatively worded items are also rarer, so they are not expected.
What to do instead
Cover the options with your hand, read the stem to the final word, and restate the ask in your own words in one short phrase. Only then uncover options. For negative stems, cross out the three true statements rather than hunting for the false one.
Answering scenario items from personal site experience when that experience conflicts with the published acceptance criteria - for example choosing the field-pragmatic action over the documented threshold or escalation path.
Experienced candidates have been rewarded for practical judgement for years, and real workplaces tolerate deviations the standard does not; the exam scores the documented requirement, not the local workaround.
What to do instead
Separate the two voices explicitly: label a scenario as 'what I do at work' versus 'what the document requires', and answer the second. Where you know your practice deviates, note the deviation and its documented rule as a study card.
Facing two options that differ only by a numeric threshold or a time interval, and choosing the middle value or the one that 'feels typical' instead of recalling or deriving the actual figure.
When the exact number is not consolidated, the candidate substitutes plausibility for recall; adjacent distractors are constructed precisely to make the middle of the range feel safe.
What to do instead
Build a one-page table of every threshold, interval, and tolerance in the syllabus and rehearse it with flashcards that hide the number, not the concept. If a number is genuinely unknown on exam day, derive it from a related formula or reject options that contradict a known boundary.
Spending a disproportionate block of time on one multi-step calculation or ambiguous scenario early in the sitting, then rushing the final items and leaving several unanswered.
Sunk-cost persistence on a single hard item plus the absence of a per-item time budget means the clock is discovered late, when the remaining items can only be skimmed.
What to do instead
Pre-set a per-item ceiling from total items divided by available minutes, flag and move on the moment an item exceeds roughly double that, and reserve the last portion of the sitting for flagged items. Never leave a blank - a marked best guess costs nothing.
Confusing role boundaries - selecting the person who performs an activity when the item asks who approves, witnesses, authorises, or must be notified, or assuming one role can hold two responsibilities simultaneously.
Roles are learned as a list of job titles rather than as a matrix of actions against accountabilities, and in small teams one person often covers several roles in practice.
What to do instead
Draw a grid of activities down one axis and roles across the other, filling in perform / verify / approve / notify cells. For each item, identify which cell the verb points to before looking at the options.
Applying a formula correctly in algebra but outside its stated conditions of validity - using a relationship beyond its linear or steady-state range, ignoring temperature or load correction, or omitting a required assumption check before substituting values.
Formula recall is easier than premise recall, so candidates rehearse the equation and skip the surrounding text that limits when it may be used; exam items often embed an out-of-range condition that invalidates the obvious formula.
What to do instead
For each formula, write a companion note listing applicability limits, required corrections, and the check that must pass before use. In the exam, scan the given data for values that violate those limits before starting the arithmetic.
On 'best answer' items, selecting the first option that is factually true rather than the one that ranks highest on the criterion the stem names - typically risk severity, criticality, or order of precedence.
Several options are deliberately true statements, so truth is a weak filter; without an explicit ranking rule the candidate stops at the first comfortable answer.
What to do instead
Before evaluating options, name the ranking criterion out loud from the stem. Then score every option against that single criterion, discarding true-but-irrelevant statements, and choose only after all options have been scored.
Revising answers during final review without a stated reason, or conversely refusing to revisit flagged items at all, so genuine misreads are either introduced or left uncorrected.
Anxiety near the end of the sitting produces undirected second-guessing, while overconfidence in first instincts prevents the targeted re-read that catches trailing qualifiers and unit slips.
What to do instead
Review only flagged items and only against a checklist: did I read the final word of the stem, did I convert units, did I answer the verb that was asked. Change an answer only when the checklist exposes a specific defect, never on a vague feeling.