---
title: "What to do when tender websites show different deadlines"
description: "Reconcile competing tender deadlines by scope, source role, version and change evidence, then preserve or escalate every unresolved conflict."
canonical: "https://zephior.com/insights/reconcile-tender-deadlines-across-websites"
last-updated: 2026-09-03
---

# What to do when tender websites show different deadlines

> Reconcile competing tender deadlines by scope, source role, version and change evidence, then preserve or escalate every unresolved conflict.

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

## Definition

A deadline authority and discrepancy log is a dated comparison of every credible deadline observed for one identified procedure, response kind and lot. Each observation retains the source, source role, notice or document version, exact field or page, original wording, publication time and retrieval time. The log first tests whether the values concern the same event and can be shown to represent the same instant. It then follows explicit corrections, amendments and replacement links. A deadline is accepted only when procurement-specific evidence establishes why that value currently governs the defined response. If the evidence does not settle a material difference, the result is unresolved conflict, not a guessed deadline.

## Problem

A supplier may see 17 October on an aggregator, 18 October in the official notice, 21 October in the procurement portal and a revised date inside an addendum. Those values are not automatically four versions of the same fact. One may belong to a clarification period, another to a request to participate, another to a different lot and another to an obsolete notice. Two clock times may also express one instant in different zones. Copying the latest date is unsafe because publication time does not by itself establish authority. Copying the earliest date avoids one kind of lateness but can distort the work plan and does not answer which deadline the buyer set. The discrepancy must be explained before the date enters qualification, scheduling or submission controls.

## Point of view

Treat every displayed deadline as an observation, not as the answer. Fix the procedure, lot, supplier audience and response event before comparing values. Preserve source roles instead of ranking whole websites: a statutory notice may establish published notice data, while a designated portal may govern the operational receipt event under the tender instructions. Establish relationships through identifiers and explicit buyer-issued changes. Normalize times only after the source zone is supported. The output must show accepted, superseded and unresolved values separately, with the evidence for each treatment. An agent can collect and compare public evidence, but it must stop when access, identity, time zone, legal effect or buyer intent remains uncertain.

## Define the deadline before comparing dates

The comparison key is more specific than the tender title. It should contain the procedure identifier, current notice chain, lot or part, response event, eligible supplier group and receipt channel. “Response event” might mean a tender, request to participate, clarification question, revised proposal, auction response or market-engagement questionnaire. A page can be accurate for one event and dangerous when its date is borrowed for another. Preserve a null when the page does not identify the event. Do not fill the gap from its visual position or nearby wording.

Identity comes first because similar titles and buyer names can hide a rebid, replacement procurement or call-off. Use the source-authority work from the official-notice check and carry its identifiers into the discrepancy log. AN-023 begins once the records have a defensible relationship. It does not decide whether two similar opportunities are duplicates, and it does not establish the legal identity of the buyer. If the procedure or lot link is still provisional, the deadline result must remain provisional too.

**Comparison key for one deadline question**

| Field | Accepted evidence | Unsafe shortcut |
| --- | --- | --- |
| procedure_id | Official identifier or supported cross-reference | Similar title |
| notice_lineage | Notice and version identifiers with explicit links | Newest search result |
| scope | Exact lot, part or whole procedure | Parent-page date |
| response_kind | Buyer wording for the required response | Generic “deadline” label |
| supplier_context | Public or named invited audience | Assumed universal access |
| receipt_route | Channel named in current instructions | Website hosting the page |

## Keep the raw observations before interpreting them

Create one row per observed value, even when two rows look identical. Copy the date and time exactly, including punctuation, zone label, offset, language and any words such as “before,” “by” or “no later than.” Record the URL, document name, page or structured field, publisher, source role, notice ID, version, issue or publication time and `observed_at`. For a dynamic page, also record whether the display was public or authenticated and whether it declared that times were localized. Store a screenshot or permitted source file with a content fingerprint when practical, but never store credentials, session tokens or private URLs in the public record.

Source role belongs to a fact, not to an entire domain. A public journal can be the statutory publication point for notice data. The tender documents can state precedence and amendment rules. A designated portal can control the act of receipt if the instructions say so. A buyer news page may only announce the opportunity, while an aggregator is usually evidence of what it displayed, not of what the buyer currently requires. Record `authority_claimed` separately from `authority_established`. A logo, official-looking hostname or API field name does not prove that a source controls the deadline.

**One row in the deadline discrepancy log**

