{"id":100,"date":"2026-07-01T09:00:00","date_gmt":"2026-07-01T09:00:00","guid":{"rendered":"http:\/\/oro-insights-1"},"modified":"2026-07-01T09:00:00","modified_gmt":"2026-07-01T09:00:00","slug":"what-is-a-method-statement","status":"publish","type":"post","link":"https:\/\/oroevents.ae\/insights\/2026\/07\/01\/what-is-a-method-statement\/","title":{"rendered":"What Is a Method Statement? (And Why Inspectors Read Yours First)"},"content":{"rendered":"

Ask an event inspector which document they open first and it usually isn’t the glossy Event Safety Plan — it’s the method statement<\/strong> 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.<\/p>\n

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.<\/p>\n

The definition, without the fog<\/h2>\n

A method statement<\/strong> (sometimes “safe system of work” or SSOW) is a step-by-step description of how a specific task will be carried out safely<\/em>: 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.<\/p>\n

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.”<\/p><\/blockquote>\n

Method statement vs risk assessment (RAMS)<\/h2>\n

The two documents travel together — the industry shorthand is RAMS<\/strong> (Risk Assessment & Method Statement) — but they do different jobs:<\/p>\n\n\n\n\n\n\n
<\/th>\nRisk assessment<\/th>\nMethod statement<\/th>\n<\/tr>\n
Question<\/strong><\/td>\nWhat are the hazards, who’s exposed, how severe × how likely?<\/td>\nWhat is the safe sequence of work, step by step?<\/td>\n<\/tr>\n
Form<\/strong><\/td>\nScored matrix (typically 5×5), controls, residual risk<\/td>\nNumbered operational steps, roles, plant, controls per step<\/td>\n<\/tr>\n
Written by<\/strong><\/td>\nA competent person assessing the task<\/td>\nA competent person who understands how the task is actually performed<\/td>\n<\/tr>\n
Read by<\/strong><\/td>\nManagers, venues, authorities<\/td>\nThe crew doing the work — plus everyone above<\/td>\n<\/tr>\n<\/table>\n

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<\/em>, cross-referenced. A risk assessment without a method statement is a diagnosis without a treatment plan.<\/p>\n

The ten parts of a method statement that passes<\/h2>\n
    \n
  1. Scope & task description<\/strong> — precisely which task, at which site, on which dates. Vague scope is the first template giveaway.<\/li>\n
  2. Responsibilities<\/strong> — named roles: supervisor, competent persons, rescue lead. “The contractor” is not a name.<\/li>\n
  3. Sequence of operations<\/strong> — numbered steps in the order the crew will actually work, from arrival to sign-off. This is the heart of the document.<\/li>\n
  4. Plant & equipment<\/strong> — what will be used, with inspection\/certification status (LOLER-style records for lifting kit, motor certs, harness inspection dates).<\/li>\n
  5. Materials & substances<\/strong> — anything hazardous, with handling controls.<\/li>\n
  6. Access & egress<\/strong> — how the work area is reached, segregated and controlled; exclusion zones drawn, not implied.<\/li>\n
  7. PPE matrix<\/strong> — per step where it changes, not a generic list of everything ever invented.<\/li>\n
  8. Emergency & rescue arrangements<\/strong> — 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.<\/li>\n
  9. Monitoring & supervision<\/strong> — hold points, permit-to-work interfaces, who checks what before the next step proceeds.<\/li>\n
  10. Sign-off & briefing record<\/strong> — evidence the crew were briefed on this<\/em> document, dated and signed. Inspectors ask for it.<\/li>\n<\/ol>\n

    The five template sins inspectors spot in seconds<\/h2>\n