Most RFIs come from problems that were visible in the drawings before the bid went out. A conflict between the structural and architectural drawings. A spec section that calls for a product the drawings never locate. A requirement nobody assigned to a trade. If your team finds it after award, it costs money. If you find it before bid day, it costs an hour.
This checklist is built for GC preconstruction teams running pre-tender drawing reviews. Use it on every pursuit. It will not replace judgment, but it will stop the patterns that cause the most expensive RFIs.
The 2024 Arcadis Global Construction Disputes Report puts the average North American construction dispute value at $60.1 million. Errors and omissions in contract documents rank as the leading dispute cause in North America. These are not site problems. They are document problems that go undetected through bid.
A 2018 PlanGrid and FMI study estimated that miscommunication and bad project data drive $31.3 billion in U.S. rework annually. A large share of that traces back to scope that was unclear at tender. The bid documents had the information. Nobody read them closely enough before bid day.
The goal of a pre-tender drawing review is simple: find what is missing, conflicting, or unassigned before the bid leaves your office. What you find becomes an RFI to the design team, a bid qualification, or a flag for your scope packages. What you miss becomes a change order.
For a deeper look at how scope gaps compound from bid through buyout, see the Scope Gap Playbook, built from interviews with more than 200 general contractors.
Before reviewing any drawings, confirm the set is complete. An incomplete document set produces false confidence. You review what you have and miss what is not there.
Addenda are where this breaks down most often. A late addendum revises a spec section and nobody updates the drawing index. Your team prices the original. The winning number reflects the original. The contract reflects the addendum. That gap is a change order before the job starts.
Drawings and specifications should tell the same story. When they do not, you have an RFI. When nobody catches it before bid day, you have a dispute.
The last item is where MEP scope gets lost. Equipment appears on the mechanical drawings. The spec section names performance requirements. Neither document says who provides the disconnect, who sets the base, or who tests the unit. That undefined scope lands in the gap between two subs. For a full breakdown of where MEP scope goes missing, see the trade-specific scope gaps chapter of the Scope Gap Playbook.
Most expensive RFIs do not come from a single discipline. They come from two disciplines that have not been read against each other. Structural versus architectural. Mechanical versus structural. Civil versus architectural. The drawings are technically correct in isolation. Together, they contradict.
The Scope Gap Index, tracking 1,290 scope packages across 24 projects in Q3 2026, found that anchors, embeds, and connections were flagged in 48% of all packages. That is the cross-discipline pattern in action: the structural drawing shows the embed, the concrete scope does not name who sets it, and the structural steel scope assumes it is already there. Find it at the Scope Gap Index.
A drawing can show every item correctly and still produce change orders if nobody has assigned the work to a trade. This is the unassigned scope problem. It is especially common on coordination items: the item is real, it is on the drawings, and it is in nobody's scope.
These eight items appear in nearly every project. They are rarely assigned clearly in the bid documents. If your scope packages do not answer each question explicitly, the sub will answer it in their bid: usually by excluding it. The trade-specific scope gaps chapter documents the dollar cost of leaving these items open. A single missed roof cover board on a $50 million project cost one GC $400,000, absorbed under readily inferable language.
As one Pre-Construction Lead at a Top-ENR Canadian GC put it: "If you miss anything, they'll bill it."
Addenda change the project. They revise drawings, modify spec sections, and sometimes contradict earlier documents. If your review does not account for every addendum, your review is out of date before you finish it.
The manual version of this check takes hours on a large document set. Provision's RFI Agent reviews drawings and specifications against each other and can surface more than 100 potential issues from a document set in an hour. Every finding carries source evidence: the exact specification page or drawing. Your estimator reviews the findings and decides what becomes an RFI, a bid qualification, or a flag for the scope package.
Not every issue you find warrants an RFI to the design team. Some issues are better handled as bid qualifications. Others require the design team's answer before you can price the work. This distinction matters. An RFI pauses the question. A bid qualification answers it on your terms.
The readily inferable question is worth flagging separately. Many standard form contracts require a GC to perform work that is "reasonably inferable" from the contract documents, even if it is not shown explicitly. Owners and designers use this language to deny change order claims on coordination items and unassigned scope. If the work is on the drawings and in the spec but not in your scope, you may own it anyway. Finding it before bid day is the only way to price it or qualify it out.
Provision's Risk Review surfaces these contract exposures in full, flagging the clause, the section, and the severity. It covers contract review, spec review, and cross-document conflict detection in one workflow.
A thorough pre-tender review on a large commercial package can take two to three days manually. Here is how most GC preconstruction teams structure the work.
Provision's RFI Agent handles the discovery step. It reads the drawing set against the specifications, finds conflicts, omissions, and unclear requirements, and produces a reviewed issue report your preconstruction team takes to the owner and design team before tender. Your estimator reviews each finding and sets the action: RFI, bid qualification, trade coordination item, or no action. The report exports as one document.
Clark Construction's Markee Foster, Project Manager, described the output directly: "I went through the first 30, and of the first 30 I picked close to 22 that I would have submitted as RFIs. It turned out that some of the subs we've been working with caught the same things."
A pre-tender drawing review is a structured check of the full project document set before a GC submits a bid. The goal is to find drawing conflicts, spec omissions, and unassigned scope items early enough to issue RFIs, write bid qualifications, or adjust scope packages before bid day.
Manual review of a mid-size commercial package typically takes two to three days for an experienced estimator. Provision's RFI Agent can surface more than 100 potential issues from the same document set in an hour, shifting time from hunting to deciding.
An RFI asks the design team to resolve a conflict or fill a gap before you price the work. A bid qualification states your pricing assumption in writing, without waiting for a design team response. Some issues warrant an RFI. Others are safer as a qualification if the design team response timeline is tight.
Cross-discipline conflicts are the most costly. Structural versus architectural dimensions, MEP routing through structural members, and unassigned coordination scope (embeds, penetrations, firestopping) each carry significant change order risk. The Scope Gap Index found these categories flagged in 39%–48% of scope packages reviewed in Q3 2026.
Provision's RFI Agent reviews drawings and specifications against each other, surfacing conflicts, omissions, and unclear requirements before tender. It produces a reviewed issue report filtered by impact, discipline, and type. Your estimator reviews each finding and decides the action: RFI, qualification, or no action. It does not issue RFIs automatically or replace estimator judgment.
Many standard form contracts require a GC to perform work that is reasonably inferable from the documents, even if not shown explicitly. This language is used to deny change orders on coordination items. Finding unassigned scope before bid day lets you price it, qualify it out, or issue an RFI. Finding it after award means you likely own it.
Yes. This checklist is format-independent. Provision's products integrate with Procore, Autodesk, and SharePoint, so your team can run the same workflow without changing where documents are stored.
RFI Agent reviews your full drawing and spec set and surfaces potential issues in under an hour.
See RFI Agent