The tender process: how it works from the supplier's side
Ten stages, and the outcome is mostly settled before anyone writes an answer. A map from the supplier's chair: who owns each stage, what goes wrong at it, and what to have ready before it starts.
Founder's Associate
On this page
The tender process is the sequence a buying organisation runs to award a contract, from advertising the opportunity to signing it. For the supplier responding, it has ten stages, and the ones that decide the outcome happen before writing starts.
Plenty of suppliers meet that process in the middle. A portal notification lands, it takes a few days to reach anyone who can judge it, and the bid team reads the specification properly for the first time with a meaningful part of the window already gone. That is not a discipline problem, it is what happens when a process designed around the buyer's timetable meets a supplier who joined it at stage three.
What are the stages of the tender process?
Ten stages, running from the moment an opportunity becomes visible to the award notice and the standstill that follows it. The tendering process is the buyer's to run. You run a parallel one against it, and the table below is that parallel process: what the buyer is doing at each of the tender process steps, who on your side owns the response to it, what usually breaks, and what needs to exist before the stage opens rather than during it.
| Stage | What happens | Who owns it, supplier side | What typically goes wrong | Have ready before it starts |
|---|---|---|---|---|
| 1. Opportunity identification | The buyer advertises, or the opportunity surfaces through a framework, a portal alert or an existing relationship | Business development, with bid support | The notice is seen late, so every decision after it is made under time pressure | Portal and Find a Tender alerts mapped to what you can actually deliver, not to every keyword |
| 2. Qualification, bid or no bid | You decide whether to respond, on capability, commercial fit and realistic win probability | Bid manager, with sales and delivery leadership | The decision defaults to yes, because declining feels like conceding revenue | A scoring framework agreed before the opportunity arrives, not argued over during it |
| 3. Tender notice and documents released | The tender notice goes out and the full pack follows: specification, pricing schedule, contract terms, response template and evaluation criteria | Bid manager | Effort is allocated before anyone has read the evaluation weightings, so the highest-scoring questions get the same attention as the lowest | A requirements matrix built from the documents in the first days, not the second week |
| 4. Eligibility and conditions of participation | The buyer tests whether you meet the conditions of participation: legal and financial capacity, or technical ability, evidenced by accreditations and references | Bid manager, with finance and compliance | An expired certificate or a missing policy removes a bid that would have scored well on merit | Current certificates, insurance schedules, accounts and reference consents, maintained continuously rather than assembled per bid |
| 5. Clarification window | You submit questions and the buyer publishes answers to every bidder | Bid manager, drawing on subject matter experts and legal | Questions are asked too late for the answer to arrive in time, or an ambiguity is resolved by guesswork instead | A full read-through completed early enough that the answer still changes what you write |
| 6. Response build | Answers are drafted, evidence attached, pricing modelled, method statements written | Bid writers, subject matter experts, pricing, legal | Expert input arrives late and in a form nobody can use, and the overrun is absorbed by review | Approved, current source content, and a named owner against every question |
| 7. Internal review and sign-off | Solution, commercial and legal review, then formal approval to submit | Bid manager, with the governance stakeholders | Review is compressed into a proofread because drafting ran over | Governance dates booked backwards from the deadline at kick-off, with the reviewers told then |
| 8. Submission | The response is uploaded to the portal in the specified format, within the stated deadline | Bid manager | An upload fails, a file type is rejected, or a mandatory field is discovered an hour before close | A dry run of the upload, and an internal deadline that sits well ahead of the real one |
| 9. Evaluation and award | The buyer scores the responses, may hold clarifications, presentations or site visits, then notifies the outcome | Bid manager holds the relationship | Post-tender clarifications answered inconsistently with the bid, an abnormally low tender enquiry mishandled, or a separately scored presentation treated as a formality | A named contact who can respond inside the buyer's window, and the bid team's reasoning still accessible |
| 10. Award notice and standstill | Your assessment summary arrives, the contract award notice is published, and a standstill period runs before signature | Bid manager, with business development | The summary is read once for the result rather than the scores, and the standstill passes before anyone decides whether to act on it | Somewhere to file scores and reasoning that the next bid on that buyer will actually look at |
What happens at each stage, and who owns it
1. Opportunity identification
The opportunity becomes visible: a notice on a portal, an alert from Find a Tender, a framework call-off, or a buyer you already work with telling you something is coming. The stage is short and it is the easiest one to lose by default, because an alert set to every keyword that vaguely fits produces a feed nobody reads by week three.
2. Qualification, bid or no bid
You decide whether to respond. This is the highest-leverage decision in the whole process and the one least often written down, because the pressure to say yes arrives before the evidence to say no does. Spreading the same capacity across more bids lowers the score on all of them, which is the argument for holding the line on a scoring framework. The mechanics are set out in go versus no go, and the call itself is a bid/no-bid decision.
3. Tender notice and documents released
The tender notice goes out and the pack follows: specification, pricing schedule, contract terms, the response template, and the evaluation criteria with their weightings. Read the weightings before allocating anyone. A question worth 20 per cent of the technical score and a question worth 2 per cent take the same effort to answer badly, and a bid plan built before anyone opened the criteria will have spread effort evenly across both.
4. Eligibility and conditions of participation
Separately from scoring your answers, the buyer checks whether you clear the bar to be considered. Under the Procurement Act 2023 these are conditions of participation, and an authority may set them only where 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, checked September 2026). Two limits are worth knowing: an authority cannot demand audited annual accounts from a supplier that was never required to have its accounts audited, and it cannot require performance insurance to already be in place before award (source: legislation.gov.uk s.22(3), checked September 2026).
This is a different test from the exclusion grounds, which ask whether you may be awarded a public contract at all. Where the buyer runs a formal pre-qualification exercise it is the same evidence problem as a PQQ response. Nothing here rewards effort. It only punishes gaps.
5. Clarification window
You may ask the buyer questions, and the answers go to every bidder. Two failures live here. The first is not asking, and resolving an ambiguity by assumption in a document that will be marked against the buyer's reading of it. The second is asking on the last permitted day, when the answer lands after the section it affects has already been written and reviewed.
6. Response build
Drafting, evidence, pricing, method statements. This is the stage people mean when they say how long the tender took, and it is rarely the stage that lost it. What makes it painful is that it runs across legal, security, finance and delivery simultaneously, each of whom has a day job, and the response is only as current as the source content it was assembled from. Where the same source content feeds tenders, RFPs and questionnaires, manage it as one problem, not three, which is what RFx management names.
7. Internal review and sign-off
Solution review, commercial review, legal review, then approval to submit. Governance stages are legitimate and they take real time, so they need dates booked backwards from the deadline at kick-off. When drafting overruns, review is what gets compressed, and a compressed review is a proofread wearing a review's name.
8. Submission
Upload to the portal, in the format specified, before the stated time. Portals reject file types, cap upload sizes, time out, and close on their own clock rather than yours. Upload a complete draft days early and replace it as answers firm up. That proves the format and size limits against your real files rather than a placeholder, and it leaves something submittable in the system if the last day goes wrong.
9. Evaluation and award
The buyer scores against the published criteria and may hold clarification questions, presentations or site visits before deciding. Bids are lost here: a post-tender clarification answered inconsistently with the submission, an abnormally low tender enquiry handled defensively, a separately scored presentation prepared as a formality. Your side of this stage is availability and consistency, which means someone who can answer quickly and a record of why the bid team answered as it did, still accessible weeks after the team moved on.
10. Award notice and standstill
Where the contract was awarded through a competitive tendering procedure under the Procurement Act 2023, the debrief letter has been replaced by the assessment summary and it arrives without being asked for. Every supplier that submitted an assessed tender gets one, the winner included, and it must be issued before the contract award notice is published (source: legislation.gov.uk s.50, checked September 2026). It does not arrive on a framework call-off, a dynamic market award or a direct award, which are the same routes that fall outside the mandatory standstill, and it does not arrive if your tender was disqualified rather than assessed. On those routes, and on anything still running under the Public Contracts Regulations 2015, feedback is something you request rather than something you receive, so ask in writing as soon as the outcome is announced. Read it for the scores and the authority's stated reasons rather than the result, because that is the evidence base you would be arguing from if you questioned the award. Then file it where the next bid team on that buyer will find it, which is not an individual's inbox.
What changes under the Procurement Act 2023
Three things change for a supplier: the notices arrive in a published sequence you can plan against, the debrief letter becomes an assessment summary that arrives automatically, and the standstill before signature is fixed at eight working days. The shape of the process is the same. The timing is not optional. Check which regime you are in before relying on any date below. The Procurement Act 2023 covers England, Wales and Northern Ireland, and applies to procurements started on or after 24 February 2025 (source: gov.uk, checked September 2026). Procurements begun before that date, and call-offs from frameworks awarded under the old rules, still run under the Public Contracts Regulations 2015. Devolved Scottish procurement is outside the Act altogether and keeps its own regime.
The practical question for you is how many times you will be asked for something. An open procedure asks once: you submit a full tender in a single stage. A competitive flexible procedure can ask three or four times, because the authority designs its own route and may put negotiation, dialogue, presentations, site visits or initial outline bids in front of the final tender (source: gov.uk, checked September 2026). Those are the only two competitive tendering procedures under the Act, and the authority must run whichever it picks in accordance with a tender notice and its associated tender documents (source: legislation.gov.uk s.20, checked September 2026). Read the tender notice for which one you are in before you plan any resource.
What that gives a supplier is a published sequence of notices to track. Each one tells you where a procurement has reached, and the useful habit is reading them as a calendar rather than as paperwork.
| Notice | What it tells you | What to do about it |
|---|---|---|
| UK1 Pipeline notice | The buyer expects to procure this in future | Qualify early, while there is still time to build the relationship or the capability |
| UK2 Preliminary market engagement notice | The buyer intends to talk to the market before competing the work | Take part. It is the earliest point at which you can shape a specification, and the last one before the requirement is fixed |
| UK3 Planned procurement notice | A competitive procurement is coming. Where it is a qualifying notice, published at least 40 days and no more than 12 months before the tender notice (s.15(3)), the authority may cut the tendering period to as little as 10 days (source: legislation.gov.uk s.54(4), checked September 2026) | Get the eligibility evidence current now, because the window may be shorter than the standard one |
| UK4 Tender notice | The competition is open | This is stage three. The clock you actually work to starts here |
| UK5 Transparency notice | The buyer intends to award directly, without competing the work | If you could have delivered this and no exemption plainly applies, it is your only warning before signature. The standstill runs from the contract award notice that follows, and for most direct awards it is the mandatory eight working days |
| UK6 Contract award notice | The buyer has decided and the standstill period has begun. Your assessment summary will already have arrived | Read the summary now. If you want the signature stopped rather than just compensated, this is the window |
| UK7 Contract details notice | The contract has been signed, and the notice carries its dates | Work back from the end date rather than waiting for it, because the re-procurement is advertised well before the contract runs out. Check the contract for extension options, because the stated end date may exclude them |
Two dates matter more than the rest, and they are commonly confused. Before publishing the contract award notice, the authority must issue an assessment summary to every supplier that submitted an assessed tender, which is your scoring feedback arriving without being asked for (source: legislation.gov.uk s.50, checked September 2026). The mandatory standstill period is then eight working days beginning with the day the contract award notice is published, and the authority cannot enter into the contract during it (source: legislation.gov.uk s.51(2), checked September 2026).
Standstill is not the deadline for challenging. It is the deadline for stopping the signature. Proceedings must generally be brought 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), but only proceedings commenced during the standstill period, and notified to the authority, prevent it entering into the contract (source: legislation.gov.uk s.101, checked September 2026). Miss the standstill and a claim is still in time. It simply runs against a contract that has already been signed.
The mandatory period also does not apply everywhere, and the exceptions are the routes suppliers meet most often: 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. In those cases the authority may set a voluntary standstill in the contract award notice instead, and where it does it cannot enter into the contract before that period ends or set one shorter than eight working days (source: legislation.gov.uk s.51(4) and s.51(5), checked September 2026).
Why suppliers lose tenders before the writing starts
Not usually in the writing, which is where the effort goes. Four patterns recur, and three of them are settled before a single answer is drafted.
The first is lost at qualification. The bid was never winnable and the team spent the whole window finding that out. The cost is not the loss, it is the stronger opportunity that got a diluted response in the same window.
The second is lost on an administrative fact. An accreditation lapsed, a policy was out of date, an insurance level fell short, a reference had not consented. The response was good. It was not read. Eligibility evidence goes stale on its own schedule, which is never the tender's, so it belongs on a renewal calendar rather than a pre-bid checklist.
The third is lost in the clarification window. An ambiguous requirement was answered the way the supplier read it rather than the way the buyer meant it, and the evaluator marked against their own reading. The window existed. Nobody used it in time.
The fourth is lost in the compression at the end. Drafting overran, review became a proofread, and a sub-question went unanswered or a claim went out without the evidence behind it. Evaluators score what is on the page. An answer that is true but unevidenced scores like one that is neither. That is the argument for keeping approved answers and their evidence together rather than reassembling both under deadline, and for treating reference mapping as maintained data rather than a per-bid scramble.
The common thread is that all four are decided by what exists before the tender arrives. A bid is won on preparation and lost on coordination, and the coordination load is what scales badly as the number of tenders goes up. Teams running this at volume end up treating it as bid management rather than as a series of documents.
Where tender processes actually lose time
None of the ten stages is difficult in isolation. The difficulty is that they run across legal, security, finance and delivery at once, against a deadline nobody in your building set, and the time goes on the coordination rather than on the writing. That is the part SEQUESTO's agentic Operating System (aOS) is built for. James orchestrates the response from intake to submission, routing each question to the person who owns it. The Agent Force, the specialist agents that execute each step, drafts against approved content held in the Knowledge Hub and keeps a record of what was used, changed and approved. Bid managers keep strategy, tone and final approval. Where tenders are a standing part of the work rather than an occasional one, that coordination is what tender management and tender response automation are for.
Every response, handled. The final word, yours.
