RAMS Rejected for a Missing Sequence of Works: How to Fix It
Having your RAMS sent back because the sequence of works is missing or inadequate is one of the most common rejection reasons on construction and facilities sites. It is also one of the most avoidable. This guide explains what reviewers are actually looking for, why it matters legally, and how to write a sequence that gets your RAMS approved first time.
What is a sequence of works?
A RAMS document has two parts. The risk assessment identifies the hazards and the people at risk. The method statement describes how the work will be carried out safely, step by step.
The sequence of works is the backbone of the method statement. It is an ordered, logical account of every significant activity from mobilisation to completion, written so that someone unfamiliar with the job could follow it and understand what is happening at each stage. Without it, the method statement is not a method statement. It is a list of generic controls floating in a document with no context.
Why reviewers reject RAMS without one
Principal contractors have a duty under CDM 2015 to plan, manage and monitor construction work so that it is carried out without risks to health and safety. Before they permit a contractor to start work, they need to be satisfied the work is properly planned. A RAMS without a clear sequence gives them no basis for that confidence.
From a broader legal perspective, the Management of Health and Safety at Work Regulations 1999 (regulation 3) require a suitable and sufficient risk assessment. "Suitable and sufficient" means the controls documented must actually relate to the specific task as it will be performed. If the method statement does not describe the task in order, it is impossible to verify that the controls are linked to the right stages of the work.
Reviewers also look for sequence because it reveals interface risks: moments where your activity affects, or is affected by, other trades or members of the public. If your sequence is missing, those interfaces are invisible on paper.
Common reasons a sequence fails review
- The method statement is a block of generic text with no step-by-step structure.
- Steps are listed but have no logical order (e.g. PPE listed before site setup, or isolation listed after energised work begins).
- Key stages are skipped entirely, such as erecting edge protection before starting work at height, or isolating services before breaking into them.
- The sequence describes the finished outcome rather than the activities to achieve it.
- The document was copied from a previous job and the sequence refers to different equipment, access or site conditions.
How to write a sequence of works that passes review
Start from arrival, not from the main task. A reviewer wants to see that you have thought about site setup: where vehicles park, how materials are delivered, how the work area is demarcated before anything technical begins.
Work through the job in the order it will actually happen. Think of it as a walkthrough. If you are installing a suspended ceiling, your sequence might read:
- Delivery and offload of materials to agreed compound area.
- Erect barriers and signage to exclusion zone beneath work area.
- Erect MEWP or working platform; check pre-use inspection completed.
- Install perimeter angles and primary grid in agreed bays.
- Cut and fix secondary grid members; use appropriate blade guards on cutting equipment.
- Lift and place ceiling tiles from platform, working inward from perimeter.
- Final inspection and snagging.
- Strike platform, remove barriers, clear debris to skip.
That is a simplified example, but it illustrates the principle: each step is a discrete activity with a clear order and a point at which a control (the barrier, the inspection, the blade guard) fits naturally.
Flag hold points and check points. If a stage requires sign-off before proceeding (an isolation certificate, a permit to work, a structural inspection), write it in explicitly at the correct point in the sequence. This is what principal contractors mean when they ask for "control measures linked to the task."
Keep each step short and specific. One activity per step where possible. Avoid combining "erect scaffold and begin demolition" into a single line. They are different activities with different hazards.
Review the sequence against your risk assessment. Every significant hazard identified in the risk assessment should be addressed by a control at the relevant step in the sequence. If you have identified a manual handling risk, that control should appear at the step where the manual handling actually occurs, not in a generic list at the end.
A note on proportionality
The HSE does not prescribe a fixed format for method statements. The depth of your sequence should match the complexity and risk of the job. A two-hour reactive repair may need five or six steps. A multi-week mechanical installation may need twenty. What matters is that the sequence is specific to your job, your site and your methods, not that it hits a word count.
Pasting in a generic sequence from a template and changing the client name is the single biggest reason a sequence of works fails review. Reviewers on busy sites read dozens of RAMS a week. Generic text is immediately obvious.
Before you resubmit
Check the following before sending your RAMS back to the principal contractor:
- Does the sequence start from mobilisation and end at demobilisation?
- Is every step in the order it will actually happen?
- Are permits, certificates and inspections inserted at the correct points?
- Does each hazard in the risk assessment have a matching control at the right step?
- Is the sequence specific to this site, this task and this team?
Getting the sequence right is not a paperwork exercise. It is the clearest evidence you can give that you have thought the job through before you start it.