How to find open tenders you still have time to answer

Decision boundary

Decide what the shortlist is allowed to claim before searching

A useful search starts with a fixed decision contract. Record the assessment instant in UTC and the operating time zone, the markets and procedure stages in scope, the organization’s working calendar, the version of its protected release and submission buffer, and the minimum lead-time profiles it has approved. The result will answer one question: does this open lot have enough verified usable time to enter detailed qualification now? It will not answer whether the opportunity is worth pursuing, whether the evidence is sufficient, whether named people are free or whether a winning response can be completed.

Define the candidate unit as a procedure stage plus lot. A single notice can contain several lots, and eForms models the deadline for receipt of tenders at lot level. A restricted procedure can also expose a deadline for requests to participate before invited tenderers receive a later deadline. Keep those dates in different fields. The same separation applies to the deadline for questions, the date answers are expected, document availability and public opening. A generic field named deadline is an invitation to compare unlike events.

The minimum floor is a screening policy, not an estimate for the tender on the screen. For example, an organization may approve different conservative floors for a simple catalog supply, a multi-lot service procurement, a regulated outsourcing and a consortium response. The policy owner records the unit, calendar, assumptions, permitted exceptions and review date. Search agents select only from these approved profiles. They do not lower the floor because an opportunity looks attractive.

Source state

Prove the live lot and receipt instant before counting time

Use search indexes and APIs to retrieve candidates, then resolve each one at the issuing source. TED’s Search API, for example, gives systems open access to published notices through expert queries. Its field list separates the lot-level tender receipt date and time from expression-of-interest, request and answer deadlines. Those fields are valuable discovery signals. They still need the current notice, change lineage and procurement documents because a search record alone does not prove that the lot remains open or that the field is the only controlling instruction.

Preserve the procedure identifier, notice identifier and version, buyer, lot identifier, source URL, retrieval instant and the exact field or passage. Follow references to change notices, cancellations and replacements. eForms change notices identify the notice being changed and can report changed sections, a document-change indicator and the date procurement documents changed. Open the consolidated current notice and the buyer portal rather than assuming that an old search result has inherited every correction. If the latest official state cannot be resolved, classify source state unresolved.

Normalize the submission deadline only after authority is settled. Record date, clock time, named zone or explicit offset, the receipt channel and the action that constitutes receipt. A missing zone or conflict belongs in a dedicated deadline review, not a guessed timestamp. Confirm that the date governs the selected lot and stage. Compare the assessment instant to the verified receipt instant only when both are expressed on the same time basis. Until then, remaining time is unknown, even if a portal displays a countdown.

• Keep the discovery record and the controlling buyer source as separate links.
• Resolve corrections, cancellations, replacements and lot scope.
• Distinguish requests to participate from receipt of tenders.
• Record the exact receipt event, not only a date and time.
• Use unresolved when authority, time zone or stage remains ambiguous.

Usable access

A document link is not the same as a response-ready pack

Open the procurement-document route as the kind of user the team is permitted to use. Record whether access is unrestricted, requires an account, requires a confidentiality undertaking, depends on buyer approval, or is unavailable. Then inventory the visible pack: instructions, specification, response schedules, pricing model, contract, declarations, lot annexes, question log and amendments. Store public identifiers, file names, versions, dates, checksums where appropriate and the observation time. A landing page that contains no files does not satisfy the access check.

Document availability is its own clock. The Open Contracting Data Standard separates the tender period, enquiry period and tender documents; its EU profile also provides a document-availability period. That structure reflects a practical truth: a tender can be open for submissions while the information needed to prepare one is not yet usable. In procedures within the scope of EU Directive 2014/24/EU, Article 53 sets rules for electronic access and certain exceptions. Treat those rules as scoped legal context, not as permission to invent an extension for a particular tender.

If one material file is missing, mark which decision or deliverable it blocks. Do not estimate its contents as zero work. An inaccessible price schedule, bill of quantities, security annex or response template can change the effort class after it arrives. Record first complete access only when the pack has been inventoried against the notice and instructions. If registration or an undertaking is required, the shortlist may record the authorized access path and owner, but it cannot claim completion until the documents are actually available.

Prerequisites

Find the date that removes the right to compete, not only the final date

Read instructions and appendices for events that create eligibility, knowledge or submission dependencies. Examples include a mandatory site visit, bidder conference, inspection, sample or prototype delivery, request for restricted documents, supplier registration, electronic signature setup, consortium confirmation, security clearance or a preliminary portal action. For every item, capture its exact source, lot, due instant, mandatory or optional wording, completion evidence and stated consequence. Do not infer that a missed event is harmless or automatically fatal when the pack is silent.

The clarification clock needs separate treatment. A passed question deadline does not automatically make an opportunity infeasible. It becomes material when a responsible response depends on information that is absent, contradictory or too ambiguous to price, design or promise. Record the unresolved question, affected requirement, whether the official Q&A already answers it, and who can judge the remaining risk. If contact is still permitted, an agent may draft a neutral question but cannot send it without authorization.

