A post-cutoff clarification recovery decision is a dated record of what remains permitted after the applicable question deadline has passed. It proves the procedure, stage, lot, controlling cutoff and observation time; isolates the unresolved buyer-controlled fact; searches current documents, amendments and published answers; tests the authorized channel and any express treatment of late questions; and compares the bid consequences of each credible answer. Its result can be resolved from source, late request authorized, reversible work only, approved offer treatment, specialist review, no-bid review or source conflict. It does not create a right to an answer, extend the tender deadline or turn silence into agreement.
A county council is buying maintenance for 62 roadside weather stations used by winter-service teams. The invitation says clarification questions close at 12:00 on 2 October and tenders close at 12:00 on 15 October. On 3 October, the supplier notices that the service schedule requires a 30-minute response to a critical station failure, while the asset table lists stations across two districts more than 90 minutes apart. The documents do not say whether the response clock means remote acknowledgement, arrival at the station or restoration of the data feed. The portal still shows a working message button. Pricing has already assumed remote acknowledgement, but no buyer source supports that assumption.
Treat the missed cutoff as a change in available options, not as permission to guess. First prove that the relevant cutoff has passed for this procedure, stage and lot. Then reduce the problem to the smallest fact the buyer controls and search the complete current record. A working message button shows technical availability only. Permission comes from the procurement documents or an authorized procedural decision. If a late request is allowed or accepted at the buyer’s discretion, submit it only through the named route and plan for no answer. Meanwhile, keep work reversible and place the final bid decision with the people who can accept compliance, delivery, price and legal exposure.
Deadline proof
A missed deadline is a sourced event, not a calendar impression
Tender timetables carry several dates that are easy to confuse: an internal question freeze, the buyer’s enquiry cutoff, a promised answer date, a site-visit booking cutoff and the tender deadline. Start with the complete buyer label and source. Preserve the printed date, time, time zone, stage and lot. Then inspect later notices, amendments and portal messages for a replacement. If the answer is still unclear, record deadline_conflict. Do not begin recovery from an unproved date.
The winter-station team finds the 2 October cutoff in the current invitation and the same date in the portal event list. The tender closes on 15 October. A project plan also contains an internal 29 September writing deadline, but missing that date would not close the official channel. Conversely, the portal message button remaining visible on 3 October does not move the buyer’s stated cutoff. These observations belong in separate fields.
Check scope as carefully as time. A two-stage procurement may have one cutoff for participation and another for tenders. Lots can receive separate extensions. A corrigendum may move the tender deadline while leaving the question deadline unchanged, or move both. The recovery record is useful only when it identifies the event the team actually missed.
| Field | Recorded evidence | What it does not prove |
|---|---|---|
| Procedure | Council winter-station maintenance invitation | A similarly named road contract |
| Stage and lot | Tender stage, all 62 stations | The earlier selection-stage timetable |
| Question cutoff | 2 October, 12:00, stated zone retained | The 15 October tender deadline |
| Source state | Current invitation plus portal event list | That no later correction exists |
| Observation | Checked 3 October through authorized access | That the open button permits a late question |
| Result | official_cutoff_passed | That all recovery options are closed |
Question scope
Write the missing fact before choosing what to do about it
“The response time is unclear” is too loose for a recovery decision. The source says 30 minutes after a critical failure. The unresolved proposition is the event that must occur within those 30 minutes: acknowledge remotely, arrive on site or restore the feed. Preserve the exact clause, defined terms and station scope. The authority owns that meaning. Travel routes and technician placement are supplier design choices that follow from it.
Split mixed questions. The team may also need to know whether the clock pauses when the council denies site access and whether two simultaneous faults count separately. Those points have different source passages and answer branches. Combining them into one late message makes a partial reply hard to use and exposes more of the planned operating model than necessary.
Name the dependent bid objects now. In this case they are the shift plan, remote diagnostic design, vehicle deployment, escalation method, fixed annual fee and the service-level answer. That list tells the team what to hold and who must review each branch. It also stops a vague uncertainty from contaminating the whole bid.
Existing answer
The cheapest recovery may already be in the official record
Read the current pack and the complete published Q&A set before asking late. Search the buyer’s language and the underlying concept. “Response” may appear as attendance, acknowledgement, rectification, restoration or incident acceptance. Follow definitions and cross-references. Inspect answers to other bidders and any file named in them. The team should be able to show which sources, versions and locations it checked, not merely that somebody searched the portal.
An earlier answer might settle one branch without settling the whole point. Suppose Q&A 14 says remote diagnostics may begin immediately, but it never defines completion of the 30-minute obligation. That answer supports remote triage. It does not prove that acknowledgement satisfies the service level. Keep the remaining proposition open rather than stretching a useful sentence beyond its scope.
The same check can reveal a moved deadline. Some authorities publish a revised timetable or corrigendum that extends both questions and tenders; others extend only submission. The corrected official date controls the recovery status within its stated procedure. An alert or team spreadsheet cannot replace that source.
| Finding | Disposition | Required evidence |
|---|---|---|
| Current clause defines the event | resolved_from_source | Exact provision and applicable scope |
| Published answer resolves every branch | resolved_from_published_answer | Answer identifier, audience and linked source |
| Answer resolves only remote triage | partially_resolved | Supported part and surviving proposition |
| Later notice moves the question date | cutoff_not_missed | Current notice and replacement relationship |
| Two current sources disagree | source_conflict | Both versions and conflict owner |
| No controlling answer found | post_cutoff_unknown | Search boundary and checked time |
Communication route
An open message box answers a technical question only
Portals often leave their correspondence function available after a question cutoff because the same function carries buyer notices, support exchanges or later procedural messages. Its availability does not tell the supplier whether a new substantive question is timely. Record three facts separately: which route the documents designate, whether the team can currently use it, and what the procurement says about late questions.
Wording matters. “Questions received after the deadline will not be answered” is different from “may not be answered” or an express reservation that the authority may answer at its discretion. Silence is another state. None gives the supplier a promise. Where the procurement permits a late request or leaves a discretionary route, the release authority can decide to send a short neutral question through the named channel. The bid plan must still work if no reply arrives.
Do not route around the process. A council engineer’s address on a site drawing, a contract manager met during market engagement and the portal helpdesk have different functions. Technical support may help with login or an error. It cannot decide what “response” means in the tender. Keep evidence of a genuine platform failure and use the published support route, but do not disguise a late procurement question as a support ticket.
Legal boundary
Public rules protect fair information, but they do not erase a bidder’s late request
The applicable procurement and its documents decide the consequence. Under Directive 2014/24/EU, Article 53 links timely requests for additional information to delivery at least six days before the tender deadline, subject to the stated urgent-procedure variation. Article 47 addresses extensions where timely requested significant information is not supplied or the documents change significantly. Those provisions do not create a general entitlement from an untimely request. German and French rules cited in the localized editions use the same “requested in good time” condition within their stated fields.
The UK Procurement Act 2023 sets objectives and time-limit duties for covered procurements. Current Cabinet Office guidance says the same time limits must apply to suppliers and that authorities may need to respond quickly to clarification questions. The guidance on modifying a competitive procurement explains how a clarification can lead an authority to amend tender material. It does not promise that a supplier’s question after the procurement-specific cutoff will receive an answer.
At international level, the WTO Government Procurement Agreement requires a covered procuring entity to reply to a reasonable request for relevant information when this gives no supplier an advantage, and to communicate modifications in time for amended tenders where appropriate. Coverage and domestic implementation matter. Use these rules to frame specialist review, not to tell the buyer that the missed date has vanished. Any suspected breach, discriminatory information gap or review right needs prompt advice under the actual jurisdiction and procedure.
| Rule or source | Supported conclusion | Unsupported conclusion |
|---|---|---|
| Tender-specific timetable | The stated question event and any late treatment | The buyer will waive it |
| EU timely-request provisions | Timeliness matters to information and extension duties | Every late request must receive a reply |
| UK time-period guidance | Authorities consider reasonable and equal time limits | A portal button extends the cutoff |
| Modification rules | A buyer may need to publish and allow time for a material change | The bidder may amend the pack itself |
| WTO GPA where applicable | Relevant information cannot give one supplier an advantage | Private late advice can be treated as controlling |
| Review procedures | A specialist can assess a possible remedy and its clock | A late clarification preserves every legal right |
Branch analysis
Price and design the branches before anyone accepts one
The winter-station ambiguity has at least three credible readings. Remote acknowledgement within 30 minutes can be supported by a centralized duty engineer. Arrival within 30 minutes may require two local crews or an additional standby arrangement. Restoration within 30 minutes may be technically impossible for a damaged roadside sensor without spare-stock and access assumptions. The record must show cost, feasibility, compliance and response-language consequences for each branch.
Use ranges only where their drivers are named. A commercial note such as “add contingency” hides whether the money covers people, vehicles, spare equipment or contractual exposure. The delivery owner should state the operating model for each branch. The estimator should price those models. The compliance reviewer should identify which branch can meet the literal requirement. Nobody should average incompatible interpretations into a comfortable midpoint.
The branch work may reveal that no safe bid basis exists. If arrival in 30 minutes is plausible and the supplier cannot staff it, a remote-acknowledgement assumption is not a recovery plan. It is an unsupported compliance bet. Route that result to no-bid or specialist review while there is still time to stop further spend.
Reconciliation
A late buyer publication replaces the temporary basis, not the audit trail
Continue checking the official Q&A, notice, documents and participant messages through the final response control. A buyer may answer another supplier, publish a general correction or move a deadline without replying directly to the late request. Record the new item’s audience, scope and publication time. Then reopen every bid object that depended on the earlier branch.
Do not overwrite the temporary decision. Mark it superseded and link the buyer publication that replaced it. Recalculate staffing and price, update affected answers and repeat their approvals. Where a material change arrives too late for a proper response, the deadline question belongs to the applicable procedural and specialist process. The supplier does not grant itself extra time.
Close the recovery record only when the proposition is resolved, an authorized bid basis has reached the released offer, or the pursuit has stopped. Retain the deadline proof, source search, unsent or sent wording, receipt, answer state, decision authorities and final reconciliation. Those facts show what the team knew and why it acted. Silence remains silence.
What good looks like
Useful outcomes from missed tender clarification deadline
- The official question cutoff is proved with its source, version, time zone, stage, lot and any later correction.
- The record distinguishes a missed internal drafting date from a missed buyer deadline.
- The unresolved point is written as one buyer-controlled proposition rather than a broad concern.
- Current documents, amendments, notices and published Q&A are checked before any late contact is considered.
- The permitted channel, its observed technical state and the rule for late questions remain separate facts.
- Each credible answer branch has named effects on compliance, solution, resources, price and response wording.
- Interim work is limited to tasks that remain useful across the live branches.
- An authorized owner chooses whether to send a late request, bid on a supported basis, seek specialist review or stop.
- A later buyer answer, amendment or deadline change reopens every dependent decision.
Operating model
How to run the work
- 01
Prove which cutoff was missed
Fix the procedure, stage, lot, source version, raw date, time, time zone and any later correction before treating the question period as closed.
- 02
Freeze the unresolved proposition
Write the smallest buyer-controlled fact that remains unknown and name the current bid objects that depend on it.
- 03
Search the current official record
Inspect the notice, instructions, schedules, amendments, published answers and referenced files for a supported answer or a changed deadline.
- 04
Read the late-question rule
Record whether the procurement expressly refuses, may consider, accepts or says nothing about questions received after the cutoff.
- 05
Verify the permitted route
Keep the buyer clarification channel, platform support route and any unrelated contact address distinct, even if more than one remains technically open.
- 06
Model the answer branches
Test each credible interpretation against compliance, operations, staffing, price, contract exposure, evidence and final response language.
- 07
Choose the remaining authorized option
Obtain the required approval for a late request, bounded interim basis, permitted qualification or variant review, risk acceptance, legal review or no-bid decision.
- 08
Watch and reconcile
Monitor the official locations through release, replace temporary decisions with later buyer information and retain the complete decision history.
Evaluation
Questions that change the decision
- Did the official cutoff pass, or did the team only miss an earlier internal review date?
- Does a later notice, amendment or message change the question deadline for this stage or lot?
- Is the missing point controlled by the buyer, by the bidder’s own design or by an external future event?
- Do the current documents or published answers already resolve the point at the required scope?
- Does the procurement state what happens to questions received after the cutoff?
- Is the visible route the authorized clarification channel, technical support or an unrelated address?
- Would asking disclose price, capacity, design weakness, partner identity or another unnecessary private fact?
- What does each plausible answer change in the offer and which branch would make the bid non-compliant or uneconomic?
- Which work remains useful if no answer arrives?
- Who has authority to send, approve the bid basis, accept exposure, seek counsel or stop the pursuit?
Failure modes
Where teams lose control
The team uses the tender deadline or an internal date instead of the actual clarification cutoff.
A timezone, daylight-saving or version error creates a false missed-deadline conclusion.
The bidder sends a late question to a convenient person outside the procedure-recognized channel.
A portal text box is treated as evidence that late questions are permitted.
The team assumes the buyer will answer because another authority did so in a different procurement.
A late question reveals the supplier’s minimum price, staffing weakness or intended solution.
Silence is recorded as acceptance of the bidder’s preferred interpretation.
A conservative estimate still fails because the ambiguity concerns a mandatory method rather than quantity.
Irreversible design, partner or pricing commitments continue while the controlling branch is open.
A suspected procurement defect is handled as an ordinary late question while a separate review deadline runs.
Measurement
Measure the finished job
Measure the completed workflow, including review effort and exceptions. Output volume on its own is not evidence of a better process.
- Post-cutoff issues with procedure, stage, lot, source version and resolved time proved
- Issues resolved from current official material without buyer contact
- Late-question rules classified from procurement-specific wording
- Visible communication routes correctly separated by function and authority
- Open propositions with complete answer-branch consequences
- Dependent work packages held at a reversible boundary
- Late requests with approved wording, route, disclosure and no-answer plan
- Final bid decisions with named compliance, delivery, commercial and release authority
- Later publications reconciled to every dependent bid object
- Issues escalated before any applicable specialist-review deadline expired
Questions
Common questions
Will the buyer answer a clarification submitted after the deadline?
Do not expect it. Read the procurement-specific rule. Some documents refuse late questions, some reserve discretion and some are silent. A technically available channel does not create an entitlement to a reply.
Should we send the question anyway?
Only after checking the named channel and late-question terms, minimizing disclosure, obtaining release authority and planning the bid on the basis that no answer may arrive. Do not route around an express refusal.
Can we email a buyer contact if the portal deadline has passed?
Use only the route the current procurement recognizes for that function. A contact on a drawing, a prior relationship and a technical helpdesk do not become clarification channels because the normal route has closed.
Does a late question extend the tender submission deadline?
No. Keep the published tender deadline until an authoritative buyer notice changes it. An extension duty, where one exists, depends on the applicable rule and facts; the bidder cannot declare the extension.
Can we put our preferred assumption in the bid?
Only if the tender permits that type of offer treatment and the exact wording is approved. An assumption cannot weaken a mandatory requirement or convert an unknown buyer fact into agreement.
What if the official documents conflict?
Preserve both current sources and their hierarchy evidence, keep the proposition unresolved and route it to the dedicated conflict and specialist review. Do not choose the convenient text solely because the question period ended.
What work can continue while the issue is unresolved?
Continue tasks that remain useful across every viable branch. Hold branch-specific commitments, final price release and wording that would represent one interpretation as buyer fact.
When should a missed clarification deadline trigger no-bid review?
Open no-bid review when no supported branch can meet a mandatory condition, when exposure exceeds delegated authority, or when the team cannot approve accurate offer wording before submission.
Sources
Primary references
- Procurement Act 2023, section 12 on covered procurement objectives UK Legislation
- Procurement Act 2023, section 21 on tender notices and documents UK Legislation
- Procurement Act 2023, section 31 on modifying a procurement UK Legislation
- Procurement Act 2023, section 54 on time limits UK Legislation
- Cabinet Office guidance on covered procurement objectives, updated 15 April 2026 Cabinet Office
- Cabinet Office guidance on time periods, updated 17 August 2026 Cabinet Office
- Cabinet Office guidance on modifying a competitive procurement, updated 17 August 2026 Cabinet Office
- Cabinet Office guidance on electronic communications, updated 17 August 2026 Cabinet Office
- Current Find a Tender notice requiring clarification through The Chest by the ITT deadline Find a Tender
- Current Ministry of Defence tender attachment with a dated question period and shared answers Find a Tender
- Directive 2014/24/EU, especially Articles 18, 47 and 53 EUR-Lex
- TED eForms BT-13 additional-information deadline Publications Office of the European Union
- WTO Agreement on Government Procurement, Articles X and XI World Trade Organization
- UNCITRAL Model Law on Public Procurement, Article 15 United Nations Commission on International Trade Law
- World Bank Procurement Regulations, seventh edition, September 2025 World Bank
- EBRD multi-stage Instructions to Participants, clarification rule at ITP 10.1 European Bank for Reconstruction and Development
About the author
Tony Kim
Tony writes about applied AI, dependable product engineering and the systems that turn complex response work into controlled delivery.
Zelius
Managed tender intelligence and bid execution for teams that want the commercial outcome.
Suppliers, founders and commercial teams pursuing public or private opportunities. Start with the workflow, constraints and evidence you already have.