A crew is standing at a layout line. The architectural plan calls for one opening width. The structural sheet shows a different condition, and the steel is due before lunch. Knowing how to route urgent RFIs is not about filling out a prettier form. It is about getting a clear, documented decision to the person who can make it before the crew guesses, waits, or builds the wrong thing.
An urgent RFI needs to move fast without becoming vague. “Please clarify” is not enough when a pour, install, or framing sequence is on the line. The person receiving it needs the exact conflict, the location, the current drawing references, and the field consequence of waiting. Give them that, and they can answer. Give them a blurry photo and a general complaint, and the job burns hours while emails bounce around.
Start by deciding whether work must stop
Not every drawing discrepancy is an emergency. Some can be logged and resolved before the affected work reaches that area. Others affect safety, structural integrity, inspection, dimensions, embeds, openings, or a critical sequence. Those are stop-and-route conditions.
If the conflict changes where concrete goes, where a beam bears, whether a header exists, the size of an opening, or the location of an anchor, do not let the crew solve it with field math. Pause only the affected operation if you can safely do so. Keep unrelated work moving. A full shutdown may be necessary during a pour or lift, but stopping an entire crew for a conflict on the other side of the floor is not always the right call.
The foreman or superintendent should make the immediate field call: continue, isolate, or stop. That call is not final design adjudication. It is risk control while the RFI moves.
Capture the conflict before the details get lost
Urgent RFIs fail when the person writing them has to reconstruct the issue from memory an hour later. Capture the conflict at the point of discovery, while the sheets, grid lines, and physical condition are in front of you.
Record the plan area, level, grid references, sheet numbers, detail or section callouts, and revision dates. State what each drawing says in plain language. For example: “A5.21 Detail 4 shows a 6-foot opening at Grid C/4. S3.12 shows a continuous shear wall at the same location. Framing is scheduled to begin at 1:00 p.m.”
That is useful. “Wall conflict at north elevation” is not.
Photos help, especially when they show the layout, rebar, embed, framing, or existing condition. But a photo does not replace drawing citations. A designer reviewing an urgent issue needs to see the source of the conflict, not just the result on the ground.
Check revisions before you send
Revision drift causes a lot of unnecessary heat. The architectural set may have a recent bulletin while the structural set in the field is older, or vice versa. Before routing the RFI, verify that the crew is looking at the latest issued sheets and that the sheets are part of the same revision package.
If the problem is simply an outdated sheet, document the finding, distribute the correct revision, and confirm the field team has it. Do not turn a document-control failure into a design RFI unless the current documents still disagree.
This is where field-first drawing comparison matters. Instead of flipping through pages on a tailgate or calling someone in the office to compare sets, tools such as TrueStruct can flag the mismatch between architectural and structural drawings and attach the cited locations. The qualified person still decides what to build. The software just removes the page-hunting when time is short.
Write the RFI so it can be answered in one pass
A good urgent RFI is short, specific, and answerable. It should identify the conflict, explain what work is affected, and ask for a decision. Do not make the engineer infer the question from a long story about the morning.
Use a direct structure in the body of the RFI:
- Identify the exact conflicting documents and locations.
- Describe the existing field condition or work status.
- State the decision needed.
- Name the schedule impact and the time when an answer is required.
- Include a proposed option only when it is based on a valid field condition and clearly marked as a request for approval.
For example: “Structural S2.04, Rev 3, calls for a 24-inch by 36-inch footing at Grid B/7. Architectural A1.10, Rev 3, locates a door opening that conflicts with the footing location. Excavation is complete and concrete is scheduled for 10:30 a.m. Please confirm whether to relocate the footing, revise the opening, or provide another approved detail before the pour.”
That request gives the architect and structural engineer a real choice. It also makes the schedule consequence visible without turning the RFI into a threat.
Avoid wording that assigns blame. “Your drawings conflict” may be true, but it does not get a faster answer. State the facts, cite the sheets, and make the decision required impossible to miss.
Route it to the person who owns the answer
The fastest path is not always the biggest distribution list. Copying every project manager, estimator, architect, engineer, owner representative, and subcontractor can create noise and delay. Someone has to recognize that they own the response.
Route the RFI through the project’s established communication path, but assign it to the party with design authority for the issue. Structural conflicts go to the structural engineer of record through the approved channel. Architectural layout, finish, or access issues typically go to the architect. Coordination issues involving MEP, structural, and architectural scopes may need the design lead or general contractor to direct the response.
The superintendent should be named as the field contact, with a phone number or immediate response method available when the work is truly time-sensitive. “Urgent” in the subject line means little if nobody knows the crew is holding a concrete truck or cannot close a wall.
Escalation should be clear before the emergency happens. If there is no response by the required time, the superintendent escalates to the project manager. The project manager escalates through the design team and owner channels as required by the contract. Keep the escalation factual: affected scope, decision deadline, and current work status.
Use a real deadline, not a vague priority flag
“ASAP” is not a deadline. It gives the receiver no information about the actual field consequence.
State the decision time in jobsite terms. “Response needed by 9:45 a.m. before reinforcing steel is placed.” “Response needed before the 2:00 p.m. delivery to avoid holding the framing crew.” “Work at Grids D through F is on hold; other areas remain active.” This helps the design team prioritize and helps project leadership understand the cost of delay.
Be honest about urgency. Marking every RFI urgent trains people to ignore the label. Reserve it for issues that affect active work, safety, inspections, critical deliveries, or irreversible installation.
Keep the crew informed without letting the answer mutate
Once the RFI is routed, the field needs one source of truth. The superintendent or foreman should tell the crew what is on hold, what can continue, and what must not be assumed. This is especially important when a bilingual crew is working under a tight sequence.
Translate the operational instruction, not just the document title. “Do not set the header at Grid 4 until approved detail is issued” needs to be understood by the people handling the material. If the formal RFI response is in English, the field direction should still be communicated clearly in the language the crew uses to work.
Do not treat a verbal call, text message, or hallway comment as the final answer unless the project’s process allows it and the direction is documented immediately. A quick phone call can speed up clarification, but the approved decision must be captured in the RFI record or formal revision. Otherwise, the job is left with a memory contest after the work is covered up.
Close the loop at the point of installation
An RFI is not complete when an answer arrives. It is complete when the answer reaches the crew, the drawing set is updated if needed, and the affected work is installed and checked against the approved direction.
Attach the response to the cited drawing conflict. Mark the area in the field set. If the answer changes dimensions, elevations, reinforcement, framing, or openings, verify it before concrete is placed or the assembly is closed. A fast answer that never makes it from the office inbox to the workface is still a field failure.
Urgent RFIs will always happen because drawings never match perfectly and jobs change under pressure. The goal is not more paperwork. The goal is a clean decision trail that keeps a crew from building a permanent mistake just because nobody answered fast enough.