Tender Standstill Periods: What to Do After a Public Sector Bid Result in 2026

A tender result is not the end of the bid process.

For public sector suppliers, the days after an award decision are now one of the most important parts of the whole cycle. Under the Procurement Act 2023 regime, unsuccessful bidders receive an Assessment Summary rather than the old style standstill letter. The standstill period is generally shorter than many teams were used to under the previous rules. The amount of feedback can be more useful, but only if the bid team knows how to read it quickly.

That creates a practical problem. Most bid teams are exhausted by the time the result arrives. The submission has been filed, the team has moved on to the next deadline, and the award email lands when nobody has capacity to take it apart properly. If the result is a loss, the first reaction is usually frustration. If the margin is close, it can turn into panic.

Neither reaction helps.

The best suppliers treat the award decision as a short, structured review window. They work out what the buyer has told them, what the scores actually mean, whether anything looks inconsistent, what clarification is worth requesting, and what lessons should be captured before the next tender starts.

This guide is written for bid managers, sales directors, commercial leads and operational teams who need a practical process after a public sector tender result. It is not legal advice. Procurement rules, exceptions and deadlines depend on the tender, the authority, the contract type and the jurisdiction. Do not use a blog post to calculate a legal deadline. If you think there has been a material breach, you should speak to a procurement lawyer quickly. But most suppliers do not need to start with litigation. They need to start with disciplined review.

Bid team reviewing a public sector contract award notice and assessment summary

Why the post-result window matters more in 2026

The public procurement landscape has become more transparent, but also less forgiving of slow internal decision-making.

Under the Procurement Act 2023, buyers are expected to give suppliers clearer information about how their tenders were assessed. Assessment Summaries should help bidders understand their scores, the evaluation criteria, the scoring approach and, for unsuccessful suppliers, information about the winning bid. At the same time, the standstill clock gives suppliers a compressed period to review the result before the contract can be entered into.

That combination changes the rhythm for bid teams.

In the old world, many suppliers treated feedback as an administrative afterthought. They might request a debrief, complain informally, update a lessons learned spreadsheet, or simply move on. In the new environment, the award decision is a source of competitive intelligence. It tells you how the buyer interpreted your answer, where your evidence was weak, whether your pricing was commercially credible, and how your proposition compared with the supplier that won.

The value is not only in deciding whether to challenge a result. That will be rare, and it needs specialist advice. The everyday value is in improving the next bid.

A good post-result review can show that your social value answer was too generic, your mobilisation plan lacked named ownership, your quality assurance section did not evidence live contract performance, or your pricing narrative failed to explain why your cost base was realistic. That is information you can use.

A poor review does the opposite. It leaves the organisation with vague conclusions such as price was too high, buyer preferred the incumbent, or we need stronger case studies. Those may be partly true, but they are not specific enough to change behaviour.

The standstill period forces urgency. The Assessment Summary gives you material. Your job is to turn both into a controlled process.

Assessment Summary versus standstill letter

The first thing to understand is the document itself.

Under the current rules, the Assessment Summary has replaced the familiar standstill letter for covered procurements. It is not simply a polite notification that someone else won. It is meant to explain how the tender was assessed against the published award criteria.

For an unsuccessful bidder, a useful Assessment Summary should normally help you identify:

the award criteria and relative weightings used by the buyer
the scoring methodology or scoring descriptors applied
your scores against the relevant criteria
narrative feedback explaining those scores
the successful supplier's scores and the reasons for those scores, where required
the relationship between your written response and the evaluator's comments

It is sent privately to bidders who submitted assessed tenders. It is not the same as the public Contract Award Notice. That distinction matters because the standstill period is generally triggered by publication of the Contract Award Notice, not simply by the moment someone in your inbox receives the Assessment Summary.

For bid teams, the practical point is simple: do not let the documents sit in an inbox.

The Assessment Summary should be saved immediately, circulated to the right internal people, and reviewed against the tender documents. The Contract Award Notice publication date should be recorded so the team understands the likely standstill timetable. If anything is unclear, the team should know who owns the buyer query, who owns the internal scoring review, and who decides whether external advice is needed.

This sounds basic. It is where many suppliers go wrong.

A bid manager opens the email. Sales forwards it to the account director. Operations only sees it three days later. Finance never checks the price comments. The managing director asks whether the decision can be challenged, but nobody has mapped the scores to the original criteria. By the time the organisation has a view, the useful window has narrowed.

The fix is not complicated. Create a standard post-result workflow before you need it.

Tender feedback review with scoring notes and assessment summary evidence

