What Is a Method Statement in Construction

At Towerstone Accountants we provide specialist CIS accountancy services for contractors and construction businesses across the UK. We created this webpage for subcontractors and contractors who want clear guidance on the Construction Industry Scheme, including registration, deductions, refunds, and ongoing reporting obligations. Our aim is to help you stay compliant with HMRC, avoid costly errors, and understand how CIS affects your tax position.

If you work in construction whether as a contractor subcontractor site manager or business owner the term method statement will come up again and again, sometimes as part of a tender pack, sometimes before work is allowed to start on site, sometimes after an incident when everyone suddenly realises paperwork matters, and yet despite how common it is many people are unclear about what a method statement actually is, why it exists, who is responsible for it, and how detailed it really needs to be.

From my own experience working closely with construction clients method statements are often seen as a box ticking exercise, something done quickly to satisfy a principal contractor or client, but when they are approached in that way they tend to miss the point, a good method statement is not about bureaucracy, it is about planning work properly, reducing risk, protecting people on site, and showing that you understand how a job will be carried out safely and competently.

In this article I am going to explain in clear practical terms what a method statement is in construction, how it fits into UK health and safety law, how it differs from a risk assessment, who needs one and when, what it should include, how detailed it needs to be, and the common mistakes I see that cause method statements to be rejected or ignored, the aim is to give you a solid working understanding rather than just a definition.

The purpose of a method statement in construction

At its core a method statement is a written description of how a specific job or task will be carried out safely, it sets out the sequence of work, the hazards involved, and the control measures that will be used to manage those risks, in other words it explains the method of work in a way that anyone involved can understand.

In the UK construction industry method statements sit alongside risk assessments as part of what is often referred to as RAMS, risk assessments and method statements, although they are closely linked they serve slightly different purposes which is where confusion often starts.

The reason method statements exist is simple, construction work is inherently risky, sites change constantly, tasks involve multiple trades, plant equipment and materials, and without clear planning the risk of injury damage or disruption increases significantly, a method statement forces that planning to happen before work starts rather than reacting once something has gone wrong.

How method statements fit into UK health and safety law

There is no single piece of legislation that says “you must have a method statement for every job” and this sometimes leads people to believe they are optional, in reality method statements arise from broader legal duties placed on employers contractors and the self employed under UK health and safety law.

The Health and Safety at Work etc Act places a duty on employers and those in control of work to ensure so far as is reasonably practicable the health safety and welfare of workers and others who may be affected by the work, supporting regulations then require risks to be assessed and controlled.

In many construction scenarios a simple generic risk assessment is not enough, the work is complex or high risk and a written method statement is the most practical way to demonstrate that risks have been identified and controlled in a structured way, this is why method statements are routinely requested by principal contractors clients and site managers even where the law does not explicitly name them.

The difference between a method statement and a risk assessment

One of the most common misunderstandings I encounter is people using the terms method statement and risk assessment interchangeably, they are linked but they are not the same thing.

A risk assessment focuses on identifying hazards and assessing the level of risk, it answers the question what could cause harm and how serious that harm could be.

A method statement focuses on how the work will actually be done, it answers the question how will we carry out this task safely given those risks.

In practical terms the risk assessment identifies the issues and the method statement explains the solution, which is why method statements often reference or sit alongside a risk assessment rather than replacing it.

When a method statement is required

Method statements are most commonly required where work is considered higher risk or more complex, this includes but is not limited to working at height, demolition, excavation, lifting operations, work involving hazardous substances, working in confined spaces, or work carried out in occupied buildings.

They are also commonly required by clients or principal contractors as part of contractual arrangements, even for relatively straightforward tasks, from their perspective the method statement provides reassurance that the contractor understands the job and has planned it properly.

In my experience method statements are also frequently requested when something has gone wrong previously, either on that site or with that contractor, as a way of tightening controls and clarifying expectations before work resumes.

Who is responsible for writing the method statement

Responsibility for the method statement usually sits with the contractor carrying out the work, this could be a main contractor or a subcontractor depending on the structure of the project, the key point is that the organisation controlling how the work is done should be the one setting out the method.

It is not uncommon for principal contractors to provide templates or minimum requirements but the content should be specific to the task and the contractor’s own working practices, copying and pasting generic statements is one of the quickest ways to have a method statement rejected or ignored.

For smaller businesses and sole traders this responsibility can feel daunting but the principles are the same, you are simply explaining how you intend to do the job safely using the equipment and people available to you.

What a method statement typically includes

While there is no single mandated format most method statements in construction include similar core sections, the aim is clarity rather than complexity.

They usually start with basic project information such as the site address the nature of the work and who is responsible for supervising it, this sets the context and makes it clear what the statement applies to.

