A column line is set. Forms are going in. Then the structural plan calls for a footing at Grid B-4 while the architectural set shows an opening that lands in the same place. Somebody pulls out a phone, somebody else starts flipping PDFs, and the crew waits for an answer that should have been caught before the pour.
That is the moment to create an RFI from a drawing conflict. Not after the concrete is placed. Not after a field fix becomes a change order. Right when the discrepancy is visible, located, and still cheap to resolve.
The goal is not to send more RFIs. The goal is to send fewer bad ones: RFIs that name the conflict, point to the exact sheets, show the relevant revision information, and ask for a decision the design team can actually make.
Why drawing conflicts turn into field delays
Architectural and structural sets are supposed to coordinate. On an active job, they often do not. A wall shifts on the architectural plan but the beam framing plan stays put. A dimension changes on one sheet without making it to the related detail. A revised grid bubbles onto one discipline's drawing set while an older reference remains on another.
The field team usually finds the gap first because the field has to build the condition as drawn. A superintendent sees it during layout. A concrete foreman finds it before reinforcement is tied. A framing crew catches it when a header has nowhere to land. The problem is not that people miss things. The problem is that the latest answer is often buried across separate sheets, dates, clouds, and discipline boundaries.
That is why a verbal call is not enough. Calls can get a crew moving, but they rarely preserve the decision, the source documents, or the exact condition that caused it. If the answer changes later, nobody wants to argue from memory beside a stack of marked-up printouts.
An RFI creates the record. Done well, it also gives the architect or engineer a short path to the answer.
Create an RFI from a drawing conflict before work moves
The right trigger is not simply, “I have a question.” The trigger is a conflict that changes what the crew can safely or correctly build.
Stop and document the issue when two current drawings give incompatible direction, when a required dimension or elevation is missing, or when a detail cannot physically work with the plan condition. You may also need an RFI when revision dates drift between related sheets and it is unclear which instruction governs.
Do not create an RFI for every minor coordination nuisance. If the contract documents already provide a clear governing note or detail, verify it with the project team's established process and proceed. But do not invent hierarchy where the documents are genuinely contradictory. The cost of a brief hold is usually lower than the cost of placing work that must be demolished, modified, or defended later.
A useful field test is simple: if two qualified people could read the issued drawings and build two different conditions, the issue needs a documented answer.
Confirm you are comparing the right sheets
Before writing anything, verify the sheet numbers, titles, and revision dates. This sounds basic because it is basic. It is also where many RFIs go wrong.
Compare the architectural plan with the structural plan, then check the referenced details, sections, schedules, and general notes. A plan conflict may be resolved in a detail. Or the detail may be the problem because it still carries an earlier condition.
For example, an architectural first-floor plan may show a 4-foot opening centered on a gridline. The structural framing plan may show a beam directly through that opening. The first task is to confirm both sheets are current and that no revised section shifts the beam, wall, or opening. If the conflict remains, you have a real field issue, not a page-management issue.
Capture the drawing identifiers exactly as issued. Include sheet number, sheet title, revision number or date, and the applicable gridline, room, elevation, or detail callout. “Plans do not match” is not actionable. “A1.2 Rev 3 and S2.1 Rev 2 conflict at Grid B-4” is.
State the conflict without guessing the fix
The best RFI language is factual. It does not accuse the architect, engineer, or another trade. It does not hide the issue under vague language. It also does not pretend the field has design authority.
Describe what each drawing directs. Then explain why both directions cannot be built together.
For the opening-and-beam example, the body of the RFI might read:
“Architectural Sheet A1.2, Revision 3, shows a 4-foot opening centered at Grid B-4. Structural Sheet S2.1, Revision 2, shows Beam B7 crossing the same opening location. No revised framing detail or header condition was found. Please confirm the required beam and opening configuration before framing proceeds at this location.”
That is enough to let the design team see the decision. It identifies the exact conflict and the effect on work without adding a paragraph of frustration.
Avoid writing, “Please advise.” It forces the reviewer to hunt for the question. Ask for the decision needed: confirm the governing dimension, provide a revised detail, identify the correct elevation, or issue direction for the missing structural element.
Attach evidence that survives the trailer meeting
An RFI is only as useful as its evidence. Attach the cited plan views or screenshots showing both conditions, with the location clearly marked. When the issue is tied to layout, include the grid intersection and a photo of the field condition if it adds clarity. When revision drift is involved, show the revision identifiers, not just the clouds.
The attachment should let someone understand the issue without calling the foreman for a guided tour. That matters when the architect is in another city, the engineer is reviewing between meetings, or the project manager forwards the RFI to a consultant who has not been on site.
Keep annotations clean. Circle the conflict, label the affected grid or dimension, and leave the drawing readable. A screenshot covered in arrows and commentary creates a second coordination problem.
Explain the field impact honestly
A good RFI includes impact, but impact should be specific rather than theatrical. Say whether layout is on hold, footing placement is pending, framing cannot continue, or a scheduled pour is affected. If work can proceed in other areas, say that too.
For example: “Footing layout at Grids B-4 through B-5 is on hold pending direction. Crews can continue layout in Areas C and D.” This gives the project team a real priority signal and shows that the field is managing the work rather than stopping everything for a single question.
It depends on the condition whether you need a full stop. A conflict involving structural load path, fire-rated assemblies, waterproofing continuity, accessibility clearance, or embedded items should not be treated like a cosmetic discrepancy. If a safe sequence of unaffected work exists, keep it moving. If proceeding would bury a bad assumption, hold the work.
A field-ready RFI workflow
The traditional workflow is page-flipping, screenshotting, emailing, then waiting while someone at a desk reconstructs the condition. That is backwards. The person looking at the forms, studs, or rebar should be able to capture the issue where it happens.
A field-first drawing reconciliation tool can compare architectural and structural sets, flag discrepancies, and attach source citations to the finding. With TrueStruct, the detected conflict can become a drafted RFI rather than another manual rewrite. The qualified person still reviews the wording, confirms the real-world condition, and makes the final call on what gets sent. Automation should find the mismatch faster. It should not replace judgment.
This is especially useful when the conflict is not obvious at a glance. A missing header, shifted gridline, mismatched dimension string, or stale revision can hide across dozens of pages. The crew does not need another enterprise system that assumes everyone is at a desktop. They need the relevant sheets, the exact discrepancy, and a clean question on a phone at the point of work.
For mixed English- and Spanish-speaking crews, clarity matters twice. The person documenting the condition and the person receiving direction must mean the same thing by “header,” “bearing wall,” “edge of slab,” or “centerline.” Keep the cited drawing language intact, use terminology the crew recognizes, and avoid vague translations that change the construction meaning.
What makes an RFI easy to answer
The fastest RFIs have a narrow decision path. They identify the conflicting documents, describe the buildability issue, show the evidence, and ask for one clear response. They do not make the reviewer search through a full plan set or guess which trade is affected.
Before sending, check four things: the sheets are current, the conflict location is unmistakable, the requested decision is specific, and the field impact is true. That last one matters. Inflating every issue as urgent trains the project team to ignore urgency. Understating a pour-day conflict leaves the crew exposed.
When the answer comes back, distribute it where the work is happening. Mark the affected sheets, brief the crew, and make sure the revised direction reaches the next shift. A closed RFI in a software log does not help if the carpenter at the wall still has the old plan in hand.
The drawings may never match perfectly. Your job is to catch the mismatch while it is still a question, document it while the facts are clear, and get a buildable answer before the work makes the decision for you.