What the standstill period is for

The standstill period is a pause between the award decision process and contract signature. Its purpose is to give suppliers time to understand the outcome and, where appropriate, raise issues before the contract is entered into.

For most covered public procurements, suppliers should work on the basis that the standstill period is short. Under the Procurement Act 2023 regime, the standard period is commonly described as eight working days. Weekends and bank holidays can affect the counting, and the exact timetable should always be checked against the notice and the procurement documents.

The key point is not the arithmetic. The key point is behaviour.

Eight working days disappears quickly. If your first serious review meeting is on day five, you have already lost most of the useful decision window. If you wait for every stakeholder to read the summary in their own time, the process will drift. If you treat clarification questions like a normal tender query with a relaxed turnaround, you may get an answer too late to matter.

That does not mean every loss is a crisis. It means every result needs triage.

The standstill period should help you answer four questions:

Do we understand why we lost?
Do the scores and comments appear consistent with the published criteria?
Is there anything material that needs urgent clarification?
What should we change before the next bid?

Only a small number of cases will move beyond those questions into formal advice about remedies or challenge. Most will become structured learning. That is still valuable. A bid team that learns quickly from every result compounds improvement over time.

The first 24 hours after the result

The first 24 hours should be administrative, calm and structured.

Do not start by writing an angry email to the buyer. Do not assume bias because the score feels unfair. Do not start rewriting history internally. And do not let the result sit with one person.

Start by collecting the facts.

Save the Assessment Summary, Contract Award Notice, tender documents, clarification log, final submission, pricing schedule, quality response, presentations, interview notes and any buyer messages. Put them in one controlled folder. If you use mytender.io, attach the result and feedback to the bid record so the team can compare it with the submission rather than hunting through email chains.

Then build a simple review sheet. It should include each evaluation criterion, the weighting, your score, the winning score if available, the evaluator's comments, the relevant section of your response, and an initial internal view.

Do not try to solve everything at once. The first pass is about orientation.

You are looking for obvious patterns:

did one criterion drive the loss, or was the gap spread across the bid?
was the difference mainly price, quality, social value, risk, mobilisation, service delivery or presentation?
did the buyer criticise missing evidence, weak detail, lack of local relevance, unrealistic claims or poor structure?
did the winning supplier outperform on a specific method, not just overall quality?
did any comment appear inconsistent with what you actually submitted?

This is also the point to identify internal owners. The bid manager should not carry the whole review alone. Operations should review delivery comments. Finance should review pricing and commercial assumptions. Compliance should review mandatory requirements. Sales should review incumbent and relationship factors. Senior leadership should only be pulled into escalation once the facts are organised.

A good first 24 hours ends with one page: what happened, what we know, what we do not know, what we need to ask, and who is deciding next steps.

How to read scoring feedback without fooling yourself

Tender feedback is easy to misread.

The most common mistake is to focus on comments that feel unfair and ignore comments that are commercially useful. Another is to treat every lost mark as something the buyer misunderstood. Sometimes buyers do misunderstand. More often, the bid made the evaluator work too hard.

Read the feedback in three layers.

First, look at compliance. Did the response answer the question, follow the page limit, include mandatory documents, match the format, and address every sub-criterion? Low scores often begin with a simple failure to cover the full question. A strong method statement can still lose marks if it ignores a stated requirement.

Second, look at evidence. Did you prove what you claimed? Evaluators are not impressed by unsupported statements such as our team is experienced, our mobilisation is robust, or our quality system is industry leading. They score evidence: named roles, relevant examples, performance data, risk controls, implementation timelines, governance forums, escalation routes, audit outputs and lessons learned.

Third, look at differentiation. Did the buyer see why your solution was more advantageous than the alternatives? Many good suppliers lose because their responses are competent but indistinct. They describe the service everyone expects. They do not show why their model reduces risk, improves outcomes, protects continuity, saves time or delivers better assurance.

The Assessment Summary should be read against these three layers. If the feedback says lack of detail, ask whether the answer was thin on process. If it says limited evidence, check whether the evidence was actually in the response or only known internally. If it says stronger response from the winning bidder, look for clues about what kind of strength: methodology, resourcing, innovation, social value, price confidence or contract management.

This is where bid teams need honesty.

If the buyer says your mobilisation plan did not explain how service continuity would be maintained, and your answer used two paragraphs of generic mobilisation language, the lesson is not buyer did not understand us. The lesson is your mobilisation library is too shallow.

When clarification is worth requesting

