How to Write a Winning Government Tender in 2026: the Process, With Numbers From 4,000 UK Notices

Most guides to winning government tenders are written from the outside. This one is written from the inside of the documents: 4,126 UK notices published in the last 90 days, and 145 full tender packs read requirement by requirement. The numbers below come from that index, updated 30 August 2026. The process is the one bid teams that win actually follow.

What the notices say before you write a word

Three facts from the last 90 days of UK public notices set the shape of every bid:

• You get about a month. The median gap between publication and deadline is 29 days. A quarter of notices close within 25 days, and 392 of the 4,126 closed within 14 days of appearing.
• The middle of the market is where SMEs win. Of the 3,201 notices that stated a value, the median was £370,000. 851 were under £100,000, where the paperwork is lighter and incumbents are weaker; 1,018 were over £1 million, where financial standing checks bite.
• A pack is long. Across 145 tender packs we read in full, the median pack carried 102 distinct requirements, and 20 of them were high-severity: pass-or-fail gates, mandatory standards, hard deadlines, insurance floors. 27% of everything in a pack can end the bid on its own.

Step 1: Find the right opportunities, then filter hard

Set up alerts on Find a Tender (the central platform since the Procurement Act 2023 took effect on 24 February 2025) and Contracts Finder for your sector keywords, and add the regional portals your buyers actually use: ProContract for many English councils, Public Contracts Scotland, Sell2Wales, eTendersNI. Then filter by value against your own turnover. A common financial standing test is turnover of at least twice the annual contract value; bidding for a £5 million contract on £500,000 turnover fails that test before anyone reads your method statement.

Step 2: Make the bid or no-bid decision on the gates, not the prize

In the UK packs we analysed, the high-severity requirements split like this: compliance gates (289 rows), legal terms (152), quality thresholds (138), delivery obligations (138), commercial terms (63) and financial standing (63). The pattern is stable: the things that disqualify are mostly compliance and legal, not price. So the first question is not "can we win" but "is there any single line we cannot meet". Insurance floors are the classic example: a £10 million public and employers' liability requirement is a pass-or-fail box on a UK council play area tender we read this week, and no amount of quality writing recovers a fail there. Read our bid or no-bid framework for the scoring version of this.

Step 3: Extract every requirement before writing

Read the whole pack, including the annexes and the special conditions of contract, before you write anything. Every "shall", "must" and "required" is a row in your compliance matrix, and so is every evaluation criterion with its weighting. The special conditions table is where the binding commercial terms hide: retention percentages, liquidated damages, defects periods, governing law. In the packs we read, those short rows are the ones bid teams most often miss, because they look like boilerplate and read like a table of contents.

Two practical rules. Page-cite every requirement as you extract it, so the person answering it can check the source in seconds. And separate the gates from the scored criteria: gates get a yes with evidence, scored criteria get the writing effort in proportion to their weight. If methodology carries 40% of the score, it gets 40% of the pages.

Step 4: Write to score, not to impress

Evaluators score against a matrix, usually with a marking scheme published in the pack. They are looking for specific evidence against specific criteria. Lead with the answer, then the proof:

• Weak: "We have extensive experience in this sector and are committed to delivering excellence."
• Strong: "We delivered 14 comparable contracts in the last three years, 97% on time, with a 4.8 out of 5 client score. Three examples with contact details follow."

Use the buyer's exact headings and numbering. If they ask for "Methodology", do not title the section "Our Approach". Mirror their language, because the evaluator is reading with the marking scheme open beside your response.

Under the Procurement Act 2023, quality-only evaluations are more common than they used to be. The play area tender above scored quality at 100% with price handled as a hard budget ceiling of £100,000 excluding VAT. Read the evaluation section before deciding how much to invest in the price schedule.

Step 5: The final compliance check

Before submitting, verify every mandatory form is signed, every question is answered inside the word count, every certificate is attached, and you are submitting on the portal named in the pack, not by email, unless the pack says email. Late is late: the deadline row is high-severity in almost every pack we read, and the rejection is automatic. Submit the day before if you can; portals slow down in the last hour.

What this looks like as a timeline

With a median of 29 days from notice to deadline, a realistic plan for a 100-requirement pack is: day 1 to 2, gates and the bid or no-bid decision; day 3 to 5, full extraction and the compliance matrix; day 6 to 20, writing against the scored criteria; day 21 to 25, review against the matrix, pricing, forms; day 26, submit. The teams that lose most often are not the ones that write badly, they are the ones that start the extraction on day 15.