How to write a public sector tender response that actually wins
Most construction tenders are lost on the quality answers, not the price. A practical method for scoring well on method statements, case studies and the selection questionnaire.
Here’s an uncomfortable truth from the evaluation side of the table: most public sector construction tenders are not lost on price. They’re lost on the quality answers, by firms who could absolutely have done the job, because they treated the written submission as a box-ticking chore rather than the thing that actually decides the award.
Evaluators score what’s on the page, against a published marking scheme, in isolation. They cannot give you credit for what you meant, what you usually do, or how good your sites obviously are. If it isn’t written down and evidenced, it didn’t happen. This guide is about getting the marks that are sitting there for the taking.
Why good firms lose winnable bids
The pattern is almost always one of three things: the firm answered a slightly different question to the one asked; the firm asserted quality (“we are committed to excellence”) instead of evidencing it; or the firm wrote a strong bid but ran out of time and submitted it half-finished at 4:58pm on deadline day. All three are avoidable, and none of them are about how good a builder you are.
The selection questionnaire is a gate, not a beauty contest
The Selection Questionnaire (SQ — the successor to the old PQQ) is mostly pass/fail. It checks you’re financially sound, properly insured, not in breach of anything, and have relevant experience. You don’t win on the SQ; you only lose on it, by getting a detail wrong or missing evidence.
- Keep a bid library. Insurances, accounts, health-and-safety policy, environmental policy, quality accreditations, equality policy, three relevant case studies — all current, all in one folder. Half the SQ is retrieval, not writing.
- Mind the financial thresholds. Buyers often set a minimum turnover (commonly no more than twice the contract value). If you don’t meet it, that’s a fail before you’ve written a sentence — so check it first and don’t waste an evening.
- Match case studies to the work. Three closely relevant projects beat ten impressive but unrelated ones.
Read the weighting before you write a word
Every compliant tender publishes how it will be scored — typically a price/quality split (say 60/40, or 70/30) and a breakdown of the quality marks across questions. Read this first. It tells you exactly where the marks are and therefore where to spend your effort.
If “social value” is worth 10% and “programme and methodology” is worth 25%, you write proportionally. Spending your best two hours polishing the 5% question while the 25% question gets a rushed paragraph is the single most common self-inflicted wound in bidding.
Answer the question they actually asked
Public sector questions are often laboriously specific, and they frequently contain the marking scheme inside the question. If a question says “describe your approach to managing the programme, including how you will manage subcontractors, mitigate delay, and report progress to the client,” then those three “including” items are your sub-headings. Answer each, in order, and you’ve made the evaluator’s job effortless.
A good habit: copy the question into your answer as headings, write underneath each part, then delete the headings at the end if format rules require it. You will never miss a sub-part this way.
Evidence beats adjectives
“We are highly experienced and committed to quality” scores nothing — it’s an assertion any firm could make. “On the Maple Street scheme we completed 14 social housing voids in 11 weeks against a 13-week programme, with a 98% first-time-fix rate verified by the client’s clerk of works” scores, because it’s specific, measurable and checkable.
Build every quality answer on the spine of: what we do → how we do it → proof we’ve done it → the outcome for the client. Numbers, named schemes, dates and third-party verification are what turn a “satisfactory” score into a “good” or “excellent.”
Writing a method statement that scores
The methodology or technical answer is usually the biggest single chunk of quality marks. Structure it the way the job runs:
- Mobilisation: how you start cleanly — site set-up, surveys, permits, who’s on site day one.
- Sequence and programme: the build logic, key milestones, and how you protect the critical path.
- Risk: the two or three things most likely to go wrong on this job, and your specific mitigation — not a generic risk register.
- Quality and handover:inspections, sign-offs, snagging, O&M information, aftercare.
Tailor it to the actual site. An evaluator can spot a recycled generic method statement instantly, and it caps your score — because it doesn’t demonstrate you’ve understood their project.
A pre-submission checklist
- Every question answered, every sub-part addressed.
- Word and page limits respected (over-length answers can be struck out).
- Claims backed by named evidence and numbers.
- All requested attachments uploaded, correctly named.
- Pricing document complete, arithmetic checked twice.
- Submitted with hours to spare — portals fail at deadline.
The honest summary
Winning public sector work is a writing discipline as much as a building one. Read the weighting, answer the exact question, evidence every claim, tailor the method to the site, and submit early. Do that consistently and your win rate climbs without you laying a single brick differently. The hard part is finding the right tenders early enough to bid them well — which is where watching the pipeline daily, rather than scrambling when something lands, makes the difference.
Stop reading. Start winning.
House of Planning Service puts every UK planning lead, government tender and framework opportunity in your inbox before your competitors hear about them. From £49/month, cancel any time.