How to check whether tender evidence will still be valid

Required dates

Start with the events the evidence must survive

Begin with the buyer wording, not the date printed on the certificate. Capture the occurrence that requests the evidence, the requirement it proves, the bidder entity, lot and stage. Then identify two separate questions: when must the supplier satisfy the condition, and when must the document be delivered? Those moments can coincide, but public procurement rules and tender instructions often separate them.

Create one event line for the procedure. It can include the participation deadline, tender submission, a buyer request for supporting documents, evaluation, intended award, contract signature, service commencement and any continuing performance checkpoint. Preserve the raw date, time and zone from the source. If an award is described only as a month or target, record a range or an unresolved event instead of choosing a convenient day.

The UK Procurement Act 2023 illustrates why the event matters. Section 22 says performance-related insurance cannot be required to be in place before award, while a condition may require third-party-verifiable evidence. That does not decide another procurement or excuse a tender-specific submission. It shows that “have now,” “commit to have at award” and “show evidence at award” are different conditions and must not be collapsed.

Validity models

Separate document lifetime, maximum age, live status and underlying truth

Four clocks can govern one file. An effective period says when the instrument is in force. A maximum-age rule says how recently it must have been issued relative to a tender event. A live status says whether the issuer currently regards it as active, suspended, withdrawn, cancelled or expired. The underlying fact may have its own time boundary, such as taxes paid through a period or insurance covering a future contract term.

A PDF that says “valid until 30 September” supplies an end date, but it may not prove the status today. ISO explains that ISO itself does not certify organizations and directs verification to the certification body, accreditation body or the recognized certification database. IAF CertSearch distinguishes active, suspended, withdrawn and expired states. Its field glossary also keeps original issue, current issue and expiry dates separate. Use those distinctions where that register and scheme are relevant.

A missing expiry is not infinity. Some extracts, declarations and financial documents remain factually historical but become unacceptable when the tender says “issued within three months.” Conversely, an expired certificate can still prove that a supplier held certification during a completed reference project if that is the exact claim. Decide validity for the stated purpose and event, not for the document in the abstract.

Rule extraction

Turn tender wording into a rule without inventing a grace period

Preserve the whole instruction around the document. “Current certificate,” “valid at the submission deadline,” “issued no more than 90 days before the request,” “to be provided by the preferred bidder” and “maintained throughout the contract” are not interchangeable. Capture the operator, event, interval, unit, subject, accepted alternative and consequence. If the tender uses “current” without defining it, mark the interpretation open and follow the stated clarification route.

Apply calendar arithmetic visibly. For an issued-within rule, calculate the earliest acceptable issue instant from the required event and the stated duration. Preserve whether the buyer speaks in days, calendar months or business days. For valid-through, compare the required end against the evidence end. Do not silently add a day, assume midnight, treat “until” as inclusive or invent a renewal grace period. A material boundary ambiguity needs a documented decision or clarification.

The UN/CEFACT certificate model provides a useful vocabulary precedent by separating issue, requested effective, actual effective and expiry date-times. It does not decide procurement law or the buyer’s interval convention. Its value here is narrower: the dates deserve different fields because they answer different questions.

Work product

Build one evidence validity timeline for the pursuit

The `evidence_validity_timeline` joins evidence items to required events through explicit rules. One document may have several rows because it must pass at submission and again at award. One requirement may also have several items because an initial declaration is followed by a supporting certificate. Keep the source requirement and the evidence record separate so a new document can replace an old one without rewriting what the buyer asked.

For each item, record the identifier, issuer, subject, scope, version and authoritative status route. Preserve original issue, current issue, effective-from, expiry and last-verified times only when they are available. Each event link records the buyer clause, rule type, raw required date, resolved instant or range, calculation, result, uncertainty, affected answer and required next action.

Use result states that preserve the reason: `valid_for_event`, `validity_window_at_risk`, `expires_before_event`, `maximum_age_failed`, `not_yet_effective`, `live_status_not_active`, `replacement_permitted_later`, `renewal_unconfirmed`, `rule_unresolved` or `source_unavailable`. A green result must name the event it covers. It must never imply that all later events also pass.

Future uncertainty

Test the whole possible award window when the date is not fixed

