A crew has forms set, steel on site, and a pour window that will not wait. Then the architectural plan calls out one opening dimension while the structural sheet shows a beam landing where that opening needs to be. That is when construction RFIs stop being paperwork and become the difference between a clean decision and expensive rework.
The drawings never match perfectly. Different disciplines issue at different times. Revision clouds disappear between sets. A detail changes but the plan view does not. The field is left holding the conflict, usually at the exact moment work needs to move.
A good RFI does not make the designer hunt through a stack of PDFs to figure out what the question means. It puts the conflict in plain view, cites the source sheets, explains the field impact, and asks for a decision that can be built.
Why field RFIs get stuck
Most delayed RFIs are not delayed because the question is difficult. They stall because the question arrives stripped of context.
“Please clarify beam at Grid C” is not enough. Which beam? Which level? Which structural revision? What does the architectural set show at that location? Is the conflict between a beam depth and a ceiling elevation, a post location and a door opening, or a dimension and the grid line? The person receiving it should not need a scavenger hunt before they can answer.
The same problem shows up when an office-based workflow forces the field to send a photo, call the superintendent, wait for someone to find the right sheets at a desktop, then retype the issue into a formal system. By the time the RFI is logged, the crew has either stopped, worked around it, or made a decision without the design team.
That is not a crew problem. It is a broken information path.
There is also a language problem on many jobsites. A lead may understand the condition perfectly but lose precision when explaining it through a rushed phone call or an English-only form. An RFI needs construction terminology that travels cleanly between the crew, superintendent, architect, engineer, and subcontractors. If the question changes meaning at every handoff, the answer will too.
What a buildable construction RFI includes
An RFI is not stronger because it is longer. It is stronger because it is specific. The best field RFIs give the reviewer enough evidence to make a decision without burying the decision inside a paragraph.
Start with the exact location. Name the building area, level, grid references, room, elevation, or footing mark that puts everyone at the same point on the job. “Level 2, between Grids 4 and 5 at Line B” is useful. “North side” may not be.
Then identify every source that conflicts. Cite the architectural sheet and revision date, the structural sheet and revision date, and the detail or schedule if it controls the condition. Do not assume the latest drawing in one discipline was coordinated with the latest drawing in another. Revision drift is common, especially when a field team receives partial updates.
State the conflict in construction terms. For example: “A-201, Rev 3 shows a 3-foot-0-inch door opening centered on Grid 5. S-102, Rev 2 shows an 18-inch-wide concrete pier centered on Grid 5. The pier blocks the opening as drawn.” That is a condition a designer can verify.
Finally, explain the immediate field consequence and ask a direct question. The consequence is not drama. It is decision-making context: forms are ready, rough opening framing cannot proceed, reinforcing steel placement is pending, or the pour sequence will be affected. Ask whether the opening moves, the pier moves, the structural member is revised, or another approved detail governs.
Avoid proposing a fix as if it is already approved. Field experience matters, and a practical option can help move the conversation forward. But label it as an option. The architect or engineer still owns the design decision. The foreman owns making sure the conflict is seen before concrete, steel, or framing locks it in.
A field-ready RFI example
Subject: Door opening conflicts with concrete pier at Level 2 Grid 5
References: A-201 Rev 3, Detail 4/A-601 Rev 3, S-102 Rev 2
Condition: A-201 shows a 3-foot-0-inch door opening centered on Grid 5. S-102 shows an 18-inch concrete pier centered on the same grid line. The pier location occupies the door opening shown on the architectural plan.
Field impact: Pier reinforcing and forms are scheduled for installation before the next concrete placement. Framing of the adjacent corridor opening cannot proceed without an approved location.
Question: Please confirm the governing layout and provide revised dimensions or a detail for the door opening and pier location.
That RFI is short. It also gives the reviewer a location, the documents, the contradiction, the schedule effect, and a decision to make. No guessing.
Find the conflict before the crew finds it the hard way
The best RFI is often the one raised before the crew is standing in front of the problem. That requires comparing architectural and structural sets as a coordinated pair, not reviewing each sheet in isolation.
On an active job, focus that comparison around work that becomes hard to change: layout lines, footing and pier locations, slab depressions, embeds, openings, headers, bearing points, roof framing, and major dimension chains. A mismatch in a finish note can matter. A mismatch in a load-bearing wall location can stop the job.
Revision dates deserve the same attention as dimensions. A current architectural sheet paired with an older structural sheet can look coordinated until a grid shifts, an opening moves, or a column schedule changes. When there is a question, confirm that the team is working from the same issued set before treating it as a design conflict.
This is where field-first drawing reconciliation changes the workflow. Instead of flipping between sheets on a trailer monitor, a crew can compare plan sets where the work is happening, identify the discrepancy, and preserve citations with the finding. TrueStruct is built around that jobsite reality: spot the conflict on a phone, review it with a qualified person, and draft an RFI while the condition is still in front of the crew.
Automation should identify and organize the issue. It should not silently decide what gets built. A superintendent, foreman, architect, or engineer still needs to adjudicate the condition. That human check is not bureaucracy. It is accountability.
Send the RFI to the person who can answer it
A clean RFI can still lose days if it goes to the wrong place. Structural conflicts belong with the structural engineer or engineer of record through the project’s approved communication path. Architectural layout, finishes, clearances, and room configuration questions generally need the architect. Conditions involving both disciplines should make the coordination visible rather than forcing one party to guess what the other intended.
Do not use an RFI to document a change that has already been directed informally. If a superintendent receives a verbal instruction, get it confirmed in writing with the controlling reference. Verbal direction may keep work moving for an hour. It does not protect the crew when the next trade arrives and sees something different.
The response also needs to return to the field in a usable form. “Coordinate in field” is not a decision when two dimensions physically cannot occupy the same space. Ask for revised dimensions, a marked-up detail, a governing sheet, or a clear instruction. Then make sure the answer reaches the people laying out, forming, framing, or installing the work - not just the project folder.
Keep a practical RFI trail
Every RFI should leave a record that a foreman can use later. Save the original cited sheets, the submitted question, the response, the date received, and any revised drawing that follows. If the answer affects work already installed, record the affected area and communicate it at the next huddle.
This matters when a response conflicts with a later revision, when a trade claims it never saw the answer, or when a small field fix turns into a change-order argument. The point is not to create more admin. The point is to stop the field from carrying risk that belongs in the design decision.
Construction moves fast. The RFI process should move at the speed of the slab, the layout line, and the crew waiting on an answer. Put the conflict on the page, cite it precisely, ask for a buildable decision, and do it before the work makes the mistake permanent.