A method statement is where public sector contracts are won or lost. Buyers already know what you have delivered in the past from your case studies and experience questions. The method statement answers the question that matters most to the evaluator right now: how, specifically, will you deliver this contract? A vague, generic, or descriptive tender method statement signals delivery risk. A specific, credible, and evidence-anchored one signals the operational confidence that earns a 5/5 method statement score.

The gap between a 3 and a 5 is rarely about the underlying capability of the supplier. It is almost always about the structure of the response. Evaluators scoring a quality response tender are looking for verifiable proof that your delivery model works, not assertions that your team is experienced. They need to see the exact mechanics of your operation. This guide breaks down the exact structure that secures maximum marks under the Procurement Act 2023, the common mistakes that drop scores, and how to write a method statement that evaluators can confidently score a 5.

What this guide covers

The standard 0–5 scoring methodology used by UK public sector buyers and what each score actually means in practice.
The six-section structure of a 5/5 method statement, broken down section by section.
A detailed worked example of a mobilisation method statement for a facilities management contract, showing both a poor and an excellent response.
The four common mistakes that drop a 5 to a 3 and how to fix them.
Frequently asked questions about tender method statements from bid writers and directors.

The 0–5 scoring methodology explained

UK public sector procurement relies on standardized scoring matrices to evaluate quality responses. While the exact wording varies slightly between contracting authorities, the underlying principles remain remarkably consistent across Construction and Facilities Management tenders. Understanding the difference between a 3 and a 5 is the first step to writing higher-scoring responses. You cannot hit the target if you do not know what the target looks like.

A score of 0 indicates no response or a complete failure to meet the requirement. This is rare for a serious bid but happens when a supplier completely misunderstands the question.

A score of 1 (Very Poor) or 2 (Poor) means the response has significant gaps or only partially meets the requirement. It gives the evaluator little confidence in your ability to deliver. These scores usually result from failing to address specific sub-questions or providing a response that is entirely theoretical without any practical application.

A score of 3 (Satisfactory) means the response meets the requirement. This is where the vast majority of competent suppliers land. A 3-scoring response describes a viable methodology but relies heavily on generic statements ("we will implement a robust framework", "our experienced team will manage the process"). It lacks specific, quantified evidence. It tells the evaluator what will happen, but not exactly how, by whom, or with what proven result. A 3 is a pass, but it rarely wins competitive tenders.

A score of 4 (Good) means the response exceeds the requirement, offering additional detail, clear processes, and strong confidence. It is a solid response but might lack the final layer of quantified evidence or a clear connection to the buyer's strategic outcomes.

A score of 5 (Excellent) requires a comprehensive response that fully meets and exceeds the requirement, demonstrating clear added value and exceptional operational confidence. A 5/5 method statement names specific processes, assigns named individuals with defined authority levels, provides quantified evidence from comparable contracts, and explicitly connects the delivery model to the buyer's desired outcomes. It leaves the evaluator with zero ambiguity about how the contract will operate on day one. It removes all perceived risk.

The six-section method statement structure

A well-structured tender method statement gives the evaluator a logical, progressive picture of delivery. It moves sequentially from the initial transition phase through daily operations, risk control, and performance management. This six-section structure works across most contract types and frameworks, including the Crown Commercial Service RM6232 Facilities Management framework.

1. Delivery overview

Open the method statement with a direct, confident overview of your delivery approach. State this in two to three sentences that answer the question immediately and set the structure for everything that follows. Name the core delivery model. Identify the key operational phases. Reference the performance framework that governs them.

The evaluator should finish the opening paragraph knowing the headline answer to the question before reading any supporting detail. Do not open with company history, general capability statements, or a restatement of the question. Every word before the first direct answer is a word that does not earn marks. If the question asks how you will manage site security, your first sentence must be: "We will manage site security using a three-tier access control system governed by our ISO 27001 protocols."

2. Mobilisation and transition