| Field | Example value | Purpose |
| --- | --- | --- |
| source_role | designated portal | Describes what the source does |
| location | Submission settings, Closing date | Makes the value findable |
| deadline_raw | 21 October 2026, 12:00 BST | Preserves buyer wording |
| published_at | 2026-09-12T08:14:00Z | Places the source in sequence |
| observed_at | 2026-09-13T09:05:00Z | Dates the retrieval |
| applicability | lot 2 tender receipt | Prevents scope transfer |
| evidence_url | Stable public notice URL | Supports later verification |

## Remove false conflicts without erasing the source text

Two values are only candidates for reconciliation after their keys match. First separate publication dates, enquiry cutoffs, participation requests, tender receipts, presentations and auctions. Then separate lots and supplier stages. A date on a summary card may omit the clock time; that makes it less precise, not necessarily contradictory. Keep both rows and label the relationship `partial_display` if the complete official value supports the same calendar date. Do not invent midnight, end of day or the buyer’s business hours to complete a date-only field.

Next test instant equivalence. A portal can display 12:00 London and the notice 13:00 Brussels on a date when those values represent the same instant. That conclusion requires supported zones and date-specific offsets. It cannot come from country names or the reviewer’s current clock. AN-035 owns ambiguous abbreviations, daylight-saving rules and conversion evidence. AN-023 consumes its verified instant and records the relationship as `equivalent_display`; it does not redo that work. If the zone is missing or disputed and the difference could affect timeliness, the result remains unresolved.

- Mark `different_event` when the dates govern different required actions.
- Mark `different_scope` when they apply to different lots or parts.
- Mark `partial_display` when one source omits detail but does not contradict the complete value.
- Mark `equivalent_display` only after both values resolve to the same supported instant.
- Keep `unresolved` when missing precision can change the operational decision.

## Use change lineage instead of page freshness

TED eForms change notices identify the notice and version being changed. The published change notice contains the original notice information with changes applied, and a later change notice consolidates earlier changes while describing the latest change in its change section. This supports a precise link from the older deadline to the revised value. It also explains why the visible date on a cached or secondary page can remain old. Record the changed notice identifier, affected section, change reason, publication time and new deadline field. Do not infer a deadline amendment merely because a later document has a later date.

Other systems express lineage differently. Current UK guidance says that when a covered procurement is modified in the relevant circumstances, the affected tender notice and associated tender documents must be updated and republished or provided again. Find a Tender’s OCDS release interface uses notice IDs and a procurement-process OCID, while its notice model can link edited versions. FAR 15.206 requires a solicitation amendment when the Government changes requirements or terms, and lists a revision to the solicitation closing date when applicable. These examples do not create one worldwide hierarchy. They show the evidence to seek: an authorized change, the object changed and the stated effect on the closing date.

**Minimum change link for a superseded deadline**

| Question | Required record |
| --- | --- |
| What changed? | Deadline field or cited instruction |
| Which source changed it? | Notice, addendum or amendment identifier |
| What came before? | Explicit previous notice or document version |
| What scope is affected? | Procedure, stage and lot |
| When did it take effect? | Publication or issue time plus stated rule |
| What value remains? | New raw deadline and supported instant |

## Accept a deadline only with procurement-specific grounds

The decision should use controlled states. `reconciled` means the observations now support one deadline for the comparison key. `superseded` applies to an older value tied to an explicit change. `separate_scope` keeps a valid date that belongs elsewhere. `unresolved_conflict` means material, credible evidence still disagrees. `source_unavailable` means a source named by the procurement cannot be inspected. `withdrawn` applies only when official evidence removes that response event. Each row keeps its status; the record never overwrites history with the accepted value.

No generic rule such as “the portal always wins” or “the PDF always wins” is safe. Read the tender’s own precedence, communication and amendment clauses. Determine what function each source is designated to perform, then cite the rule or buyer-issued link that settles this fact. A publication timestamp can order observations but does not alone prove legal effect. An API’s compiled value can be useful current-state evidence, yet OCDS also permits releases and a versioned record precisely because values change over time. If the chain or authority basis is incomplete, keep the conflict open.

**Decision states for the discrepancy record**

| State | Meaning | Downstream rule |
| --- | --- | --- |
| reconciled | One supported deadline governs the fixed key | May feed planning with citations |
| superseded | Explicit change displaced this older value | Retain as history |
| separate_scope | Value is valid for another event or lot | Route to that scope only |
| unresolved_conflict | Credible values disagree materially | Block silent use |
| source_unavailable | Named source cannot be inspected | Escalate access |
| withdrawn | Official evidence removes the response event | Route to status review |