Suppliers can and should ask sensible clarification questions after a result, especially where the Assessment Summary is unclear or appears inconsistent.

The best clarification requests are specific, evidence-based and proportionate. They do not accuse. They do not rehearse the whole bid. They ask the buyer to explain a defined point so the supplier can understand the evaluation.

For example, a useful request might say:

the feedback states that no named mobilisation lead was provided, but section 3.2 of our response identified the mobilisation lead and escalation route. Please clarify whether this part of the response was considered.
the score for social value appears to refer to apprenticeships only, but the published sub-criteria also covered local employment and supply chain opportunities. Please explain how those elements were assessed.
the Assessment Summary says the winning bidder provided stronger evidence of contract performance. Please clarify the type of evidence that distinguished the winning response so we can improve future submissions.

A weak request says:

we disagree with the score and want a full explanation.
please send all evaluator notes immediately.
our answer was clearly better than the winning bidder.

Tone matters. Buyers are more likely to respond constructively when the request is precise and professional. The goal is to understand the evaluation and preserve options, not to vent frustration.

There is also a timing point. If clarification is needed during standstill, it should be sent quickly. A question sent at the end of the period may not produce useful information in time. If the issue could be material, take advice early rather than waiting for perfect information.

The eight working day action plan

A simple action plan helps the organisation move quickly without creating chaos.

Day one should be about capture and triage. Save the documents, record dates, confirm the standstill timetable, set up the review sheet, and identify whether there are any obvious red flags.

Days two and three should be about criterion-level review. Compare every score and comment against the published evaluation criteria and your submitted response. Mark each issue as accepted lesson, clarification needed, possible inconsistency, or commercial insight.

Days three and four should be about internal review. Bring together bid, sales, operations, finance and subject experts. Keep the meeting disciplined. The agenda should follow the scoring criteria, not people's feelings about the buyer.

Days four and five should be about buyer questions, if needed. Send targeted clarification requests. Do not overload the buyer with speculative questions. Focus on points that materially affect understanding of the score.

Days five and six should be about decision-making. Decide whether the result is understood, whether more information is needed, whether external legal advice is required, and what lessons should be added to the bid library.

Days seven and eight should be about closing the loop. Confirm any outstanding actions, update the opportunity record, brief leadership, and schedule the fuller lessons learned session after emotions have cooled.

This timeline is not a legal timetable. It is an operational rhythm for bid teams. The exact steps will depend on the procurement, the buyer and the information received. But having a rhythm prevents drift.

Eight working day tender standstill action plan for bid teams

Red flags that deserve faster escalation

Most tender losses are disappointing but ordinary. Some need faster attention.

Red flags can include:

scoring comments that appear to ignore a major part of your submitted answer
feedback that refers to a weakness not linked to the published criteria
evidence that different bidders may have been assessed against different expectations
mathematical errors in weighted scores or totals
comments suggesting the buyer relied on unstated requirements
a failure to explain key parts of the winning score where disclosure is expected
major inconsistencies between the buyer's clarification answers during the tender and the evaluation comments after award
signs that a mandatory requirement was treated flexibly for one bidder but strictly for another

None of these automatically means the award is wrong. They do mean the team should stop treating the review as ordinary lessons learned and get the right internal and external advice.

The biggest practical mistake is waiting too long because nobody wants to overreact. If an issue looks potentially material, escalate it quickly and calmly. You can always decide not to pursue it. You cannot recover time once the standstill window has passed.

At the same time, do not confuse disappointment with a red flag. A lower score than expected is not itself evidence of an error. A buyer preferring another method is not automatically unfair. A strong incumbent win is not automatically suspicious. The question is whether the evaluation appears to have followed the published criteria and whether the feedback supports the scores.

What to include in a post-result evidence pack

Even where there is no challenge, a good evidence pack protects learning.

The pack should contain:

the Contract Award Notice or award communication
the Assessment Summary
the tender notice and procurement documents
the award criteria and scoring descriptors
the submitted quality response
pricing and commercial schedules
clarification questions and buyer responses
presentation or interview materials, if used
internal approval notes and solution assumptions
review sheet mapping feedback to criteria
agreed lessons and owners

This pack has two purposes.

The first is immediate. It helps the organisation understand whether the result makes sense and whether any clarification is needed.

The second is long-term. It becomes evidence for future improvement. If the same weakness appears across three losses, you have a bid library problem, not a one-off scoring issue. If buyers repeatedly mark down mobilisation, you need a better mobilisation model. If social value scores vary wildly, you may need more localised and measurable commitments. If technical teams keep providing evidence too late, you need a better capture process before tenders are live.

