10 Tips For Writing A Method Statement

A method statement is a document that describes how to do a task safely. It plans out how an activity can be done without harm and is especially useful for complex or risky activities that need completing a certain way. You'll find method statements used in construction and other high-risk industries.

Since method statements are usually only required in high-risk activities, they must be thorough. You need to know that the hazards have been removed or controlled before you begin. But you also need to make sure that the method statement is clear and understood. After all, what use is a good plan if no one follows it?

Finding the right balance can make method statements difficult to write. Include too little information and the activity becomes unsafe as shortcuts or failure to control risks happen during the work. Include too much information and the important parts could be missed or ignored.

So where should you start? What should you include? What should you leave out?

Here are 10 tips for writing a method statement:

1. Research the activity

The first step in creating a method statement is a little bit of research on:

• The activity
• The environment
• The people

Your method statement will need to include all the information necessary to complete the task and keep people safe. Step-by-step. You can't write a method statement until you know what steps are needed.

You may have done this task hundreds of times, but each project is different. Even if you know the task back-to-front, check if any site-specific hazards need addressing.

Take a look at the activity, the environment and the people who will be doing the work. And once you have these details, you can move on to the next step.

2. Assess the risks

A method statement is not a risk assessment. A risk assessment is an entirely different document. But you will need one to accompany your method statement.

Unlike method statements, risk assessments are a legal requirement, and you need one for all of your business activities (not just the high-risk ones). When you need a method statement, it's a good idea to do a risk assessment first. The 5 steps to risk assessment will help you identify hazards and controls, and this will help you plan the activity (and write your method statement).

A risk assessment is an assessment of risk - it tells you what hazards are present and what controls are needed. But if it's not self-explanatory how to use those controls, or in what order, or if the work requires a safe sequence of events, then a method statement will provide that additional detail.

These two documents support each other, so make sure any controls you have identified in your risk assessment are also covered in your method statement.

3. Plan the activity

Think of a method statement as a safe system of work. Or a set of instructions to get you safely from start to finish. A method statement is simply a plan of how you are going to carry out the work safely and what methods you will follow.

Write down all the key steps that will need to be taken to complete the job. This will be your framework to plan out the activity and identify what key tasks need to be covered.

Start with a simple set of bullet points or a numbered list. Imagine the activity happening and write down the actions needed - even if something seems obvious to you, like wearing safety boots, it might not be to someone else.

4. Plan before the activity

It might be a cliché, but failing to prepare is preparing to fail. If your method statement only starts when the task starts, someone might arrive with the wrong equipment, or carry out the activity in unsafe conditions.

What needs to be done in preparation for the task?

Don't just focus on the task at hand. Think about what safety precautions are needed before you begin. What needs to be done before the task starts?

• Barriers
• Signage
• Temporary access

Do you need to warn others? Do you need safe access? Is the work going to make the area unsafe? Do you need an exclusion zone?

Detail these safety measures in the method statement so that work doesn't start until all of the requirements are in place. If these precautions are critical, consider adding a permit to work for extra control.

5. Plan after the activity

Your task probably doesn't end as soon as the work is complete. If your method statement ends when the task finishes, the workplace might be left unsafe.

What needs to be done on completion of the task?

Think about what safety precautions are needed after you finish. What needs to be done to leave the area safe?

• Packing away tools and equipment
• Removing restrictions and lock-offs
• Testing
• Clearing up waste and rubbish
• Signing off
• Cancelling permits

There are often several requirements to make the work area safe again once the task is done. You might need to allow access to the area again, remove barriers and signage or cancel diversions. You may need to let people know that precautions that were in place are no longer there. Or that temporary rules don't apply anymore.

Some of these steps might seem obvious, but things like this can get forgotten, especially if the set-up was some time ago or work finishes near the end of a shift.

Never assume or rely on people to remember what they need to do to return an area to use - include these steps in your method statement.

6. Give contact details

Method statements are for higher-risk activities. This type of work is often more tightly controlled, with a number of people having responsibilities for performing different roles in the task.

In addition to those carrying out the work, there might be a project manager involved. Or a supervisor. And someone else might be in charge of issuing a permit or installing access equipment.

Your method statement should provide information on the people involved in the task, with contact details for those with responsibilities.

Everyone involved in a task has an important part to play.

7. Use a template

Method statements need to be understood by various people. The client might want to review it. Supervisors need to check it. And, most importantly, the people doing the work need to follow it.

A method statement template will help you with consistency, with each method statement you create following a standard format. This will make it easier to create your method statement, and you'll be able to add your site-specific information without starting from blank each time. Using a similar template for each task will make it easier for those who need to read and understand the method statement and know the standard format you follow.

A template will also save you time, and help you write a method statement in minutes instead of hours.

Need a method statement template? You can start with the free blank method statement template or develop your own!

8. Be logical

It's no good just listing a bunch of controls in random order. You can't expect workers to work out what sequence to follow if you haven't provided clear directions. Imagine if your sat nav gave you a route in the wrong order, would you be able to work out where you needed to go?

Your method statement needs to be a set of useful instructions, and your team should be able to work through it in a logical sequence. From A to B and so on.

Earlier, we started planning the activity with a simple set of bullet points or a numbered list. We then considered the steps needed before, and after the task.

Now it's time to put those steps in a logical order. You don't have to number them, but it should be easy to follow along to complete the task.

9. Keep it simple

Your method statement needs to contain all the essential information to keep your workers (and others) safe. And that's it. Don't bloat it with unnecessary content.

Workers are not going to thank you for writing them a novel. If much of the information is things they already know, inaccurate or unhelpful, they are more likely to scan the document. And they might miss the important information hidden amongst the waffle.

As well as a good layout, consider what information needs to be included in your method statement. Keep it clear, concise and easy to understand.

10. Get acknowledgement

And the award for the best method statement goes to...

No, not that sort of acknowledgement!

But for your method statement to be effective, it needs to be used. How do you use a method statement? You share it with the people involved with the task - they read it and - most importantly - follow it.

There could be several people in your team working on the project or task. Have they all read and understood the method statement? Keep a record of who has, and get their signatures before work starts.

---

Get more help with how to write a method statement in 5 minutes, and use one of our method statement templates for your task.