The covering email says please find attached our requirements for the referenced package. Everything that decides the bid is in the twenty-two files below it.
This is the normal shape of technical procurement, and it is where most automation quietly gives up. Documents get stored, indexed, made searchable. Storage is not reading. A file that has been indexed but never parsed into requirements contributes nothing to the next draft, and the system behaves as though it does not exist.
A document you have stored and not read is worse than one you never received, because it makes the record look complete.
Three ways the requirement hides
- In a scan. Older specifications and many customer-issued forms arrive as images. Without optical character recognition they are pictures of text, invisible to every downstream step.
- In a table or a drawing note. The operating temperature is a cell in a datasheet. The coating standard is a note in the corner of a drawing. Neither reads like prose and both are binding.
- In an amendment. Issued after everyone read the original, changing a small number of things, and usually arriving as a document that looks like the one you already processed.
The third is the one that costs bids. The team read the tender properly on day one. The amendment landed on day nine, changed the delivery date and one material grade, and was filed by someone who assumed it was a resend.
What an amendment has to trigger
Capturing an amendment is not the same as noticing one. Noticing produces a notification. Capturing means the downstream work actually changes.
- The document is parsed and its requirement lines replace or add to the existing ones, so the matrix reflects the current tender rather than the original.
- Any quote that was audited against the old requirement is re-queued, because a changed material grade may have invalidated a price that was previously usable.
- The deadline is updated everywhere it is enforced, not just displayed, since the send rules depend on it.
- The people working the deal are told what changed, in specific terms rather than an alert saying a document was added.
Without that chain, an amendment is a notification, and notifications are the thing everybody has learned to dismiss.
The completeness question
There is a prior question that is easy to skip: do you have everything. Portals issue documents in batches, some behind separate links, some added later without announcement. A tender that appears to have eleven documents may have nineteen.
So the useful artefact is an inventory of what the request should contain against what has actually been read, with the gaps named. Not a folder. A count you can act on.
Sample data. Complete means read, not stored.
Why this is the unglamorous foundation
None of this is interesting to demonstrate. Parsing a scanned datasheet does not look like intelligence, and an inventory count is not a feature anyone asks for in a first meeting.
But every capability further up depends on it. The matrix cannot prove compliance against a requirement it never extracted. The reply cannot avoid contradicting a specification nobody parsed. The gate cannot check a claim against a document that was only ever filed.
Reading the attachment is not preparation for the work. On a technical tender it is most of the work.