Two kinds of gap, and they need different fixes
Referenced but not supplied
The tender explicitly asks for a document — a financial capacity statement, a specific certification, a signed returnable form — and it simply isn't in the pack your team assembled. This is the costliest kind, because evaluators typically check mandatory-adjacent attachments first, and a missing one can flag the whole submission before anyone reads the narrative response.
Implied but unaddressed
The tender doesn't name a specific document, but a requirement can't credibly be answered without evidence behind it — a claim of "5 years' experience in this exact scope" with no project references to back it up, for instance. These are subtler because nothing is technically "missing" from a checklist; the response is just weaker than it should be.
Why these slip through
Both kinds of gap share a root cause: they're most visible when someone reads the entire pack in one structured pass, cross-referencing every requirement against every supplied document. Most bid teams don't read it that way — they divide the pack by section, each contributor reads their part, and nobody has the full cross-reference in their head at once. A gap that spans two people's sections is nobody's specific responsibility to notice.
A practical way to catch them
- Build one inventory of what was actually supplied — every file, cross-checked against every document the tender mentions by name, including inside nested folders or archives.
- List every "must provide," "must demonstrate," or "must evidence" statement in the pack, regardless of which document it's in.
- Match the two lists. Anything on the second list without a clear match on the first is a gap — flag it as either "chase the document" or "someone needs to write supporting evidence."
- Re-run the match after every addendum. A late addendum can add a new evidence requirement that easily gets missed if the compliance check only happened once, early.
What a real gap looks like
In our alliance RFT teardown, the schedule of alliance participant financial capacity statements was referenced in the Tender Conditions document as a required attachment — and wasn't among the five documents actually supplied. That's exactly the pattern: a specific, named, mandatory-adjacent document, invisible until someone checks the reference against the inventory rather than just reading the pack front to back.