REPA common mistakes
REPA · Understand the traps and how to avoid them.
Treating ISO 14001 clauses as a checklist of documents to confirm exist, rather than evaluating whether the environmental management system (EMS) is effective and risk-based.
Candidates study the standard as a list of required procedures and equate 'documented' with 'conforming', which is a common habit from document-focused training and misses the process-approach and risk-based thinking that exam questions reward.
What to do instead
For each clause, ask 'what is the intended outcome, and what objective evidence shows it is achieved?'. Practise rewriting each requirement as an effectiveness question (e.g., not 'is there an aspects register?' but 'does the register drive controls that match the significance of impacts?').
Confusing the roles of ISO 14001, ISO 19011, and ISO 17021, and attributing audit-programme management or auditor-competence requirements to the wrong standard.
These standards overlap in vocabulary (audit, competence, programme), and candidates memorise clause numbers without mapping each standard to its scope: EMS requirements versus auditing guidance versus certification-body requirements.
What to do instead
Build a one-page table with columns for scope, intended user, and whether it is normative or guidance, and place each concept (audit programme, competence, nonconformity, corrective action) in the correct column. Test yourself by naming the source standard for each concept.
Answering legal-compliance questions from general intuition about 'environmental law' instead of identifying the specific obligation, permit condition, or regulator involved.
Candidates without a jurisdiction-specific legal background generalise from general principles and overlook that compliance is defined by the applicable permits, licences, and reporting duties of the site.
What to do instead
Study the compliance-obligation evaluation process: identify legal and other requirements, determine how they apply, and evaluate compliance. Practise questions by first naming the type of obligation (permit limit, monitoring/reporting duty, notification duty) before choosing an answer.
Missing that an auditor must verify the organisation's own determination of its legal and other requirements, rather than accepting the legal register at face value.
The legal register is often presented as an authoritative document, and candidates treat it as evidence of compliance instead of as a claim requiring verification against current requirements.
What to do instead
Treat the legal register as an assertion. Ask what evidence shows it is complete and current (review process, update triggers, ownership, coverage of new activities) and how compliance is evaluated and recorded.
Writing audit objectives, scope, and criteria as interchangeable statements, for example putting the audit criteria into the scope or omitting boundaries such as sites, shifts, and outsourced processes.
The three terms are defined close together and candidates learn them as a single 'planning' topic without separating what the audit is for (objectives), what it covers (scope), and what it is measured against (criteria).
What to do instead
Draft three separate one-sentence statements for a fictional organisation and check each against its definition: objectives state purpose and intended outcomes; scope states boundaries and limitations; criteria state the standards, permits, and internal requirements used.
Designing sampling and audit trails that follow the audit plan's clause order rather than following processes, significant aspects, and risk across functions.
Checklist-driven planning feels thorough and is easier to prepare, but it fragments evidence and hides cross-functional issues such as a significant aspect whose controls depend on several departments.
What to do instead
Plan by process and by significant aspect, tracing each from identification through controls, monitoring, and review. Use the clause list only as a completeness check at the end of planning.
Recording observations as conclusions ('waste management is poor') instead of verifiable evidence linked to a criterion, making findings indefensible.
Candidates compress evidence into judgements while writing notes, then cannot reconstruct what was seen, where, when, or against which requirement.
What to do instead
Record in a fixed pattern: criterion, evidence (what was observed or sampled, source, date, sample size), and result. Keep conclusions out until the evidence is complete, and test each note by asking whether a second auditor could re-verify it.
Classifying every issue as a nonconformity, or downgrading real nonconformities to observations to avoid conflict.
Candidates lack practice applying the definition of nonconformity (failure to meet a requirement) and are influenced by the auditee's reaction or by fear of escalation.
What to do instead
Practise sorting a set of findings against the criterion: if a requirement is not met, it is a nonconformity regardless of severity; grade it by significance and risk, and record observations separately as improvement opportunities. Justify the classification in writing using the criterion text.
Writing reports that list findings without stating the audit conclusion, and closing corrective actions on the strength of a proposed action rather than verified implementation and effectiveness.
Report templates emphasise findings, and follow-up is often treated as an administrative step, so candidates accept a corrective-action plan as closure.
What to do instead
Structure reports around objectives, scope, criteria, conclusion, and findings. For follow-up, require evidence of implementation and a check that the root cause was addressed; state explicitly what evidence would justify closure.
Describing environmental aspects as impacts, or listing impacts without linking them to activities, products, and services and to the significance criteria used.
The terms are closely related and often used loosely in workplace language, and candidates memorise definitions without practising the cause-and-effect chain from activity to aspect to impact.
What to do instead
Practise chains: activity (spray painting) leads to aspect (solvent emission) leads to impact (air quality and health effects), then apply the organisation's significance criteria. Check that each aspect traces to an activity and each impact traces to an aspect.
Choosing end-of-pipe treatment as the answer when the question tests the waste hierarchy or pollution prevention, and ignoring source reduction and substitution.
Treatment feels concrete and familiar, while prevention options require reasoning about the hierarchy and life-cycle thinking, which candidates under-practise.
What to do instead
For each scenario, list options in hierarchy order (prevent, reduce at source, reuse, recycle, recover, treat, dispose) and identify the highest applicable option before evaluating feasibility and cost.
Overlooking independence, objectivity, and confidentiality conflicts, such as auditing a process the auditor previously managed or disclosing site information casually.
Technical content dominates study time, so ethical requirements are treated as common sense rather than as auditable requirements with specific behaviours.
What to do instead
Learn the specific conflict situations (recent operational responsibility, consultancy, personal relationships) and the required response (decline, disclose, reassign). Rehearse short scenarios and identify the correct action and the reason for it.