How to Write a Method Statement for a Tender (With Examples)

Method statements are one of the most heavily weighted sections in public sector tenders. They ask you to explain how you will deliver the contract, not just that you can deliver it. A strong method statement demonstrates your understanding of the buyer's requirements, your planned approach, and your ability to manage risks.

This guide explains how to structure method statements that evaluators reward with high scores.

What Evaluators Actually Want

Before writing a single word, understand what evaluators are looking for. A method statement is not a brochure or a company profile. It is a detailed explanation of your delivery approach for this specific contract.

Evaluators want to see that you understand the scope and requirements, that your approach is realistic and deliverable, that you have considered the risks and challenges, that your team has the right skills and experience, and that you can demonstrate how you will measure and report on performance.

Generic statements about "delivering excellent service" score poorly. Specific commitments about what you will do, when, and how, supported by evidence from comparable contracts, score well.

The Structure of a Strong Method Statement

Opening: Direct Answer

Start with a clear summary of your approach. The first paragraph should tell the evaluator exactly what you will deliver and how. Do not begin with your company history or general capability statements.

Weak opening: "ABC Ltd is a leading provider of facilities management services with over 20 years of experience across the UK public sector."

Strong opening: "We will deliver the cleaning and waste management service across all 14 sites within the contract area, using a dedicated team of 28 operatives managed by a regional contract manager based within 15 miles of the authority's main office."

Mobilisation Plan

Explain how you will transition into the contract. Buyers want confidence that service delivery will begin smoothly, especially when an incumbent supplier is being replaced.

Cover your mobilisation timeline with key milestones, how you will manage TUPE transfer of existing staff, your approach to site surveys and baseline assessments, how you will introduce your management team to the buyer's stakeholders, and your communication plan during the transition period.

Delivery Methodology

This is the core of your method statement. Break it down by work stream or service area, mirroring the structure of the buyer's specification.

For each element, explain what you will do and how frequently, who will be responsible, what equipment, materials, or systems you will use, how you will maintain quality standards, and how you will handle variations or additional requirements.

Use specific numbers and timeframes rather than vague commitments. "Our supervisor will conduct weekly quality audits of each site, completing a 42 point checklist and submitting the report to your contract manager within two working days" is far stronger than "we carry out regular quality checks."

Risk Management

Identify the key risks specific to this contract and explain how you will mitigate them. This shows the evaluator that you have thought carefully about what could go wrong and have contingency plans in place.

Focus on risks that are relevant to the buyer's context, not generic risks that apply to any contract. If the contract involves working in occupied buildings, address how you will minimise disruption. If it involves seasonal variation in demand, explain how you will flex your resources.

Continuous Improvement

Explain how your approach will develop over the contract term. Buyers want to see that you will not simply maintain the status quo but will actively seek opportunities to improve service quality, efficiency, and value.

Reference specific improvement mechanisms such as regular service reviews, staff development programmes, technology upgrades, or process refinements. Where possible, quantify the expected benefits.

Examples by Sector

Construction and Maintenance

For construction tenders, method statements typically need to cover programme and sequencing of works, health and safety management, quality assurance processes, environmental management, traffic management and site logistics, and community engagement and disruption minimisation.

Example paragraph: "All works will be delivered in three phases over 18 weeks, sequenced to maintain public access to the main entrance throughout the programme. Phase 1 covers internal strip out and structural works (weeks 1 to 6), Phase 2 covers mechanical and electrical installation (weeks 7 to 12), and Phase 3 covers finishing trades and commissioning (weeks 13 to 18). Our site manager will conduct daily briefings at 07:30 with all operatives, covering the day's programme, safety considerations, and interface management."

Facilities Management

For FM contracts, focus on service delivery models, staffing structures, response times, planned preventative maintenance schedules, and performance monitoring.

Example paragraph: "Reactive maintenance requests will be logged through our client portal, with automatic acknowledgement within 15 minutes. Priority 1 calls (safety critical) will receive an on site response within two hours, with a target resolution within four hours. All reactive works will be completed by our directly employed multi skilled operatives, reducing reliance on subcontractors and ensuring consistent quality."

Common Mistakes to Avoid

Copying from previous bids without tailoring. Evaluators spot generic content immediately. Every method statement must reference the specific contract, buyer, and requirements.

Describing what you do generally instead of what you will do specifically. Method statements should be written in future tense with specific commitments, not present tense descriptions of your usual approach.

Ignoring the word limit. Use 90% to 95% of the available word count. Too few words suggests insufficient depth. Exceeding the limit risks truncation or disqualification.

Listing capabilities without explaining how. Saying you "have extensive experience in project management" tells the evaluator nothing. Explaining how you will manage this specific project, with named roles, defined processes, and measurable targets, tells them everything.

Forgetting the human element. Strong method statements name key personnel, describe their relevant experience, and explain their specific role in the contract. Buyers want to know who will actually deliver the work.

Getting Professional Support

Writing effective method statements requires the ability to extract practical detail from your delivery teams and present it in the structured, evidence based format that evaluators reward.

If your team excels at delivery but struggles to capture their approach in writing, professional bid writing support can bridge that gap. TenderVera bid specialists work with your team to understand your methodology and present it in clear, compelling language that scores well against the evaluation criteria.

Conclusion

Method statements win and lose tenders. They test your understanding of the buyer's needs, your planning capability, and your ability to deliver. Invest the time to write them properly, tailor them specifically to each contract, and support every commitment with evidence from comparable experience.