mytender.io is built around this kind of structured bid intelligence. When submission content, evidence, feedback and lessons sit in one place, bid teams can stop learning the same lesson repeatedly. AI can help draft faster, but the real performance gain comes when the system can draw on accurate previous answers, evaluator feedback and live evidence rather than generic boilerplate.

Procurement standstill evidence pack with feedback, criteria and bid documents

Turning feedback into better future answers

The most commercially valuable part of the process happens after the standstill panic has passed.

A proper lessons learned review should not be a blame session. It should be a content and process improvement session. The goal is to update the way the organisation bids.

Start by separating issues into four categories.

The first category is content gaps. These are weaknesses in reusable bid material: missing evidence, thin method statements, outdated case studies, weak social value commitments, generic risk registers or unsupported claims.

The second category is process gaps. These are failures in how the bid was produced: late operational input, poor answer ownership, rushed reviews, unclear pricing assumptions, weak document control or insufficient red team challenge.

The third category is strategy gaps. These are decisions about whether the opportunity was right in the first place: weak buyer relationship, poor fit, low margin, incumbent advantage, lack of local presence or overconfidence in a sector where evidence was thin.

The fourth category is buyer intelligence. These are insights about what the market is rewarding: stronger contract management evidence, more specific mobilisation plans, measurable social value, better reporting, sharper pricing narrative or more convincing risk controls.

Each category needs a different response.

A content gap should update the bid library. A process gap should change the bid workflow. A strategy gap should feed the bid or no-bid decision. Buyer intelligence should shape future win themes.

This is where many organisations waste feedback. They write a lessons learned note, save it somewhere, and then start the next tender from the same old template. That is the bid equivalent of touching a hot pan twice.

If an Assessment Summary says your answer lacked evidence, attach the missing evidence to the relevant library answer. If it says your mobilisation response was less detailed than the winner's, rewrite the mobilisation section before the next deadline. If it says your price was not clearly explained, develop a standard value-for-money narrative that connects cost to delivery risk, resilience and outcomes.

Feedback only matters if it changes the next bid.

Pricing feedback needs special care

Price is often the easiest explanation for a loss, and sometimes it is the correct one. But suppliers should be careful not to over-simplify pricing feedback.

A tender can lose on price because the number was too high. It can also lose because the commercial model looked risky, the assumptions were unclear, the mobilisation cost was not explained, the resourcing model did not match the quality response, or the buyer did not understand the value behind the price.

If the feedback mentions price, ask three questions.

First, was the price genuinely uncompetitive against the market? If so, the lesson may sit in cost model, margin expectations, supply chain pricing or bid selection.

Second, was the price aligned with the solution? If the quality answer promised senior oversight, enhanced reporting, proactive compliance and rapid mobilisation, but the price model did not visibly support that level of service, the buyer may have doubted deliverability.

Third, did the pricing narrative explain value? Under Most Advantageous Tender thinking, buyers are not simply looking for cheap. They are looking for an offer that delivers the best overall outcome against the criteria. A higher price can still be competitive if the evidence shows lower delivery risk, better continuity, stronger performance control or measurable benefits.

The lesson may not be lower the price. It may be explain the price better.

How AI should help after a tender loss

AI is useful after a tender result, but only if it is grounded in the actual documents.

A generic AI tool can summarise feedback, but it does not know your bid history, your evidence library, your previous scores or your sector-specific win themes. That creates a risk of shallow conclusions.

A tender-specific platform should do more. It should help the bid team compare evaluator feedback with the submitted answer, identify recurring weaknesses, suggest library updates, surface relevant evidence for future bids, and track improvements across opportunities.

For example, if a facilities management supplier repeatedly loses marks on contract management, the platform should help identify which answers need stronger KPI governance, reporting examples, meeting structures and escalation pathways. If a construction supplier is marked down on mobilisation, it should help build a better mobilisation evidence pack using previous programmes, named roles, risk logs and handover templates.

The aim is not to automate judgement. The aim is to make judgement better informed.

mytender.io helps bid teams generate first drafts in minutes, manage knowledge, check compliance and collaborate across bid contributors. Post-result feedback strengthens that loop. The more structured your feedback data becomes, the more useful your future bid drafting becomes.

Common mistakes after an unsuccessful tender

There are seven mistakes we see again and again.

The first is moving on too quickly. The team is busy, the next deadline is live, and the loss is emotionally awkward. So the feedback is filed away and never used.

