A crew has forms set, rebar tied, and a pump truck booked. Then someone notices the architectural plan shows one opening width while the structural sheet calls for another. That is when knowing how to resolve design conflicts stops being an office exercise. It becomes the difference between a controlled delay and expensive rework.
The drawings never match perfectly. Different disciplines issue sheets on different dates. A structural revision moves a beam, but the architectural reflected plan still shows the old condition. A gridline shifts. A detail references a wall type that no longer exists. The field does not need a vague promise that someone will look into it. It needs a defensible answer before concrete, steel, framing, or finish work makes the wrong condition permanent.
Start by treating the conflict as a field hold point
Do not solve a drawing conflict by picking the sheet that looks most familiar or following the last verbal instruction somebody remembers. That is how assumptions become change orders, callbacks, and arguments about who saw what.
When a conflict affects layout, safety, structural capacity, inspections, material ordering, or work that cannot be easily reversed, stop work only in the affected area. Keep the crew moving where the plans are clear. A hold point should be specific: do not pour the east footing at Grid C-4, do not frame the second-floor opening, or do not install the header at Door 214.
This is not about slowing the job down. It is about containing the delay. A ten-minute pause around one footing is cheaper than tearing out concrete because a dimension on S2.1 disagreed with A1.2.
How to resolve design conflicts without guessing
The fastest reliable process is simple: identify the exact discrepancy, confirm the governing information, document the evidence, and send a question that can be answered without another round of confusion.
Put both conditions side by side
Start with the actual source sheets, not a cropped screenshot passed through a text thread. Capture the sheet number, detail or plan reference, revision date, grid location, and the conflicting callout on each drawing.
For example, do not write, “Beam location is unclear.” Write: “At Grid B-6 on Level 2, architectural plan A2.03 locates the opening 4 feet 0 inches from Grid B. Structural framing plan S3.12 locates the supporting beam 3 feet 4 inches from Grid B. Please confirm required beam and opening location before framing.”
That level of detail matters because the designer should not have to hunt through a 200-sheet set to understand the field condition. It also protects the crew. Everyone can see exactly what was found and where.
Check revision drift before debating intent
A surprising number of conflicts are not true design disagreements. They are revision-control failures. One sheet may be current while another is not. Before escalating, compare revision clouds, issue dates, bulletin references, and addenda across the architectural and structural sets.
A newer date alone does not automatically make a drawing govern. The sheet may have been reissued for an unrelated note, while an older structural detail remains the latest approved direction for that element. Look for a revised reference that directly touches the affected condition.
Also check whether the issue is already answered elsewhere in the set. A plan may conflict with a section, but a keyed detail may clarify the intended bearing elevation, connection, or wall buildout. The goal is not to play designer. It is to make sure the team is not sending an RFI for an answer already issued in the documents.
Separate conflicts from constructability questions
A conflict is a direct contradiction: two dimensions for the same opening, a column shown in two locations, a missing header where the structural plan requires one, or an architectural ceiling that occupies the same space as ductwork.
A constructability question is different. The drawings may agree, but the shown condition cannot be built as drawn without a sequence change, inaccessible connection, unsafe access, or interference discovered in the existing field condition. Both deserve attention, but they should not be written the same way.
Calling everything a “conflict” muddies accountability. State whether the documents contradict one another or whether the field condition prevents execution of the documented design. The response path, schedule impact, and responsible party may differ.
Build an RFI that produces a decision
A weak RFI creates another delay because it asks the architect or engineer to diagnose the problem from scratch. A useful RFI gives them the conflict, the location, the evidence, and the decision needed.
Use a plain structure: identify the location, cite each conflicting sheet and detail, describe the work affected, and ask a direct question. Add a proposed path only when the field team has a practical option worth considering. Do not present a workaround as an approved solution.
For a slab conflict, that might read: “Structural S1.01, Detail 5, shows a 24-inch thickened edge at Grid D between Lines 8 and 9. Architectural A1.01 shows a 36-inch door opening at the same location with no thickened edge indicated. Forms are scheduled for placement tomorrow. Confirm required slab edge and opening configuration.”
That is far stronger than “Please clarify slab detail.” It ties the question to a location, preserves the design team’s authority, and gives the superintendent a clear record of why work was held.
If Spanish-speaking crew members are involved, the field instruction also needs to be understood in Spanish, not loosely translated after the fact. The technical terms, dimensions, and hold point must carry the same meaning for the person laying out the work as they do for the person answering the RFI.
Keep the decision tied to the work area
An RFI response is only useful when it reaches the people doing the work before the condition changes. Too many answers live in an email chain, a meeting note, or a desktop folder while the crew is working from a printed set in a lift or on the slab.
Once a response arrives, mark the affected location and communicate the approved direction in the field. Confirm what changed: the beam elevation, opening rough size, anchor layout, wall type, or pour limit. Then update the current drawing set so the crew does not return to the same conflict tomorrow.
This is where field-first drawing reconciliation earns its keep. Tools such as TrueStruct compare architectural and structural sets, flag discrepancies with source citations, and draft the RFI from the detected condition. The tool can find the mismatch faster than manual page-flipping. A qualified superintendent, engineer, or architect still makes the final call. That human adjudication is not a weakness. It is the control that keeps field speed from becoming field guesswork.
Avoid the habits that turn a mismatch into rework
The most damaging response is silent interpretation. A foreman may have enough experience to make a likely call, but “likely” is not a design direction when a beam, footing, fire-rated assembly, or code-required clearance is involved.
Another bad habit is sending an RFI without stopping the affected work. If the crew keeps building while waiting for an answer, the RFI becomes paperwork after the decision has already been made in lumber, concrete, or steel.
Do not bury the issue in a daily report either. Daily reports record what happened. They do not obtain a design decision. Use the report to document the impact and hold point, but send the specific question through the project’s RFI path.
Finally, do not assume the office has the same set in front of them. Cite the sheets. Include the revision information. Show the two conditions. Field teams should not have to pay for document-control mistakes with overtime and demolition.
Make conflict resolution part of the daily field rhythm
The best time to find a design conflict is before the crew is standing at the work face. Review upcoming work by area during look-ahead planning: foundations before forms arrive, framing before material is cut, penetrations before a pour, and ceiling coordination before rough-in closes.
Focus on the handoffs where disciplines collide. Architectural dimensions against structural grids. Door and window openings against headers. Mechanical penetrations through beams. Finish elevations against slab steps. Revision dates across sheets that control the same location.
When a discrepancy appears, make it visible early and make the question answerable. The job does not need more software theater, bigger meetings, or another person flipping pages at a desk. It needs the crew to see the conflict, cite it, hold the affected work, and get a real decision while there is still time to build it right.
A clean answer before the pour is never just an answered RFI. It is a crew that gets to keep moving, a schedule that holds, and work that does not have to be built twice.