Tender Method Statements That Win: When Quality Can Be 60% of Score

A method statement in a tender is a site-specific document that proves, step by step, how you will carry out the work safely and to what standard. Public-sector buyers use it to verify capability before award, so it must show more than good intentions. The Health and Safety Executive (HSE) treats it as the standard written record for higher-risk construction work, and it feeds directly into how buyers score submissions on the Find a Tender service. Tools such as BidBlock can help teams organise the evidence a strong method statement needs.

TL;DR:

• Method statements must include detailed operational sequences with controls mapped to each step, specific plant and equipment information, and named responsible personnel.
• Effective submissions are built upon a completed risk assessment, with site information shaping all control measures and a chronological work sequence.
• Visual aids such as site plans, lifting diagrams, and briefing records enhance credibility and demonstrate actual site understanding to reviewers.
• Evidence of compliance, including certificates, inspections, and competence records, should be embedded in operational steps rather than stored separately.
• Tailoring the method statement to the specific project type and buyer priorities, along with internal sign-offs and evidence organization, significantly improves scoring chances.

Table of Contents

• What a tender method statement needs to include
• How do you write a method statement for a tender?
• Mapping method statement controls to UK regulations
• Using visuals and briefing records to prove the plan works
• Common mistakes that get method statements rejected
• How buyers actually score method statements
• Submission checklist and a compact template
• How BidBlock helps teams produce tender-ready method statements
• Getting internal sign-off before submission
• Why one template never fits every tender
• Fitting the method statement into your wider bid strategy
• Demonstrating compliance and continuous improvement over time
• Aligning stakeholders during tender evaluation
• Author's practical priorities for busy UK bid teams
• Try BidBlock for your next method statement
• Where to check the rules yourself
• Sources
• FAQ

What a tender method statement needs to include

Procurement reviewers work through a method statement looking for specific fields, not general reassurance. Missing one of these is a common reason scores fall short, even when the underlying work plan is sound.

• Delivery overview covering scope, site location, the principal contractor, and an overall timeline for the works.
• Mobilisation and start-up detail, including a mobilisation programme, resourcing levels, named mobilisation days, and site contacts.
• A step-by-step operational sequence, with the relevant control measure mapped against each individual step rather than bundled into a generic list.
• Roles, competence and training records, naming supervisors and specialists where the risk profile requires it.
• Plant and equipment details, including inspection or examination certificate references, alongside PPE specified against the relevant EN standard.
• Emergency arrangements, naming the responsible person on site and the nearest emergency care facility.
• Proposed sub-contractors, with supporting evidence of their competence and track record.
• Continuous improvement and KPIs, showing how quality and performance will actually be measured during delivery.

Buyers reading dozens of submissions notice quickly which bidders have simply reused a generic template. A method statement that names the site, the actual plant being used, and the specific supervisor responsible reads as credible in a way that generic phrasing never does.

How do you write a method statement for a tender?

Every strong method statement starts before you write a single sentence of prose: with a completed risk assessment. Gather the site information first, including boundaries, access routes, existing services, and utilities, because these details shape almost every control measure that follows. SafetyStack's guidance is clear that the method statement should be authored directly from that risk assessment, not written in parallel or from memory.

From there, the workflow follows a consistent order:

1. Sequence the work chronologically, describing tasks in the order they will actually happen on site, not the order that feels easiest to write.
2. Mark transitions explicitly wherever the hazard profile changes, such as moving from ground-level preparation to work at height.
3. Attach the control and its evidence to each step, including the inspection number, date, and competence record, rather than pushing controls into a separate appendix the reviewer has to cross-reference.
4. Specify equipment by make and model, with the date of its last inspection, and specify PPE against its EN standard rather than a vague description like "appropriate protective equipment."
5. Include briefing and induction records, plus a versioned sign-off block showing who approved the final document and when.
6. Run a self-audit before submission, checking every step against the checklist above.

Pro Tip: Write the operational sequence and the control measures in the same pass, not in two separate drafting stages. Splitting them is exactly how controls end up vague or disconnected from the step that actually needs them.

The chronological structure matters more than it might seem. A reviewer scoring dozens of statements against a tight deadline reads far more confidently when hazard and control appear together, step by step, than when they must hold the sequence in mind while flipping to an appendix. Tender word limits often force compression, and the temptation is to cut detail from individual steps and move it elsewhere. Resist that. A shorter statement with controls embedded at the point of use consistently reads as more credible than a longer one that scatters detail across sections.

