Completeness check

Completeness checking is the gate in front of the gate. Authorities and expertise bodies check submissions against a codified intake checklist and reject incomplete sets without reading further; owners and contractors run the same discipline on tender packages, vendor documentation and handover dossiers. The logic is procedural fairness and efficiency in one: substantive review clocks should not start on packages that cannot pass.

The check is mechanical in principle — does item 14 exist, is it signed, is it the required revision — and laborious in practice, because "the required contents" is itself a moving target that varies by jurisdiction, project category and submission type, and because the set being checked runs to hundreds or thousands of files assembled from multiple organisations.

What makes incompleteness expensive is asymmetry. The missing item is usually trivial to produce; the rejection that discovers it costs a full resubmission cycle. Teams that treat completeness as a formality to be checked at the end, rather than a structure the package is assembled into from the start, pay for the same trivial items several cycles in a row.