Definition
Method Statement
A written explanation of how you will deliver the requirement.
A method statement is a written response describing, in practical detail, how a supplier will carry out a specific part of the contract — a process, a mobilisation activity, a health and safety approach, or a service delivery method. Evaluators mark it against stated criteria, so structure and specificity matter more than general reassurance.
What evaluators are actually looking for
A method statement is not a description of general capability; it is a step-by-step account of what will actually happen, who does it, in what sequence, and how risks are managed. Evaluators mark against the wording of the question and any published criteria, so an answer that reads well but doesn't map onto those specifics tends to score in the middle band even if the underlying approach is sound.
Method statements that score highly usually name responsibilities (which role does what), state timescales or sequencing, reference relevant standards or contractual requirements, and show awareness of risks specific to that buyer's context rather than generic risks that could apply anywhere.
A workable structure
There is no single mandated format, but a structure like this consistently helps markers find what they need quickly.
- Brief statement of understanding of the requirement, tailored to the buyer's specifics
- Step-by-step description of the method, in the order it will actually happen
- Roles and responsibilities for each step
- Risks specific to this contract and how they are mitigated
- How performance will be monitored or assured
- A short closing statement linking back to the outcome the buyer wants
Common weaknesses
The most frequent problem is genericism — a method statement copied from a previous bid with only the client name changed, which evaluators who read many submissions spot quickly. The second is failing to address every element of a compound question, leaving gaps that get marked down even if the rest of the answer is strong.
Frequently asked questions
- How long should a method statement be?
- Whatever the word or page limit set by the buyer allows, used fully but without padding. If no limit is given, aim for enough detail to demonstrate a credible, specific method without repeating the same point in different words.
- Should a method statement include diagrams or process maps?
- Where the format allows and it genuinely clarifies sequencing or responsibilities, yes — a clear process diagram can make a complex method easier to mark. Check whether diagrams count towards word or page limits and whether the portal accepts embedded images.
- Can the same method statement be reused across different tenders?
- A base version can be reused as a starting point, but it must be tailored to the specific buyer's context, terminology, and stated risks each time. Untailored reuse is the single most common reason otherwise capable suppliers score poorly.
Related terms