The anchor bolts are laid out. The concrete truck is on the road. Then the architectural plan shows one opening size, the structural sheet shows another, and the detail does not clean it up. Which sheet governs installation? The answer is not whoever has the loudest opinion, or whichever PDF was opened last. It is controlled by the contract documents, the scope of the work, revision status, and the specific instruction being installed.
That sounds straightforward until you are standing at the slab with a crew waiting for an answer. Drawings never match perfectly. The field needs a defensible decision before material gets cut, concrete gets placed, or framing gets buried.
Which sheet governs installation when plans conflict?
There is no universal rule that architectural sheets always beat structural sheets, or that the detail always beats the plan. Every project has its own document hierarchy, usually in the owner-contractor agreement, general conditions, specifications, Division 01 requirements, drawing cover sheet, or supplementary conditions.
Start there. If the contract documents spell out an order of precedence, that is the rule. It may establish that specifications govern over drawings, that larger-scale details govern over smaller-scale plans, or that addenda and revisions supersede earlier issued documents. Do not invent a hierarchy because it worked on the last job.
Even where a formal hierarchy exists, it does not automatically settle every clash. Architectural drawings generally define layout, finishes, openings, clearances, and intended appearance. Structural drawings define load paths, member sizes, reinforcement, connections, bearing, and stability. Mechanical, electrical, plumbing, fire protection, and civil sheets define their own scopes. One discipline cannot casually override another where its decision affects that other discipline's work.
A structural beam callout may govern the beam size and connection. It does not necessarily give structural authority to move an architectural opening or reduce a required clearance. An architectural reflected ceiling plan may locate a fixture, but it does not authorize drilling through a structural member to make it fit.
The practical rule is blunt: install only what the current, coordinated contract documents clearly support. If they do not support one answer, stop the affected work and get direction.
Read the conflict before you read the sheet number
A sheet conflict is not always a true conflict. Many disputes start because someone compares different dates, different areas, or different levels of detail.
First, confirm you are looking at the same location. Check grid lines, column lines, room numbers, wall tags, elevation markers, detail references, and floor level. A footing at Grid D-4 is not interchangeable with one at Grid D-5 just because the symbols look similar.
Next, verify the issue date and revision cloud. A newer sheet may supersede an older sheet, but only if it was formally issued through the project process. A PDF saved in someone's downloads folder, an unapproved sketch, or a screenshot from a coordination call is not automatically a construction revision.
Then identify the instruction type. Is the mismatch a dimension, a material, a member size, an elevation, a connection, a penetration, or a missing element? The answer changes who needs to respond and how urgent the risk is.
For example, an architectural floor plan may dimension a wall at 12 feet from Grid 3. A structural foundation plan may place a pier that makes that wall location impossible. That is not simply an architecture-versus-structure contest. It is a grid and load-path conflict. The crew needs clarification before forms go in, because a field adjustment could affect bearing, rebar placement, embeds, and the next trade's layout.
Specific details often control general plans
On many sets, a larger-scale detail provides more specific installation direction than a small-scale overall plan. A 3-inch detail of a steel connection usually carries more installation value than a 1/8-inch floor plan symbol. Likewise, a wall section may clarify a header, flashing, blocking, or firestopping condition that is only broadly indicated on plan.
But “more detailed” does not mean “newer” or “fully coordinated.” A detail can still conflict with a revised plan, schedule, or structural note. Read the revision dates and reference callouts. If the detail was not updated when the plan changed, it is evidence of a coordination gap, not permission to guess.
Schedules and notes can carry controlling requirements
Do not overlook schedules, keynote legends, general notes, and specifications. A door schedule may establish a rated opening, hardware group, or frame type that changes how a rough opening must be built. A structural general note may require a particular anchor, weld, or reinforcing procedure even when the plan view does not repeat it at every location.
Specifications matter especially when drawings show intent but not the complete installation standard. They can define approved materials, tolerances, testing, fastening, sequencing, and manufacturer requirements. The field still needs an installation location and dimension, but the spec may govern the method and quality standard.
A field-first process for deciding what to do next
When a conflict is found, protect the work first. That does not always mean shutting down the whole job. It means isolating the affected area and refusing to make an irreversible call without authority.
A good field review follows a tight sequence:
- Capture both instructions with sheet number, detail reference, revision date, grid location, and the exact conflicting dimensions or notes.
- Confirm the current issued set and check for addenda, ASIs, bulletins, sketches, or approved change documents.
- Review related sheets, including sections, details, schedules, structural notes, and the relevant specification section.
- Identify the consequence of each possible installation: safety, code, load path, waterproofing, clearance, cost, schedule, or rework.
- Send an RFI that asks for a decision, not a vague request to “please clarify.”
That last point matters. A weak RFI creates another round of emails. A usable RFI names the exact conflict and gives the design team a clean decision point.
Instead of writing, “Plans do not match. Please advise,” write: “At Grid B-6, A2.1 Revision 3 dimensions the storefront rough opening at 8 feet 0 inches. S4.2 Detail 7 shows the tube steel jamb spacing at 7 feet 8 inches. Steel is scheduled for installation September 12. Please confirm required rough opening and revise affected sheets if needed.”
Now the architect, structural engineer, and superintendent can see the location, source documents, conflict, and schedule impact without making the crew repeat the problem three times.
Do not use field logic as design authority
Experienced crews solve problems all day. That experience is valuable, but there is a line between identifying the likely intent and authorizing a design change.
You may know that a structural header cannot disappear because an architectural elevation looks cleaner without it. You may know a sleeve cannot be moved after a pour without affecting reinforcing. Use that knowledge to explain the risk in the RFI and propose an option if appropriate. Do not turn it into an undocumented field redesign.
This is where schedule pressure causes expensive mistakes. “We have always done it this way” does not protect a contractor when the installed work conflicts with the final direction. Neither does a verbal answer from someone without documented authority. Get the response in the project record, then mark the affected drawings so the entire crew is working from the same answer.
Keep the answer where the crew can use it
A resolved RFI is only useful if it reaches the people laying out, forming, framing, and installing. Too many answers live in an office platform while the field keeps working from a printed set, an old PDF, or a text message.
The crew needs the citation, not a lecture. They need to see that the conflict was between A2.1 and S4.2 at Grid B-6, that RFI 047 established the required dimension, and that the answer applies before steel installation. That is accountability at the point of work.
TrueStruct is built around that field reality. It compares architectural and structural sets, flags discrepancies with sheet citations, and helps turn the mismatch into a draft RFI while a qualified person keeps final decision authority. The goal is not to replace the superintendent, architect, or engineer. It is to stop crews from burning time flipping pages while the pour clock keeps running.
When the documents disagree, the right move is rarely to pick a side and hope. Pin down the current sheets, identify the exact scope conflict, protect the affected work, and force a documented answer before the mistake becomes permanent. That is how a crew keeps the job moving without carrying someone else's coordination failure.