---
title: "Was this tender cancelled, corrected or replaced?"
description: "Trace the official notice lineage, classify the affected scope and identify any successor before stopping work or moving a bid to another tender."
canonical: "https://zephior.com/insights/verify-a-cancelled-or-replaced-tender"
last-updated: 2026-09-03
---

# Was this tender cancelled, corrected or replaced?

> Trace the official notice lineage, classify the affected scope and identify any successor before stopping work or moving a bid to another tender.

By [Tony Kim](https://zephior.com/authors/tony-kim). Published 2026-09-03; updated 2026-09-03. 17 minute read.

## Definition

A tender disposition record is a dated graph of official publication events for one identified procurement and its lots. Each event keeps its notice identifier, version, procedure identifier, notice type, publication time, affected scope, stated reason and links to earlier or later events. The record returns one bounded finding for each scope: current_after_correction, notice_cancelled_only, cancellation_intended, procedure_suspended, lot_ended_without_award, procedure_ended_without_award, successor_confirmed, successor_candidate, status_conflict or insufficient_evidence. A successor is a separate procedure node, not a renamed version of the old notice. The record also states whether bid work should continue, pause, stop or be requalified.

## Problem

Public portals use the word “cancelled” for different objects. A publisher can cancel a notice because the notice itself is defective while the buyer continues the procurement through another publication. A buyer can end one lot and continue the others. A review can suspend the procedure without ending it. A result notice can report no winner. A new competition can resemble the old one without being its replacement. Search indexes often flatten those events into one badge and keep the old deadline visible. Acting on that badge can waste a bid team’s time, discard a still-live procedure or carry confidential working files into an unrelated competition.

## Point of view

Classify the event before classifying the opportunity. Start with the exact procedure, notice version and lot. Follow typed references rather than titles. In current eForms, a Change Notice reproduces its parent in consolidated form, identifies the changed notice version through BT-758 and records a reason through BT-140. The TED FAQ draws a critical boundary: reason “Notice cancelled” makes that publication null and void but does not by itself cancel the procurement procedure. Whole-procedure cancellation is represented by a result notice with “No winner chosen” and a non-award reason. A replacement needs its own verified identity and an explicit buyer or publication relationship. An agent may build this lineage from public evidence. It must not infer legal effect from a colour, remove history, or treat a similar new title as a confirmed successor.

## First identify what was cancelled

A tender is not safely closed because one page says “cancelled”. Ask which object the publisher describes. The object may be an unpublished submission to the publication service, a published notice, one lot, the whole procurement before award, or a contract that already exists. Each has a different evidentiary route and a different effect on bid work.

The first output should therefore be a scope statement, not a yes or no. A useful statement reads: “Result notice R3 closes LOT-0002 without a winner as of 2 September 2026; LOT-0001 and LOT-0003 are outside that finding.” Another reads: “Change notice C2 cancels notice version N1-01 because of publication errors; no evidence yet proves that procedure P1 ended.” These statements can be checked and updated.

Keep the raw portal term beside the normalized state. Publishers and jurisdictions use cancellation, withdrawal, abandonment, discontinuation, no award, unsuccessful, closed and termination differently. The mapping earns authority only from the fields, reasons and relationships in the official record. If those are missing, return insufficient_evidence and preserve the apparent status as an observation.

**Disposition states and their immediate consequence**

| Finding | Required evidence | Work instruction |
| --- | --- | --- |
| current_after_correction | Linked consolidated change notice | Use the new version and reassess changed fields |
| notice_cancelled_only | Official notice-cancellation reason | Stop using that notice; keep checking the procedure |
| cancellation_intended | Explicit intent field or message | Pause affected work and schedule a recheck |
| procedure_suspended | Official suspension event and scope | Freeze time-sensitive work without declaring closure |
| lot_ended_without_award | Result or decision for named lot | Stop only the named lot |
| procedure_ended_without_award | Whole-scope result or termination record | Stop current-procedure bid work |
| successor_confirmed | New identity plus official relationship | Run qualification again on the successor |
| status_conflict | Material official records disagree | Block the affected decision for review |

## A cancelled eForms notice may leave the procurement alive

Current TED guidance describes a Change Notice as a consolidated reproduction of its parent. It has its own Notice Identifier, points to the changed notice version through BT-758 and uses BT-140 for the change reason. The current version contains earlier changes already applied, while the change section describes the latest change. The parent remains published and belongs in the lineage.

The change reason code list includes buyer correction, eSender correction, publisher correction, information release, information update, suspension due to review, cancellation intention and notice cancelled. These labels are not interchangeable lifecycle decisions. The TED FAQ states that a Change Notice with reason “Notice cancelled” can make a defective notice null and void without cancelling the procurement procedure. A system that maps the code directly to procedure_ended_without_award is wrong.

For an entire procedure, TED instructs publishers to use a Result Notice with “No winner chosen” and a corresponding non-award reason. The winner-status code clos-nw means no winner was chosen and the competition is closed. It differs from open-nw, where no winner has been chosen yet but the competition continues. Save BT-142 with BT-144 and the affected lot results. Reading one field without the other loses the buyer’s disposition and its reason.

Lot withdrawal is narrower again. Current TED guidance says it is handled through a result for the affected lot, and in a limited pre-deadline case a later Change Notice may remove that lot if the result is clearly referenced. Unaffected lots remain separate. A procedure with one technical lot still needs its scope recorded, because the apparent lot-level result may in practice cover the complete competition.

## Build the publication lineage before choosing the current node

Make each official event a node. Store publisher, public URL, notice type, notice identifier, version, procedure identifier, lot identifiers, dispatch and publication times, retrieved representation and content fingerprint where practical. Add buyer messages as separate nodes because a direct communication can reach participants before an open-data feed updates. Never replace a node in place.

Edges need a type and evidence anchor. changed_notice_version points from a Change Notice to the version named in BT-758. same_procedure relies on the scheme-qualified procedure identifier. result_for_lot connects a result to the lot it decides. originating_notice connects a termination notice to the event the regime requires it to reference. successor_of needs a buyer statement or official reference that identifies the later procedure. similar_to is only a search lead.

The Open Contracting Data Standard offers a useful representation where it applies. Its release and record model preserves versioned history, and its amendments array can name the release before and after a change. That structure is evidence transport, not a legal conclusion. An OCDS tender status, amendment description or related process is only as authoritative and current as the publisher that supplied it. Retain the source URL and publication time.

Choose the current node separately for each fact. A consolidated correction may control the deadline while a later result controls lot disposition. A portal message can be the first operational warning but not yet the final public record. The graph should allow an agent to explain that sequence without pretending every source updated at the same instant.

**Minimum fields for a tender disposition event**

| Field | What it records | Why it matters |
| --- | --- | --- |
| event_id | Local immutable event key | Keeps observations distinct |
| source_identity | Publisher, URL and source role | Shows where the assertion came from |
| notice_identity | Notice ID, version and type | Separates correction from replacement |
| procedure_identity | Identifier plus scheme | Groups events in one procurement |
| affected_scope | Procedure, group, lot or notice | Prevents scope leakage |
| raw_disposition | Field, code, text and reason | Preserves the official assertion |
| relationships | Typed targets and evidence anchors | Makes the chain reproducible |
| observed_at | Retrieval time and next trigger | Bounds freshness |

## A relaunch statement does not identify the replacement

A buyer can state that it plans to restart a procurement. That statement proves intent, not the identity or terms of the future competition. Keep the old procedure ended and open a successor watch. When a new notice appears, compare its procedure identifier, originating references, buyer, scope, lots, classifications and dates. Only an authoritative link or explicit buyer statement upgrades successor_candidate to successor_confirmed.

Shared wording is weak evidence. Buyers reuse titles, annual programmes and framework names. A later tender may cover a different region, contract period, delivery model or lot structure. Even an identical internal reference can be copied by mistake. Similarity can nominate a candidate for review, but it cannot transfer deadlines, registrations, clarifications, supplier invitations or submitted files.

After confirmation, do not continue the old bid as if only the identifier changed. Create a new qualification decision for the successor. Recheck eligibility, scope, procedure, deadlines, documents, language and portal route. Link reusable internal work through a reviewed provenance record. Do not copy buyer-issued forms or signed declarations across procedures without checking the new pack.

This boundary also separates current disposition from forecasting. A confirmed successor answers what replaced the ended procedure. A hunch that an expiring contract will be rebid belongs in a renewal forecast until an official procurement event exists.

## The UK regime separates procurement and contract termination

Under section 55 of the Procurement Act 2023, a contracting authority that decides not to award after publishing a tender or transparency notice must give notice as soon as reasonably practicable, subject to the stated private-utility exception. Current Cabinet Office guidance calls this a procurement termination notice and requires it to refer back to the originating notice. That relationship is strong closure evidence for the procurement described there.

The guidance also draws two useful boundaries. If some lots reach award and others cease, the buyer uses ceased-lot information in the contract award notice rather than a whole procurement termination notice. Once a contract has been entered into, a later contract termination notice describes the end of that contract, not cancellation of the earlier competition. Agents must classify the stage before using the word termination.

A public termination notice does not by itself name a replacement. The required statement says that the authority decided not to award the contract and records the decision date. If a new tender follows, connect it only through the central-platform record, an originating reference or a buyer statement. Until then, the safe output is procedure_ended_without_award plus an unfulfilled successor watch.

## One facilities procurement can produce three different answers

A fictional city publishes procurement CP-2026-184 for facilities services in three lots. Notice CN-01 invites bids until 30 September. Change notice CN-02 points to CN-01 and corrects the site list and deadline for all lots. A search index keeps both notices and labels CN-01 “cancelled”. The Change Notice reason is buyer correction, not notice cancellation. CN-02 is the current consolidated notice.

Two weeks later, a Result Notice reports clos-nw for LOT-0002 with insufficient funds as the non-award reason. LOT-0001 and LOT-0003 remain in the competition and retain the corrected deadline. The disposition graph returns lot_ended_without_award for LOT-0002 and current_after_correction for the other two. It does not close CP-2026-184 as a whole.

In November the city publishes procurement CP-2026-241 for a smaller cleaning package. The title resembles LOT-0002 and the buyer mentions in its public note that the new competition replaces the ceased cleaning lot from CP-2026-184. The new procedure identifier and explicit reference support successor_confirmed. The old lot remains closed; the new procurement receives its own qualification record and deadlines.

If the public note were missing, the similar title and buyer would support successor_candidate only. An agent could alert the capture owner and show the comparison, but it could not move the old bid workspace, reuse declarations or tell the team that the replacement is open without a separate current-status check.

**Disposition output for the fictional procurement**

| Scope | Finding | Next action |
| --- | --- | --- |
| CN-01 | Historical parent corrected by CN-02 | Retain for comparison |
| CN-02 | Current consolidated competition notice | Use corrected fields |
| LOT-0001 | Current after correction | Continue against CN-02 |
| LOT-0002 | Ended without award | Stop this lot and retain evidence |
| LOT-0003 | Current after correction | Continue against CN-02 |
| CP-2026-241 | Confirmed successor to ceased cleaning scope | Qualify as a new opportunity |

## Return the decision, its scope and the evidence that could change it

An agent-readable result should expose procedure_id, notice_id, notice_version, notice_type, lot_id, source_role, raw_status, raw_reason, normalized_disposition, effective_at, published_at, observed_at, predecessor_edges, successor_edges, decisive_evidence, contrary_evidence, work_instruction, review_owner and recheck_trigger. The result must remain understandable without rerunning an opaque similarity model.

The agent may retrieve public notices, parse typed identifiers, compare versions, preserve a lineage graph and recommend that internal work continue, pause, stop or return to qualification. It must stop when identifiers conflict, the affected scope is missing, a private participant message cannot be accessed lawfully, the legal effect is disputed or a proposed successor rests only on resemblance.

External acts remain separately authorized. The agent does not withdraw a tender, cancel monitoring, accept portal terms, contact the buyer, submit a clarification or migrate bid files because it found a disposition record. Its output supplies evidence for those decisions. A named human or authorized workflow takes them.

## Useful outcomes

- Every finding names the procedure, notice, version, lot and checked time it covers.
- Notice cancellation is kept separate from termination of the procurement itself.
- Corrections retain the parent and changed fields while identifying the consolidated current notice.
- Intent to cancel and suspension remain non-final states with a defined recheck trigger.
- Lot-level non-award does not close unaffected lots or the whole procedure.
- A whole-procedure stop is supported by the prescribed result or termination evidence for the regime.
- A replacement is confirmed only through authoritative identity and relationship evidence.
- Downstream work receives an explicit continue, pause, stop or requalify instruction with its basis.

## Workflow

1. **Fix the object and scope.** Record the buyer, regime, procedure identifier, notice identifier and version, lot, response stage, source and observation time before interpreting a status label.
2. **Collect every relevant event.** Retrieve the original competition notice, linked changes, result notices, termination notices, buyer messages and any candidate successor without overwriting earlier records.
3. **Follow typed references.** Use changed-notice, originating-notice, procedure and lot references to draw edges. Treat title, description, buyer and dates only as corroboration.
4. **Classify the event.** Separate correction, notice cancellation, cancellation intention, suspension, lot non-award, whole-procedure termination and later competition.
5. **Apply the narrowest effect.** Attach the finding to the exact notice or lot it affects. Do not let a ceased lot close its siblings or a cancelled publication close the procedure.
6. **Test the proposed successor.** Confirm the new procedure’s identifier, buyer statement or official reference and compare scope. Leave similarity-only matches as successor_candidate.
7. **Issue a bounded instruction.** State which work continues, pauses, stops or returns to qualification, cite the decisive event and set the next check or review owner.

## Key decisions

- Which procedure, notice version, lot and response stage does the label concern?
- Does the later publication explicitly reference the earlier notice or merely resemble it?
- Is the event a correction that preserves the competition, or a cancellation of the publication itself?
- Does the source express an intention, a suspension or a completed decision?
- Does a result close one lot, several named lots or the entire procedure?
- Was no winner chosen, or has the winner simply not been chosen yet?
- Does the governing regime require a distinct procurement termination notice?
- Is a new notice another version, another event in the same procedure or a new procedure?
- What official evidence connects a proposed successor to the discontinued requirement?
- Which bid tasks and stored assumptions are affected by the verified disposition?

## Risks

- A portal badge collapses notice cancellation and procurement termination into one state.
- An old future deadline survives beside a later no-award result.
- A cancellation intention is treated as a completed cancellation.
- A review suspension causes permanent closure of the opportunity record.
- One cancelled lot stops work on other lots that remain in competition.
- The absence of an award is mistaken for a formal decision not to award.
- A similar title, value or buyer is promoted to replacement without an official link.
- A corrected notice overwrites the parent, erasing what changed and when.
- Files and qualification decisions move automatically to a new procedure with different terms.
- An agent contacts the buyer, withdraws a bid or deletes monitoring state without authorization.

## Metrics

- events with preserved notice, version, procedure and lot identifiers
- change notices connected to the exact parent version
- cancel labels classified by affected object rather than copied raw
- no-award results with winner status and reason captured together
- partial dispositions prevented from leaking to unaffected lots
- successors supported by an official relationship rather than text similarity
- historical nodes retained after a consolidated correction
- work instructions carrying decisive evidence and checked time
- unresolved conflicts routed for review instead of silently normalized

## Frequently asked questions

### Does an eForms “Notice cancelled” code mean the tender is over?

No. Current TED guidance says that code can make the notice null and void without cancelling the procurement procedure. Look for the prescribed procedure or lot result as well.

### What proves that an entire eForms procedure ended without award?

A Result Notice covering the relevant scope should show that no winner was chosen and provide the applicable non-award reason. Verify the procedure and every lot affected.

### Is “no winner yet” the same as cancellation?

No. The eForms winner-status list distinguishes a closed competition with no winner from a competition that is still ongoing while no winner has yet been selected.

### Can one cancelled lot close the whole tender?

Only if the official decision covers the whole procedure or all lots. A result for one named lot must not be applied to unaffected lots.

### When is a later tender a confirmed replacement?

When the later procedure has its own verified identity and an official reference or buyer statement connects it to the discontinued scope. Similarity alone leaves it a candidate.

### Should the old notice be deleted after a correction?

No. Retain it as a historical node and link the consolidated current notice to it. The earlier values explain what changed and support audit.

### Does a procurement termination notice end an existing contract?

No. In the current UK regime it concerns a procurement that ends before contract entry. A contract termination notice belongs to the later contract stage.

### What should an agent do when official sources disagree?

Preserve both records, return status_conflict for the affected scope, stop irreversible workflow changes and route the evidence to the named reviewer.


## Primary sources

- [TED eForms FAQ on linked, changed and cancelled notices](https://docs.ted.europa.eu/eforms-common/FAQ/index.html), Publications Office of the European Union
- [TED eForms Change Notice schema and business terms](https://docs.ted.europa.eu/eforms/latest/schema/change-notice.html), Publications Office of the European Union
- [TED change and corrigendum justification codes](https://docs.ted.europa.eu/eforms/latest/reference/code-lists/change-corrig-justification.html), Publications Office of the European Union
- [TED winner-selection status codes](https://docs.ted.europa.eu/eforms/latest/reference/code-lists/winner-selection-status.html), Publications Office of the European Union
- [TED non-award justification codes](https://docs.ted.europa.eu/eforms/latest/reference/code-lists/non-award-justification.html), Publications Office of the European Union
- [Cabinet Office guidance on Procurement Termination Notices](https://www.gov.uk/government/publications/procurement-act-2023-guidance-documents-procure-phase/guidance-procurement-termination-notices-html), UK Cabinet Office
- [Procurement Act 2023, section 55](https://www.legislation.gov.uk/ukpga/2023/54/section/55), The National Archives
- [Open Contracting Data Standard release and amendment reference](https://standard.open-contracting.org/latest/en/schema/reference/), Open Contracting Partnership


## Related articles

- [How to verify that a tender is still open](https://zephior.com/insights/verify-that-a-tender-is-still-open)
- [Which language version controls when a tender is multilingual?](https://zephior.com/insights/identify-the-controlling-language-of-a-tender)
- [How to verify which legal entity is buying](https://zephior.com/insights/verify-the-contracting-authority)
- [Tender, grant, concession or market consultation?](https://zephior.com/insights/separate-procurement-notices-from-grants)