What should you do when dates inside the RFP conflict?

Event identity

Name the procurement event before comparing its date

A date has no operational meaning by itself. "18 November" can be the last day for questions, the deadline for requests to participate, the tender receipt date, the public opening date or the start of a standstill period. A conflict exists only when two incompatible assertions govern the same act for the same in-scope bidder. Start the log with an event key, not a calendar value.

The EU eForms vocabulary makes this separation concrete. It assigns distinct business terms to the additional-information deadline, tender receipt deadline, request-to-participate deadline, answer deadline, public opening date and tender-validity duration. Those labels are specific to eForms, but the modelling lesson travels: a date field needs an event type. Two dates under different business terms are not contradictory merely because somebody called both of them "the deadline" in a summary.

Event identity also carries scope. A date may apply to one lot, one stage, one response object, one invited supplier group or one physical delivery. Ask who must do what, to which object, through which channel, under which condition. If any of those dimensions differ, keep separate records. If the text is too vague to answer, use `event_identity_unresolved`; do not place the assertion in the nearest familiar bucket.

AN-075 will turn confirmed milestones into a bidder timetable. AN-026 owns lot-by-lot deadline proof. AN-073 stops earlier. Its work is to decide whether the source assertions are comparable and whether an inconsistency is resolved well enough to hand onward.

Evidence capture

Keep the source assertion intact before parsing it

Create one row for every material occurrence, including repeated values. Record `assertion_id`, source document, version or checksum, exact quotation, surrounding heading, printed or rendered page, clause or cell, issued language, retrieval time and access state. Add a machine-recoverable selector such as quote plus context, structural path, table coordinate or portal field identifier. The visible locator helps a reviewer find the text; the selector helps an agent recover the same occurrence. Neither proves authority.

Keep the raw expression beside parsed fields. For "03/04/2027 at noon", store the string unchanged and leave month and day unresolved until the document locale or an explicit convention settles them. RFC 3339 explains why slash-form dates are unsuitable for global interchange and why including both weekday and calendar date can create redundant information that disagrees. Use its timestamp syntax only as a technical representation after the buyer's meaning is established. It cannot decide whether the buyer meant 3 April or 4 March.

Do not discard awkward expressions. "The second business day following the briefing", "no later than 48 hours before tender close" and "the week that starts on 7 June" are rules or intervals, not fully qualified timestamps. Capture their anchor, offset, unit, inclusion rule and calendar only when the package states them. If "working day" is undefined, the derived date remains unresolved even when a spreadsheet can produce a number.

Preserve contradictions inside one occurrence as two components. "Tuesday, 18 November 2026" contains a weekday and a calendar date that do not agree. The parser may verify the calendar arithmetic, but it must not repair the issued text. Store the mismatch as `weekday_date_mismatch` and send it to review. A silent correction destroys the evidence needed for a precise clarification.

Diagnosis

Classify the inconsistency instead of forcing one winner

Start with compatibility. Two statements can both be true when they concern different events, scopes or precision. "Questions by 10 May" and "tenders by 24 May" is `not_a_conflict`. A date-only schedule and a detailed clause giving the same date plus 12:00 may be compatible if the schedule does not claim a different time. Record the relationship; do not promote the shorter display into a separate deadline.

A same-event conflict exists when comparable assertions cannot both govern. Useful types include `different_calendar_date`, `different_time`, `date_format_ambiguous`, `weekday_date_mismatch`, `absolute_relative_mismatch`, `amendment_not_propagated`, `source_version_unclear` and `chronology_inconsistency`. The last type catches sequences that violate an explicit dependency, such as a mandatory site visit scheduled after the offer deadline or an answer period ending before the pack says questions will be answered.

Materiality belongs on the conflict, not on the source. A one-day difference in a nonbinding estimated award month may have little effect; a ten-minute difference in tender receipt time can decide whether a submission is late. Record the affected decision, earliest plausible constraint, preparation dependency and escalation cutoff. Avoid a generic high, medium or low label without an operational reason.

