Risk assessments and method statements in a safety file
The useful question is not whether a document exists, but whether it describes the actual work, hazards, controls, people, and review process for the site. Use the assessment and method statement as work instructions connected to evidence.
Describe the work as it will happen
Record the task sequence, location, equipment, materials, people, interfaces, access, duration, and conditions that can change the risk. A copied document may use the right headings while describing a different job.
Use the client or principal-contractor requirements as the project boundary, then confirm the document matches the actual work package and the people who will perform it.
Identify who can be exposed
Consider workers, subcontractors, visitors, the public, neighbours, other trades, vulnerable people, and anyone affected by vehicles, tools, materials, dust, noise, electricity, height, or changing access.
Record assumptions that affect exposure, such as working hours, exclusion zones, weather, traffic, shared equipment, and emergency access. An unnamed affected person is easy to forget during implementation.
Connect hazards to controls
For each significant hazard, identify who may be exposed, the control or hierarchy being used, the responsible person, and how implementation will be checked. Explain what the crew must do before, during, and after the task.
Controls should be practical for the workface and visible in the induction, briefing, inspection, permit, and supervision records. A control that cannot be observed or maintained is difficult to defend.
Write a usable method statement
Describe the sequence, tools, materials, access, set-up, isolation, lifting or handling, work steps, inspection points, emergency response, and close-out. Use language the crew can understand and include drawings or photographs when they remove ambiguity.
Separate instructions from background explanation. The person doing the work should be able to identify the current method, the stop point, and who to ask when conditions differ.
Review when assumptions change
New equipment, weather, access, subcontractors, materials, incidents, or a changed sequence may require the assessment or method statement to be reviewed. A client request can change the scope even when the work title stays the same.
Record the version, date, reviewer, approval, change reason, and how the updated control was communicated. Remove superseded copies from active use while retaining them in the project record.
Keep evidence of briefing and supervision
Record who received the instruction, when, which version was used, what questions were raised, and what follow-up was assigned. Keep inspection, permit, toolbox, corrective-action, and incident records linked to the same work package.
A signature proves that a form was signed, not that every person understood or followed the control. Note language, accessibility, competency, and supervision needs where they affect safe implementation.
Do not use the document as a guarantee
A template or digital product can help with structure and document control, but it cannot replace competent project review, current site information, client requirements, or the decisions of the responsible person.
SafetyFile SA provides preparation guidance and keeps product links separate from any claim about legal or client acceptance.
Close the work package
At completion, record whether the task was completed as described, which changes occurred, what defects or corrective actions remain, and where the final evidence is stored.
The final record should let another responsible person understand the work, the controls, the changes, and the evidence without reconstructing the project from disconnected documents.