A crew has layout snapped, forms staged, and concrete scheduled. Then the structural plan calls for a footing at one dimension while the architectural plan shows a wall line somewhere else. That is when the question of what belongs in an RFI stops being paperwork and becomes a field decision that can hold up a pour, a framing crew, or both.
A useful RFI gives the design team enough verified information to make a decision without making the field team hunt through an email chain, guess which sheet is current, or translate a vague problem into an actual condition. It should be fast to read, hard to misunderstand, and tied to the exact documents in conflict.
What Belongs in an RFI From the Field
The basic purpose is simple: document a conflict, state what needs to be decided, and preserve the answer for the people doing the work. But basic does not mean bare. An RFI that says, "Please clarify" creates a second round of questions. That costs time when a crew is standing by.
A field-ready RFI contains the project and location information, the affected documents, the observed conflict, the direct question, and the practical impact if the issue is not resolved. It also identifies the person submitting it and the date, so nobody is left guessing whether the condition was raised before or after the work moved forward.
The strongest RFIs answer five things immediately:
- Where is the issue in the building, including level, grid lines, room, elevation, or nearby reference point?
- Which sheets, details, notes, and revisions create the conflict?
- What does each source actually say or show?
- What decision does the field team need from the architect or engineer?
- What work, cost, safety concern, or schedule activity is affected while the answer is pending?
That is the difference between a record of frustration and a document someone can act on.
Start With the Exact Field Location
"At the north wall" is usually not enough. On a large floor plate, it can still leave a designer looking at the wrong bay. Identify the location the way a superintendent or foreman would direct a crew: Level 2, grid intersection C/5, east side of Stair 3, wall type W4, or footing F-12 at the south property line.
Use a photo, plan markup, sketch, or screenshot when the condition benefits from one. A visual does not replace the written question, but it cuts down on interpretation. If the issue is a beam pocket, call out the beam mark, the supporting wall, and the grid location. If it is a slab penetration, include the sleeve location, diameter, and the nearby column or control joint.
Physical conditions matter too. The drawing may be unclear because existing steel is in the way, a surveyed elevation differs from the plan, or installed work reveals a coordination miss. State what was found in the field and when it was observed. Do not turn that into a theory about who caused it. Stick to verifiable facts.
Reference the Right Drawing Sources
An RFI needs more than a sheet number. Include the drawing discipline, sheet title, detail number, and revision date or issue date. When architectural and structural sets conflict, identify both sides of the conflict.
For example, do not write: "Dimension discrepancy on plans." Write: "Architectural Sheet A2.11, Revision 3, shows the face of CMU Wall W4 at 12 feet 8 inches from Grid 5. Structural Sheet S2.03, Revision 2, locates the associated strip footing centerline at 13 feet 2 inches from Grid 5. Please confirm the governing wall and footing location before excavation."
That language gives the reviewer a clean path to the source. It also creates accountability later. If the response changes the work, the record shows exactly which documents drove the question.
Revision drift deserves special attention. A conflict may not be a design error at all. The field may have an older structural sheet while the architect issued a newer reflected ceiling plan, or vice versa. List the revision identifiers rather than assuming everyone has the same set. Before submitting, confirm that the documents in hand are the current documents distributed to the job. If they are not, the first action may be a drawing update instead of an RFI.
Describe the Conflict, Not the Fix You Prefer
The body of an RFI should state the issue in plain construction language. Quote the relevant dimension, note, schedule entry, or detail callout. Explain what cannot be reconciled.
Avoid loaded language such as "wrong," "missed," or "your plans do not work." The point is not to win an argument. It is to get a clear direction before the crew installs something that will later be torn out.
It is fine to state a proposed field solution when it helps the designer evaluate the choice. A concrete superintendent might propose shifting a blockout 2 inches to maintain cover and avoid rebar interference. A framing foreman might suggest extending a header because the architectural opening exceeds the structural detail. Label it as a proposed option, not an approved instruction.
That distinction matters. The engineer or architect owns the design decision. The foreman owns raising the issue before it turns into rework.
Ask One Clear, Answerable Question
Every RFI needs a decision request. Questions such as "Please advise" are weak because they do not define what advice is needed. Ask for the specific direction required to release the work.
Good questions sound like this: "Confirm whether the footing is to follow the architectural wall location or the structural footing centerline." Or: "Provide the required header size and connection detail for Opening 12, which is not shown on Sheet S4.02." Or: "Confirm whether the revised duct opening may be located within the indicated beam web, and provide required reinforcement if permitted."
Keep related questions together only when one answer depends on the other. If an RFI contains six unrelated issues across several trades, it becomes difficult to route, answer, and track. Separate RFIs make the response history cleaner. The trade-off is administrative volume, but a few focused RFIs are usually cheaper than one sprawling thread that nobody fully answers.
State the Real Impact Without Inflating It
The recipient needs to know whether the issue affects a future task or a crew currently waiting. State the impact accurately: excavation at this location is on hold, the slab pour is scheduled for Thursday, rough framing can continue in other bays, or the affected area has been temporarily bypassed.
Do not claim a total project delay if the crew can work around the condition. At the same time, do not hide a real deadline to avoid sounding difficult. If forms must be stripped, steel must be fabricated, or an inspection is booked, say so. A specific date and activity are more useful than the word "urgent."
The RFI should also identify whether work proceeded under an existing direction, a field condition, or a temporary measure. That protects the crew from being blamed for decisions made under pressure with incomplete information.
Make the Record Usable After the Answer Arrives
An answered RFI is only useful if the answer reaches the people laying out, pouring, framing, or installing the work. Make the final response easy to connect back to the exact location and sheet conflict. Update field sets, mark superseded sheets, and make sure the crew knows what changed before the next shift begins.
This is where office-centered workflows often break down. A detailed answer can sit in a desktop platform while the person at the slab is still looking at the conflicting sheets. TrueStruct is built around that field moment: it compares architectural and structural drawings, identifies the discrepancy with source citations, and drafts the RFI from the detected conflict. A qualified person still checks the issue and makes the call. The tool removes the page-flipping and gives the team a cleaner starting point.
For English- and Spanish-speaking crews, clarity also means using terms the recipient will understand. Keep technical references exact, avoid casual shorthand that can be misread, and ensure the final direction is communicated in the language used by the people performing the work. A correct answer that never reaches the crew is not a resolved issue.
The Standard Is Simple: Could Someone Build From the Answer?
Before sending, read the RFI as if you are the engineer receiving it with no knowledge of the conversation at the job trailer. Can you find the location? Can you open the cited sheets and see the conflict? Can you answer the question without guessing what the crew is asking? Can the crew use the response to move work forward?
If the answer is yes, send it. If not, take another minute at the point of discovery. A precise RFI is not bureaucracy. It is how a field team turns conflicting drawings into a documented decision before concrete, steel, lumber, labor, and schedule get buried under a bad assumption.