Direct answer: scope gaps usually arise when project documents describe the same work from different angles without being systematically reconciled. The earlier those interfaces are surfaced, the more options the team has to clarify, price, redesign or allocate responsibility.
One package can be defined by many documents
| Document | What it may define | Potential misalignment |
|---|---|---|
| Head contract | Principal obligations, programme, notices, quality | Flow-down duty not captured in subcontract |
| Subcontract | Package scope, price, risk allocation | Broad wording conflicts with tender exclusions |
| Drawings | Geometry, interfaces, details | Interface shown but not allocated |
| Specification | Performance, materials, workmanship | Requirement not visible in BOQ |
| Clarifications | Tender assumptions | Not incorporated into signed documents |
| Programme | Sequence, access, milestones | Duration assumes unavailable predecessor work |
A realistic example
A facade subcontract prices supply and installation to issued drawings. The specification requires perimeter fire-stopping, the drawings show the interface, the BOQ has no separate item, and tender correspondence says “builder by others” without identifying who “others” means. The gap may not become visible until the facade is ready to close.
At that point it affects access, sequence, delay, testing and commercial position. Before signature, the same issue could have been an ordinary clarification.
Structured comparison helps
A document-comparison workflow can extract requirements by package, identify conflicting descriptions, surface exclusions, compare programme duties and produce an issue register. AI can accelerate that preparation, but the output is a set of potential inconsistencies, not a legal conclusion.
Experienced review still decides
Commercial, project and legal personnel remain responsible for document precedence, contractual incorporation, risk allocation, entitlement and practical resolution. The value of finding a gap early is optionality: it can be priced, clarified, redesigned, excluded, reassigned or consciously accepted.
For Australian readers, see TEMRIK's Australian construction AI overview.
TEMRIK describes an AI-assisted construction scope review workflow and a related subcontract review process.
For commercial teams, the same comparison logic appears in quantity-surveying workflows, RFI preparation and variation evidence, where the issue has to be traced back to source documents rather than guessed.
General workflow information only, not project-specific legal advice.
External sources support the specific propositions attributed to them. Workflow examples are practical editorial examples, not statistics.