How to win tenders: why competent bids lose
Losing bids are rarely badly written. They are compliant, competent and unevidenced. Here is where the marks actually go, and the checklist that catches the failures before submission.
Founder's Associate
On this page
Knowing how to win tenders means knowing where they are lost. Bids fail in two populations: those disregarded before anyone reads them, and those that are read, are competent, and lose on evidence they never supplied.
Every bid lead has had the conversation that follows a loss on a bid the team expected to win. The team is certain the response was good, the reviewer agreed it was good, and the score says otherwise. Somewhere between those two positions is the thing worth finding, and it is almost never the prose. A bid that reads well to the people who wrote it is being marked by someone who has never met them, against a scheme they did not see written, using only what is inside the submission. That gap is where competent bids go to lose, and it is closeable.
What actually separates winning from competent?
Three things, and none of them is writing quality. Winning submissions are eliminated less often on the mechanics, they evidence claims the losing bid merely makes, and they come from teams that read their losses properly. Take those in order, because the first one costs the most and gets the least attention.
Most eliminations happen before anyone reads your answers
Under the Procurement Act 2023 a contracting authority must disregard any tender from a supplier that does not satisfy the conditions of participation (source: legislation.gov.uk s.19(3)(a), checked September 2026). Must, not may. That is a different order of risk from the discretionary grounds sitting next to it, where an authority may disregard a tender that breaches a procedural requirement set out in the tender notice or associated tender documents (source: legislation.gov.uk s.19(3)(d), checked September 2026). One is a decision the authority takes. The other is a decision the Act takes for it.
Conditions of participation are not paperwork. An authority may set them only if it is satisfied that they are a proportionate means of ensuring suppliers have the legal and financial capacity or the technical ability to perform the contract (source: legislation.gov.uk s.22(1), checked September 2026). They reach you with the tender notice and the associated tender documents, which may not go out unless the authority is satisfied they carry information sufficient for a supplier to prepare a tender (source: legislation.gov.uk s.21(5), checked September 2026). Every gate you can fail is visible on day one. A bid team that reads them on the day of submission has already lost the chance to do anything about the one it fails.
An unevidenced claim and a false one score the same
This is the uncomfortable one. An evaluator working from the submission alone cannot tell the difference between a capability you have and cannot demonstrate, and one you do not have. Both produce the same mark. Teams know this in the abstract and still submit claims that are true and unverifiable, then lose to a competitor who attached a contract name and a date to the same claim.
The evidence failures that decide contracts are boring and repetitive: a certification that expired between the last bid and this one, an accreditation held by a subcontractor rather than by the bidding entity, a case study whose numbers nobody can now source, a referee who was never told they were named. Reference mapping is the discipline that catches the last of those, and it is the one most often left to the day before. None of these is a writing problem, and none of them is caught by a proofread.
What to do in the eight working days after you lose
Losing well is a capability, and the Act gives you more to work with than most teams use. Where a contract is awarded under a competitive tendering procedure, an authority must provide an assessment summary to each supplier that submitted an assessed tender before it publishes the contract award notice (source: legislation.gov.uk s.50(3), checked September 2026). It carries information about the authority's assessment of your tender and, where different, of the most advantageous tender (source: legislation.gov.uk s.50(4), checked September 2026). That means the scores and the reasoning behind them, not the winning answers, and read as a pair the two assessments show you where the gap actually sat. There is a catch, and it lands on the suppliers described above. An assessed tender is one that was not disregarded in the assessment of tenders (source: legislation.gov.uk s.50(5), checked September 2026), so a bid put aside under s.19(3) receives no summary at all. Fail the gate and you lose the contract and the explanation.
Then the clock starts, and it is shorter than most teams assume. The mandatory standstill period is eight working days beginning with the day the contract award notice is published, and the authority may not enter into the contract before it ends, or before the end of any longer standstill period the contract award notice provides for (source: legislation.gov.uk s.51(1) and s.51(2), checked September 2026). Those eight days are the only window in which the award is still reversible.
What makes the window worth anything is the automatic suspension. An authority may not enter into the contract where, during the standstill period, proceedings are commenced and the authority is notified of that fact (source: legislation.gov.uk s.101(1), checked September 2026). Act inside the eight days and the contract stays unsigned while the claim is heard. Miss them and the contract completes, and what is left is a damages claim rather than the contract.
The 30-day limitation period is not a second run at the award. Proceedings must generally be commenced within 30 days beginning with the day you first knew, or ought to have known, of the circumstances giving rise to the claim (source: legislation.gov.uk s.106(2), checked September 2026), and a court may extend that for good reason but in any case not beyond three months from the day you knew or ought to have known (source: legislation.gov.uk s.106(3) and s.106(4), checked September 2026). Proceedings to set a contract aside run to a different rule again: the earlier of those 30 days or six months from the day the contract was entered into (source: legislation.gov.uk s.106(1), checked September 2026).
The mandatory standstill does not apply everywhere. Call-offs under a framework, awards by reference to a dynamic market, light touch contracts, direct awards for extreme and unavoidable urgency or to protect life, and direct awards by private utilities all sit outside it, though a voluntary standstill of at least eight working days may be offered instead (source: legislation.gov.uk s.51(3), s.51(4) and s.51(5), checked September 2026). Read the contract award notice rather than assuming you have the eight days.
Seven checks a proofread will not catch
This is the artefact worth keeping. It is not a proofreading pass and it is not the same job as the quality review, which reads for argument. This one is mechanical, it is done by somebody who did not write the answers, and every line of it is a way bids that deserved to win have been thrown out.
| Check | What good looks like | What it costs when it is missed |
|---|---|---|
| Every sub-question answered | Each clause of each question mapped to a paragraph, ticked off against the question text rather than against the answer | A zero on a sub-part you could have answered, invisible until the assessment summary arrives |
| Word limits respected | Every answer inside the stated limit, with the counting convention settled in the clarification window rather than assumed | A stated ground for disregarding the tender under s.19(3)(d) |
| Evidence current and named | Every certification, policy and accreditation in date on the submission deadline, expiry recorded, and any held by a subcontractor rather than the bidding entity flagged as such | A claim the evaluator cannot verify, or elimination where a mandatory certificate has lapsed |
| Claims supported | Each performance claim tied to a named contract, a figure and a date | The claim scores as an assertion, which is the gap between meeting the requirement and exceeding it |
| Mandatory attachments present | Every listed document present, in the specified format and file naming, final version, signed by someone with authority to bind, tracked changes and comments cleared | The commonest single cause of a technically non-compliant submission |
| Pricing consistent with the narrative | The resourcing in the method statement reconciles line by line with the price, and the schedule itself recalculates: totals sum, formulas fire, the VAT basis matches the one stated | A credibility mark against the method, or an abnormally low price enquiry you cannot answer |
| Portal requirements met | A complete draft pack uploaded two to three days out and files swapped as they finalise, because large packs upload slowly and portals lock to the second | A late or partial submission, which no amount of quality recovers |
Two disciplines make it work. The person running it did not write the answers, because a writer checking their own submission reads what they meant rather than what is there. And it runs against the clarification window, not after it: anything on this list that the tender documents leave ambiguous, from the word-count convention to what counts as acceptable evidence, is a question you can still ask, and the answer normally goes to every bidder. The supplier who asks shapes the ground everyone competes on.
Why compliant bids still lose
Run that checklist honestly and you will stop losing bids on the mechanics. You will still lose some, and the reason sits one layer up. Compliance proves you followed the instructions. It does not put a single piece of evidence in front of the evaluator.
The failure is not that content libraries lack version control. Most have review dates, owners and expiry fields, and the teams reading this configured them. The failure is that the review date lives in the library and the claim lives in the submission, and nothing carries the first across to the second. An answer gets retrieved, it is accurate, and it goes out with the contract name, the figure and the date stripped away, because whoever assembled it was working to a deadline and the source sat two clicks away in a system the evaluator will never open.
That is the problem SEQUESTO's agentic Operating System (aOS) is built for. Approved content lives in the Knowledge Hub with its source attached, so an answer arrives carrying the contract, the document, the date and the owner it came from, and those travel into the response instead of staying behind in the system. The Agent Force, the specialist agents that execute each step, works against that approved content and keeps a record of what was used, changed and approved. James orchestrates the response from intake to submission and routes each question to the person who owns it, so the certification question reaches whoever holds the certificate rather than whoever wrote about it last time.
The step that decides the score is approval, not assembly. Nothing is submitted unless a named human has approved it, and what they approved is recorded against the answer. The evaluator never sees that record and does not need to. What reaches them is a claim that arrives already cited, which is the whole distance between an assertion and a mark. For a team running tenders continuously rather than occasionally, that is the work bid management does, bid management automation is where it runs, and the piece on building an auditable content library covers the mechanics. Tender management is the same discipline applied across every open opportunity at once.
None of it rescues a bid you should not have entered. That decision belongs weeks earlier, at the go or no-go call, and the honest position is the uncomfortable one: a rushed response to a strong opportunity scores worse than a resourced response to fewer of them. The go versus no-go article takes that properly, and the full sequence from opportunity to standstill sits in the tender process guide. The craft of the answers themselves, question type by question type, is in the guide to how to write a tender bid.
Cited. Auditable.