EU Directive 2014/24/EU gives a scoped example of why these gates matter. Article 47 says that where tenders can be made only after a site visit or on-site inspection, the time limit must allow operators to obtain the needed information. It also addresses extensions after late additional information or significant document changes. The supplier must still wait for an official change. Neither a legal expectation nor a buyer conversation changes the recorded deadline until the controlling source does.

• Capture the gate, its due instant, lot, wording and stated consequence.
• Distinguish a required event from a recommended information session.
• Require evidence of completed registration, attendance or delivery.
• Link unresolved questions to the work they block.
• Never apply a rumored or expected extension to the calculation.

Arithmetic

Convert gross calendar time into a reproducible usable window

Start with gross window = verified receipt instant minus assessment instant. This number is useful for explanation but not sufficient for classification. Calculate working time through the approved calendar for the team or screening policy. Remove time before first complete document access. Remove only fixed unavailable periods that the policy explicitly recognizes, such as an unavoidable wait for a mandatory buyer event. Protect the approved release, packaging, upload and receipt-verification buffer at the end. Do not subtract speculative writing effort or the current workload of named people. Those belong to detailed qualification and capacity planning.

The resulting usable window is compared with the approved minimum lead-time floor. Screening slack = usable working time minus the floor. Keep every unit explicit. If the calendar reports hours, convert neither side to days without a declared working-day length. Keep the calendar identifier, holiday set, daily working bands and buffer version beside the result. A number without those inputs cannot be reproduced by another agent and should not control ranking.

A positive slack means only that the opportunity clears the discovery floor on the verified inputs. It does not prove that the actual response fits. A negative slack means the row cannot receive automatic viable status. Policy may classify it below floor or send it to authorized urgent review. An unknown input produces unknown slack. Never replace a missing document-access time, time zone or gate consequence with zero merely to finish the formula.

Decision states

Use states that say what is known and what happens next

Use a small controlled vocabulary. Viable for immediate qualification means the lot is verified open, the receipt instant and pack are current, no fixed gate is missed, and usable time meets the policy floor. Urgent review means the evidence is complete but slack sits inside a predefined review band or a material question needs authorized judgment. Window below policy floor means the calculation is complete and insufficient for automatic promotion. Missed fixed prerequisite identifies the exact event and preserves uncertainty about legal consequence unless the source states it.

Source or access unresolved applies when the current official state, time zone, pack, amendment chain or material gate cannot be proved. Closed or superseded removes a record from the active queue while preserving lineage. Second stage not yet open distinguishes a future invitation from a current submission opportunity. These states must not collapse into a single red or green score. An agent and reviewer need to know whether the problem is time, missing evidence, procedure state or organizational policy.

Rank viable rows by the organization’s declared discovery priorities only after classification. Contract value, strategic buyer or semantic relevance must not override a failed gate or unresolved source. Pass the row to detailed qualification with a warning that effort, eligibility, commercial attractiveness, contract risk, delivery fit and named capacity remain undecided. The next process may reject the opportunity immediately. That does not make the screening result wrong; it means the shortlist performed its bounded job.

Work product

Publish the evidence and permissions beside the answer

Each shortlist row identifies buyer, procedure, stage, notice and lot; records the current official state and source version; gives assessment and retrieval instants; preserves the exact receipt instant and receipt event; lists pack access and inventory status; names fixed gates and clarification state; cites the calendar, buffer and floor versions; shows gross and usable time, slack and classification; exposes missing facts; names the reviewer; and gives one permitted next action. Keep previous versions so a changed deadline does not erase the basis of an earlier choice.

Publish machine-readable values with stable field names, ISO 8601 instants, explicit time zones, enumerated states, source URLs and explicit nulls. Keep source passages close to the facts they support. A human should see the same state and calculation as an API or agent. Do not expose account identifiers, restricted documents, internal calendars, confidential opportunity notes or private buyer communications. Public discovery can describe that access is gated without publishing what the gate protects.

An agent may search public sources, follow notice lineage, download permitted public documents, inventory files, extract dates, convert verified instants with the approved calendar, apply the policy formula and draft a provisional row. It must stop on conflicting deadlines, an unknown time zone, inaccessible or materially incomplete documents, ambiguous lot scope, an unclear mandatory-gate consequence, any expected but unpublished extension, and every decision about priority, capacity, external contact or submission. Refresh on a new notice, changed document, Q&A publication, access transition, deadline change or policy-version change.

• Expose the original source, current version and observation time.
• Return exact values and explicit nulls instead of a hidden score.
• Keep the arithmetic reproducible from named policy inputs.
• Separate public evidence from private access and bid records.
• Require human authority at source ambiguity and business judgment.
• Reopen the row whenever a controlling fact or policy changes.