Before submission, run a short internal QA pass: does every step have a named control, does every piece of plant have a certificate reference, and does every named individual have a competence record attached? If any answer is no, the document is not ready.

Mapping method statement controls to UK regulations

The Construction (Design and Management) Regulations 2015 (CDM 2015) is the reason method statements exist for demolition, structural alteration, and other higher-risk construction activity. It requires that higher-risk work is properly planned, managed, and monitored, and a method statement is the usual mechanism for demonstrating that in practice.

Beyond CDM 2015, most controls trace back to a specific task-based regulation:

• Work at height hazards map to the Work at Height Regulations 2005, so phrasing should reference edge protection, inspection of access equipment, and rescue arrangements.
• Hazardous substances map to COSHH 2002, so the statement should name the substance, its control measures, and any exposure monitoring in place.
• Work equipment maps to PUWER 1998, meaning the statement should reference inspection regimes and operator training for each machine used.
• Lifting operations map to LOLER 1998, requiring lift plans, thorough examination certificate references, and named appointed persons.

Phrasing that demonstrates compliance is specific: "edge protection inspected daily, recorded on Form X" reads far stronger than "safe access maintained throughout." Naming the actual training course, the certificate ID, or the EN standard turns a compliance claim from an assertion into something a reviewer can verify at a glance.

Using visuals and briefing records to prove the plan works

Text alone rarely convinces a reviewer that a method has been thought through at street level. HSE guidance notes that method statements work best when they include diagrams and are actively used in inductions and toolbox talks, not filed away as static appendices.

The visuals that matter most are site layout plans, lifting plans, exclusion zones, and sequence diagrams showing how work areas change over time. Annotate them properly: numbered reference points, anchor test points, plant positions, and marked safe routes all help an operative on site recognise the plan they were briefed on.

Pro Tip: Keep a briefing record template alongside the method statement itself, capturing attendance, date, and document version. If the method statement changes mid-project, the briefing record proves the whole team was told.

That link between diagram and briefing record is what separates a document that exists on paper from one that visibly shapes how work is carried out.

Common mistakes that get method statements rejected

Reviewers see the same deficiencies repeatedly, and most are quick to fix once identified.

• Vague steps and generic controls score poorly. Replace "work safely at height" with the specific access equipment, inspection frequency, and rescue plan for that step.
• Missing inspection or competence evidence is one of the most common gaps. Add certificate IDs, dates, and named individuals rather than referring to "trained operatives."
• Unclear emergency procedures undermine confidence in the whole document. Name the responsible person and the nearest accident and emergency facility rather than a generic "emergency services will be called."
• Recycled template text is the fastest way to lose marks. A statement that mentions a different site name, or ignores a genuine site constraint, tells the reviewer the bid was rushed. Revise the template with site facts every time, and update it again if conditions change during mobilisation.

How buyers actually score method statements

Quality can dominate a UK public tender's evaluation. The National Framework for Major Works 2026 notice on Find a Tender is a working example of a framework weighting quality at 60% against price at 40%, which means the method statement often carries more weight in the outcome than the number on the price schedule.

What actually drives those quality marks:

• Realism of mobilisation, meaning named resourcing and a credible mobilisation timeline rather than an optimistic best case.
• Measurable KPIs, giving the buyer something concrete to hold the contract against once work starts.
• Contingency and continuous improvement, showing what happens when something goes wrong and how performance will be reviewed over time.
• Social value, increasingly scored alongside technical delivery in public-sector frameworks.

Principal contractors and framework buyers consistently reward bidders who replace vague promises with named commitments: a specific number of mobilisation days, a stated number of trained full-time staff, a measurable KPI target. Put those figures near the top of the statement rather than burying them in the final paragraph, since reviewers working through a stack of submissions often score the opening content most carefully.

Submission checklist and a compact template

Before a method statement goes into a tender submission, run it against a short pre-submission checklist:

1. Header confirms the specific site, principal contractor, and project reference.
2. All relevant certificates and inspection dates are attached or referenced.
3. Competence records are named against the individuals doing the work.
4. Annotated visuals (site plan, sequence diagram, lifting plan where relevant) are included.
5. Sign-off and version number are recorded on the document itself.
6. Named contacts for site management and emergencies are listed.
7. Sub-contractor evidence is attached where sub-contractors are proposed.

