A document access-state record is a dated, evidence-backed account of how the material for one procedure, lot, stage and supplier audience is meant to be released and what a permitted reviewer could actually obtain. It keeps notice publication, promised document release, first observed availability and authorized access grant as separate events. It records the designated channel, every access gate, the visible document inventory, retrieval and opening results, unresolved conflicts, `checked_at`, `valid_until`, `next_check_at` and one permitted next action. The record can support `publicly_available`, `available_with_authorized_access`, `scheduled_not_released`, `registration_required`, `approval_pending`, `invitation_only`, `partially_available`, `listed_not_retrievable`, `unreadable`, `conflicted` or `unknown`. None of these states proves that the tender is open, the amendment chain is complete or the opportunity is worth pursuing.
A publication alert can arrive before the specification, price schedule or response forms. A notice can point to a portal that shows filenames only after registration. A public solicitation can include a general package while technical drawings remain controlled. A staged procedure can release material only to shortlisted suppliers. The reverse also happens: a notice may contain all information the buyer says is needed, so the absence of a separate ZIP file is not automatically a defect. If an agent collapses these cases into “documents available” or “documents missing,” it can start qualification from an incomplete package, wait for files that were never promised, cross an authorization boundary or report an access failure as evidence that no documents exist.
Treat publication and document access as different claims. Read the current notice and its instructions to learn what should exist, when, for which stage and through which channel. Observe the public route without creating an account, accepting terms, requesting an invitation or disclosing bidder interest. If an authorized supplier context is required, record the gate and hand it to the person who controls that identity. Inventory what the source lists, what was retrieved and what opened successfully. Keep a missing document, a future release, a broken link and a restricted file in different states. An agent should return evidence and a next check, not improvise credentials, contact the buyer or declare the pack response-ready.
Event model
A published notice and an available pack are different events
“Published” normally describes a notice event. It tells you that a named publication became public at a recorded time. It does not, by itself, tell you whether the specification, pricing workbook, response schedules, contract, declarations or technical annexes were released through the operational portal. Even where the rules expect both events to coincide, they remain two facts that should be observed separately. One source can prove publication; another can prove what documents a permitted user could obtain.
Use four clocks. `notice_published_at` comes from the official publication record. `documents_promised_at` is the release time stated by the buyer, including a condition such as “after shortlist confirmation.” `first_observed_available_at` is the first recorded check that could retrieve the object. `access_granted_at` belongs only to an authorized supplier context where a gate was completed. Do not backfill one from another. If a notice dated 10 September says the documents will appear on 14 September, the record on 11 September is `scheduled_not_released`, not missing and not available.
The legal pattern depends on the procurement. Article 53 of Directive 2014/24/EU generally calls for unrestricted, full, direct and free electronic access to procurement documents from notice publication, while stating routes for specified exceptions and confidential material. UK guidance distinguishes an open procedure, where associated documents used to prepare a tender are needed at the outset, from staged competitive flexible procedures where later documents can be released at later stages. U.S. FAR 5.102 generally requires solicitations and pertinent material through the governmentwide point of entry, but also provides for enhanced controls and specified alternative arrangements. These sources tell an agent which evidence to seek. They do not permit it to decide legal compliance for a particular buyer.
| Field | What it records | Acceptable evidence |
|---|---|---|
| notice_published_at | Official notice publication | Publication record and notice identifier |
| documents_promised_at | Buyer-stated release time or condition | Notice or designated instructions |
| first_observed_available_at | First successful permitted retrieval | Dated retrieval evidence |
| access_granted_at | Authorized gate completion | Private audit reference, never public credentials |
| checked_at | Instant covered by this conclusion | Reviewer or agent observation log |
Scope
Ask whether these documents are available to this supplier now
Availability has a subject. Fix the procedure identifier, current notice and version, lot or part, stage, supplier audience and check time before opening the document link. A public request-to-participate pack may be fully available while the invitation-to-tender pack does not yet exist for that supplier. One lot may have a public specification and another a restricted security annex. A bidder that has passed selection can possess material that a new public visitor cannot see. A result without those dimensions cannot be safely reused.
Carry the source roles from the official-notice record instead of resolving them again by domain reputation. The statutory notice proves its publication fields. The document portal named in that notice proves the file inventory observed there. An official API can expose document metadata and stable identifiers. A secondary index can help recover the route. None should silently take over a different role. If identity, source designation or current version is unresolved, stop with `unknown` and send the case back to source verification.
Also name the access context. `public_anonymous` means the check used no account. `authorized_supplier` means a named internal owner permitted the use of an existing supplier account under the organization’s controls. `unavailable_context` means the required supplier identity or invitation could not be inspected. Never publish usernames, tenant identifiers, invitation URLs, session addresses, private correspondence or restricted filenames that reveal protected scope. The public output can state that an approval gate exists and point to a private evidence reference.
| Field | Example | Failure prevented |
|---|---|---|
| procedure_id | CA-ICT-2026-41 | Mixing a rebid with the original |
| notice_version | notice UUID, version 02 | Using a replaced instruction |
| scope | lot 3, tender stage | Inheriting another lot or stage |
| supplier_audience | shortlisted suppliers | Claiming public availability |
| access_context | public_anonymous | Hiding the tested permission |
| checked_at | 2026-09-11T09:20:00Z | Turning a dated observation into a permanent fact |
Release promise
Read what the buyer says will be released, where and when
Search the current notice and designated instructions for document-access fields, direct URLs, restricted-document indicators, stage descriptions, dispatch dates and plain-language release statements. TED eForms keeps procurement-document terms together: BT-14 records that documents are restricted, BT-15 provides the non-restricted document URL, BT-615 points to information about restricted access, and related terms cover the justification and document languages. The eForms mapping describes BT-15 as a direct route to the non-restricted part rather than a general home page. Capture the raw field and the human-readable notice passage because either representation can expose context missing from the other.
Do not assume that a separate pack must exist. Under the current UK framework, associated tender documents supplement a tender notice, and official guidance says a contracting authority need not provide them when the notice itself contains all information needed to prepare the tender. Record `notice_stated_as_complete_basis` only when the procedure materials support that conclusion. A sparse landing page and silence about attachments do not prove it. Conversely, when the notice says later documents will be supplied after selection or negotiation, create one expected release object for each named stage rather than one generic “documents pending” note.
For every promise, preserve the document group, lot, audience, release time or trigger, channel and source passage. A phrase such as “available following execution of the confidentiality agreement” contains both a gate and a release condition. A future calendar date needs its stated time zone; if none is supplied, keep the instant unresolved and schedule a conservative source check without inventing a legal deadline. If the notice and portal disagree about what should be public, record both statements. The discrepancy is evidence, not permission to choose the more convenient one.
| Field | Record | Do not infer |
|---|---|---|
| document_group | Technical schedules for lot 3 | Every lot uses the same pack |
| release_trigger | After shortlist notice | A public release date |
| designated_channel | Supplier workspace named in section 2.4 | Any buyer webpage |
| access_condition | Approved confidentiality undertaking | Approval already granted |
| source_statement | Exact field or cited passage | A summary written by an index |
Permitted observation
Test the public route without turning research into an external act
Open the exact address named for the relevant lot and stage. Record the requested URL, final public URL, redirects, response time, status, page title, visible access message and observation instant. If the route returns a page, confirm that it is the procurement document area rather than a portal home page, search form or generic registration screen. If a supposed PDF returns `text/html`, inspect whether it is an error or login page. A status code of 200 proves that a response arrived. It does not prove that the named file was delivered.
An anonymous agent may follow public links, read public instructions, enumerate publicly exposed document metadata and retrieve files expressly available without a gate. It should respect access controls, rate limits and site terms. It must stop before creating an account, using a person’s identity, accepting click-through terms, declaring an entity, requesting access, joining an interested-vendor list, completing a confidentiality statement, solving a challenge intended for a person or sending a message. Those steps can disclose commercial interest or create obligations. The agent records the exact gate and prepares a handoff instead.
Do not classify a timeout, temporary server error, bot challenge or geographic failure as `not_published`. Use `route_unavailable` inside a broader `unknown` or `listed_not_retrievable` decision, preserve the error and try a permitted official alternative. Recheck according to a bounded retry policy. If the notice supplies a contact route for access, an agent may draft a cited request for an authorized person. It may not send it merely because the public route failed.
| Action | Agent treatment | Recorded result |
|---|---|---|
| Open designated public page | Permitted | URL, redirect, status and checked time |
| Download an unrestricted public file | Permitted under site policy | Object identity and retrieval result |
| Create or use supplier identity | Requires explicit authorization | Gate and responsible owner |
| Accept terms or confidentiality duty | Human-controlled act | Text reference and pending decision |
| Request approval or invitation | External communication | Draft only unless authorized |
| Bypass a control or challenge | Not permitted | Stop and escalate |
Access gates
Name the gate instead of calling the documents private
Access conditions have different consequences. A free account may reveal a public pack after email verification. Entity validation can require corporate data and an administrator. Buyer approval can remain pending after the request is filed. Invitation-only access depends on the supplier’s stage. A confidentiality undertaking or export-control check can restrict distribution even after access is granted. Record the observed mechanism and its current status without generalizing from another procurement on the same platform.
Use a small gate vocabulary: `none_observed`, `registration`, `entity_validation`, `terms_acceptance`, `buyer_approval`, `invitation`, `confidentiality`, `controlled_information` and `alternative_delivery`. More than one can apply. Keep `gate_required`, `gate_requested`, `gate_approved`, `access_tested` and `access_revoked` as separate statuses. A screenshot of a request button supports `gate_required`; it does not support `gate_requested`. An approval email supports approval in a restricted record; it still does not prove that every promised file can be retrieved.
FAR 5.102 illustrates why “public notice, private document” is too crude. It directs agencies to make solicitations and pertinent material available through the GPE in the general case, provides enhanced controls for information needing monitored distribution, and names circumstances where another route can be used. The access state must retain that route and its requirements. Never copy protected material into a public content record to prove that it exists. A private evidence pointer, access owner, classification and observed file count are enough for the public decision surface.
| Gate state | What is proved | Next permitted action |
|---|---|---|
| registration_required | The designated route asks for an account | Assign authorized account owner |
| approval_pending | An authorized request exists but is undecided | Monitor the recorded request |
| invitation_only | Access is tied to a selected audience | Verify stage and invitation with owner |
| controlled_information | Distribution has stated controls | Use approved secure handling process |
| alternative_delivery | Buyer specifies another delivery method | Follow that method under authority |
| access_revoked | Previously authorized route no longer opens | Stop intake and investigate |
Document inventory
Separate listed, retrieved, opened and sufficient-for-intake
Build one row per document object or portal response surface. Start with the roles promised or required by the notice: instructions, specification, qualification forms, response schedules, pricing, contract terms, declarations, lot annexes, technical data, clarification log and portal-only fields. Then capture what the designated channel lists. For each object, record the source identifier, buyer title, lot, stage, language, publication or update metadata, media type, size where shown, retrieval result and opening result. Preserve null when the source supplies no value.
Listed is not retrieved. Retrieved is not readable. Readable is not applicable. And an apparently complete download folder may omit interactive fields that only appear after a permitted response workspace opens. Use object states such as `expected_not_listed`, `listed_not_retrieved`, `retrieved_unreadable`, `opened_not_scoped`, `opened_for_intake` and `portal_surface_uninspected`. Detect archive corruption, password prompts, unsupported formats and HTML error bodies without attempting to defeat protection. Malware scanning and secure storage belong to controlled document intake, not to a public discovery process.
OCDS can make the inventory more portable. Its Document object separates `id`, `documentType`, `title`, `description`, `url`, `datePublished`, `dateModified`, `format` and `language`; it also allows the description to explain how to obtain an offline document. These fields are useful inputs, not an availability verdict. A populated URL still needs an observed retrieval, and a missing URL can coexist with a documented alternative route. Preserve the official data representation and the observed human route rather than forcing either one to carry evidence it does not contain.
| Object | Listed | Retrieved | Opened | Decision note |
|---|---|---|---|---|
| Instructions to tenderers | yes | yes | yes | Available for intake |
| Pricing schedule | yes | no | no | Link returns login page |
| Security annex | restricted | no | no | Buyer approval required |
| Portal response questions | unknown | no | no | Authorized workspace uninspected |
| Contract terms | expected | no | no | Not present in listed inventory |
Decision record
Return the narrowest state supported by the observations
Expose `claim_key`, `release_promises`, `channels`, `access_context`, `gates`, `document_objects`, `contrary_evidence`, `decision_state`, `blocked_uses`, `checked_at`, `valid_until`, `next_check_at`, `invalidation_triggers` and `next_action`. Give every decisive field a public citation or a restricted evidence reference. Use ISO 8601 instants with an offset where the source supports one. Keep unknowns as null and descriptions as sourced text. A numeric confidence score cannot replace a missing price schedule or an uninspected supplier workspace.
Choose one top-level state. `publicly_available` means the expected public objects were retrieved and opened for the defined scope. `available_with_authorized_access` means the same happened inside a permitted supplier context. `scheduled_not_released` requires an explicit future release promise or stage trigger. `registration_required`, `approval_pending` and `invitation_only` describe the blocking gate. `partially_available` names at least one material expected object or surface that is not yet usable. `listed_not_retrievable` and `unreadable` describe observed technical failures. `conflicted` preserves incompatible official statements. `unknown` covers insufficient evidence. Never upgrade a state because a deadline is close.
The record expires when its evidence can change: at a promised release time, a stage decision, a portal approval, a notice version change, a new document event, an amendment, or a bounded recheck before qualification. Route `publicly_available` or `available_with_authorized_access` to controlled document intake, not directly to drafting. Route a gate to its authorized owner. Route a conflict to source resolution or a buyer question under the permitted communication process. Route a technical failure to another official path or support process. No state authorizes the agent to register, accept obligations, communicate, interpret legal compliance, decide to bid or submit.
| State | Minimum evidence | Downstream effect |
|---|---|---|
| publicly_available | Expected public set retrieved and opened | Controlled intake may begin |
| available_with_authorized_access | Permitted supplier context and usable set | Secure controlled intake may begin |
| scheduled_not_released | Buyer states future time or trigger | Schedule recheck |
| partially_available | Named expected object or surface remains unusable | Block complete-package use |
| listed_not_retrievable | Object is listed but retrieval fails | Preserve error and resolve route |
| conflicted | Official promise and observation disagree | Escalate without choosing |
| unknown | Evidence cannot support another state | Do not start pack-dependent work |
Worked example
A notice published today can correctly produce a wait decision
Consider a fictional competitive flexible procedure, CA-ICT-2026-41. Its notice is published at 08:00 BST on 10 September. The notice invites requests to participate and says the full invitation-to-tender documents will be released through the supplier workspace to shortlisted suppliers on 18 September. An anonymous check at 09:20 UTC on 11 September finds the participation instructions and selection form. It does not find the pricing schedule, response form or draft contract. Those absences match the stated stage rather than contradicting it.
The record is scoped to the public participation stage and reports that its participation documents are `publicly_available`. A separate object for the invitation-to-tender stage is `scheduled_not_released`; its `next_check_at` is tied to the stated release on 18 September and its invalidation trigger includes an earlier shortlist notice. The agent does not call the tender pack missing, and it does not call the future bid pack available. It also does not infer that this supplier will be shortlisted.
If an authorized shortlisted supplier later opens the workspace and retrieves all listed documents except the pricing workbook, the new decision becomes `partially_available`. The record identifies the workbook, portal path, observed error and blocked pricing work. It can prepare a support note for the authorized owner. The open-status check, deadline verification, amendment register and bid decision still run separately. This access record has done its job once it states what can be inspected, what cannot, why, and when to look again.
| Key | Value |
|---|---|
| claim_key | CA-ICT-2026-41, ITT stage, shortlisted supplier |
| notice_published_at | 2026-09-10T08:00:00+01:00 |
| documents_promised_at | 2026-09-18, supplier workspace |
| decision_state | scheduled_not_released |
| blocked_uses | pack qualification, pricing and drafting |
| next_action | Recheck after stage release or earlier notice |
| checked_at | 2026-09-11T09:20:00Z |
What good looks like
Useful outcomes from tender documents availability
- Notice publication and each promised or observed document event have separate timestamps and sources.
- The access decision is bound to one procedure, lot, stage, supplier audience and permitted access context.
- Every gate is named without implying that registration, terms acceptance or buyer approval has occurred.
- Listed, retrieved, opened and expected documents are reconciled without treating one list as the complete pack.
- Conflicts, unavailable routes and unreadable files remain explicit and block unsupported downstream work.
- The result exposes an expiry, event triggers and the next action that an authorized person or agent may take.
Operating model
How to run the work
- 01
Fix the access question
Record the procedure, notice and version, lot or part, procurement stage, supplier audience, access context and exact `checked_at` instant.
- 02
Extract the release promise
Read the notice and named instructions for the document channel, release timing, stage conditions, restricted-document statement and any claim that the notice itself is sufficient.
- 03
Observe the permitted route
Follow the designated public link, preserve redirects and errors, and stop before account creation, terms acceptance, access requests, invitations or private credentials.
- 04
Reconcile the document inventory
Record each expected, listed, retrieved and opened object by role, lot, stage, language, source identifier and observation time. Include portal-only response fields as a separate surface.
- 05
Issue a perishable state
Choose the narrowest supported access state, cite supporting and contrary evidence, set `valid_until` and `next_check_at`, and route only the permitted next action.
Evaluation
Questions that change the decision
- Does the publication invite a tender now, invite participation, announce a later stage or only signal a future procurement?
- Does the governing material promise a separate pack, later documents, restricted documents or no separate documents?
- Which channel is designated for each document group, and is the link public, direct and recoverable?
- Does access require only viewing, or does it require registration, entity validation, terms, approval, an invitation or a confidentiality act?
- Which documents are merely listed, which were retrieved, and which opened in a form that can be inspected?
- Are pricing, response forms, specifications, contract terms, annexes or portal-only questions absent from the observed set?
- Can the evidence support an availability state, or do source conflict and missing access keep the result unknown?
- What event or time should invalidate the record and trigger the next check?
Failure modes
Where teams lose control
A publication timestamp can be copied into a document-release field even though no file was available then.
A login page can be mistaken for proof that any registered user will receive the full package.
Accepting portal terms or requesting access can bind the supplier, disclose interest or start a controlled process.
A document list can omit portal fields, stage-specific material, lot annexes or controlled technical data.
A successful download can return an HTML error page, corrupt archive, password prompt or unsupported file instead of the named document.
A failed public request can be misreported as evidence that the document does not exist.
A complete notice can be labelled incomplete merely because the reviewer expected a conventional tender pack.
An old access result can survive a new notice, stage transition, portal change or document publication.
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.
- access records with procedure, lot, stage, audience and `checked_at` populated
- declared release events separated from first observed availability
- designated document channels checked without an unauthorized external action
- expected document roles reconciled to listed, retrieved and opened objects
- access gates with an authorized owner and no implied completion
- conflicts and failed routes resolved before document intake
- rechecks completed at promised release times and stage transitions
- downstream decisions prevented from using partial or unverified material
Questions
Common questions
Does a published tender mean the bid documents are available?
No universal rule supports that inference. Read the applicable notice and instructions, then observe the designated document channel. Some regimes expect access at publication, staged procedures can release later material, and controlled documents can require authorized access.
Is a registration screen proof that the documents are available?
It proves that the observed route presents a registration gate. It does not prove that registration is sufficient, that approval will be granted or that the expected document set exists behind the gate.
Should an agent create a portal account to check the pack?
Not without explicit authorization and an approved identity process. Registration can disclose bidder interest, require company data and accept terms. The agent should record the gate and hand it to the account owner.
What if the notice says no separate tender documents will be issued?
Record the exact statement and test whether the notice is identified as the complete basis for the current stage. Do not invent a missing pack, but do not infer completeness merely from the absence of attachments.
Does a visible filename prove that the document can be used?
No. Keep listed, retrieved, opened and scoped-for-intake as separate states. A link can return a login page, error body, corrupt archive, password prompt or file for another lot.
Is a failed download proof that the buyer did not publish the file?
No. It is evidence that this route failed in the recorded access context and time. Preserve the error, check permitted official alternatives and use an unknown or retrieval-failure state.
When can document intake begin?
After the expected set for the defined stage and scope has been retrieved and opened through public or authorized access. Intake must still apply security, version, amendment and applicability controls.
When should the access record be checked again?
At the promised release, after a stage or approval event, when the portal inventory or notice changes, and before pack-dependent qualification. Record the new observation rather than overwriting the earlier result.
Sources
Primary references
- Directive 2014/24/EU, Article 53 on procurement-document access European Union
- TED eForms procurement-document business terms Publications Office of the European Union
- OCDS for eForms mapping of document-access fields Open Contracting Partnership
- UK guidance on competitive tendering procedures UK Cabinet Office
- Procurement Act 2023, section 21 UK Parliament
- FAR 5.102 on solicitation availability Acquisition.gov
- SAM.gov Contract Opportunities public API U.S. General Services Administration
- Open Contracting Data Standard document schema Open Contracting Partnership
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.