LGSS Law All articles
Public Procurement

Reasoned and Recorded: Award Notices, Debriefs and the Standstill Discipline

LGSS Law
Reasoned and Recorded: Award Notices, Debriefs and the Standstill Discipline

The evaluation is closed, the moderation record is signed and the contract is drafted. In most authorities the sense of completion arrives well before the standstill period begins. That is precisely when the exposure is greatest: for a short, defined window, the authority hands its reasoning to the people with the strongest incentive to test it, and does so in writing.

The standstill period is sometimes treated as an administrative pause — a box to log before the seal goes on. It is better understood as the first disclosure event of the award. Everything published in that window will be read twice: once by an unsuccessful bidder deciding whether to accept the outcome, and once, potentially, by a court considering whether the decision was defensible. Under the Procurement Act 2023 regime, now into its second year of operation, the mechanics are settled enough that failures tend to be procedural and human rather than interpretive.

The notification is a legal instrument, not a covering letter

The notification of the award decision is the document that starts the clock. Where it goes, when it goes and what it contains all matter, and errors in any of the three can leave an authority believing it is in standstill when it is not.

The common failures are unremarkable and recurring. A notification sent only to the winning supplier, on the assumption that unsuccessful bidders have been told informally and will follow up. A notification that omits the assessment summary, or reproduces a mark sheet without any narrative explaining why the gap in scores mattered. A notification issued with the evaluation report still in draft, then quietly corrected a week later — leaving two versions of the reasoning in circulation and no clear answer to which one informed the decision. And the recurring assumption that an exemption applies, when the exemptions are narrow and technical and the consequence of getting them wrong is that the period relied upon never began.

The safest position is to treat the assessment summary as the authoritative statement of why the contract was awarded as it was. It should identify the successful supplier, the scores or evaluation against each criterion, the reasons the unsuccessful tender lost, and the characteristics and relative advantages of the winning offer. If the summary and the evaluation record cannot be reconciled without explanation, the summary is not ready to send.

Debriefs: the same reasons, at greater length

There is a persistent temptation to treat the formal debrief as a negotiation. An unsuccessful bidder asks a pointed question; the officer drafting the reply wants to be helpful, or wants the conversation closed, and adds a little colour. A new justification appears that was not in the evaluation record. It is offered in good faith and it is almost always a liability.

A debrief should be an expansion of the recorded reasoning, not an addition to it. The discipline is straightforward: every statement in a debrief should be traceable to a line in the evaluation record, the moderation notes or the assessment summary. Where the record is thin — and on the margins between closely scored bids it often is — the answer is not to reconstruct the reasoning months later in an email. It is to acknowledge what was assessed and on what basis, and to resist the invention of detail.

Two further points are worth building into the routine. First, consistency across recipients: bidders talk to one another, and differing explanations of the same decision are far more damaging than a single blunt one. Second, tone. A debrief that reads as dismissive, or that attributes the loss to matters outside the published criteria, converts a disappointed bidder into a motivated one.

The clock does not pause while you explain

The standstill period and the limitation period are different things, and conflating them is a familiar error. Standstill restrains the authority from entering into the contract; it does not suspend the time within which a supplier may bring proceedings, which runs from the point the supplier knew or ought to have known of the grounds. A late notification does not buy time — it shortens the authority's opportunity to correct its own position before a claim crystallises.

Where a challenge is issued before signature, the authority's ability to proceed is constrained in any event. The practical consequence is that the period between notification and signature should be used, not waited out. If the assessment summary reveals an inconsistency, the moment to address it is before the contract is entered into, not after.

A defensible routine

A short checklist, applied consistently, removes most of the avoidable risk:

Conclusion

Most procurement challenges are not built on a single catastrophic decision. They are built on a discrepancy between what an authority says, what it recorded and when it said it. The standstill period concentrates that risk into a fortnight. Handled as a controlled act of disclosure — one record, one voice, one timeline — it is also the cheapest opportunity an authority will get to identify its own weaknesses while it can still do something about them.

All Articles

Related Articles

The Modification Test: Keeping Contract Change Inside the Rules

The Modification Test: Keeping Contract Change Inside the Rules

Drift, Not Decision: Keeping the Teckal Exemption Honest as a Delivery Company Grows

Drift, Not Decision: Keeping the Teckal Exemption Honest as a Delivery Company Grows

The Enforceable Firewall: Contracting for Cyber Resilience in Public Services

The Enforceable Firewall: Contracting for Cyber Resilience in Public Services