UK Tender Deadline & Cancellation Changes

See which published deadlines or statuses changed before updating your bid calendar. This Actor compares official UK Find a Tender notice histories for a procurement watchlist and returns one evidence row per changed notice.

Start with the prefilled historical example, then replace the procurement ID and change window with your own. You receive the old value, new value, publication time, exact source links and source hashes. A deadline changing from16 October 2026 at 12:00 BST to30 October 2026 at 12:00 GMT is a real example in the supplied history; it is not a fabricated demo or a promise of future results.

Price and output

0.02 USD per delivered changed-notice row. No Actor start fee. An unchanged notice, invalid input or unavailable source produces no new paid row. One notice with both a deadline and status change is one row. maxEvents limits row count;100 rows cost at most 2 USD in Actor event charges. Apify account and platform terms apply. This is payment for automated comparison and structured output; the underlying government data is free.

Use the Changes output for the dataset. Read the Status output before relying on a run: CHANGES, NO_NEW_CHANGES, PARTIAL, INVALID_INPUT, UNKNOWN and DELIVERY_UNKNOWN have different meanings. A successful container exit alone does not mean source coverage was established. If any requested history cannot be fetched or interpreted, no new rows are pushed for the watchlist. A delivery error can be ambiguous: inspect the dataset before retrying.

Inputs and repeated runs

Supply 1–100 ocds-h6vhtk-xxxxxx identifiers from Find a Tender and a timezone-aware publishedAfter timestamp. Only changes published strictly after that time are eligible. The API history supplies earlier values for comparison.

Copy nextSeenEventIds from OUTPUT into seenEventIds on the next run, keeping the same change window while retrieving remaining rows. This suppresses repeat charges for those delivered events. Separate runs do not automatically share history. Omitting previously delivered IDs may charge for the same historical change again. Keep at most4,500 seen IDs; archive a completed window before advancing it. A capped or partial batch does not justify advancing the timestamp past undelivered events.

What the comparison means

• Timezone-equivalent instants do not produce a deadline change. Small published corrections remain small deltas, not urgency claims.
• Date-only deadlines keep their original precision. Switching between a date and a timestamp is marked PRECISION_CHANGED, without an invented time difference.
• Omitted fields retain the last explicit observation. An explicit null breaks that comparison chain and is flagged as uncertain.
• Cancelled or withdrawn status changes are reported as published. The Actor does not infer that a tender is open, that a bid is eligible, or that a deadline can safely be relied on without checking the official notice.

The watchlist is limited to this official source, 1,000 releases and 10 MiB per procurement, 20 MiB per run and a 65-second retrieval budget. Oversized, incomplete or contradictory histories produce UNKNOWN. No attachments, amendment PDFs, bid submission, notifications, buyer-account login or arbitrary-site scraping are included. Native portal alerts may be sufficient if you do not need structured old/new values across a watchlist.

Source and support

Source: UK Find a Tender API. Contains public sector information licensed under the Open Government Licence v3.0. This product is independent of the Cabinet Office.

Use the Actor's Issues tab for reproducible errors. Include the run ID and procurement ID; do not post credentials or confidential bid material. No uptime, response-time, tender-win or business-outcome guarantee is made.