Most GCs have a review process. Very few have a workflow. The difference shows up on bid day and again at final accounting.
A process is a list of things someone intends to do. A workflow is a sequenced, accountable system with defined inputs, outputs, and owners. When your estimating team reviews 2,000 pages of specs under time pressure, intent is not enough.
According to the 2024 Arcadis Global Construction Disputes Report, the average North American construction dispute is worth $60.1M. "Errors and omissions in contract documents" has repeatedly ranked as the leading dispute cause in North America. That is not a design problem. It is a review problem. And it is happening during preconstruction, not construction.
This article walks through how to build a preconstruction document review workflow that actually catches scope gaps, not just the obvious ones.
Scope gaps do not announce themselves. They hide in drawing conflicts, vague spec callouts, and the white space between trades. By the time they surface in the field, you are negotiating change orders you should never have needed.
Consider a few real examples from Provision's Scope Gap Playbook, drawn from interviews with 200+ general contractors:
None of these were estimating failures. They were review failures. The documents contained the information. Nobody had a system to find it.
A 2018 study by PlanGrid and FMI projected that miscommunication and bad project data cost the U.S. construction industry $31.3B in rework annually. Communication breakdowns alone accounted for 26% of that rework. Bad project data accounted for 22%.
Those numbers start in pre-construction.
A reliable scope gap review process has four phases. Each phase has a defined purpose, a defined owner, and a defined output. Miss one and you are back to hoping for the best.
Before anyone reviews anything, every document in the project set needs to be logged, version-controlled, and distributed to the right people. This sounds obvious. It is almost never done correctly.
The intake phase must capture:
Addenda handling is where most GCs slip up. An addendum issued on day 3 of a 10-day bid period can rewrite scope for two trades. If your team is still working off the original set, you are pricing the wrong project.
Assign one person as the document-of-record owner. That person tracks every revision and flags changes to the estimating team within 24 hours of receipt.
This is the phase most GCs skip or compress. It is also the phase that produces the most recoverable scope gaps before bid day.
The goal is to read the drawings as a system, not as individual sheets. Structural drawings need to be read against architectural drawings. MEP overlays need to be read against the ceiling plan. Civil grades need to be read against architectural floor elevations.
Common conflicts to flag in this phase:
Each conflict becomes a bid clarification request, a cost allowance, or a documented exclusion. The point is to make the decision before bid day, not after.
This is also where Chat Agent is useful. It lets your team ask direct questions about specifications, drawings, and contracts and get cited answers in under 20 seconds. Instead of spending 40 minutes hunting through a 2,000-page project manual, your estimator asks the question and gets the answer with the exact clause and page reference attached.
Once conflicts are logged, the next step is building a complete scope matrix by trade. Every scope item needs a designated owner: a sub, an allowance, or an explicit GC-self-perform line.
The anti-pattern here is writing "as per plans and specs" in the scope sheet. That phrase has produced more disputes than almost any other in construction. It transfers risk to your subs on paper and then brings it back to you in the field.
As one Estimating Manager at a Canadian ICI GC told us: "We have fewer subs who just take things on a gentleman's agreement. They've become more quick to clarify that they're not including that one piece of scope."
Every scope sheet needs specific document references, not generic incorporation. Instead of "as per plans and specs," write "as per Structural Drawing S3.1, Rev. 2, dated March 14, 2026, and Specification Section 03 30 00."
For GCs handling high volumes of pursuits, Scope Agent generates complete, trade-by-trade scope packages directly from the project documents. It reads the full project set, drawings and specs together, and produces structured output in under 60 minutes. Internal validation shows 97% match accuracy on scope item extraction. Human estimators working the same exercise averaged 91.3% at roughly four days per project.
That gap matters at buyout. It matters more when a sub brings a claim.
For a deeper look at how top GCs structure subcontract language, the subcontract language chapter of the Scope Gap Playbook covers the most common clause-level failures in detail.
The final phase is a structured review gate before the bid goes out. Not a five-minute scan. A documented checkpoint with defined questions and a sign-off requirement.
The pre-bid review should answer these questions:
The pre-bid checkpoint is one of the Eight Habits documented across 200+ GC interviews in the Scope Gap Playbook. Firms that run it consistently report fewer post-award surprises and faster buyout conversations. It does not take long. It takes discipline.
The Scope Gap Playbook identifies eight habits that separate GCs with tight margins from those constantly fighting change orders. A structured review workflow gives you the infrastructure to practice all eight consistently:
None of these require more staff. They require a workflow that makes them the default behavior.
AI does not replace structured review. It makes structured review faster and more thorough, which matters when your team is running eight pursuits simultaneously.
Provision has processed over 100,000 construction documents and reviewed over $100 billion in project value. The patterns that produce scope gaps are consistent. They repeat across project types, geographies, and firm sizes.
Here is where AI tools add genuine value in the workflow described above:
Risk Review has identified over 1,000,000 risks across the projects Provision has processed. Every risk is cited to the exact clause, section, or page. That is not a summary. That is a reference you can use in a negotiation or a claim.
See how EllisDon used Provision to save $1.8M on a single project, or review the NAC case study to see how structured AI-assisted review changed their pre-construction process.
Every GC's pre-construction workflow is different. But a reliable bid document review checklist has the same core structure regardless of project type or delivery method.
Use this as your starting point. Adapt it to your project type, your subs, and your contract model.
For trade-specific scope gaps by division (MEP, envelope, concrete, steel, and more), the trade-specific chapter of the Scope Gap Playbook is the most detailed public resource available for GCs in 2026.
If you want to see how Scope Agent handles scope package generation from your actual project documents, book a demo with Provision.
A preconstruction document review workflow is a sequenced process for reviewing all project documents (drawings, specs, contracts, addenda) before bid submission. It assigns owners, defines outputs, and includes checkpoints to catch scope gaps, drawing conflicts, and contract risks before they become field problems or disputes.
For a complex commercial or ICI project, a thorough manual review takes 30–40 hours per bid. With AI tools like Scope Agent reading the full project set (drawings plus specs), that process can be completed in under 60 minutes. The time savings allow your team to pursue more bids with the same staff.
Based on 200+ GC interviews for the Scope Gap Playbook, the most common gaps occur in MEP (generator conditioning, motor starters, fire-rated louvres), envelope (roof cover board, masonry flashings), concrete (slab assemblies, base plate grouting), and specialty trades (lead-lined glass, curtainwall mock-ups). Most gaps are visible in the documents. They are missed because no one had a system to find them.
"As per plans and specs" is the most cited anti-pattern in scope writing. It looks like a complete reference but transfers risk without actually defining scope. When a dispute arises, that language gives subs room to argue what was and was not included. Replacing it with specific drawing and spec references eliminates most of that ambiguity.
AI built for construction can read the full project set (drawings, specs, contracts, and addenda together), identify cross-discipline conflicts, extract trade-by-trade scope items, and flag contract risks with exact clause citations. Provision's Risk Review delivers an 80% reduction in contract and spec review time. Chat Agent answers specific document questions in under 20 seconds, with the source cited.
A bid document review checklist covers what to check. A scope gap review process defines who checks it, when, and what the output looks like. The checklist is a tool inside the process. Without the process, checklists get skipped under bid-day pressure. You need both, structured in sequence, with defined sign-offs.
Post-award change orders are the clearest signal. If your team regularly fields sub change orders in the first 30 days after award, those gaps were visible in the bid documents. A structured review with cross-discipline conflict checking and trade scope assignment will surface most of them before bid day. The Scope Gap Playbook offers a detailed diagnostic across all major trades.
Scope Agent reads your full project set and builds trade-by-trade packages in under 60 minutes.
See Scope AgentMore Articles
