Ask an event inspector which document they open first and it usually isn’t the glossy Event Safety Plan — it’s the method statement for the riskiest task on site. Because a safety plan tells them what you intend in general; a method statement tells them whether the crew flying your LED wall at 02:00 actually knows what they’re doing.
This is the working definition we use across hundreds of documents a year, what separates a method statement from a risk assessment, and what a good one contains — written for event organisers in the UAE and Saudi Arabia, where documentation standards have risen faster than most suppliers have noticed.
The definition, without the fog
A method statement (sometimes “safe system of work” or SSOW) is a step-by-step description of how a specific task will be carried out safely: the sequence of operations, who does what, with which equipment, under which controls. It is task-specific and site-specific — a method statement for rigging a kabuki reveal at one Dubai ballroom is not the method statement for the same reveal in a Riyadh exhibition hall.
If a risk assessment answers “what could go wrong and how badly?”, the method statement answers “so here is exactly how we’ll do it without that happening.”
Method statement vs risk assessment (RAMS)
The two documents travel together — the industry shorthand is RAMS (Risk Assessment & Method Statement) — but they do different jobs:
| Risk assessment | Method statement | |
|---|---|---|
| Question | What are the hazards, who’s exposed, how severe × how likely? | What is the safe sequence of work, step by step? |
| Form | Scored matrix (typically 5×5), controls, residual risk | Numbered operational steps, roles, plant, controls per step |
| Written by | A competent person assessing the task | A competent person who understands how the task is actually performed |
| Read by | Managers, venues, authorities | The crew doing the work — plus everyone above |
For any high-risk event task — rigging, working at height, hot works, temporary structures, electrical energisation — venues and authorities in this region increasingly expect both, cross-referenced. A risk assessment without a method statement is a diagnosis without a treatment plan.
The ten parts of a method statement that passes
- Scope & task description — precisely which task, at which site, on which dates. Vague scope is the first template giveaway.
- Responsibilities — named roles: supervisor, competent persons, rescue lead. “The contractor” is not a name.
- Sequence of operations — numbered steps in the order the crew will actually work, from arrival to sign-off. This is the heart of the document.
- Plant & equipment — what will be used, with inspection/certification status (LOLER-style records for lifting kit, motor certs, harness inspection dates).
- Materials & substances — anything hazardous, with handling controls.
- Access & egress — how the work area is reached, segregated and controlled; exclusion zones drawn, not implied.
- PPE matrix — per step where it changes, not a generic list of everything ever invented.
- Emergency & rescue arrangements — the section weak documents skip. For work at height this means a real rescue plan: who, with what kit, in how many minutes — “call 999” is not a rescue plan for a rigger suspended in a harness.
- Monitoring & supervision — hold points, permit-to-work interfaces, who checks what before the next step proceeds.
- Sign-off & briefing record — evidence the crew were briefed on this document, dated and signed. Inspectors ask for it.
The five template sins inspectors spot in seconds
- Another event’s name surviving find-and-replace (yes, still, constantly).
- A sequence of operations that doesn’t match the drawings on the wall.
- Equipment lists with no certification references.
- Rescue arrangements copied from a construction site that had a tower crane.
- A revision box that says Rev 0 on a document clearly older than the company.
The pattern behind all five: the document was produced about the task instead of from it. Our rule is simple — method statements are written from the production drawings and the actual crew plan, which is why our safety files pass on first submission.
UAE & Saudi expectations in practice
In Dubai, method statements for high-risk tasks ride alongside the event permit stack — venue submissions, civil-defense coordination and municipality layers — and inspection culture has matured to the point where a mismatched document can stop a build mid-shift. In Saudi Arabia, the mega-project era imported world-class documentation culture wholesale: GEA-regulated events and giga-project venues expect RAMS as a matter of course, and an Arabic version is frequently the professional courtesy that smooths everything.
Quick answers
Who is allowed to write a method statement? A competent person — someone with the training and experience to understand the task’s hazards and its real-world execution. Certification (NEBOSH, IOSH) supports competence; task experience completes it.
How long should one be? Long enough to be followed, short enough to be read: 4–8 focused pages for a typical event task. Fifty pages of boilerplate protects nobody.
How fast can a proper one be produced? From good site data, 48 hours for a single task; a full event file in 5–7 working days. Details on our event safety plans & RAMS page — and if you need certified officers to enforce it on site, that’s event HSE staffing.
RAMS RULE — THE PAPER MUST MATCH THE ROOM. EVERYTHING ELSE IS COMMENTARY.