A compact template that fits most tender word limits runs: header, delivery summary, mobilisation plan, operational steps with mapped controls, plant and PPE schedule, emergency arrangements, and an approval or briefing record block. Keep the core document tight and push detailed certificates or CVs into appendices where the tender rules allow it. That keeps the narrative readable for the scorer while the supporting evidence remains available for verification.

How BidBlock helps teams produce tender-ready method statements

Building a method statement from scratch for every tender wastes time you could spend refining the operational detail that actually wins marks. BidBlock's evidence library stores past RAMS documents, certificates, and briefing records so a team can pull proven content into a new draft rather than rewriting it, with version control keeping track of what changed between submissions.

BidBlock reports that clients using this workflow, which draws on historical evidence and social value contributions rather than generic AI output, have achieved a 75% win rate. That is the client's own reported outcome, not a guarantee for every bidder, but it reflects the underlying principle that evidence-backed detail scores better than freshly generated prose. Used well, the platform speeds up the parts of method statement writing that are repetitive, leaving more time for the site-specific detail reviewers actually mark on.

Getting internal sign-off before submission

A method statement that only the bid writer understands is a risk, because the site team delivering the contract needs to recognise the plan as their own. Circulate the draft to the site manager and any named supervisors before submission, not after award, so operational reality gets checked against what has been promised on paper.

Where multiple people contribute, a short review meeting works better than an email chain. Walk through the operational sequence step by step, confirming that the named plant, certificates, and competence records are accurate and current. This is also the point to catch a mismatch between what the bid team has written and what the site team actually plans to do, which is a common source of post-award disputes.

Keep a simple sign-off log recording who reviewed the document, on what date, and what version they approved. If the tender allows a query stage, use it to clarify ambiguous scoring criteria before finalising the statement, rather than guessing at what the buyer wants. A short, recorded review process costs little time and closes off one of the more avoidable reasons a strong technical plan reads as unconvincing on paper.

Why one template never fits every tender

A method statement written for a groundworks package will not transfer cleanly to a fit-out contract, even within the same framework. Different project types carry different dominant hazards, different regulatory triggers, and different buyer priorities, and a generic template flattens all of that into language that convinces nobody.

Tailoring starts with the risk profile. A demolition tender needs heavy emphasis on structural stability and CDM 2015 duties; a highways contract needs traffic management and public safety front and centre; a school refurbishment needs safeguarding arrangements that simply do not appear in most other sectors. Reusing the wrong emphasis is one of the fastest ways to signal that a bid was assembled quickly rather than considered carefully.

Buyer priorities shift too. A framework weighted heavily towards social value expects that theme woven through the operational narrative, not bolted on as a final paragraph. A framework focused on programme certainty rewards granular mobilisation detail over broader ambition statements. Reading the specific evaluation criteria for each tender, rather than assuming a proven structure will transfer, is what separates a method statement that scores well from one that merely exists.

Fitting the method statement into your wider bid strategy

The method statement rarely stands alone. It sits alongside pricing, social value commitments, and case studies, and buyers often expect consistency across all of them. A method statement promising rapid mobilisation loses credibility if the pricing schedule assumes a longer lead time, and a bid strategy built around technical excellence needs the method statement to carry that message through in detail, not just in the executive summary.

Treat the method statement as one thread in a coordinated response rather than a document written in isolation. Case studies referenced elsewhere in the bid should match the competence claims made in the method statement. Social value commitments described in a separate response section should be reflected in the resourcing and community engagement detail within the operational plan itself.

Bid teams working under tight deadlines often draft each section separately and reconcile them only at the end, if at all. That approach leaves gaps a careful reviewer will spot. A stronger process drafts the method statement early enough that its commitments can inform, and be informed by, the rest of the submission, keeping the whole response internally consistent.

Demonstrating compliance and continuous improvement over time

A method statement that only proves compliance at the point of submission misses half of what buyers are actually assessing. Frameworks increasingly score continuous improvement as its own criterion, which means the document needs to show how performance will be monitored and refined once the contract is live, not just how the work will start.