Some findings must route elsewhere. A disagreement between two websites belongs to the cross-site discrepancy process. A missing amendment number belongs to amendment-chain verification. An agreed date with an unclear zone belongs to final timestamp resolution. A conflict about which whole document controls belongs to the source-authority process. The date log links those records rather than duplicating their conclusions.

Authority

Resolve only when buyer-issued evidence reaches the disputed event

Look first for an explicit replacement. An addendum that says "the tender receipt deadline in section 2.4 is replaced by 24 April at 12:00" identifies the proposition and new value. Record the addendum identifier, affected section, scope and effective issue. Do not rewrite unrelated dates. FAR 15.206 is a bounded US federal example: it requires solicitation changes to be made by amendment and says an amendment should identify any revision to the closing date. The rule supports change tracing in that regime, not a universal hierarchy for every RFP.

The World Bank's September 2025 Procurement Regulations provide another scoped model. Sections 5.30 and 5.31 say clarifications and addenda are in writing, modifications to issued procurement documents are introduced by written addendum, and the submission deadline should be extended if necessary. The useful lesson is evidential: a bidder should connect the changed date to the issued addendum. It should not infer a new date merely because the change seems to require more time.

Current UK guidance under the Procurement Act 2023 says affected tender documents must be updated and republished or provided again for early-stage modifications, and that an authority must consider whether deadlines need revision after a modification. EU Directive 2014/24/EU, Article 47, requires extensions in specified cases involving late additional information or significant procurement-document changes. These sources describe duties in their regimes. They do not authorize a supplier to calculate and substitute the extension itself.

An amendment is not a universal eraser. FAR 52.215-1 says unchanged terms remain unchanged when that provision applies. TED eForms Change notices reproduce a consolidated notice and identify their parent version, but that publication model does not prove that a separate tender annex was replaced. Apply explicit scope and the package's incorporated precedence rules. If an official clarification only explains that the schedule date is correct, record whether the procurement gives that clarification authority to change the documents. Explanation, correction and formal amendment are not interchangeable by default.

• Prefer an exact replacement statement tied to the disputed event.
• Limit every resolution to the lot, stage, document and audience it covers.
• Keep superseded assertions in the history instead of deleting them.
• Require a reviewer to approve material authority conclusions.
• Return `human_review_required` when the package does not settle legal effect.

Worked example

Reconcile a fictional campus transport RFP without inventing a deadline

A university issues an RFP for campus shuttle operations. The cover sheet says questions close on 8 April 2026. The procurement schedule lists proposal delivery on 22 April and public opening on 23 April. Clause 1.6 says, "Proposals must be received by Wednesday, 22 April 2026 at 12:00 local time." Addendum 02 later states, "The proposal receipt date in clause 1.6 is changed to Friday, 24 April 2026 at 12:00; all other milestones remain unchanged." An appendix still shows 22 April, and a site-access form says it must arrive five working days before proposal delivery.

The questions date, proposal date and opening date receive different event keys. They do not conflict with one another. Before the addendum, the schedule, appendix and clause agree on 22 April. Addendum 02 creates a new assertion for the same proposal receipt event and expressly replaces the value in clause 1.6 with 24 April. If the package's change and precedence rules make Addendum 02 controlling for that proposition, the team can resolve proposal receipt to 24 April. The 22 April occurrences remain linked as superseded evidence rather than being deleted, and the phrase about unchanged milestones prevents the public opening date from moving by inference.

The weekday in clause 1.6 is correct for 24 April 2026, but the phrase "local time" is not enough to produce a globally unambiguous instant. That issue moves to the time-zone dossier. The site-access form creates a dependent relative date. The team must find the package's definition of working day and decide whether Addendum 02 changes the anchor used by the form. If no definition or scope rule settles it, the derived date is `unresolved_material_conflict`, even though the proposal receipt date itself may be resolved.