An expected award date is often a planning assumption, not a buyer commitment. If the published timetable says “October 2026,” represent the possible interval supported by that wording. If it merely says “approximately six weeks after submission,” retain the derivation and any unresolved calendar rule. Test evidence against the earliest and latest supported event boundary instead of a single midpoint.

An item that covers the earliest possible award but not the latest belongs in `validity_window_at_risk`. That state does not predict that the buyer will be late or reject the item. It says the evidence decision changes inside the plausible window. The treatment may be renewal, an updated certificate at a permitted stage, or clarification. If no range can be supported, use unknown and set a review trigger tied to the next buyer notice.

Recalculate after any addendum, standstill change, evaluation extension, delayed buyer request, contract-start movement or evidence-status change. Preserve the previous result so the team can see why a document once passed. A moving date should update the affected event links, not silently recast the old decision as an error.

• Keep fixed buyer dates separate from internal target dates.
• Record ranges only from explicit wording or a disclosed derivation.
• Test both ends of a supported future interval.
• Reopen only the evidence items linked to the changed event.
• Do not call a renewal certain because it is scheduled.

Procedure stage

Do not demand the final certificate at the wrong stage

Identify what the procedure permits at each stage. Under Article 59 of Directive 2014/24/EU, the ESPD is preliminary evidence, may be reused only when its information remains correct, and supporting documents can be requested during the procedure. Before award, the intended winner is generally required to provide up-to-date supporting documents, subject to the Article’s exceptions. This is an EU rule with defined scope, not permission to delay evidence in every tender.

German VgV section 48 requires the buyer to indicate which declarations, certificates and other evidence are required and when they must be presented. French Code Article R2143-14 says documents already given to the same buyer need not be resubmitted when they remain valid, while R2143-15 allows an additional tax or social-status certificate at award in the stated circumstances. Read the current procedure text before converting any of these examples into an action.

United States FAR clauses provide a different timeline. Current FAR 52.204-7 generally requires active SAM registration when submitting an offer and at award. FAR 52.204-13 then requires maintenance during performance and through final payment, with a stated annual review obligation. The lesson is not that every registration follows SAM. It is that one requirement can have several checkpoints and a continuing interval.

Worked example

A certificate passes submission but fails the possible award window

A software supplier is answering a security RFP. The pack asks for an ISO/IEC 27001 certificate covering the offered service, valid at submission and at award. Submission is fixed at 18 September 2026. The timetable gives an intended award during October, without a day. The current certificate is effective through 30 September 2026 and its status is active when checked on 4 September. A renewal audit is booked for 9 September, but no renewed certificate has been issued.

The timeline produces two different results. The current certificate is valid for the fixed submission event, assuming its scope and status remain unchanged at that point. It expires before every possible October award date, so it fails the award event. The booked audit is evidence of a renewal activity, not evidence of a future certificate, future scope or approval date. The overall requirement is therefore not green.

The certification owner records the issuer’s expected process and a conservative internal follow-up date without turning either into a guarantee. The bid lead checks whether updated award-stage proof is expressly allowed and whether clarification is needed. The response cites only the current certificate and does not promise that renewal is complete. When a renewed item arrives, it is checked as a new version for entity, scope, standard, effective date, expiry and live status before the award link can change.

Release decision

Release evidence by event, and keep neighbouring decisions separate

Before each evidence release, confirm the tender version, requirement occurrence, item version, event result and intended destination. Open the rendered file, not only the source folder. Check the legal entity, identifier, issue and expiry dates, scope, status observation and attachment name. If an item has been replaced, remove the stale file from the release package while preserving it in the decision history.

A failed event does not have one universal remedy. A newer extract may close a maximum-age gap. A renewal may close an expiry gap only after issuance and review. A commitment may be permitted where a condition need not be in place before award. An adjusted claim may be necessary where no suitable proof exists. A material unresolved condition can reopen the bid decision. The timeline reports which gap exists; the governing tender and responsible reviewer determine the treatment.

This task has firm boundaries. The missing-certification dossier decides whether a not-yet-held credential can become ready in time. Certification citation checks entity and scope wording. Evidence hierarchy selects the strongest support for a claim. Evidence-scope review tests product, geography and period. Price validity governs a commercial offer, and digital-signature validation governs a signing credential. This dossier owns the time relationship between an identified evidence item and the tender events at which it must be acceptable.