Concrete KPIs work better here than aspirational language. Naming a specific defect rate target, a programme milestone tracking method, or a review cadence gives the buyer something to hold the contract against, and it signals that quality management continues past mobilisation. Referencing how lessons from previous contracts have shaped the current approach, backed by specific examples rather than a general claim of "lessons learned," reinforces that continuous improvement is a genuine practice rather than a phrase.

Compliance evidence should be treated the same way. Rather than a single compliance statement at the start of the document, weave certificate references, training records, and audit frequency into the relevant operational steps throughout. A reviewer checking for regulatory alignment should be able to find the specific evidence exactly where the corresponding hazard appears, not have to search for it separately.

Aligning stakeholders during tender evaluation

Method statements often go through several hands before submission, including estimators, site managers, health and safety advisors, and the bid writer pulling it all together. Without a clear communication process, those contributions drift out of sync, and the final document reads as though several different people wrote it without reading each other's sections.

A short kick-off conversation at the start of drafting helps more than a long review at the end. Agree who owns each section, confirm what evidence already exists versus what needs gathering, and set a realistic deadline that leaves time for a technical review before submission. Site managers and supervisors should see the operational sequence before it is finalised, since they are the ones who will need to deliver against it and are best placed to flag an unrealistic step early.

During evaluation itself, buyers occasionally raise clarification questions about a method statement's content. Having a single point of contact who understands the full document, rather than routing questions through several people, keeps responses consistent and fast. Some frameworks also run moderation panels or site visits as part of evaluation, and briefing the person attending on exactly what was written, including the reasoning behind specific control choices, avoids answers that contradict the submitted document.

Author's practical priorities for busy UK bid teams

Site-specific evidence beats polished prose every time procurement reviewers open a document. A statement built around a real named plant, a real certificate, and a real supervisor will consistently outscore something eloquent but generic. Visuals and briefing records matter because they convert a written claim into something a site team can be checked against. A short internal QA gate, even fifteen minutes before submission, catches the gaps that cost marks.

— Syed

Try BidBlock for your next method statement

There are other ways to build a method statement library, including shared drives and static templates passed between colleagues, but they rarely keep certificates, competence records, and past RAMS examples in one searchable place. BidBlock is built specifically for UK public-sector bid teams who need that evidence organised and ready to reuse, not rebuilt from scratch every time a tender lands.

The platform offers multiple subscription plans scaled to usage, including a free plan and various paid tiers with different features and limits. BidBlock is a productivity tool for organising evidence and drafting support, not a substitute for legal or health and safety advice, but it does help teams keep certificates, briefing records, and previous method statements in one version-controlled workspace. If your team is preparing its next submission, explore BidBlock's plans and see which tier fits your current tender pipeline.

Where to check the rules yourself

• HSE guidance on method statements sets out when and why they are used in construction safety planning.
• The Procurement Act 2023 governs notice types and publication duties for UK public procurement.
• Find a Tender's notice types page explains where higher-threshold contract notices, including framework opportunities, are published.

Sources

• Administration - HSE (Method statements)
• National Framework for Major Works 2026 - Find a Tender
• Legislation
• How to write a method statement — SafetyStack

FAQ

Is a method statement a legal requirement?

No single law requires a document specifically labelled a method statement, but HSE guidance treats it as the standard written record for planning and monitoring higher-risk construction work under CDM 2015. In practice, most public-sector tenders and principal contractors require one as evidence of safe delivery.

Does the UK still use OJEU?

No. OJEU notices were replaced when the Procurement Act 2023 came into force, and higher-threshold public contracts are now published through the Find a Tender service instead.

What is the UK tender process?

The UK public tender process involves a buyer publishing a notice, usually via Find a Tender for higher-value contracts, bidders submitting technical and pricing responses, and the buyer scoring submissions against published criteria such as quality and price weightings. Platforms like BidBlock help bidders track these opportunities and organise the evidence needed to respond.

What is a UK4 tender notice?

A UK4 notice is one of the notice types introduced under the Procurement Act 2023 framework published via Find a Tender, generally used for specific stages of the procurement process such as competitive tendering procedures. The exact notice type required depends on the procurement route the buyer has chosen, so bidders should check the specific notice details for their opportunity.

What should a tender method statement example include?

A strong example includes a delivery overview, a step-by-step operational sequence with controls mapped to each step, named competence and inspection records, and an emergency procedure naming a responsible person. Reviewers consistently favour site-specific detail over generic template language.