A live bid stop decision determines what should happen when a verified fact changes after pursuit work has begun and before a tender is submitted. Its work product is a `live_bid_stop_decision`. The record fixes the procedure, lot, current stage, prior proceed authority and submission state; proves the change event and the earlier assumption it defeats; reopens only the dependent eligibility, delivery, contract, security, partner, price, evidence, capacity and investment gates; recalculates the usable clock; and returns an authorized continue, pause or stop state. If work stops, a linked closure record freezes submission authority, releases avoidable commitments, preserves required evidence and assigns every remaining obligation. This is not an initial bid qualification, a new return-on-investment model, legal advice, notice to the buyer or withdrawal of an offer already submitted.
Once a response has visible drafts, booked specialists and money behind it, teams start treating completion as the neutral choice. A failed dependency is described as a challenge. An addendum is absorbed without revisiting the delivery plan. A missing approval receives one more day even when the safe decision point has passed. The opposite reaction is also costly: a rumor, a difficult clarification or a lower win estimate can trigger an improvised stop even though the original plan still works. Both failures come from comparing emotion with effort instead of comparing a proved change with the conditions that supported the last decision. Quiet abandonment then creates a second problem. Drafts remain marked as live, partners keep working, portal access stays active and nobody can explain why the pursuit ended.
Stop decisions should be prepared before the team needs one. Every proceed authority needs named expiry events and hard conditions. When an event occurs, compare the current fact with the exact prior assumption, follow its dependencies and reopen the affected gates. Do not restart every review by habit, and do not preserve an unaffected approval by guesswork. Record elapsed spend for learning, but decide from remaining choices, including cancellation charges, closure work and the alternative use of scarce people. A buyer amendment may alter the legal timetable in some procedures, yet the bid team plans only from the current official deadline. The human with delegated authority decides whether to continue or stop. An agent may watch authorized sources, compare versions, calculate time and assemble the decision record. It cannot accept risk, contact the buyer, terminate a partner commitment, delete the workspace or withdraw a submitted tender.
Change event
A stop review begins with a contradiction, not a feeling
The trigger record needs two sides. On one side is the fact used by the last proceed decision: the named subcontractor could supply a tested interface by 12 September, the required insurance was expected to renew, or the buyer allowed a four-week mobilisation. On the other is new evidence that changes that statement. Preserve both sources, their versions, observation times and owners. Then state the contradiction in one sentence. “The partner is worried” is not enough. “The partner’s delivery director withdrew the 12 September commitment in a signed message received at 09:10 on 3 September” can reopen a gate.
Classify where the event came from because the verification route differs. A buyer event may be an addendum, clarification, cancellation or timetable change at the designated portal. A supplier event may be lost capacity, an expired control, a changed price basis or revoked authority. A bid event can be a failed sample, late internal gate, unsupported claim or cost overrun. An external legal, sanctions, insurance or regulatory event goes to the competent specialist. An agent may identify a possible change, but an authorized source or owner must support the fact used for a decision.
The prior record must be recoverable. Retain its decision, scope, conditions, spend cap, expiry and evidence versions. A stop review cannot prove change by comparing a current fact with a memory of what the team expected. If the earlier assumption was never recorded, mark `prior_basis_missing`, rebuild only what can be proved and lower confidence. Do not manufacture a neat baseline after the event.
| Field | Evidence | Failure response |
|---|---|---|
| bid_identity | Authority, procedure, lot and stage | Stop if objects are mixed |
| submission_state | Portal receipt and internal release log | Route uncertainty before any action |
| prior_basis | Proceed state, condition, source and expiry | Return prior_basis_missing |
| change_source | Current document, message, test or owner record | Keep the event unverified |
| contradiction | Old value, new value and affected condition | Do not reopen by intuition |
| observed_at | Timestamp, time zone and observer | Do not reconstruct sequence from file dates |
Dependency review
Follow the changed fact through the bid before choosing a path
Build the dependency chain from fact to requirement, from requirement to planned response, and from that response to evidence, price, schedule, contract position and approval. If a lead engineer leaves, the effect may reach a scored methodology, a mandatory résumé, a delivery milestone, a day-rate assumption and a key-person clause. The eligibility gate may remain valid while delivery, evidence, price and contract gates reopen. A visible graph prevents both a shallow review and a wasteful restart.
Each reopened gate returns its own state: still valid, failed, conditionally curable, evidence missing, authority missing or source conflict. A cure must identify the permitted route, owner, evidence, cost and last completion time. Replacing a named expert, narrowing a lot, qualifying a term or changing a mandatory answer may require buyer permission or a separate internal authority. Keep the route blocked until that permission is proved. Hope is not a cure path.
Preserve unaffected work with its scope and expiry. A current security approval for an unchanged hosting design should not be discarded because a pricing assumption changed. Nor may it be reused if the cure introduces a new processor or country. The decision record should show why each gate was reopened or retained, enabling another reviewer or agent to reproduce the boundary rather than trust a colored dashboard.
| Gate state | Required proof | Decision effect |
|---|---|---|
| still_valid | No dependency changed and original scope remains current | Carry forward with expiry |
| failed | Mandatory condition cannot be met | Recommend stop unless an authorized exception route exists |
| conditionally_curable | Permitted cure, owner, cost and time all fit | Pause only through the cure gate |
| evidence_missing | Material fact lacks acceptable proof | Block dependent work |
| authority_missing | No role can approve the required choice in time | Do not treat analysis as permission |
| source_conflict | Current sources disagree on a controlling fact | Escalate and preserve both versions |
Time and cost
The latest safe stop matters more than the tender deadline
First verify the current receipt deadline and the response event it governs. Procurement rules in several jurisdictions require buyers to consider or grant more time after certain document changes. The UK Procurement Act guidance tells authorities to consider the nature and complexity of a modification when revising time limits. Article 47 of Directive 2014/24/EU addresses proportionate extensions for significant changes. Neither source gives a supplier permission to invent a new date. Until the designated source issues one, the recorded deadline remains the planning boundary.
Work backwards from a safer internal point. Reserve time for specialist approval, executive decision, partner notice, cancellation of external work, document freeze, portal control and the ordinary submission margin. A cure that completes ten minutes before the buyer deadline is not viable if pricing needs four hours and the portal release needs two. Record separate latest times for evidence, authority, commitment and stop. Once the last safe stop passes, continuing to wait is itself an unapproved choice.
The economic view also starts now. Import actual spend, irrevocable commitments, cancellable commitments, remaining internal effort, remaining external cash and opportunity cost from the current bid investment record. HM Treasury defines sunk costs as incurred costs that cannot be changed and says they should not affect what to do next. The Green Book governs public appraisal rather than a supplier bid, but the distinction is useful here. Keep sunk effort for audit and calibration. Compare the paths using what still changes, including cancellation charges and the work needed to close safely.
| Item | Decision treatment | Record to retain |
|---|---|---|
| sunk_actual | Exclude from the choice between future paths | Amount, work, owner and date |
| irrevocable_commitment | Show future cash but no avoidable difference | Contract, invoice and due date |
| cancellable_commitment | Compare continuation with cancellation cost | Terms and last cancellation time |
| remaining_work | Include only approved future effort and cash | Range, capacity and assumptions |
| closure_cost | Include in the stop path | Required action, owner and amount |
| latest_safe_stop | Use the earliest dependent control time | Source deadline, margins and time zone |
Worked case
A live integration demonstration ends a digital triage pursuit
In this fictional case, a supplier is preparing a response for a national health authority digital triage service. The proceed record assumes a production-like integration demonstration can use the partner’s tested endpoint on 18 September. At 09:10 on 3 September, the authority issues an addendum requiring the demonstration on 12 September and advances mobilisation by six weeks. The official deadline moves from 16 to 20 September. At 11:40, the integration partner confirms that its tested endpoint cannot be available before 17 September. Those two sources contradict the delivery and evidence conditions behind the prior decision.
The dependency review reopens the demonstration, delivery schedule, partner, security, price and investment gates. Eligibility remains valid. The team has spent £44,000, which stays in history. Another £9,000 is irrevocably committed. The current estimate shows £19,000 of avoidable response work plus an £11,000 demonstration booking that becomes non-cancellable at 15:00 on 5 September. Safe release needs one day after a technical route is approved. The buyer clarification deadline is noon on 4 September, so the authorized owner permits one question and a two-day technical check. State: `pause_for_evidence`.
The authority replies on 5 September that the demonstration must use the stated live test interface and the date will not move. The technical owner finds no approved alternative. At 14:20, the bid director records `stop_before_submission`, before the booking becomes firm. The submission role is removed, the draft is marked not for submission, £11,000 is released, the partner receives the agreed notice and the security owner takes custody of the authority’s test material. A £2,400 closure cost is recorded. The £44,000 already spent explains the loss and informs later estimates; it does not change the failed demonstration gate.
| Record | Evidence | Treatment |
|---|---|---|
| change_event | Addendum plus partner commitment withdrawal | Reopen six dependent gates |
| official_deadline | 20 September | Do not confuse with the 12 September demonstration |
| sunk_actual | £44,000 | Audit history only |
| remaining_avoidable | £19,000 plus £11,000 booking | Booking released before 15:00 |
| decisive_gate | Required interface unavailable on 12 September | No approved cure |
| decision | stop_before_submission at 14:20 on 5 September | Controlled closure started |
What good looks like
Useful outcomes from stop a bid after work has started
- One procedure, lot, response stage and verified submission state define the decision.
- The previous proceed decision, its evidence, conditions, owner and expiry remain reconstructable.
- Every trigger identifies the new fact, source, observation time and prior assumption it contradicts.
- A dependency graph reopens affected gates without discarding still-valid review work.
- The official deadline, internal release margin and latest safe stop are recalculated after the change.
- Sunk, irrevocable, cancellable, remaining and closure costs keep different decision treatments.
- Continue, pause and stop states carry evidence, authority, conditions, blocked actions and expiry.
- A stopped pursuit freezes submission, releases avoidable work and preserves the required record.
- Partner, buyer-contact, data, access, retention and learning obligations receive named owners.
- Agents can explain and route the decision while abstaining from commitments and external action.
Operating model
How to run the work
- 01
Fix the live bid boundary
Record the authority, procedure, lot, stage, current source versions, official deadline, submission state and prior proceed authority. Stop the analysis if the bid may already have been submitted.
- 02
Prove the change event
Retain the new source, observation time, issuer or internal owner, exact changed value and the earlier assumption or condition it defeats. Keep rumors and unverified messages outside the decision.
- 03
Traverse the dependencies
Map the changed fact to affected requirements, claims, price lines, people, partners, controls, evidence and approvals. Reopen each dependent gate and retain unaffected approvals with their scope.
- 04
Rebuild the usable clock
Verify the current deadline at the designated source. Subtract portal, approval and release margins, then set the last time at which each cure, commitment and stop can still be executed safely.
- 05
Import the economic cut
Bring forward the approved bid investment record. Update actual-to-date, irrevocable, cancellable, remaining and closure amounts without allowing sunk work to justify continuation.
- 06
Compare bounded paths
Test the current plan, a permitted cure and a stop path against hard gates, time, authority and remaining investment. A scope reduction appears only if the tender permits it and the lot decision is separately approved.
- 07
Obtain the decision
Give the authorized owner decisive facts, contrary evidence, assumptions, latest safe decision time and recommendation. Record the chosen state, conditions, prohibited actions and expiry.
- 08
Close under control
If stopped, freeze new work and submission authority, release cancellable commitments, notify approved internal and partner roles, protect buyer material, retain the record and assign every unresolved action.
Evaluation
Questions that change the decision
- Which exact procedure, lot, version and pre-submission stage does the record govern?
- What authority allowed work to continue before the new event?
- Which sourced fact changed, when was it observed and who owns its accuracy?
- Which earlier assumption, condition or threshold no longer holds?
- Which requirements, work products and gates depend on that fact?
- What current official deadline and internal release margin apply?
- What is the last safe time for evidence, authority, cancellation and a stop?
- Can a permitted cure restore every failed dependency before that time?
- Which remaining cost, commitment and scarce capacity changes between the paths?
- Who may approve the cure, renewed spend, exception or stop?
- What action follows immediately if the decision is to stop?
- Has any submission occurred, making the later withdrawal procedure the correct route?
Failure modes
Where teams lose control
A concern may be treated as a changed fact without a source or observation time.
An addendum may be reviewed in isolation while its effect on claims, price and delivery remains hidden.
The team may assume that a material amendment automatically grants enough extra time.
A global restart may consume the remaining clock even though only two gates were affected.
An earlier green state may survive outside the scope or expiry for which it was approved.
Money already spent may become the main argument for spending more.
A cure may depend on buyer permission, partner consent or legal interpretation that nobody has obtained.
A pause may continue beyond the last safe stop and become an accidental decision to submit late or weak work.
A stop may be announced by someone without commercial or contractual authority.
Partners may keep incurring cost after the internal team has stopped.
Buyer-confidential files, credentials or draft claims may remain accessible without a retention owner.
An agent may send a message, cancel work, delete evidence or withdraw a tender without permission.
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.
- change events linked to a source, timestamp and prior assumption
- affected gates reopened before more dependent work is authorized
- unaffected approvals retained with valid scope and expiry
- deadlines verified at the designated source after every buyer change
- decisions issued before their latest safe stop
- records importing a current remaining-investment cut
- stopped bids with submission authority frozen before closure begins
- cancellable external commitments released by their deadline
- closure actions with owner, evidence, due time and completion state
- unauthorized buyer contact, submission, withdrawal, deletion or commitment; target zero
Questions
Common questions
Does a lower win probability automatically mean we should stop?
No. Reopen the approved forecast and investment records if new evidence changes them. A probability movement may alter the recommendation, but the authorized owner decides from the whole current case and every hard gate.
Should we finish because most of the work is already done?
No. Keep completed work and cost in the history, then compare only the consequences that still differ. A failed mandatory gate does not recover earlier spend.
Does a buyer addendum always extend the deadline?
Do not assume it. Applicable rules may require the buyer to consider or grant an extension for certain changes. Plan from the current deadline published through the designated source and obtain specialist review where legal effect matters.
Can the team pause instead of stopping?
Yes, when one bounded evidence or authority task can finish before the last safe stop. The pause must name permitted work, owner, spend cap, due time and the state returned if it expires.
Who should make the final stop decision?
The role holding the relevant commercial delegation, with required input from delivery, finance, legal, security or other specialists. Analysis does not substitute for authority.
Can we reduce scope to keep the bid alive?
Only if the tender permits the proposed lot or scope choice and the organization approves it. Route that choice through the separate lot and compliance decisions instead of treating it as a quick cure.
What if the tender may already have been submitted?
Freeze further action, verify the receipt and route the case to the authorized post-submission withdrawal process. Do not assume that deleting or replacing a portal file reverses submission.
What must remain after a bid is stopped?
Keep the decision, decisive sources, approvals, financial cut, required communications and retention ownership under policy. Mark invalid claims and reusable approved work so neither is misapplied later.
What may an AI agent do during the stop review?
Within approved access, it may monitor sources, compare versions, trace dependencies, calculate times, import cost states and draft the record. It must stop before external contact, commitment, cancellation, access changes, deletion, submission or withdrawal.
Sources
Primary references
- The Green Book 2026 HM Treasury
- Guidance: Modifying a Competitive Procurement UK Cabinet Office
- Guidance: Time Periods UK Cabinet Office
- Directive 2014/24/EU, consolidated text EUR-Lex
- AI Risk Management Framework Core National Institute of Standards and Technology
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.