## Protect the bid while the conflict remains open

An unresolved conflict needs an owner and a deadline of its own. Record the clarification cutoff, permitted buyer channel, access requirements, business impact and the latest safe time to act. Draft one question that quotes both source locations and values, identifies the procedure and lot, and asks the buyer to confirm the controlling deadline and time zone. An agent may prepare that draft. It may not create an account, accept portal terms, use someone’s credentials or send the question without authorization. Store the buyer’s response with its message identifier and propagate it as new evidence, not as an informal note.

Operationally, the team can adopt the earliest credible instant as a temporary risk envelope when an authorized owner chooses that control. Label it `internal_risk_limit`, never `buyer_deadline`. This may protect work from a late submission, but it must not become an unsupported claim about the procurement. If the conflict changes bid feasibility or the clarification channel has closed, escalate to the accountable bid owner and qualified counsel where needed. Do not assume a late-submission exception. EU rules, UK guidance and FAR examples all show that deadline changes follow particular legal and publication mechanisms; the supplier should expose the conflict rather than invent the missing act.

- Keep the buyer deadline field null while authority remains unresolved.
- Show any internal risk limit beside its owner and approval time.
- Block submission automation from consuming a provisional value.
- Recheck every named source after a buyer response or published change.
- Preserve the full evidence package for final receipt review.

## Return evidence that another agent can challenge

Lead with structured facts. The record should expose `comparison_key`, `observations`, `relationships`, `change_edges`, `decision_state`, `accepted_deadline`, `authority_basis`, `unresolved_questions`, `checked_at`, `valid_until` and `next_check_at`. Each decisive field needs a public citation or a precise private-source reference visible only to authorized users. Retain original-language text beside any explanation. Use nulls rather than guessed dates. A short human explanation can follow, but another agent should be able to reconstruct why a value was accepted without parsing persuasive prose.

Retrieval time is not publication time, and publication time is not necessarily effective time. Keep all three when available. Set `valid_until` according to decision risk and source volatility, then invalidate the record when a new notice, amendment, portal message or document appears. The output may feed opportunity qualification and schedule planning only when its state is reconciled and its validity window remains open. A submission agent must independently refresh the controlling source before acting and must still operate under explicit human authorization.

**Fictional agent-readable result**

| Key | Value |
| --- | --- |
| comparison_key | NTA/ICT/26/17, lot 2, tender receipt |
| decision_state | unresolved_conflict |
| observations | Official notice: 16 Oct; portal: 18 Oct |
| accepted_deadline | null |
| internal_risk_limit | 16 Oct, approved by bid owner |
| next_action | Authorized clarification quoting both fields |
| valid_until | Next source change or stated review time |

## Useful outcomes

- Every credible deadline remains traceable to its original source, scope, version and observation time.
- Values for other lots, stages or response events are separated instead of being treated as contradictions.
- Explicit amendments and notice-version links explain which older values were superseded.
- Equivalent local displays are reconciled only after a supported time-zone conversion.
- One accepted deadline reaches downstream systems when the evidence supports it.
- An unresolved material conflict blocks silent calendar updates and prompts authorized clarification.

## Workflow

1. **Freeze the comparison question.** Name the procedure, notice chain, lot, response kind, supplier audience and checked time. Do not compare dates until those fields match.
2. **Capture each value as published.** Record the page or field, exact date and time text, source role, identifiers, version, publication time, URL and retrieval time without correcting the value.
3. **Test scope and instant equivalence.** Separate other stages and lots, then determine whether remaining values express the same instant. Route unresolved zone questions to the dedicated time-zone check.
4. **Follow the change chain.** Use explicit previous-notice, changed-notice, amendment and buyer references. Record the stated effect on the deadline rather than assuming the newest page replaces everything.
5. **Publish the decision or stop.** Accept a value with cited grounds, or mark the conflict unresolved, set a risk envelope and prepare a focused clarification for an authorized person to send.

## Key decisions

- Do all observations concern the same procurement procedure and notice lineage?
- Does each value apply to the same lot, response kind and supplier audience?
- Are different displays equivalent once an independently supported zone is applied?
- Does an official change identify the earlier notice, version or document it changes?
- Do the tender instructions assign an operational role to the portal deadline?
- Is the evidence strong enough to mark one value accepted and another superseded?
- Would the unresolved difference change qualification, planning or timely receipt?
- Who is authorized to seek clarification or approve a temporary internal risk envelope?

