A tender method statement explains exactly how you will deliver a requirement: the steps, the people, the resources, the timings, how you will manage risk and how you will measure quality. The best method statement examples mirror the question's sub-points, commit to specifics and prove each claim with evidence.
Context for method statement writing in UK tenders
Award test
Most advantageous tender
Quality answers, including method statements, are scored against published criteria.
Procurement Act 2023Assessment summaries
Scores explained
Bidders receive reasons for their scores under the Act.
GOV.UK guidanceCDM 2015
Construction safety
Construction method statements must reflect the Construction (Design and Management) Regulations.
HSEPPN 017
AI disclosure
Buyers may ask how AI was used to prepare answers.
GOV.UKWhat is a method statement in a tender?¶
In a tender, a method statement is your written answer to 'how will you deliver this?'. It may be one big question (a delivery methodology worth 30% or more) or several smaller ones on mobilisation, service delivery, quality, staffing, health and safety or contract management. It is different from a construction site method statement, which is an operational safety document describing how a specific task will be done safely. Tender method statements often draw on the same thinking, but their job is to win marks, so they must be written to the buyer's scoring criteria.
| Tender method statement | Site safety method statement (RAMS) | |
|---|---|---|
| Purpose | Persuade evaluators you will deliver well | Instruct workers how to do a task safely |
| Audience | Buyer's evaluation panel | Site operatives and supervisors |
| Written when | At tender stage | Before work starts |
| Judged by | Scoring criteria and weighting | Health and safety compliance |
| Tone | Commitments with evidence | Clear instructions and controls |
A method statement structure you can reuse¶
Most method statement tender questions can be answered with the same backbone. Adapt the headings to match the buyer's sub-points and keep their order. If the question asks for five things, your answer should have five clearly signposted sections.
- 1
Summary
Two sentences stating your approach and key commitment.
- 2
Approach
The steps you will follow, in sequence, with timings and frequencies.
- 3
People
Named roles, numbers, qualifications and responsibilities.
- 4
Resources
Equipment, systems, materials, vehicles and suppliers.
- 5
Quality
How you check the work, KPIs, reporting and improvement.
- 6
Risk
What could go wrong and your controls and contingencies.
- 7
Evidence
Where you have done this before and the results.
How to write a method statement for a tender¶
Method statement writing in eight steps
Step 1
Map the question to the specification
List the specification clauses, service levels and KPIs the question relates to.
Step 2
Break down the sub-points
Turn every part of the question into a heading, in the buyer's order.
Step 3
Walk through delivery
Describe a real day, week or project stage on this contract, step by step, before you write.
Step 4
Assign people and resources
Say who does each step, how many of them, and with what equipment or systems.
Step 5
Set timings and measures
Give frequencies, response times and the KPIs you will report.
Step 6
Add risk controls
Name the two or three biggest risks and how you prevent and recover from them.
Step 7
Prove it
Add a case study or data showing you have delivered the same method before.
Step 8
Edit to the limit and review
Cut generic text, meet the word or page limit, and have someone score it against the criteria.
Method statement example 1: service delivery¶
Provide a method statement describing how you will deliver the grounds maintenance service across the 18 school sites, including scheduling, staffing and quality control.
Scheduling: the 18 sites are grouped into three geographic rounds of six, each served by a dedicated two-person team with a crew-cab tipper. Grass cutting follows the specification's 14-cut season, with every site visited on a fixed weekday so schools know when to expect us. Work near play areas is scheduled outside break times agreed with each site business manager during mobilisation. Staffing: six operatives holding PA1/PA6 certificates for pesticide application, plus a supervisor with seven years on education contracts. All hold enhanced DBS checks. Quality control: the supervisor audits each site monthly against the specification using a photo-evidenced checklist, shared with you in a monthly report. Defects are rectified within five working days, safety defects within 24 hours. Evidence: we use this model on a 12-site academy trust contract, where we met 98% of cut schedule dates in 2025.
Why it scores
- Answers scheduling, staffing and quality in order
- Specific numbers and qualifications
- Written for schools (break times, DBS)
- Measurable standards and evidence
Illustrative example. Replace figures with your own verified data.
Method statement example 2: mobilisation¶
Describe your mobilisation method, including how you will manage TUPE transfer and ensure continuity from the start date.
Mobilisation runs over eight weeks from award, led by a named Mobilisation Manager and tracked on a plan shared with your contract manager weekly. Weeks 1-2: request employee liability information from the incumbent, as required under the TUPE Regulations, and hold group consultation with transferring staff. Weeks 3-5: one-to-one meetings, measures letter, uniform and ID issue, systems access. Weeks 6-7: site inductions and training on our reporting app. Week 8: shadow running and readiness review. For continuity, the incumbent's supervisors are retained on day one, and a relief pool of four staff covers any gaps in the first month. A risk log covers late staff data, attrition and access delays, each with an owner and mitigation.
Why it scores
- Week-by-week plan
- TUPE steps named
- Specific continuity measures
- Risks and owners
Illustrative example. Timescales depend on the contract.
Method statement example 3: health and safety¶
Explain how you will manage health and safety on this refurbishment project, including your approach to occupied buildings.
We will act as Principal Contractor under CDM 2015 and produce a Construction Phase Plan before work starts, reviewed by our CSCS-carded Site Manager, who holds SMSTS. Because the building stays occupied, works are zoned into four phases with solid hoarding between work areas and occupied space, separate contractor access and a daily 8am briefing with your facilities team on noise, dust and access. Noisy work runs 8am to 10am and 2pm to 4pm by agreement. Task-specific RAMS are issued for each activity and briefed to operatives before work. Our independent health and safety adviser audits the site monthly and the reports are shared with you. Our accident frequency rate over the past three years is published in our annual report, and we will provide it at clarification.
Why it scores
- Named regulations and roles
- Specific controls for occupied buildings
- Assurance through audits
- Verifiable evidence offered
Illustrative example based on CDM 2015 duty-holder roles.
Method statement example 4: IT service desk¶
Describe how you will deliver the first-line service desk, including hours of operation, incident prioritisation and escalation.
The service desk will operate 8am to 6pm Monday to Friday, as required in section 3.2, with out-of-hours P1 cover by an on-call engineer. Calls, emails and portal tickets are logged in our ITIL-aligned service management tool. Incidents are prioritised using the four levels in your specification: P1 (service down) responded to in 15 minutes and resolved or workaround in 4 hours; P2 in 1 hour and 8 hours; P3 in 4 hours and 3 working days; P4 in 1 working day and 10 working days. Unresolved incidents escalate automatically to second line at 50% of the resolution target, and to our Service Delivery Manager at 75%. You will receive a monthly SLA report and a quarterly service review. On a comparable public-sector contract of 1,200 users we have met the P1 target every month since 2024.
Why it scores
- Uses the buyer's own priority levels
- Precise hours and targets
- Automatic, timed escalation
- Comparable evidence
Illustrative example. Targets should match the buyer's specification.
Turning your operating procedures into a method statement¶
Most businesses already have the raw material for strong method statements in their operating procedures, checklists, training records and management reports. The work is translation. A procedure written for staff says 'check the vehicle before leaving the depot'. A method statement written for an evaluator says 'drivers complete a 14-point walkaround check in our fleet app before every shift; any defect grounds the vehicle and a spare from our pool of three is deployed within two hours'. Same process, but now it has a number, a system, a consequence and a contingency the evaluator can score.
Interview the people who do the work. Ask them to walk you through a normal day on a similar contract, and what happens when something goes wrong. Those answers produce the specific, credible detail that separates a 5 from a 3, and they make sure you promise only what your operation can deliver.
What evaluators look for in a method statement¶
- Every sub-point in the question answered, in order, and easy to find.
- Clear sequence: what happens first, next and last, with timings.
- Specific resources: numbers of people, qualifications, equipment and systems.
- A clear grasp of the buyer's context: sites, users, constraints, current issues.
- Measurable quality: KPIs, inspection regimes and reporting.
- Realistic risk management rather than a promise that nothing will go wrong.
- Evidence that the method works, from similar contracts.
Method statement tender tips by sector¶
| Sector | What to include | Common gap |
|---|---|---|
| Construction | Programme, sequencing, CDM 2015 roles, logistics, waste management, quality inspections | Generic programme not tied to site constraints |
| Cleaning and soft FM | Frequencies, staffing hours, BICSc or similar training, COSHH, audit scores | Hours per site not stated |
| Social care | Care planning, safeguarding, CQC standards, staff training and supervision | Outcomes for people not measured |
| IT services | Service desk model, SLAs, incident and change management, security | No exit or transition plan |
| Consultancy | Methodology, stages, deliverables, named experts, quality review | Deliverables not dated |
| Transport and logistics | Routes, vehicles, driver checks, contingency for breakdown | No contingency vehicle plan |
Common method statement mistakes¶
| Mistake | Why it loses marks | Fix |
|---|---|---|
| Pasting a health and safety policy | Policies describe intent, not delivery on this contract | Explain how the policy is applied here |
| Describing your company instead of the method | Evaluators score the method, not your history | Start with the steps |
| No numbers | Evaluators cannot judge resourcing without them | State headcount, hours, frequencies and times |
| Ignoring constraints | Shows you have not understood the site or service | Name the constraints and your response |
| Inconsistent with pricing | Resource promised but not costed raises doubts | Build price and method from one resource plan |
| Diagrams without explanation | Some portals strip images or limit pages | Check format rules; describe key points in text |
Formatting method statements for tender portals¶
Check the instructions before choosing a format. Some buyers ask for answers typed into a text box on the e-tendering portal, which strips formatting and counts characters rather than words. Others ask for uploaded documents with a page limit, font size and margin rules. Where tables and diagrams are allowed, a Gantt-style mobilisation timeline or a staffing table can save words and make scoring easier. Where they are not, use short numbered steps and clear headings in plain text.
- Text box answers: draft in Word, check the count the portal uses, paste and preview before saving.
- Page limits: check whether appendices, covers and diagrams count towards the limit.
- File names: follow the buyer's naming convention, for example question number and supplier name.
- Cross-references: avoid them unless the buyer allows it, as each answer is often scored in isolation.
Tools that help¶
If you write method statements often, compare AI bid writing software and construction tender software, or see the tender writing services that write them for you.
Related guides: Construction bid writing · Tender writing examples · How to answer tender questions · Tender response template · How to write a bid
Sources
FAQs
Frequently asked questions
- It is your written explanation of how you will deliver the contract or a part of it: the steps, people, resources, timings, quality controls and risk management. It is scored against the buyer's criteria.
- Map the question to the specification, use each sub-point as a heading, describe the steps in sequence with named roles, resources and timings, add quality measures and risk controls, and prove the method with evidence from similar contracts.
- As long as the buyer's word or page limit allows. Use most of it if you have relevant detail, but never exceed it, as excess text may be ignored or the answer rejected.
- No. RAMS (risk assessment and method statement) is an operational safety document for a specific task. A tender method statement is a scored answer explaining how you will deliver the contract, though it may refer to your RAMS process.
- A summary, the approach step by step, people and qualifications, resources and equipment, quality control and KPIs, risk management and evidence of past delivery, adapted to the question's sub-points.
- Use a template for structure and reusable content such as processes and CVs, but rewrite each statement for the buyer's specification, sites and question. Generic method statements score poorly.
- Only if the buyer's instructions allow it. Where permitted, timelines and tables can help; check whether they count towards page limits and whether the portal accepts images.