ICC C5 common mistakes
ICC C5 · Understand the traps and how to avoid them.
Memorizing code section numbers and clause titles instead of learning what each requirement actually obliges a duty holder to do, so questions that describe a real scenario in plain language are answered by pattern-matching the wording rather than by applying the requirement.
The code is long and number-heavy, so candidates build flashcards of references because they feel measurable and testable. Scenario questions then arrive without the trigger words the candidate memorized, and the reference knowledge cannot be converted into an answer.
What to do instead
For each major clause, write a one-sentence paraphrase in your own words starting with 'The duty holder must...' and then a second sentence naming who is responsible and what evidence proves compliance. Practise by reading a scenario first, deciding the obligation, and only then looking up the clause number to check yourself.
Treating the exam as a single-discipline test and skipping the domains that feel least familiar, so whole question blocks are answered from general knowledge rather than from the specific framework the exam expects.
Candidates often come from one background (engineering, inspection, project management) and unconsciously weight study time toward that background, leaving adjacent domains under-prepared until the week before the exam.
What to do instead
Build a study plan that allocates time in proportion to the number of questions per domain, not to personal comfort. For the weakest domain, do a diagnostic set of 20 questions early, log every wrong answer with its underlying concept, and revisit that log weekly rather than rereading notes.
Answering 'what should be done' questions with the most thorough or safest-sounding action rather than the action the framework actually requires at that stage, for example jumping to full remediation when the correct answer is to record, notify, and monitor.
Real-world instinct rewards doing more, and exam distractors are deliberately written as plausible over-reactions. Candidates who reason from good practice rather than from the documented process pick the strongest-sounding option.
What to do instead
Learn the process as an ordered sequence with defined decision points, and for each step note what is explicitly not required yet. When two options both seem defensible, ask which one matches the stage described in the stem and which one belongs to a later stage.
Ignoring the qualifiers in the question stem, such as 'first', 'most likely', 'except', 'before any work begins', or 'the primary responsibility of', and selecting an option that is true but does not answer the question asked.
Under time pressure candidates read for the topic and not the instruction, and the brain completes familiar question patterns. Negatively worded items are especially prone to being misread as positive ones.
What to do instead
Adopt a mechanical routine: underline or mentally flag the qualifier before reading the options, restate the stem in your own words in one line, and eliminate options on the basis of the qualifier rather than on plausibility. For 'except' items, mark each option T or F before choosing.
Failing to distinguish roles and responsibilities, so answers attribute an obligation to the wrong party, such as assigning a verification duty to the executing team or a reporting duty to the designer.
The framework uses several overlapping roles whose names sound similar, and candidates learn the duties as a list without mapping each duty to its owner. In practice these roles often overlap in small organizations, which reinforces the confusion.
What to do instead
Draw a responsibility matrix with roles as columns and key obligations as rows, and fill it from the source text rather than from memory. Then answer role-attribution questions by locating the obligation in the matrix before looking at the options.
Skipping the calculation or estimation questions because they look time-consuming, or estimating them mentally and selecting the nearest option without writing the working.
These items often sit late in a section, and candidates protect time by guessing. Mental arithmetic also hides unit and conversion errors that would be obvious on paper.
What to do instead
Treat calculation items as guaranteed marks: write the formula, substitute with units shown, and check the order of magnitude before choosing. Practise a fixed set of 15 calculation types until each takes under 90 seconds, and always sanity-check whether the answer is plausible for the scenario.
Choosing answers based on how documentation is usually produced in the candidate's own organization rather than on what the framework requires, so informal practices such as verbal sign-off or retrospective records are treated as acceptable.
Habitual workplace practice feels authoritative, and the exam's insistence on documented, traceable, contemporaneous records can seem like bureaucracy to experienced practitioners.
What to do instead
Separate 'what my site does' from 'what the requirement says' explicitly in your notes. For each record-related topic, write the required content, the required timing, and the required retention or traceability, then test yourself on which of those three an option violates.
Reading the whole paper once and answering in strict order, so difficult items consume disproportionate time and later, easier items are left blank or rushed.
Candidates fear missing questions and distrust their ability to return, so they grind through blockers. Anxiety about unfinished sections also degrades accuracy on the items they do attempt.
What to do instead
Use a two-pass strategy: answer items you can resolve within about a minute, flag the rest, and return only after the first pass. Before the exam, rehearse the pass structure with two full timed mock papers and record how many flagged items you convert on the second pass.
Studying only from summaries and slide decks and never attempting full-length timed practice, so knowledge is recognized but not retrievable under exam conditions.
Rereading feels productive and is comfortable, but it builds familiarity rather than recall. Candidates then experience the exam as harder than their preparation suggested and lose confidence mid-paper.
What to do instead
Shift the majority of study time to retrieval practice: closed-book recall, spaced self-testing, and at least three full timed papers under exam conditions. Review every error by writing the correct reasoning in one or two sentences, and re-test those items a week later.
Leaving items blank when unsure, or changing correct first answers on review without a specific reason, because of second-guessing driven by time pressure.
Candidates believe a blank is safer than a wrong answer, or they reinterpret a familiar stem as a trick question during review. Both behaviours reflect anxiety rather than evidence.
What to do instead
Confirm the exam's scoring rule in advance and, if there is no penalty for wrong answers, answer every item. On review, change an answer only when you can name the specific fact or qualifier you misread; otherwise keep the first response and move on.