IRATA Level 3 common mistakes
IRATA Level 3 · Understand the traps and how to avoid them.
Answering Level 3 questions with Level 1 or Level 2 logic, for example describing how to descend a rope safely instead of describing how to plan, supervise and sign off the whole operation including the rescue and the exclusion zone.
Candidates revise the practical syllabus they already know and never study the supervisory responsibilities that separate Level 3 from lower grades, so they answer the question they wish had been asked.
What to do instead
For every scenario question, first state who is in charge, what the safe system of work is, and what happens if it fails, then add the technique detail. Practise writing a one-page method statement and rescue plan for a simple job and check it against the IRATA work guidelines headings.
Treating the IRATA qualification as a standalone licence and ignoring the requirement to work under a Member Company with a valid, in-date certificate and logbook.
Technicians remember their own training and assessment but not the employer-side validity conditions, so they give incomplete answers about when someone is legally and contractually allowed to work.
What to do instead
Memorise the three-part chain: valid technician certification (grade, in date, logbook current), employment by a Member Company, and a site-specific risk assessment and permit. Rehearse checking an expiry date and a company's membership status before mobilisation.
Describing a rescue as 'call the emergency services' or 'lower the casualty' without stating the rescue method, the rescuer's access, the anchor and the time target.
Rescue is often learned as a practical drill rather than as a planning question, so candidates give a headline answer and miss the elements the examiner is scoring.
What to do instead
Use a fixed structure for every rescue answer: casualty situation, rescue method (self-rescue, pick-off, descent, ascent, or separate rigging), equipment needed, anchor and rope setup, who performs it, and how the area is controlled. State that the rescue must be achievable by the team on site without relying on external services.
Giving generic hazard lists ('falls, weather, fatigue') instead of identifying the specific hazards of the described environment, such as hydrogen sulphide on an offshore platform, arc flash on a live substation, or rockfall on a natural cliff.
Candidates prepare broad health and safety content and then fail to transfer it to the industry context in the question stem.
What to do instead
Build a one-page hazard map for each sector in the syllabus: offshore oil and gas, power generation and petrochemical, and built and natural environments. For each, list the top five environment-specific hazards, the control measure, and the monitoring or permit requirement.
Omitting the reporting chain and timescales when asked what to do after an incident, near miss or equipment defect, and failing to say what evidence is preserved.
Candidates focus on the immediate first aid or rescue and treat paperwork as an afterthought, so they lose marks on the accountability part of the question.
What to do instead
Answer incident questions in sequence: make the area safe and treat casualties, preserve the scene and equipment, notify supervision and the Member Company, report through the site and company systems within the required timescale, then record and share the lesson learned. Name who is notified and what is quarantined.
Assuming a certificate number or a company logo proves validity, without checking grade, expiry date, logbook entries, and whether the Member Company's status is current.
Verification is treated as a clerical step, so candidates cannot describe what a client or site manager should actually inspect before allowing work.
What to do instead
Write out a verification checklist: technician name and grade, certificate expiry, logbook hours and recent work, employer's Member Company status and validity, and the site-specific assessment. Practise applying it to a short written scenario with one deliberately expired item.
Rigging answers that name anchors and knots but never mention edge protection, back-up devices, rope protection, or the consequence of a single-point failure.
Practical rigging is learned by repetition, and candidates describe what they do with their hands rather than the redundancy principles behind it.
What to do instead
For each rigging answer, explicitly state the main and back-up anchor arrangement, the rope protection at edges, the back-up device on each rope, and what happens if the primary system fails. Use the phrase 'independent back-up' and explain why independence matters.
Ignoring access, egress and the working platform when planning a job, and answering only about the descent or the work position itself.
The interesting part of rope access is the work at height, so candidates skip how the team gets to the anchor, how tools and materials reach the work front, and how the area below is controlled.
What to do instead
Plan every scenario from arrival to demobilisation: approach and anchor access, rigging and pre-use checks, tool and material transfer, the work position, the escape or rescue route, and derigging. Include the exclusion zone and the person controlling it.
Answering with absolute or overconfident statements about standards, such as quoting a specific rope diameter, anchor strength or rescue time as a universal legal requirement, when the correct answer is that it depends on the assessment and the manufacturer's instructions.
Candidates memorise numbers from training courses and then present them as fixed rules, which the examiner treats as a failure of judgement.
What to do instead
Frame answers around principles and sources: manufacturer's instructions, the site risk assessment, the IRATA work guidelines, and the client's permit. Where a figure is quoted, say what it depends on and who confirms it.
Describing lessons learned as 'the team was reminded to be more careful' rather than identifying the root cause, the change to the system of work, and how the change is communicated and verified.
Candidates treat the lessons-learned question as a soft closing item and do not connect it to the reporting and review process.
What to do instead
Use a root-cause structure: what happened, why the existing controls did not prevent it, what control or procedure changes, who owns the change, how it is communicated to other teams, and how its effectiveness is checked at the next review.