How to Catch Drawing and Spec Contradictions Before They Become RFIs
Most RFIs are not surprises. They are contradictions that were already in the set on the day it was issued: a detail callout that points nowhere, a door schedule that disagrees with the plan, an equipment cut sheet heavier than the structure below it. The conflict was there to be found. Review just ran out of time before it reached that page.
The fix is not heroics on the night before the deadline. It is a repeatable workflow that treats the set as one cross-referenced document instead of a stack of independent sheets. Here is the sequence that works.
Assemble the full set, not just the sheets you changed
Contradictions live in the seams between disciplines, so a partial review finds partial conflicts. Pull every drawing, the complete project manual, and all schedules into one place before you start. If the set syncs from Procore or another system, confirm you are reviewing the current revision, not last month's.
Reconcile the schedules against the plans first
Schedules are where the highest-frequency conflicts hide. Walk the door, window, finish, and equipment schedules against what is actually drawn. A door that appears on the plan but not the schedule, or a hardware set the spec never defines, is a rough-in RFI waiting to happen.
Trace every reference to its destination
Every detail bubble, section cut, and sheet note should resolve to something real. Follow them. A callout to 5/A-501 means nothing if A-501 ends at detail 4. These dead references are cheap to fix in review and expensive to discover in the field.
Cross-check the disciplines against each other
Lay the architectural backgrounds against structural and MEP. Look for the duct routed through a beam, the equipment that lands where there is no support, the dimension that disagrees between two disciplines drawing the same wall. This is the coordination pass that the trades will otherwise run for you on site.
Rank what you find by field impact
Not every conflict is worth a phone call. Sort the findings by what they cost if they reach the field, cite each one to the exact page, and route the ones that matter into RFIs while there is still time to resolve them on paper.
The takeaway
Run this pass on the whole set, every issue, and the RFI log gets shorter and cheaper. Lintel automates the cross-referencing so the five steps above happen across thousands of pages in one pass, with every finding cited to its source.