For most contracts, the transition from the incumbent provider to your organisation is the highest-risk phase of the entire delivery period. Buyers evaluate mobilisation sections with particular care because poor mobilisation is the most common cause of early contract failure. They have likely been burned by poor transitions in the past.

A strong method statement addresses this risk directly. Describe your mobilisation programme in distinct phases, with named activities, named responsibilities, and specific timeframes attached to each. Reference your parallel operations model or equivalent transition risk management approach. Evidence this approach with the outcome from a comparable mobilisation you have successfully managed.

A supplier who describes a twelve-week phased transition programme with named roles, defined activities, and a referenced track record of zero-disruption mobilisations provides the specific confidence that earns full marks. Generality does not. Do not just say you will "work closely with the incumbent"; explain exactly how your transition team will interface with their departing team, including data handover protocols and TUPE timelines.

3. Operational delivery processes

The operational delivery section is the core of the method statement. It describes the day-to-day processes through which the contract requirement will be met. This section must be highly specific to the buyer and the contract, not a generic description of how your organisation typically delivers this type of service.

Name the specific processes involved. Describe how they connect to each other and align with the specification requirements the buyer has published. Reference the technology platforms, management systems, or accredited frameworks (such as ISO 9001 or ISO 14001) that govern their operation. The evaluator reading this section should finish it with a clear mental picture of your organisation in delivery. Walk them through a typical day or a typical process lifecycle, from ticket logging to resolution.

4. Roles, responsibilities, and team structure

Buyers award contracts to people as much as to organisations. The team section of your method statement gives the evaluator confidence that the right people will be delivering the contract, equipped with the necessary experience, authority, and organisational support to maintain performance throughout the term.

Name your contract manager. Describe their relevant experience in specific terms, citing similar contracts they have successfully run. Explain their reporting line, their authority level (e.g., their financial sign-off limit), and their deputy arrangements for when they are on leave. Present the wider team structure and the specific responsibilities of each role. Resist the temptation to use generic job titles and vague descriptions of responsibilities. Specificity at this level earns full marks.

5. Risk management

Every contract carries delivery risks. A method statement that does not address them signals naivety about the complexity of the contract or a lack of genuine planning. A method statement that identifies specific risks, names mitigations, and evidences their effectiveness from comparable delivery signals operational maturity.

Identify the three to five most significant risks for the specific contract. Name each risk precisely (e.g., "supply chain delays for specialized HVAC components" rather than just "supply chain issues"). Describe the specific mitigation. Evidence the mitigation with a specific outcome from a comparable contract where the approach worked. This three-part risk structure (named risk, specific mitigation, evidenced outcome) earns maximum marks in every risk section across every sector.

6. Performance management and continuous improvement

Close the method statement with a clear description of how you will monitor performance, report it to the buyer, and improve it continuously throughout the contract term. Name the KPI framework you will operate. Describe the review cycle (weekly, monthly, quarterly) and what each review covers.

Explain your escalation protocol: what triggers it, who activates it, how quickly corrective action is implemented, and how it is independently verified. Describe your continuous improvement methodology and evidence it with a specific improvement you delivered on a comparable contract. Finally, conclude with a benefit statement that connects your delivery model directly to the specific outcomes the buyer cares most about.

Worked example

The following example illustrates the stark difference between a 3-scoring response and a 5/5 method statement for a mobilisation question on a facilities management tender.

The Question: Describe your methodology for mobilising the facilities management contract across the Council's estate, ensuring zero disruption to frontline services on day one.

The 3-Scoring Response:

"We have extensive experience mobilising FM contracts for local authorities. Upon contract award, our dedicated mobilisation team will implement a robust framework to manage the transition from the incumbent supplier. We will work closely with the Council to ensure a smooth handover of services. Our experienced contract manager will oversee all operational activities, and we will conduct regular progress meetings to keep stakeholders informed. We have a proven track record of successful mobilisations."