They then move on to a description of the work, often broken down into logical steps, explaining the sequence in which tasks will be carried out, this is the heart of the method statement and where the focus should be.

Hazards and risks are identified in relation to those steps, and crucially the control measures are explained, this might include the use of specific equipment safe systems of work barriers signage or permits.

Information about plant tools and equipment is often included along with details of who is authorised to use them, this helps demonstrate competence and control.

Method statements will also usually cover personal protective equipment site access arrangements emergency procedures and welfare facilities, all of which contribute to a safe working environment.

The level of detail required in a method statement

One of the hardest things to judge is how detailed a method statement needs to be, too vague and it is useless, too detailed and it becomes unreadable and impractical.

In my experience the right level of detail is enough that someone unfamiliar with the job could read it and understand how the work will be carried out safely, without needing to fill in major gaps themselves.

This means avoiding generic phrases like “work will be carried out safely” and instead explaining what that actually looks like on site, for example how access will be gained, how materials will be moved, how falls will be prevented, and how interaction with other trades will be managed.

It also means tailoring the statement to the specific site and task, a method statement for installing windows in a new build is very different from one for replacing windows in an occupied building even if the end result looks similar.

Method statements and competence

A method statement is not just about the task, it is also about the people doing it, competence is a key part of health and safety law and method statements are often used to demonstrate that the right people with the right skills are involved.

This is why method statements often reference training qualifications or experience, particularly for higher risk activities, it reassures the client or principal contractor that those carrying out the work understand both the task and the risks involved.

From a practical point of view this also protects the contractor, if something goes wrong being able to show that competent people were assigned to the work and that a clear method was in place can be critical.

Communication and briefing on method statements

A method statement is only effective if it is communicated properly, simply writing it and filing it away does very little to improve safety.

On most sites the method statement will be briefed to workers before the task starts, often as part of a site induction or toolbox talk, this gives workers the opportunity to ask questions and raise concerns before work begins.

In my experience this step is often rushed or skipped especially on smaller jobs, but it is one of the most important parts of the process, a well written method statement combined with a proper briefing significantly reduces misunderstandings and unsafe behaviour.

Reviewing and updating method statements

Construction sites are dynamic environments and method statements should reflect that, if conditions change if the scope of work changes or if an unexpected hazard arises the method statement may need to be reviewed and updated.

Treating a method statement as a fixed document can be dangerous, it should be seen as a living plan that can adapt as circumstances change, this is particularly important on longer projects where site conditions evolve over time.

From a compliance perspective being able to show that method statements are reviewed and updated where necessary demonstrates a proactive approach to safety rather than a tick box mentality.

Common mistakes I see with method statements

There are several recurring issues that undermine the effectiveness of method statements.

One is over reliance on generic templates that are not tailored to the job, these often look impressive but fail to address the real risks on site.

Another is excessive length and complexity, method statements that run to dozens of pages are rarely read properly and important points get lost.

Lack of worker involvement is also common, method statements written in isolation without input from those doing the work often miss practical realities.

Finally poor communication means that even a good method statement has little impact if workers are not aware of it or do not understand it.

Method statements and liability

Method statements can play an important role if something goes wrong, they are often reviewed during investigations following accidents or near misses, both by clients and by regulators.

A clear realistic method statement that was properly communicated and followed can help demonstrate that reasonable steps were taken to manage risk, whereas a generic or unrealistic statement can have the opposite effect.

This is another reason why copying and pasting without thought is risky, the document you submit may later be scrutinised in far more detail than you expect.

Method statements for small contractors and sole traders

Smaller businesses and sole traders sometimes assume method statements are only for large projects or big companies, in reality the same principles apply regardless of size.

The difference is usually scale rather than substance, a method statement for a small job may be shorter but it should still explain how the work will be carried out safely and how risks will be controlled.

In my experience taking the time to produce clear sensible method statements actually makes work easier for small contractors, it helps clarify what needs to be done and reassures clients that the job is being taken seriously.

Final thoughts from experience

A method statement in construction is far more than a piece of paperwork, at its best it is a practical planning tool that improves safety efficiency and communication on site.

Understanding what a method statement is, why it exists, and how to use it properly can make a real difference, not just in meeting legal and contractual requirements but in protecting people and projects.

When method statements are clear realistic and properly communicated they support good working practices, when they are treated as an afterthought they quickly lose their value, and that difference is usually reflected in how smoothly a job runs.

You may also find our guidance on what is procurement in construction and how to get into the construction industry helpful when dealing with related CIS questions. For a broader overview of CIS rules, compliance, and support, you can visit our CIS guidance hub.