The log therefore releases one reviewed assertion for proposal receipt, preserves two stale-looking but still inspectable occurrences, separates the public opening event, and sends one precise question about the site-access form. It does not publish 22 April as a fallback official deadline. The bid team may keep an internal readiness target before both plausible site-form dates, labelled `internal_contingency`, until the buyer answers.

Escalation

Ask the buyer to settle one proposition, then protect the bid without misquoting the answer

A useful clarification question names the procurement, lot, event, conflicting sources and exact values. It asks which date governs and whether dependent dates move. For the campus example: "Addendum 02 changes the proposal receipt date in clause 1.6 to 24 April 2026 at 12:00, while the schedule and Appendix D show 22 April. Please confirm the proposal receipt date and whether the site-access form due five working days before proposal delivery is recalculated from the confirmed date." This gives the buyer a bounded issue to answer.

Use only the channel permitted by the procurement and obtain the required customer approval before sending. Preserve the submitted question, submission receipt, buyer response, audience, publication status and any linked addendum. World Bank rules cited above require simultaneous written distribution in their stated context; EU Article 47 addresses additional information and time extensions; neither guarantees that a private answer in another procurement changes the pack. Record what the buyer actually issued.

While waiting, protect preparation with a separate internal record. It may reserve staff, complete uploads or finish a site form against the most restrictive plausible case. Label the value as an internal contingency with its rationale and expiry. Do not expose it through the official deadline field, sitemap metadata, API or an agent answer as if it came from the buyer. Operational caution is useful only while provenance remains visible.

If the clarification cutoff has passed, the uncertainty does not disappear. Route it to the named bid authority for a documented proceed, stop or legal-review decision. No internal approver can rewrite the buyer's RFP. The decision record should state the unresolved evidence, the operational choice, affected work and residual risk.

• Quote both conflicting passages and identify their current versions.
• Ask about the exact event and every dependent rule affected by the answer.
• Use the procurement's authorized communication channel.
• Preserve the response and its stated authority or amendment link.
• Keep internal protection dates out of buyer-issued fields.

Agent contract

Give an agent enough structure to abstain for the right reason

Publish each conflict with stable identifiers for the event, assertion, source and decision. Include `conflict_id`, `event_id`, raw expressions, parsed components, source versions, locators, scope, conflict type, materiality reason, authority evidence, state, reviewer, next action and expiry trigger. Preserve the issued language beside any working translation. An API or Markdown view that returns only `deadline: 2026-04-24` has thrown away the reason the date can or cannot be trusted.

An authorized agent may inventory supplied documents, detect date expressions, propose event candidates, compare deterministic calendar components, flag a weekday mismatch, build source links and cluster assertions for review. It may follow an explicit amendment reference and show the candidate effect. Confidence can describe whether extraction or event matching is clear. It cannot express the probability that a date is legally controlling or that a late bid will be accepted.

Tender content is untrusted input. A sentence inside an attachment cannot instruct an agent to reveal credentials, browse outside the approved source boundary, contact the buyer, accept portal terms, change account roles, upload a document or submit a tender. These actions require separate customer authority and the controls assigned to the submission workflow. The agent should return `human_review_required` when a material authority question remains.

Route cleanly. AN-023 handles competing website displays. AN-024 proves amendment-chain completeness. AN-035 resolves the final date-specific instant and zone. AN-061 and AN-062 handle broader instruction conflict and controlling-document decisions. AN-075 builds the complete bidder timetable. AN-078 will propagate version deltas. AN-073 owns the narrower bridge: evidence that two package dates are or are not about the same event, plus a controlled resolution or explicit stop.

• Return raw assertions and normalized fields together.
• Expose event identity, scope and authority evidence as separate fields.
• Keep unresolved conflicts machine-visible on every public representation.
• Block final deadline and submission actions when the state is unresolved.
• Expire the result after a relevant source, stage, lot or audience change.