If you are asking when do businesses need method statements, the practical answer is usually this: when work needs to be carried out in a defined, controlled and clearly communicated way. That often means higher-risk tasks, contractor work, site-based jobs, or any activity where people need more than a general instruction to work safely.
For many small and medium-sized businesses, method statements become relevant the moment work moves beyond routine low-risk office activity. If your team installs equipment, carries out maintenance, works on construction sites, uses hazardous substances, works at height, or completes tasks on a client’s premises, a method statement can quickly go from useful to expected.
When do businesses need method statements in practice?
A method statement is a document that sets out how a task will be completed safely and in the right order. It explains the sequence of work, the equipment being used, the hazards involved and the control measures that need to be followed.
In practice, businesses tend to need method statements in three common situations. The first is where the work itself carries a level of risk that cannot be managed by informal instructions alone. The second is where a client, principal contractor or site manager asks for one before allowing work to start. The third is where the business needs a clear written system so staff and subcontractors carry out the same task consistently.
That means the question is not only whether method statements are legally named for every job, but whether your business can show that work has been planned properly. In many sectors, especially construction, facilities management, maintenance, engineering and specialist trades, that written planning is part of day-to-day compliance.
The jobs that usually call for a method statement
Method statements are most often used where there is a realistic chance of harm if the job is done incorrectly or out of sequence. Construction and trade businesses see this regularly, but the same principle applies across many industries.
A method statement is commonly expected for work at height, hot works, demolition, lifting operations, electrical work, confined spaces, excavation, roofing, asbestos-related controls, machinery maintenance and tasks involving chemicals or dust. It can also be needed for lower-risk work if the location creates added complexity, such as occupied buildings, schools, healthcare settings, retail units or live operational sites.
There is also a commercial reality here. Even if a job is fairly straightforward, a contractor may still be asked to provide a method statement as part of pre-start paperwork. This is especially common when working for larger organisations that operate permit systems, approved supplier processes or formal contractor control procedures.
Method statements and risk assessments are not the same thing
One of the most common points of confusion is the difference between a risk assessment and a method statement. They work together, but they do different jobs.
A risk assessment identifies hazards, considers who might be harmed and sets out the control measures needed. A method statement then takes that information and turns it into a workable process. It explains how the task will actually be done, in what order, using which equipment and under what controls.
This is why businesses are often asked for RAMS rather than a standalone document. RAMS means risk assessments and method statements provided as a package. The risk assessment explains the hazards and controls. The method statement shows how those controls will be applied during the job.
For simple tasks, a separate method statement may not be necessary. For more involved work, relying on a risk assessment alone can leave gaps. Staff may know what the hazards are, but still not have a clear, documented method for carrying out the work safely.
When method statements are expected by clients or contractors
Sometimes the answer to when do businesses need method statements is very simple: when the contract or site rules say they do.
Many clients now expect method statements before contractors arrive on site. This is common in construction, commercial maintenance, refurbishment, cleaning in sensitive environments, fire safety work, electrical installation and mechanical servicing. A principal contractor may require RAMS for all trades, regardless of size, because they need visibility over how each activity will be managed.
This does not mean every document has to be lengthy or over-engineered. In fact, overly generic paperwork can cause its own problems. A short, relevant method statement that matches the actual task is usually more useful than a large document filled with copied text. Site managers and clients want to see that the business understands the work, the hazards and the controls, not that it can produce paperwork for its own sake.
When smaller businesses should not leave it to chance
Small businesses sometimes assume method statements are only for major contractors or large construction projects. That is not really the case.
If your business sends staff to carry out non-routine tasks, uses subcontractors, works in shared spaces, or takes on jobs where the sequence of work matters, method statements can protect both safety and credibility. They give your team a reference point, help with inductions and briefings, and reduce the risk of different people doing the same task in different ways.
They are also valuable when you need to show due diligence after an incident, near miss or client query. A method statement will not solve poor site management on its own, but it does help demonstrate that the work was planned, communicated and controlled.
For smaller firms without an in-house safety adviser, this is often where delays start. The work needs to begin, the client wants RAMS, and someone has to assemble documents at short notice. Having a professional, fully editable template can save a lot of time, provided it is tailored properly to the job.
Signs your business probably needs a method statement
A useful rule of thumb is to ask whether verbal instructions would be enough if something went wrong. If the answer is no, a written method statement is likely to be worth having.
That is especially true where there are several stages to the work, more than one contractor involved, specialist plant or tools in use, or restrictions on access, timing or supervision. The more moving parts a job has, the stronger the case for documenting the method.
You should also think about who needs the information. If staff are new, temporary, visiting, or not familiar with the site, a method statement helps standardise expectations. If the work affects members of the public, other contractors or the client’s own staff, written controls become even more important.
What a good method statement should actually do
A method statement should make the work easier to understand and safer to manage. It should not read like a legal textbook.
A good document normally explains the scope of works, who is responsible, what plant and materials are needed, any training or competence requirements, the sequence of tasks, the main hazards and controls, emergency arrangements and any site-specific rules. It should be clear enough that a supervisor can brief the team from it and specific enough that the client can see it reflects the real job.
This is where generic documents fall down. If a method statement says the same thing for every project, it may look tidy but it will not offer much value. The right approach is usually to start from a solid template and then edit it to suit the actual work, location and risks.
It depends on the work, but planning is the real test
There is no single trigger that covers every business and every task. Some jobs absolutely need a method statement because of the risks involved. Others need one because the client requires it. And some fall into a middle ground where it is not strictly demanded, but still makes operational and commercial sense.
That middle ground matters. Businesses often focus on whether a document is compulsory, when the better question is whether it helps them manage the work properly. If a written method would prevent confusion, support supervision, satisfy a client or improve consistency, it is usually worth having.
For UK businesses trying to keep compliance practical, that is the real value. Method statements are not about producing paperwork for a shelf. They are about setting out how work will be done safely, clearly and with confidence.
If you are unsure whether a particular job needs one, the safest approach is to look at the risk, the complexity, the site rules and who needs to understand the process. When those factors start to build, a method statement is usually the right call.