## Risks

- A search result may retain a date copied before an official correction.
- A newer publication may concern another stage rather than revise the tender deadline.
- A procedure-level date may be applied to a lot with its own receipt cutoff.
- A clarification or participation deadline may be mislabeled as the tender deadline.
- A portal may localize a time while a PDF shows the source zone.
- A consolidated notice may hide the old value unless its change link is inspected.
- A login-only message may contain a change that public pages do not expose.
- The team may repeat an unproved date until repetition is mistaken for authority.

## Metrics

- deadline observations with exact source, field, version and retrieval time
- values separated because their lot or response scope differs
- superseded values connected to explicit change evidence
- equivalent displays independently reconciled to one supported instant
- accepted deadlines with a stated procurement-specific authority basis
- unresolved conflicts open before the clarification cutoff
- downstream calendars and plans linked to the current decision record
- rechecks completed after notices, portal messages or documents change

## Frequently asked questions

### Should we always use the earliest tender deadline?

No. The earliest credible instant can be an approved internal risk limit while a conflict is investigated, but it does not become the buyer’s deadline. Establish the governing value from the procurement’s sources and change rules.

### Does the procurement portal deadline override the PDF?

Not automatically. Check what the tender instructions say about the portal, document precedence, amendments and receipt. Preserve both values and seek authorized clarification if those rules do not settle the conflict.

### Can the newest web page be treated as the current source?

Publication order is useful evidence, but freshness alone does not establish scope or authority. Require a notice-version link, amendment, updated document or other buyer-issued evidence showing what the new page changes.

### What if two websites show different times but the same date?

Test whether they display one instant in different time zones. Preserve the raw values and use the dedicated time-zone review. If either zone is unsupported and the difference affects timeliness, keep the conflict unresolved.

### Is an aggregator deadline ever enough?

It can support discovery and show what the aggregator displayed at a stated time. It should not become the operational deadline without current buyer or official evidence tied to the same procedure, lot and response event.

### Should an old deadline be deleted after an amendment?

Keep it as a superseded observation. Link it to the amendment or changed notice, record the affected scope and prevent it from feeding current calendars. The history proves why the accepted value changed.

### Can an agent resolve the discrepancy without a person?

An agent can retrieve public records, compare identifiers, follow explicit changes and reconcile supported instants. It must stop at login, missing authority, disputed interpretation, buyer contact, calendar approval or submission.

### When should the deadline record be checked again?

Recheck after any notice, amendment, clarification, portal message or document update, before material resource commitment, and again before submission. Store a specific next-check time rather than claiming continuous monitoring.


## Primary sources

- [TED eForms change notices](https://docs.ted.europa.eu/eforms/latest/schema/change-notice.html), Publications Office of the European Union
- [TED notice and version identifiers](https://docs.ted.europa.eu/eforms/latest/schema/notice-information.html), Publications Office of the European Union
- [TED deadline for receipt of tenders, BT-131](https://docs.ted.europa.eu/eforms/latest/reference/business-terms/BT-131.html), Publications Office of the European Union
- [Directive 2014/24/EU, Article 47](https://eur-lex.europa.eu/eli/dir/2014/24/2024-01-01/eng), EUR-Lex
- [Guidance on modifying a competitive procurement](https://www.gov.uk/government/publications/procurement-act-2023-guidance-documents-procure-phase/modifying-a-competitive-procurement-html), UK Cabinet Office
- [Find a Tender open contracting data](https://www.gov.uk/government/publications/open-contracting), UK Cabinet Office
- [OCDS updates and amendments](https://standard.open-contracting.org/latest/en/guidance/map/amendments/), Open Contracting Partnership
- [OCDS record and version history](https://standard.open-contracting.org/latest/en/schema/records_reference/), Open Contracting Partnership
- [FAR 15.206, amending the solicitation](https://www.acquisition.gov/far/15.206), Acquisition.gov


## Related articles

- [What should you do when dates inside the RFP conflict?](https://zephior.com/insights/resolve-inconsistent-rfp-dates)
- [Do all tender lots share the same deadline?](https://zephior.com/insights/verify-lot-level-tender-deadlines)
- [Which time zone controls a tender submission deadline?](https://zephior.com/insights/resolve-a-tender-deadline-time-zone)
- [Tender published: are the bid documents available?](https://zephior.com/insights/distinguish-notice-publication-from-document-release)