← Back to blog

10 November 2026

How to Write a Method Statement That Scores in a Public Tender

A hand writing notes on a yellow lined pad

Most public tenders are won and lost in the quality questions, and the heart of the quality questions is the method statement: describe how you will deliver this service.

It is also where most bids are weakest. Not because suppliers do not know how to do the work — they usually know far better than the buyer — but because they describe it the way they would to a colleague, not the way an evaluator is told to mark it.

How an evaluator actually reads your answer

Evaluators score against a published methodology. A typical scale runs 0 to 5 or 0 to 10, and each band has a written description. The top band usually says something close to "a comprehensive response that fully addresses the requirement, with clear evidence and detail giving the authority high confidence in delivery." The middle band says "addresses the requirement but lacks detail in some areas."

Notice what that does. The difference between a 3 and a 5 is not whether your method is good. It is whether the evaluator, reading only what you wrote, can be confident it is good. Confidence comes from specifics and evidence.

Evaluators often mark individually and then meet to agree a moderated score. If one of them could not find where you answered part of the question, you will be argued down, not up.

Before writing a word

Break the question into its parts. Most method questions contain three to six separate asks hidden in one paragraph: how you will mobilise, staff, manage quality, report performance and handle complaints. Write each one down. Each becomes a heading.

Read the specification against the question. The question tells you what is scored; the specification tells you what "good" means to this buyer. If the spec says response within four hours, your method should say how you guarantee four hours, not "prompt response".

Find the scoring guidance and the weighting. A question worth 20% deserves more of your time than one worth 5%, and the guidance sometimes lists exactly what a top answer includes.

A structure that works

There is no magic template, but this shape consistently does well:

  1. A one-paragraph summary of your approach that answers the question directly in its own language. Evaluators read this first and it frames everything after.
  2. One section per part of the question, in the order they asked it, with their words as the heading. Make it impossible to miss where each element is answered.
  3. Who does what. Named roles, and ideally named people, with relevant experience. "Our Contract Manager, who has run three similar contracts for district councils" beats "an experienced team".
  4. How, when and how often. Timescales, frequencies, tools, checklists, the actual steps. Specific numbers are believable; adjectives are not.
  5. What happens when it goes wrong. Risks, escalation routes, contingency. This is where many mid-band answers lose the top mark.
  6. Evidence. A short example from a real contract where you did this and what the measurable result was.
  7. Commitments. What the buyer can hold you to — and will be able to measure in contract.

The phrases that score nothing

Every evaluator has read these a thousand times:

  • "We are committed to providing a high-quality service."
  • "Our experienced and dedicated team…"
  • "We pride ourselves on…"
  • "Customer satisfaction is at the heart of everything we do."

None of them are wrong. None of them can be scored. Replace each one with the fact behind it: what your complaint rate actually is, how long your supervisors have been with you, what your last client measured.

Word limits and formatting

Respect the limit exactly. Anything past it may simply not be read, and some portals cut text off.

Use the space for substance, not repetition. Do not restate the question at length or repeat your company history in every answer.

Make it scannable. Short paragraphs, headings that mirror the question, bullet points for lists of steps, and a simple table if you are showing a timeline or a resourcing plan — if the buyer allows formatting. If they only accept plain text in a portal box, use clear numbered paragraphs instead.

Do not attach what was not asked for. If the question does not permit attachments, evaluators are generally told not to look at them.

Reuse without copying

A good answer library is the biggest time saver in bidding. But a method statement pasted unchanged from a previous bid reads like one — it mentions the wrong service, the wrong locations, the wrong volumes — and evaluators spot it in a sentence.

Keep the proven structure and the evidence; rewrite the detail for this specification every time.

Getting the first draft down faster

The hardest part of a method statement is the blank page. TendersHub can draft a first answer for you: upload the buyer's tender questions as a PDF or Word file and get AI answers based on your company profile to edit, or generate a full AI bid draft from the tender itself. It does not replace your knowledge of the work; it gets you to the editing stage on day one instead of day four.

Find the tenders worth writing for among 11,100+ live UK opportunities: browse tenders, or see your best matches free.

Find tenders you can actually win

Plans from £24.99/month inc. VAT.

Get started →