The second is obsessing over the buyer's wording without checking the submitted answer. Sometimes the answer really did miss the point. The review should be honest enough to admit that.

The third is treating price as the whole story. Even when price matters, quality feedback often contains clues about how to make the offer more credible next time.

The fourth is asking vague questions. Buyers cannot respond meaningfully to broad disagreement. Focused clarification gets better results.

The fifth is leaving legal escalation too late where a serious issue may exist. If there is a potentially material concern, get advice early. Do not wait until the organisation has perfect internal consensus.

The sixth is failing to update reusable content. Feedback should change templates, evidence packs, case studies and answer structures.

The seventh is not tracking patterns. One weak score may be a one-off. The same weak score across multiple tenders is a system problem.

Fix those seven behaviours and the post-result process becomes a competitive advantage.

A practical template for your review meeting

Keep the review meeting short and structured. Ninety minutes is usually enough for the first serious session.

Use this agenda:

Outcome summary: contract, buyer, winner, score gap, price position and key dates.
Criteria review: walk through each scoring criterion and the Assessment Summary comments.
Evidence check: compare feedback with the submitted response and identify missing proof.
Clarification points: agree any buyer questions and who will send them.
Escalation decision: decide whether anything needs external advice.
Lessons learned: capture content, process, strategy and buyer intelligence actions.
Library updates: assign owners and deadlines for improving reusable material.

Do not let the meeting become a general debate about whether the buyer was right. The discipline is to tie every comment back to the criteria, the submitted answer and the evidence.

The most useful output is not a long report. It is a short action list that changes the next bid.

Sector examples

In facilities management, standstill feedback often highlights mobilisation, service continuity, helpdesk reporting, PPM planning, TUPE handling, subcontractor control and social value delivery. A strong review should turn those comments into better mobilisation plans, clearer governance diagrams and stronger contract performance evidence.

In construction, feedback often centres on programme realism, site logistics, health and safety evidence, supply chain management, design coordination, carbon reduction and project experience. A good lessons learned process updates project case studies and evidence matrices, not just the written method statement.

In healthcare and care services, feedback may focus on safeguarding, workforce resilience, continuity, quality assurance, CQC-related evidence, clinical governance and mobilisation risk. The review should involve operational leads, not only the bid team.

In IT and professional services, buyers may focus on implementation approach, data security, user adoption, service management, governance, innovation and value for money. A useful review should connect scoring comments with delivery methodology and proof from previous implementations.

In waste and environmental services, common themes include mobilisation, route planning, fleet resilience, contamination reduction, resident communications, carbon reporting and performance monitoring. Feedback should improve both technical evidence and local authority-specific answer structures.

The pattern is the same across sectors: the Assessment Summary is only useful if the right subject experts read it and update the evidence base.

Build the workflow before the result arrives

The smartest bid teams do not wait for a loss to invent a process.

Before the next major submission, agree the post-result workflow. Decide where feedback will be stored, who will review it, how quickly the first meeting will happen, what review template will be used, who can send clarification questions, and when external advice may be needed.

Add the workflow to your bid management process. It should sit alongside qualification, capture, answer planning, review, submission and contract handover. Tendering does not end at upload. It ends when the result has been understood and the learning has been absorbed.

This also changes team culture. A loss becomes less personal when the organisation has a standard review process. People are more willing to be honest when the meeting is about improving the system, not finding someone to blame.

That matters because tendering is a compound game. The supplier that improves five percent after every loss will eventually outperform the supplier that treats each result as isolated bad luck.

Bid team turning tender feedback into reusable bid library improvements

Final thoughts

The standstill period is short, but its value is large.

It gives suppliers a defined moment to understand the result, check the evaluation, ask sensible questions and capture learning while the evidence is fresh. The Assessment Summary gives more structure than many old debriefs did, but it only helps if bid teams have the discipline to use it.

The best response to a tender loss is not anger and it is not resignation. It is controlled curiosity.

What did the buyer value? Where did our evidence fall short? Did we answer the real question? Did our price tell the right story? Was there anything materially inconsistent? What must change before the next bid?

If you can answer those questions quickly, you turn every tender result into useful intelligence. If you cannot, you will keep losing marks for reasons you should already have fixed.

mytender.io helps bid teams bring that intelligence into the bid process: capturing feedback, organising evidence, drafting stronger first responses, checking compliance and improving the bid library over time. The result is not just faster tender writing. It is a bid function that learns.

And in public sector tendering, the teams that learn fastest usually win more.

Tender Standstill Periods: What to Do After a Public Sector Bid Result in 2026