Method Statement
A written explanation of how a supplier will deliver a specific contract; a core scored element of most ITT responses.
Definition
A method statement is a written explanation of how a supplier will deliver the contract. Method statements are a core component of most Invitation to Tender responses and are scored against the published evaluation criteria. They typically cover the supplier's proposed approach, team structure, mobilisation plan, key risks, and quality and assurance arrangements. The method statement is where the supplier shows the buyer how the work will actually be done, as opposed to the capability statement which evidences the supplier's general ability to do that kind of work.
How it works in practice
A strong method statement is specific to the requirement. Generic language about the supplier's methodology will score lower than language that engages with the specific specification, the buyer's stated priorities, and the contract's practical constraints (location, volume, mobilisation timeline). Structure matters: most buyers publish a response template with named sub-sections (approach, mobilisation, team, risk, quality, assurance) and word or page limits. Bidders should mirror the template structure exactly; deviating risks confusing evaluators or breaching the response format rules. Each section should follow a problem-approach-evidence shape: state what the buyer needs, describe how the supplier will deliver it, evidence with named case studies or comparable contracts. Avoid bullet-point dumps without narrative; evaluators score against the rubric and need joined-up evidence. Diagrams and tables save words and make complex approaches easier to evaluate; use them where the response template allows. Get a fresh-eyes review of the method statement before submission: the bid team has read it ten times and stops noticing gaps that an outsider will spot in five minutes. The KimonBids method-statement module surfaces relevant reusable content from the Bid Library while leaving the bidder to adapt it to the specific opportunity.
Common questions
How long should a method statement be?
Whatever the ITT specifies. Most ITTs set per-section word or page limits (typically 500 to 2000 words per section for service contracts). Exceeding the limit can cause the excess to be ignored or, in strict ITTs, the whole response to be disqualified. Hitting the limit cleanly and using the full space is usually right; substantially under is a missed scoring opportunity.
What distinguishes a high-scoring method statement?
Specificity to the contract, evidence-backed claims (named comparable contracts, quantified outcomes), clear engagement with the buyer's stated priorities, and a credible mobilisation timeline. Generic capability narrative without engagement with the actual requirement consistently scores low even when the underlying capability is strong.
Should I include the same case studies in both the capability statement and the method statement?
Generally no; pick the strongest case studies for the capability statement (evidencing track record) and use the method statement to walk through how those case study approaches translate to this specific contract. Duplicating content uses bid space without adding evaluation value.