A dated open-status check is a reproducible decision about one procedure, lot and response kind at one stated instant. It records the official notice and operational portal examined, their versions and observation times, the stage that currently invites a response, the deadline exactly as published, any defensible normalized timestamp, relevant changes or termination records, and the availability of the designated response channel. The decision uses one controlled result: open-confirmed, not-open-yet, closed, cancelled, superseded, access-limited, conflicted or unknown. “Open” is incomplete without the response object. A procedure may be open for requests to participate but not for tenders, or a dynamic market may accept membership applications while a particular call-off remains restricted. The check therefore states who may provide what response, for which lot, through which channel and until when.
Search services collapse several different ideas into labels such as active, live or open. TED explains that its active scope includes recent planning notices and result notices as well as competition notices whose deadline has not passed. The SAM.gov opportunities API distinguishes active from archived, yet its own example returns an active award notice with no response deadline. A future date can also survive beside a later cancellation, apply to another lot, name a clarification cutoff, or belong to an earlier version. Conversely, a competition may still accept requests even when an index has archived the record. A team that copies the badge and date into its pipeline can mobilize against a closed procedure or reject a valid opportunity. Current status has to be proved from the procedure’s notice stage, explicit status, latest relevant change, exact response deadline and designated channel at the time of the check.
Use the source-authority record first, then answer a narrow question: can this supplier make this defined response for this exact lot now? Treat status labels and dates as separate evidence. A valid invitation identifies the response stage; a current official record establishes whether that stage continues; the controlling deadline places the observation inside or outside the window; changes, cancellation and replacement evidence can override an earlier invitation; and the response channel shows whether the route is operationally available. None of those facts proves the others. Preserve the words and timestamps used by the publisher, and calculate an instant only when the time zone is explicit or has already been resolved. An agent may retrieve public records, follow official identifiers, compare versions and return a bounded state. It must abstain when the lot, time zone, change lineage or official sources remain uncertain. It may not create an account, accept portal terms, use credentials, contact the buyer or submit anything without separate authority.
State model
Define open for one response, lot and instant
A tender is not open in the abstract. It is open to a particular class of supplier for a particular act. In a single-stage open procedure, that act may be submitting a tender. In a selective or flexible procedure, the public stage may accept requests to participate while the later tender round accepts submissions only from invited suppliers. A dynamic market can remain open to membership without making each procurement under it public to every supplier. Write the question in full before researching: “At 14:10 Europe/Zurich on 3 September 2026, may an eligible supplier submit a request to participate for lot 2 of procedure X through the designated channel?”
The result should describe the observed state, not predict what the buyer intended. Open-confirmed requires compatible evidence from the invitation stage, the latest official current-state record, a response window containing the checked instant and the designated route. One explicit closing event can defeat several weak positive signals. A termination notice overrides a stale search card. An award notice does not become a competition because an API calls it active. Where an inaccessible portal prevents the route check, the correct result is access-limited, not open-confirmed and not closed.
Controlled states prevent soft language from leaking into downstream work. They also make rechecks possible. Closed means the verified deadline passed without evidence of an extension. Cancelled requires explicit official cancellation or termination evidence for the relevant scope. Superseded requires a supported replacement relationship. Conflicted means material official evidence disagrees. Unknown means the evidence is missing or cannot yet support any narrower result. Each state carries a reason and expires when its evidence becomes too old for the next decision.
| State | Minimum basis | What it permits | Required next action |
|---|---|---|---|
| open-confirmed | Current invitation, applicable future deadline, no defeating notice and usable designated route | Proceed to qualification for the named response only | Recheck on update and before material bid investment |
| not-open-yet | An official future invitation or start condition is identified | Monitor, but do not prepare as a live submission | Recheck at the stated trigger |
| closed | Applicable verified deadline has passed and no extension is found | No submission under the expired stage | Watch only for an official reopening or new procedure |
| cancelled | Official cancellation or termination covers the procedure or lot | Stop bid work for the cancelled scope | Preserve the notice and check for an explicit successor |
| superseded | An official link identifies a replacement or controlling later procedure | Do not use the earlier record operationally | Run a new check on the successor |
| access-limited | Identity is known, but a required official source or route cannot be lawfully inspected | No confident open or closed decision | Route access to an authorized person |
| conflicted or unknown | Official evidence conflicts or remains insufficient | No downstream reliance on the disputed state | Preserve both values and escalate the named gap |
Scope
Freeze identity before asking for current status
Start with the source-authority record, not a new keyword search. Copy the procedure identifier, notice identifier and version, buyer reference, contracting authority, lot or part, jurisdiction and stable public links. Then add the supplier context and response kind. If the opportunity was discovered on an aggregator, retain that URL as provenance but do not use its badge as current-state evidence. If the identity record is unresolved, stop. A status check cannot repair a mistaken merge between a planning notice, a competition and an award.
Time needs the same discipline as identity. Record `checked_at` as a full timestamp with an offset, plus the human-readable zone used for the decision. Record `observed_at` separately for each source because a notice page and a portal may be fetched minutes apart. Preserve any source update time as `source_updated_at`; do not substitute it for your observation. Relative phrases such as today, two days left or recently closed are copied only as source text. They never become the decision clock.
Near a deadline, clock uncertainty is material. A date with no time does not prove that a window remains open through the end of the supplier’s local day. A time with no stated zone cannot safely be normalized from the buyer address or browser locale. Route that issue to the dedicated deadline time-zone review. Until it is resolved, use conflicted or unknown if the ambiguity can change the result at the checked instant.
| Field | Record | Do not infer |
|---|---|---|
| subject | Procedure, notice, version, buyer, lot and response kind | Scope from the title alone |
| checked_at | Decision instant with numeric offset | A hidden server or browser time zone |
| observed_at | Fetch time for each cited page or endpoint | That all sources were seen simultaneously |
| deadline_as_published | Exact date, time, zone and label from the source | That a displayed date is the submission cutoff |
| deadline_instant | Normalized instant only after the zone is supported | A zone from geography or language |
| supplier_context | Public applicant, invited participant or named membership class | That every supplier has the same right to respond |
Invitation
Prove what the current publication invites
Classify the formal stage before reading the date. Planning, preliminary engagement, competition, result, award, contract modification and termination records can all remain searchable. Only some invite a supplier response, and even then the response may not be a tender. TED’s own help describes active notices as a search range that includes planning notices from the past 364 days, competition notices with unpassed deadlines and result notices from the past 99 days. The label is useful for retrieval, but it cannot stand in for the notice type.
Write the invitation as a verb and object taken from the current official record: submit a tender, request participation, confirm interest, apply to a qualification system, register for a market event, or no response invited. Then record the eligible audience. UK guidance says publication of a tender notice formally begins the procedure and invites either tenders or requests to participate. Find a Tender separately describes UK1 pipeline, UK2 market engagement, UK3 planned procurement, UK4 tender, UK6 award and UK12 termination notices. A future deadline on UK3 does not turn it into UK4.
APIs require the same reading. In OCDS, `tender.status` has values such as planning, planned, active, cancelled, unsuccessful, complete and withdrawn, while `tenderPeriod` is the period during which submissions are open. In SAM.gov, `active` means active rather than archived, and the payload separately exposes current notice type and response deadline. The documented example of an active award notice with a null response deadline shows why an agent must test the fields together instead of mapping one boolean to open-confirmed.
| Signal | Question answered | Cannot prove by itself |
|---|---|---|
| Notice type | What lifecycle event was published | That its window is current |
| Displayed status | How that source classifies the record | The meaning used by another source |
| Deadline field | A labelled time limit for some event | Correct stage, lot or current version |
| Search scope or badge | Why the record appears in retrieval | A legal or operational right to respond |
| Portal action | What the current interface offers | Why it is offered or which notice controls |
| Award or termination record | A later lifecycle event | Its scope without checking procedure and lot links |
Lineage
Look for evidence that defeats an earlier invitation
Reopen the latest version through the official identifier and inspect linked changes after the original publication. TED’s eForms model treats a change notice as consolidated text: it contains the initial notice with changes applied and identifies the notice version being changed. A change can alter notice fields or signal changed procurement documents. The model also allows cancellation and intent-to-cancel reasons. That means the earlier notice remains evidence of history, while the current-state check must use the consolidated current publication and preserve the relationship to its predecessor.
Search for explicit defeating events: cancellation of the procedure, cancellation or cessation of the relevant lot, a procurement termination, an unsuccessful result, completion of the tender stage, or a supported replacement process. UK termination guidance says the notice informs the market that the authority decided not to award and terminate the procurement; it also requires the termination notice to refer to the originating notice. FAR 15.206 requires a solicitation amendment when requirements or terms change and includes a revised closing date where applicable. If a proposed amendment is so substantial that a new competition is needed, the provision calls for cancellation and a new solicitation. These are stronger signals than an unchanged card.
Do not turn this check into the full amendment register planned for a separate workflow. Record only the changes required to determine current status: changed notice or solicitation identifier, publication time, affected procedure or lot, stated effect on the invitation, and deadline or cancellation consequence. If the chain has a missing link, preserve the gap and return conflicted or unknown. If the official source explicitly identifies a successor, return superseded and run a separate status check on that successor rather than transferring the old deadline.
Operational check
Test the clock and response route together
Choose the deadline that matches the response kind and scope. A procedure can show separate cutoffs for clarifications, requests to participate, tenders, auctions and presentations. TED eForms models a tender-receipt deadline and a participation-request deadline at lot level as separate date and time components. The working comparison should retain the original text and field, then compare `checked_at` with a supported normalized instant. Equality at the cutoff is not a safe assumption; use the portal and governing instruction, and flag any precision gap.
The designated channel supplies operational evidence. Confirm that its buyer reference, procedure and lot agree, and that it exposes the relevant response action. A requirement to sign in does not mean the competition is closed, but it can prevent a public agent from proving route availability. Record public landing-page status separately from authorized-account status. If the team has not lawfully checked the gated view, return access-limited. Do not ask an agent to register, accept contractual terms, reset credentials or test an upload in another person’s account.
Document access is adjacent but narrower work. EU Directive 2014/24 requires unrestricted direct electronic access to procurement documents in the usual case and provides for other access arrangements in stated exceptions. It also requires extensions where significant changes are made to procurement documents. UK time-period guidance likewise connects the start of tendering to the invitation and says modifications can require revised deadlines. For this status decision, record whether the response route and necessary current pack are available enough to support the open claim. A detailed pack-release diagnosis belongs in AN-025, and a conflict between two deadline displays belongs in AN-023.
Agent contract
Return evidence, contrary evidence and an expiry
An agent-facing result should be data before it is prose. Keep stable keys, original-language values and nulls for missing facts. Every decisive value needs a source URL, source role, field or quoted location and observation time. Separate `displayed_status` from `decision_state`; separate `deadline_as_published` from `deadline_instant`; separate `evidence_for` from `evidence_against`. The short explanation can then be regenerated or localized without changing the underlying judgment.
The record needs a validity boundary. A check made three weeks before a deadline may support initial qualification, but it should not authorize submission-day assumptions. Set `valid_until` or `next_check_at` from the procedure’s volatility: immediately after an official update, daily for a live high-priority opportunity, and again before resource commitment and submission. Do not imply that a source was monitored continuously unless a real monitor and event log exist.
Tool permissions belong in the result. Public retrieval, identifier search, format comparison, explicit link following and time calculation from an established zone are allowed. Login, account creation, acceptance of terms, buyer communication, legal interpretation and submission are reserved actions. When evidence crosses one of those boundaries, the agent returns the partial record and names the human action needed. Abstention is a valid result when it protects the pipeline from a fabricated answer.
| Field group | Required values | Why an agent needs it |
|---|---|---|
| subject | Jurisdiction, buyer, procedure, notice/version, lot, response kind, supplier context | Prevents facts from crossing scopes |
| clock | Checked instant, decision zone, per-source observation times | Makes current a reproducible statement |
| invitation | Notice type, invitation wording, eligible audience, start condition | Defines the act being tested |
| deadline | Published value, source field, normalized instant or null, resolution note | Supports a bounded time comparison |
| lineage | Relevant change, cancellation, termination or replacement references | Exposes events that defeat old evidence |
| route | Designated channel, public visibility, authorized access state, response action | Separates formal and operational availability |
| decision | Controlled state, reason, evidence for, evidence against, confidence boundary | Allows review without accepting a bare label |
| expiry | Valid-until time, trigger, owner and next action | Prevents stale status from becoming a standing fact |
Worked example
A future deadline does not rescue a cancelled lot
A fictional supplier finds Northbridge Transit Authority procedure NTA-26-114 in a commercial index. The card says active and displays 18 September 2026. The source-authority record already links it to a formal competition notice and the buyer-designated portal. The team asks about a tender for lot 2 at 10:30 Europe/London on 3 September. The original official notice invited tenders for two lots and showed 18 September at 12:00 Europe/London. The latest linked change notice extends lot 1 to 25 September but marks lot 2 as cancelled. The portal’s public page shows the same two-lot procedure and no submission action for lot 2.
The result for lot 2 is cancelled. The index badge, future original deadline and open lot 1 do not create contrary authority for lot 2. The record cites the original invitation as historical evidence, the latest changed-notice identifier and cancellation field as defeating evidence, and the portal observation as operational confirmation. It stores 18 September only as a superseded lot-2 value. No bid team is assigned.
A separate question about lot 1 would receive its own record. If the latest notice clearly preserves the invitation, the extended deadline is normalized from its explicit zone, and the designated portal exposes the lot-1 submission action, the state can be open-confirmed for a tender to lot 1. That decision says nothing about supplier eligibility or response feasibility. Those are later qualification decisions.
| Observation | Value | Effect |
|---|---|---|
| Search index | Active; 18 September 2026 | Discovery evidence only |
| Original competition notice | Tenders invited for lots 1 and 2 | Historical positive evidence |
| Latest official change | Lot 1 extended; lot 2 cancelled | Defeats the earlier lot-2 invitation |
| Designated portal | Procedure visible; no lot-2 response action | Consistent operational evidence |
| Decision | cancelled for a lot-2 tender at the checked instant | Stop work and preserve the evidence chain |
What good looks like
Useful outcomes from verify tender is still open
- One procedure, lot and response kind are fixed before status evidence is collected.
- The check carries an exact observation time and time zone instead of the word current.
- Notice stage, displayed status, deadline and response-channel state remain separate facts.
- The latest relevant official change or termination record is examined without erasing earlier evidence.
- A future deadline is rejected as sufficient proof when the notice does not invite the response in question.
- The result uses a controlled state with supporting evidence, contrary evidence and an explicit confidence boundary.
- Access, source and time-zone gaps stop a confident open result and receive an owner and recheck time.
- Another person or agent can repeat the decision from stable links, identifiers, source fields and timestamps.
Operating model
How to run the work
- 01
Fix the subject and the clock
Name the procedure, notice, lot, supplier context and exact response being tested, then record the check time with its time zone.
- 02
Reopen the official sources
Use the statutory publication and buyer-designated operational portal from the source-authority record. Retrieve them in a clean session and record each observation time.
- 03
Classify the invitation stage
Determine whether the current notice invites a tender, request to participate, expression of interest, qualification application or no supplier response.
- 04
Follow current-state evidence
Inspect explicit status, latest versions, changed-notice references, cancellations, termination notices and replacement links for the same procedure and lot.
- 05
Test the window and route
Compare the verified current instant with the applicable deadline, then confirm that the designated response channel still exposes the relevant procedure and action.
- 06
Issue and schedule the decision
Return one controlled state, cite evidence for and against it, state every unresolved field and set the next check according to volatility and deadline proximity.
Evaluation
Questions that change the decision
- Which procedure identifier, notice version and lot define the subject of this check?
- What response is being tested: tender, participation request, interest, qualification or another named submission?
- Does the current notice type formally invite that response, or is it planning, award or contract information?
- Has the response period begun for this supplier and stage?
- What is the deadline exactly as published, including date, time, time zone and lot scope?
- Has a later official notice, portal message or consolidated version changed that deadline or status?
- Is there explicit cancellation, termination, unsuccessful outcome, completion or replacement evidence?
- Does the designated channel expose the same procedure, lot and response action?
- Do official sources agree strongly enough to make a current operational decision?
- When must the state be checked again, and who owns any access or authority gap?
Failure modes
Where teams lose control
An active search scope can contain a planning notice or recent result that accepts no bid.
An API value can mean not archived rather than open for the response under review.
A future date can be a clarification, participation, auction or award date instead of the tender deadline.
A deadline can belong to the parent notice or another lot.
An older notice can remain public after a change, cancellation or replacement.
A staged procedure can be public while the current tender round is invitation-only.
A date without a resolved time zone can cross the cutoff differently for supplier and buyer.
A public notice can remain visible while the designated portal no longer exposes the response action.
A temporary portal failure can be mistaken for formal closure, or formal closure for a temporary fault.
A confident label can conceal an official conflict that requires buyer clarification or legal review.
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.
- checks with procedure, notice, version, lot and response kind fixed
- decisions carrying a machine-readable checked-at instant and stated time zone
- official observations with stable URL, source role, field and retrieval time
- deadlines preserved both as published text and as a normalized instant when justified
- open-confirmed results supported by stage, status, time and route evidence
- cancellation, change and replacement records reviewed before mobilization
- access-limited, conflicted and unknown results assigned to an owner
- status decisions independently reproduced without a search result
- decisions rechecked after their scheduled expiry or an official update
Questions
Common questions
Does an active tender badge mean I can still submit?
No. Active can be a search or archival state. Verify the notice type, exact response stage, lot, current deadline, later changes and designated submission route before calling the opportunity open.
Is a future deadline enough to prove that a tender is open?
No. The date may apply to another event, lot or older version, and a later notice may cancel or replace the invitation. It becomes useful only after its label, scope, version and time zone are verified.
Can a tender be open for participation but not for bids?
Yes. Multi-stage procedures can first invite requests to participate and later invite tenders only from selected suppliers. State the response kind and supplier context in every result.
What if the notice is public but the portal requires a login?
A login requirement does not by itself close the procedure. A public agent should record the restriction and return access-limited unless an authorized user confirms the relevant lot and response action inside the account.
Should a temporary portal error be marked closed?
No. Preserve the error, time and public notice evidence, then classify the route as access-limited. Closed needs deadline or explicit official lifecycle evidence, not an assumed meaning for a technical failure.
Which source controls when the notice and portal disagree?
Use the documented source roles and any explicit change relationship. If two official sources still disagree on a material status or deadline, return conflicted and use the dedicated discrepancy workflow or authorized clarification.
How often should an open-status check be repeated?
Recheck after every official update, before committing substantial bid effort, and again near submission. The record should carry its own next-check time rather than claim permanent validity.
Can an AI agent perform this check without human involvement?
It can inspect public evidence and issue a bounded state when the chain is complete. It should stop at logins, ambiguous time zones, missing lineage, official conflicts, buyer communication, legal interpretation and any submission action.
Sources
Primary references
- TED search and browse help, including active scope and latest versions Publications Office of the European Union
- TED eForms schema usage for deadlines, change notices and cancellation reasons Publications Office of the European Union
- Directive 2014/24/EU on time limits and access to procurement documents European Union
- Find a Tender notice types and lifecycle sequences UK Cabinet Office
- UK Procurement Act guidance on time periods UK Cabinet Office
- UK Procurement Act guidance on procurement termination notices UK Cabinet Office
- SAM.gov Get Opportunities public API documentation U.S. General Services Administration
- Open Contracting Data Standard schema and tender status model Open Contracting Partnership
- Federal Acquisition Regulation 15.206 on solicitation amendments U.S. General Services Administration
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.