This response is entirely generic. It describes what will happen ("robust framework", "smooth handover") but not how it will happen. It relies on assertions rather than evidence. Any supplier could have written this paragraph.

The 5/5 Method Statement Response:

"Our mobilisation methodology guarantees zero disruption to the Council's frontline services by running a 12-week phased transition programme, governed by our ISO 9001-accredited parallel operations model.
Phase 1: Discovery and TUPE (Weeks 1-4). Our Mobilisation Director, Sarah Jenkins, will lead the initial phase, completing the TUPE consultation for the 45 transferring staff and auditing the asset register across all 12 core sites.
Phase 2: Parallel Operations (Weeks 5-10). We will deploy our CAFM system, running it concurrently with the incumbent's helpdesk to verify data transfer accuracy. During this phase, our incoming Contract Manager, David Chen, will shadow the incumbent's site leads.
Phase 3: Go-Live Readiness (Weeks 11-12). We will conduct a full operational stress test of the reactive maintenance SLA response times.
We deployed this exact 12-week parallel operations model for the recent £4m FM contract with Coventry City Council, achieving 100% statutory compliance on day one and zero missed SLAs in the first quarter. This approach eliminates the risk of service downtime during transition, ensuring Council staff can deliver public services without facility interruptions from the moment the contract begins."

This response earns maximum marks. It opens directly, names specific individuals and phases, provides quantified evidence from a comparable contract, and closes with a strong benefit statement tied directly to the buyer's required outcome.

Common mistakes

The gap between an adequate tender response and an outstanding one is not the gap between a capable and an incapable supplier. It is the gap between a supplier who understands what scoring requires and one who does not. Here are the four common mistakes that drop a 5 to a 3.

Opening with company history or general capability statements. Evaluators read dozens of responses. Do not waste the opening paragraph restating the question or summarizing your 20-year history in the sector. Open directly with your delivery methodology. The first sentence should tell the evaluator exactly how you will deliver the contract.
Using generic methodology descriptions. Phrases like "robust framework," "experienced team," and "industry best practice" earn minimal marks because they assert rather than demonstrate. Replace them with specific processes, named roles, defined metrics, and accredited standards. Name the CAFM system you use. Name the Contract Manager. Name the specific risk mitigation.
Failing to quantify evidence. "We have delivered similar contracts across the Midlands" is an assertion. "We delivered a £2.5m housing repairs contract for Birmingham City Council, completing 98.3% of routine repairs within the 4-hour target response time" is evidence. Every claim requires a specific, verifiable proof point with numbers attached.
Ending without a benefit statement. A method statement should not just trail off after the methodology is described. It must connect the delivery model to the buyer's specific outcomes. Close every answer with a forward-looking statement explaining exactly what the buyer gains from your approach, referencing their stated priorities.

Frequently asked questions

What is the difference between a method statement and a standard operating procedure?

A standard operating procedure (SOP) is an internal document detailing how your business completes a routine task. A tender method statement is a bespoke, external-facing document written specifically for a buyer, explaining how you will apply your SOPs to deliver their specific contract requirements.

How long should a method statement be?

The length is usually dictated by the word or page count limits set in the tender documents. If no limit is provided, aim for concise, structured detail. A 5/5 method statement is rarely the longest response; it is the most specific. Focus on density of evidence rather than volume of words.

Do I need to include health and safety in every method statement?

Only if the question specifically asks for it, or if health and safety is a critical risk factor for the delivery methodology being described (common in Construction tenders). Otherwise, keep the focus strictly on the operational delivery requirements outlined in the specific question.

Can I reuse method statements across different tenders?

You can reuse the core structure and the quantified evidence from your bid library, but you cannot copy and paste the entire response. A 5/5 method statement must be tailored to the specific buyer, their named risks, and their stated outcomes. Generic, recycled answers rarely score above a 3.

How to write a method statement that scores 5/5