An amendment completeness register is a time-bounded record of every buyer-issued notice, addendum, amendment, clarification or replacement that can change an identified tender pack. It fixes the procedure, notice lineage, lot, supplier audience and response stage; names every authoritative publication and delivery channel checked; records each change object with its identifiers, issue and observation times, applicability, listed files and acknowledgement duty; and tests the links between them. Its strongest decision is `complete_through_checked_at`. That means the defined sources and chain support the package through the recorded instant. It never means that no later or access-restricted change exists.
A bidder can hold “Amendment 04” and still be missing Amendment 03. A portal can show the newest consolidated notice while an email contains a revised workbook that the public page does not expose. A buyer can replace one attachment without changing its filename, or publish a clarification that changes the practical answer but is not called an addendum. Search results and many APIs favour the current state, which is useful for discovery but weak evidence of how that state was reached. If the team accepts the newest visible date as proof of completeness, it may price against an obsolete schedule, miss a mandatory acknowledgement or submit under requirements the buyer has already replaced.
Treat “latest” as a claim with scope, sources and a clock. Start from the procurement identity and its designated communication rules, then inventory every channel the buyer uses for this supplier and stage. Follow explicit notice references, amendment numbers, publication histories and portal messages. Compare the issued package with the file list, not merely with the buyer’s summary of changes. Keep issue, publication, receipt and observation times separate. An agent may inspect public histories, compare identifiers, calculate file fingerprints and prepare a missing-document request. It must stop at authentication, private correspondence, ambiguous applicability, acknowledgement, buyer contact, legal effect, response editing or submission unless a person with the right authority takes over.
Claim boundary
Replace “latest” with a claim another reviewer can test
“We have the latest amendment” is too broad to audit. A defensible claim reads more like this: “For procedure NTA/ICT/26/17, lot 2, open-tender stage and the bidder audience defined in the instructions, the official notice history and designated supplier portal were checked through 14:05 UTC on 18 September 2026. The chain is complete through Amendment 04, subject to the recorded inability to inspect private messages.” The longer sentence is useful because each limit can be challenged. If the reviewer changes the lot, supplier status, source coverage or time, the decision must be run again.
Start with the source-authority record established during official-notice verification. Carry forward the procedure identifier, notice identifier and version, buyer, lot and designated operational portal. Add the response stage because a change sent to shortlisted bidders may not appear in the public tender history. Add supplier audience because a negotiated procedure can distribute material only to participating suppliers. Finally, state the access context: public, authenticated with authorized access, or unavailable. Never publish private URLs, session tokens, credentials or the contents of restricted correspondence on a public page.
Four clocks may appear. `issued_at` is the time the buyer says it issued the amendment. `published_at` is when the publication service made it available. `received_at` records arrival in the bidder’s authorized channel. `observed_at` is when the reviewer inspected it. None can silently replace another. The completeness decision uses `checked_at`, which should be at least as late as the last relevant observation. It expires at `valid_until` or earlier when a new notice, portal event, document or buyer message arrives.
| Field | Example | Why it matters |
|---|---|---|
| procedure_id | NTA/ICT/26/17 | Prevents a rebid from entering the chain |
| notice_lineage | notice UUID and version | Anchors published changes |
| scope | lot 2, tender stage | Stops cross-lot inheritance |
| supplier_audience | all current bidders | Exposes selective distribution |
| source_coverage | TED plus named portal | Bounds what was inspected |
| checked_at | 2026-09-18T14:05:00Z | Dates the conclusion |
Coverage
Find the channels before looking for amendment numbers
The tender’s own communication clause is the channel map. Read where notices are published, where documents are downloaded, how clarifications are released, how invited suppliers receive later material and where acknowledgements occur. A statutory publication service, buyer profile, e-sourcing workspace, Q&A board and direct email can perform different jobs. Do not rank whole domains. Record the function assigned to each channel and the evidence for that assignment. A journal may prove the published notice lineage while the named portal proves which workbook was available to this bidder.
Inspect the history view, not only the current landing page. TED eForms provides notice and version identifiers, and its change-notice model references the changed notice. A change notice contains consolidated notice information, while only the latest changes appear in its changes section. That makes the current notice useful but also explains why the chain still matters. Find a Tender can return OCDS releases for a notice or whole procurement process. OCDS distinguishes individual releases, a compiled current view and a versioned history. The current value is not a substitute for the release index when the question is whether anything was missed.
An interface can expose less history than the underlying service. GSA’s public Opportunities API states that it returns only the latest active version and points users elsewhere for all versions. That is a documented evidence limit. Record `latest_view_only` and use the permitted history source rather than calling the API complete. If the complete route requires an account, API key, accepted terms or named-supplier access, an agent should stop and request authorized access. It must not work around the boundary or infer that the public view contains everything.
| Channel | Assigned role | Recorded result |
|---|---|---|
| Official notice history | Published notice changes | checked, 14:00 UTC |
| Designated supplier portal | Pack and operational messages | checked, 14:05 UTC |
| Buyer Q&A area | Clarifications and corrections | checked, no new item |
| Named bidder inbox | Audience-specific distribution | access required |
| Secondary tender index | Discovery lead only | not used for completeness |
Register
Give every change object its own evidence row
Create a row whenever the buyer issues an object that can change the tender pack or the bidder’s obligations. Names vary: amendment, addendum, corrigendum, change notice, revised invitation, bulletin, question-and-answer release or replacement attachment. Preserve the buyer’s label in `change_type_raw`, then classify its function separately. A portal alert that says “new files available” is a distribution event, not the amendment itself. Link the alert to the issued object. If no object can be found, keep `announced_but_missing` open.
Each row needs a stable identifier or a recorded absence of one; issue, publication, receipt and observation times; issuer and channel; procedure, lot, stage and audience; predecessor or changed-object reference; change description; file manifest; acknowledgement instruction; and public or controlled evidence locations. Record how the row was discovered. Preserve the source text for identifiers and scope. Normalized values help agents compare records, but they sit beside the original rather than replacing it.
FAR 15.206 gives a concrete example of useful amendment fields: issuing activity, solicitation number and date, amendment number and date, page count, change description, point of contact and any revised closing date. Standard Form 30 exposes the solicitation reference, amendment number, effective date, description and acknowledgement instruction. Those fields belong to the U.S. federal context, not a universal template. Their value here is evidentiary: they show that identity, scope and bidder action must travel together. In another jurisdiction, use the fields and rules the buyer actually issued.
| Field | Record | Do not substitute |
|---|---|---|
| change_id | Buyer identifier plus source | Local filename alone |
| changed_object | Notice, clause or prior version reference | Assumed predecessor |
| applicability | Procedure, lot, stage and audience | Tender title |
| times | Issue, publication, receipt and observation | Browser modified date |
| package_manifest | Listed and observed files | Change-summary prose |
| bidder_action | Acknowledgement or other instruction | Receipt assumed complete |
Completeness
Test continuity instead of choosing the highest number
Order the rows with the buyer’s own sequence and explicit references. If a system uses consecutive amendment numbers and the visible set is 01, 02 and 04, the result is `sequence_gap` until 03 is found or the buyer’s record explains why it does not exist for this scope. Amendment 04 may contain the newest date and still fail the completeness test. The same rule applies to a change notice that references a predecessor you cannot retrieve, an email that cites an attachment you do not hold, or an OCDS amendment whose `amendsReleaseID` is absent from the inspected releases.
Do not manufacture continuity when numbering restarts by lot, office, fiscal year or procurement stage. First learn what the identifier means in that system. Some changes are consolidated: TED says a later change notice integrates earlier changes into the notice text while the changes section describes the latest changes. A consolidated view can support the current notice state, but it does not prove that the bidder possesses every external document or understands every earlier bidder action. Record `consolidated_current_state` and retain the referenced chain.
Check negative evidence carefully. A history page that shows no amendments means “none found on that history page at `observed_at`.” It does not prove that the buyer issued none through a designated portal or audience-specific message. The valid state is `no_amendment_found` with source coverage and time, not `no_amendment_exists`. If a channel was required but unavailable, use `source_unavailable`. If an item was found but its lot or audience is unclear, use `applicability_unresolved`. These states keep missing knowledge from becoming a false assurance.
| State | Meaning | Permitted consequence |
|---|---|---|
| complete_through_checked_at | Covered sources support a continuous applicable chain | Route package to controlled intake |
| sequence_gap | Expected link or number is missing | Block completeness claim |
| source_unavailable | A designated channel could not be checked | Seek authorized access |
| applicability_unresolved | Scope or audience cannot be fixed | Escalate interpretation |
| acknowledgement_pending | Package is known but required action is open | Assign authorized owner |
| no_amendment_found | No change found within stated coverage | Keep qualified and recheck |
| stale_check | Validity window or change trigger has passed | Run the check again |
Files
Prove which files arrived, not only which amendment was listed
An amendment row can be present while its package is incomplete. Capture the buyer’s attachment list or a permitted portal inventory, then reconcile each listed object with the controlled copy. Record the source filename, media type, byte size and a cryptographic fingerprint when local policy permits. Also record whether the file opens and whether password protection, corruption or unsupported format prevented inspection. A fingerprint proves that two byte streams match. It does not prove that the file is authoritative, safe, readable or applicable.
Names and timestamps are weaker signals. “Pricing.xlsx” can replace an earlier file of the same name. A browser download time says when the bidder saved the file, not when the buyer issued it. A PDF creation property can come from export software and need not be the publication time. Keep those observations, but do not promote them. Prefer a buyer manifest, portal object identifier, issue metadata and content fingerprint in combination. Where the portal offers only a mutable download link, preserve the stable procedure and document identifiers plus the permitted evidence needed to retrieve it again.
The buyer’s change summary is an index, not a completeness certificate. Compare the manifest even when the summary names one clause. Revised workbooks can contain formula, validation or layout changes not explained in prose. This dossier stops after proving receipt and identity. The separate live-addendum workflow compares old and new content, determines impact and changes the response. Do not edit answers, prices, schedules or submission fields during the completeness check.
- Preserve the buyer’s observed file list before downloading replacements.
- Store fingerprints beside source and observation metadata, not as standalone proof.
- Mark missing, unreadable and access-restricted objects separately.
- Retain superseded files under control so later comparison remains possible.
- Pass only the accepted package boundary into response-change analysis.
Bidder action
Keep receipt, applicability and acknowledgement separate
Downloading an amendment proves neither applicability nor acknowledgement. Read the amendment and the tender’s communication rules for lot, stage, supplier audience and required act. FAR 52.215-1, for example, says offerors must acknowledge solicitation amendments by the date and time specified in the amendments. FAR 52.214-3 lists permitted acknowledgement methods for covered invitations for bids and requires receipt by the specified place and time. Standard Form 30 also carries acknowledgement instructions. These are procedure-specific duties. Elsewhere, the portal may use a click, signed form, message or no formal acknowledgement at all.
Put the duty in a separate action record: `required`, `method`, `due_at`, `authorized_actor`, `evidence_location` and `status`. An agent can extract the instruction and prepare the correct reference. It cannot click acceptance, sign, return a form or send an email simply because it found the amendment. Those acts can bind the bidder, disclose participation or affect admissibility. They require the authority and controls that govern external procurement communication.
An acknowledgement receipt does not prove that the response was updated. Conversely, a revised response does not prove that the buyer received the acknowledgement. Keep both traces. When applicability is disputed, cite the exact lot or audience text and escalate. Do not decide legal effect from a filename, a generic “all suppliers” banner or a colleague’s recollection. A qualified reviewer may conclude that a change does not apply, but the amendment row remains in the register with the grounds for that decision.
| Control | Question | Evidence |
|---|---|---|
| Receipt | Did the bidder obtain the issued object? | Channel event and matched file |
| Applicability | Does it govern this lot, stage and bidder? | Buyer text and authority review |
| Acknowledgement | Was the required act completed on time? | Authorized action and receipt |
| Response update | Were affected bid artifacts corrected? | Separate controlled change record |
Agent handoff
Return a result that expires and can be independently checked
Lead the output with machine-readable facts rather than a confidence score. Expose `claim_key`, `source_coverage`, `amendments`, `chain_edges`, `package_objects`, `decision_state`, `unresolved_items`, `acknowledgement_actions`, `checked_at`, `valid_until`, `next_check_at` and `next_action`. Every decisive field should point to a public citation or a precise restricted evidence reference visible only to authorized users. Unknown values remain null. A second agent should be able to challenge the chain without reconstructing it from narrative prose.
Set `valid_until` from the procurement’s change rate, response deadline and notification pattern. An event trigger is usually stronger than a distant date: invalidate the record when the notice version changes, the portal inventory changes, a new buyer message arrives or a package fingerprint differs. Schedule another check before major pricing approval and immediately before submission. “Continuous monitoring” is not an evidence state unless a named service supplies auditable events and its coverage is known.
The next action follows the state. `complete_through_checked_at` routes the accepted package and register to controlled document intake. `sequence_gap` routes a missing-object request for authorized review. `source_unavailable` routes an access request. `applicability_unresolved` routes a cited question to the bid owner, buyer or counsel as permitted. `acknowledgement_pending` routes the exact required act to its authorized owner. No state permits the discovery agent to modify the bid or submit it. That boundary keeps a useful research agent from becoming an uncontrolled bidder.
| Key | Value |
|---|---|
| claim_key | NTA/ICT/26/17, lot 2, tender stage |
| observed_sequence | 01, 02, 04 |
| decision_state | sequence_gap |
| missing_object | Amendment 03 or buyer explanation |
| package_intake | blocked |
| next_action | Prepare access request for authorized sender |
| checked_at | 2026-09-18T14:05:00Z |
What good looks like
Useful outcomes from latest tender amendment
- The latest-available claim is tied to one procedure, lot, supplier audience, stage and checked time.
- Every designated public, portal and direct-notification channel is either checked or recorded as unavailable.
- Each amendment has an identifier, source, issue time, scope, package manifest and link to the object it changes.
- Sequence gaps, inaccessible messages and uncertain applicability remain visible instead of being silently waived.
- Mandatory acknowledgement is tracked as a separate controlled action with its own evidence.
- Only a complete, current package enters controlled document intake and downstream response-change work.
Operating model
How to run the work
- 01
Fix the claim boundary
Record procedure, notice lineage, lot, response stage, supplier audience, designated channels and the exact `checked_at` instant before searching for changes.
- 02
Enumerate every change channel
Use the tender instructions and source-authority record to list the official notice history, document portal, buyer page, Q&A area and any named direct-notification route.
- 03
Build the amendment chain
Create one row per change object and connect it to the notice, document or earlier amendment it changes. Preserve missing sequence positions and unresolved references.
- 04
Reconcile the issued package
Match listed attachments to controlled files by name, size, date and fingerprint where practical. Record unreadable, absent and silently replaced files.
- 05
Decide, expire and route
Publish a controlled state with citations, `valid_until`, `next_check_at` and the next permitted action. Route a complete package to intake; route gaps to access or clarification.
Evaluation
Questions that change the decision
- Does every candidate change belong to the same procedure and notice lineage?
- Which lots, stages and supplier groups does each amendment cover?
- Do the tender instructions name more than one publication or notification channel?
- Does the observed sequence have a missing number, broken predecessor or unexplained jump?
- Does each issued file match the buyer’s manifest or a captured portal inventory?
- Does a change require acknowledgement, registration, a new form or another controlled act?
- Can the evidence support `complete_through_checked_at`, or must the state remain qualified?
- When must the sources be checked again before planning, response work or submission?
Failure modes
Where teams lose control
A current-state page can hide the publication path that produced it.
A numerically highest amendment can coexist with an earlier missing amendment.
A public notice can be complete for publication data while a designated portal contains additional files.
A notification email can announce a change without carrying the controlling attachment.
A file can change while retaining its name and apparent document type.
A clarification can alter the required response even when it is not labelled as an amendment.
An amendment may apply to one lot, invited group or negotiation stage rather than every bidder.
Receiving the correct file can be mistaken for completing a required acknowledgement.
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.
- designated change channels checked with a recorded observation time
- amendment rows with stable identity, applicability and predecessor evidence
- listed files matched to controlled copies and content fingerprints
- sequence gaps and unavailable sources resolved before package intake
- acknowledgement duties with an authorized owner and completion evidence
- completeness decisions that state their source coverage and expiry
- rechecks completed after new notices, messages or file changes
- downstream response updates traceable to an accepted amendment record
Questions
Common questions
Does the highest amendment number prove that I have the latest pack?
No. It identifies the highest number you found. Check the expected sequence, predecessor references, all designated channels and every listed file. A missing earlier amendment leaves the chain incomplete.
Can a consolidated notice replace the amendment history?
It can support the current notice state. Keep the change references and check external documents, messages and bidder actions separately. Consolidated notice text does not prove possession of every changed attachment.
What should I record if no amendment is visible?
Use `no_amendment_found` with the procedure scope, channels checked and `checked_at`. Do not convert that bounded observation into a claim that no amendment exists.
Is the date in the filename reliable?
It is an observation, not authority. Prefer the buyer’s amendment identifier, issue metadata, portal object record and publication history. Keep filename dates only as supporting evidence.
Does a file hash prove that the document is current?
No. A matching hash proves that two byte streams are identical. Authority and currency still depend on the buyer source, object identity, applicability and check time.
Should an official Q&A release enter the register?
Yes when it changes, corrects or authoritatively explains a bidder obligation. Preserve its buyer-defined status instead of automatically relabelling every answer as a formal amendment.
Can an agent acknowledge an amendment for me?
Only within an explicit authorization and controlled external-action process. Discovery alone never grants permission to click, sign or send. The agent can extract the duty and prepare the action for its authorized owner.
When does the completeness decision expire?
At the recorded `valid_until`, or sooner when a notice, portal inventory, buyer message or file changes. Recheck before material approval and again immediately before submission.
Sources
Primary references
- TED eForms change notices Publications Office of the European Union
- TED notice and version identifiers Publications Office of the European Union
- TED eForms notice-reference guidance Publications Office of the European Union
- UK guidance on modifying a competitive procurement UK Cabinet Office
- Find a Tender OCDS release-package API UK Cabinet Office
- OCDS updates and amendments Open Contracting Partnership
- OCDS record and version history Open Contracting Partnership
- FAR 15.206, amending the solicitation Acquisition.gov
- FAR 52.215-1, amendment acknowledgement Acquisition.gov
- SAM.gov Opportunities public API limits U.S. General Services Administration
- Standard Form 30 U.S. General Services Administration
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.