On a construction project a method statement is not a formality, it is how the principal contractor works out whether your sequence of work is compatible with everybody else's. They have duties to plan, manage and monitor the construction phase and to coordinate the contractors doing the work, and your statement is one of the inputs. That is the frame to write in: not a document proving you take safety seriously, but a description your reader can plan around.
Where it sits in the project's documents
The principal contractor draws up and maintains the construction phase plan for the project. Your method statement describes your work within that. The two are not interchangeable, and submitting the wrong one is a recognisable sign of a contractor who is unclear about their role. If you are the only contractor on a small project the roles may collapse into one organisation, but the documents still do different jobs and both are still needed.
What a site rejects a statement for
Generic content with no site detail. A sequence whose stages do not chain, so the preconditions are impossible in the order written. Plant or access that the site cannot actually provide. Competence claimed but not evidenced. Emergency arrangements copied from another project, naming a muster point that does not exist here. And, very often, a statement for work that has already changed since the tender, submitted unrevised.
Interfaces are the part that only you can write
Your work touches other people's: deliveries through a shared gate, a scaffold somebody else erected, an isolation that affects an occupied floor, a lift shared with two other trades. Those interfaces are where site incidents cluster and they are exactly what the principal contractor is reading for. A statement that describes your work as if the site were empty has skipped the section that mattered.
Revision is normal; version confusion is not
Expect to revise. Sites change, sequences slip, and a statement accepted in week one may be wrong in week four. The discipline that matters is being able to say which version was live on a given day and who was briefed on it. Held as records against the job rather than as email attachments, that question has an answer, and the free risk assessment form worksheet prices the assessment revisions that travel with it.
Questions people ask about construction method statement
What is a method statement in construction?
A written description of how a contractor will carry out a specific package of work on a specific site, in sequence, with the people, plant and precautions for each stage, supplied to the principal contractor or client before the work starts.
Is a construction method statement a legal requirement?
The document by that name is not named in the regulations, but the duties it evidences are real: contractors must plan, manage and monitor their work so it is carried out without risks to health and safety, and principal contractors must coordinate the work of contractors. In practice the method statement is how those duties are demonstrated and it is routinely a contractual condition.
Who reads it once it is submitted?
Usually the principal contractor's site or safety team, reading it against the programme and the other trades on site that week. They are checking compatibility as much as content, which is why site-specific detail moves a pack through review faster than length does.