UK public sector tender evaluations score against a published rubric, typically 70/30 or 60/40 quality-to-price. Winning bids follow the four-section structure (executive summary, method statement, case studies, pricing), use the buyer's terminology verbatim, quantify everything (numbers beat adjectives), and treat social value as a measurable commitment using TOMs rather than a generic CSR statement.
What buyers actually score
Public sector tender evaluation is a structured, transparent process. The Invitation to Tender (ITT) document tells you exactly what's being evaluated, the weighting of each criterion, and the scoring scale. Most contracts use a 70-30 or 60-40 split between quality and price. Quality is then broken down into specific scored sections — typically experience, methodology, social value, and sometimes innovation.
Each section has its own weighting and a scoring rubric: usually 0 (unacceptable) to 5 (exceptional) or 0 to 10. The rubric is published. To score 4 or 5, your response has to demonstrate specific qualities described in the rubric — not generic competence.
Read the scoring rubric before writing a single word. Most SMEs skip this step and write a generic capability statement that scores 2-3 across the board. Winning bids target specific scoring criteria explicitly.
The four-section structure that scores
1. Executive summary
Maximum one page. Three things only: what you're proposing in one sentence, the three biggest reasons you're the right supplier, and the headline outcomes the buyer will get. Skip the company history. Skip the philosophy. The evaluator may read only this page before deciding whether to engage with the rest.
Lead with the buyer's outcome, not your capability. "We will deliver fully compliant fire door installations across 240 properties on the LHC framework within the 24-month delivery window, with zero RIDDOR-reportable incidents and a 98% first-time fix rate" beats "We are a leading fire door installer with X years of experience."
2. Method statement
The longest section. For each phase of the work, describe what you'll do, who will do it, when, and how you'll evidence completion. This is where social value, risk management, and technical detail land. Structure it to map directly to the scoring criteria — if the rubric scores "Approach to mobilisation", "Approach to delivery", "Approach to handover", "Approach to social value", use those exact headings.
Each subsection should follow STAR — Situation, Task, Action, Result. State the context, what you propose to do, the specific action, and the measurable outcome. Evaluators score on evidence of past results, not future promises. If you've done something similar, say so, with the contract name, value, and outcome metrics.
3. Case studies and references
Three case studies. Each one chosen to demonstrate a different capability the buyer cares about. Don't pick your three biggest — pick the three most relevant. A £100K council maintenance contract is better evidence for a similar council contract than a £2M private-sector job.
For each case study: client name (with permission), contract value, dates, scope, your role, the outcomes achieved (measurable — completion rate, defect rate, customer satisfaction score, cost variance). Reference contact details for the buyer to call. The strongest case studies are reproducible — meaning you can describe doing the same thing again on this contract.
4. Pricing
Use the buyer's pricing template exactly. Don't add line items they didn't ask for. Don't combine items they wanted separated. Pricing comparability matters as much as headline price — if your bid is structured differently from the template, the evaluator has to do conversion work, which costs you in their evaluation.
Tactically: do not be the cheapest bid. The cheapest gets scrutinised. Aim mid-low on price with a strong quality submission. Public sector buyers are explicitly told to evaluate on most economically advantageous tender (MEAT), not lowest price.
The language that scores
Public sector evaluators read hundreds of responses. They reward specific, evidenced, measurable language. They penalise vague, generic, capability-statement language. The difference matters more than most SMEs realise.
Replace adjectives with numbers. "We deliver high-quality work" → "We achieved a 98% first-time fix rate across 2,400 council maintenance jobs in 2024." Specific beats descriptive every time.
Use the buyer's terminology. If the tender says "operational excellence", use "operational excellence" — not "best-in-class delivery". If they say "social value outcomes", don't paraphrase as "community benefits". Evaluators score by looking for the rubric's keywords in your text.
Quote published policies. Reference the buyer's own published documents — their strategy, their net zero targets, their procurement priorities. A response that explicitly aligns with the buyer's stated priorities scores higher than one that doesn't.
Social value: the section everyone gets wrong
Social value is now mandatorily weighted at 10% minimum in central government procurement and similar levels in most local authority and NHS procurement. Most SME responses lose points here by writing generic CSR statements.
What scores: specific, measurable, contract-linked commitments. "We will offer two apprenticeship placements during contract delivery, drawn from the local authority's NEET register" beats "We are committed to creating apprenticeship opportunities". Use the TOMs (Themes, Outcomes, Measures) framework if the buyer asks for it — that's the standard most local authorities now use.
Calculate the financial value of your commitments using the National TOMs Plus methodology or the buyer's own social value calculator. A commitment with a £ value attached scores higher than one without, because evaluators can compare it on the same basis as other bids.
Common mistakes that lose otherwise winning bids
Late submission. Submit at least 6 hours before deadline. Portal uploads fail, files corrupt, networks go down. Last-minute submissions fail more than any other category combined.
Word count overruns. If a section is capped at 1,000 words, evaluators stop reading at 1,000. Anything after isn't scored. Counts are enforced strictly.
Missing mandatory documents. Insurance certificates, ISO certificates, signed declarations. Check the appendices list and tick each one off twice before submission.
Wrong file format. PDF when they asked for Word, or vice versa. Buyers sometimes reject on format alone. Read the submission instructions.
How ENKII helps with tender response writing
ENKII Easy Apply structures your response against the specific tender's evaluation criteria. Your founder profile pre-fills the supplier information sections. The AI assistant supports the longest sections — method statement and social value — with scoring-criteria-aware suggestions.
The readiness score per tender tells you whether to bid in the first place. There's no point writing a great response to a contract you can't win on baseline requirements. ENKII filters out unwinnable tenders so your bidding effort lands on the right opportunities.
Frequently asked questions
How long should a tender response be?
As long as the page or word count allows — and no longer. Most public sector ITTs cap each section explicitly. Use all of it where the section's important; don't pad if you've genuinely answered. A short response that hits every scoring criterion concretely beats a long one that hits them vaguely.
Should I include diagrams and graphics?
Sparingly. A method statement diagram that genuinely clarifies workflow earns points. Decorative graphics that fill space don't. PDFs render unpredictably across portals — check the buyer's submission rules and don't rely on visual formatting that may not survive upload.
Can I reuse a tender response from a similar contract?
The structural sections (capability, references, policies) reuse cleanly with light edits. The method statement and social value sections need genuine rework — each contract is different and evaluators spot recycled language quickly. Easy Apply takes your previous responses, lets you select which sections to carry forward, and prompts you for the bits that need updating.
What's the difference between PQQ and a tender response?
PQQ (pre-qualification) tests whether you meet minimum standards to bid at all. Tender response (ITT) is your actual bid — what you'll deliver, how, with what evidence, at what price. Pass PQQ and your ITT gets evaluated; fail PQQ and your ITT never gets read.