The footing is laid out. The rebar crew is waiting. Then someone notices the architectural plan shows a wall line that does not land on the structural grid. There is no BIM model to interrogate, no coordinator in a trailer with time to spare, and no room for a guess. Drawing coordination without BIM is not a theoretical problem. It is a field decision with concrete, labor, and schedule attached to it.
For a lot of small and mid-sized builders, PDF plan sets are still the working truth. Architectural, structural, MEP, civil, and revisions arrive as separate sheets, often from separate teams, on different dates. That does not make the job uncoordinated by default. It means the coordination process needs to be disciplined enough to catch conflicts before the crew builds them into the work.
Why drawing coordination without BIM breaks down
The failure is usually not that nobody looked at the drawings. The failure is that the comparison happens too late, on the wrong sheet, or from a set that is no longer current.
A foreman may have the architectural A2.1 open on a phone while the superintendent is looking at an older structural S1.2 in the trailer. One detail calls for a header. The other leaves the opening unsupported. A dimension chain works on the floor plan but does not match the foundation layout. By the time the discrepancy reaches the engineer, forms are set or framing is underway.
Page-flipping also hides the source of the problem. Someone says, “The plans don’t match,” but cannot point to the exact sheet, detail, grid line, revision date, and conflicting callout. That creates a weak RFI. It also gives every stakeholder a different version of what the issue is.
BIM can help when it is current, complete, accessible, and maintained by people who understand the work being built. Those conditions are not guaranteed. Many field teams receive PDFs only. Others work on projects where the model is behind the issued sheets, excludes key structural detail, or is locked behind office workflows. Waiting for a perfect model is not a coordination plan.
Start with issued documents, not assumptions
The first job is document control. Before comparing anything, confirm that the architectural and structural sheets are from the latest issued package. Check the cover sheet, issue date, revision clouds, and sheet-level revision blocks. A newer architectural sheet paired with an older structural sheet can create a conflict that exists only because the team is comparing the wrong documents.
This sounds basic because it is basic. It is also where expensive mistakes begin. A revision to a door opening may affect a lintel, a header, a footing, a shear wall, or a transfer condition. If the revision changed only one discipline’s sheets, the field needs an answer before work continues.
Keep the active set available where the work happens. Not just on a laptop in the office. The lead carpenter at the wall layout, the concrete foreman at the pour, and the superintendent walking the site need the same current information. Offline access matters when the signal drops, which it will on plenty of jobsites.
Compare the points where trades collide
Do not try to compare every line on every sheet with equal effort. Start with the locations where an architectural decision becomes a structural consequence. That is where drawing conflicts turn into rework.
Grids, dimensions, and control lines
Check that architectural grids, structural grids, column lines, and dimension strings agree. A grid mismatch can shift more than one element. It can move a pier, create a wall offset, or leave a beam bearing where no support was intended.
Compare overall building dimensions first, then work inward to bay dimensions, offsets, and opening locations. If the outside footprint agrees but an interior line does not, isolate which sheet governs and ask the design team to confirm. Do not “make it work” with a field adjustment unless it has been approved.
Openings, headers, and load paths
Doors, windows, cased openings, and large pass-throughs deserve a direct comparison between architectural elevations, floor plans, framing plans, and structural details. The architectural drawing may show the opening size and finish intent. The structural set needs to show how loads get around it.
A missing header callout is not a minor drafting issue. It can stop framing, force a redesign, or leave the crew installing material based on habit instead of engineering. The same goes for posts that land on beams but have no clear path to a footing below.
Foundations, slabs, and embeds
Before a pour, compare foundation plans, structural notes, architectural dimensions, sections, and any embed or anchor-bolt schedules. Look for wall lines that miss thickened slabs, columns that do not center on piers, and hold-downs that do not have room around reinforcing steel.
This is the moment to be stubborn. Once concrete is placed, a drawing discrepancy becomes demolition, engineering review, patch work, and a schedule conversation nobody wants.
Revision drift
Revision drift is what happens when one sheet changes and the related sheets do not clearly follow. A revised architectural partition can affect framing, electrical rough-in, fire blocking, and ceiling layout. The change may be marked on one page but never called out on the structural plan the crew uses for layout.
When you find a revision, check adjacent sheets and details. Follow the impact through the work instead of treating the cloud as a self-contained change.
Build an RFI that can be answered
An RFI should not make the architect or engineer hunt for the problem. It should state the conflict, identify both sources, locate the condition, and ask a decision-ready question.
A usable field RFI might read: “Architectural sheet A2.1, Revision 3, shows a 6-foot opening on Grid B between Lines 4 and 5. Structural sheet S3.2, Revision 1, shows no header detail or supporting posts at this opening. Please provide required header and bearing detail before framing.”
That is better than “Need clarification at opening.” It gives the design team enough information to respond without a long email chain. It also creates a record of what the crew saw, when they saw it, and why work paused.
Attach marked-up excerpts or direct citations to the relevant sheets. The goal is accountability, not paperwork. If the response changes the work, make sure the answer returns to the people holding the tools, not just the project management folder.
Use automation for detection, not judgment
Software can compare architectural and structural sets faster than a tired person flipping pages at the end of a long day. It can flag conflicting dimensions, missing structural elements, grid conflicts, and revision differences. That is useful because the field does not need more documents. It needs the conflict located.
But a flagged discrepancy is not an automatic field directive. Drawings contain intentional variations, design choices, and conditions that require professional judgment. The qualified superintendent, engineer, architect, or responsible lead still decides what gets built.
That distinction matters. A useful tool reduces the time spent finding mismatches, preserves the source citations, and helps draft the RFI. It does not pretend to replace the person accountable for the decision. TrueStruct is built around that field-first workflow: compare the sets, identify the issue, cite the sheets, and move a clear question to the people who can answer it.
Put coordination into the daily work plan
The best time to coordinate is before the crew reaches the condition, not when the condition is already blocking production. Add drawing review to look-ahead planning. If framing starts next week, compare the relevant architectural and structural sheets before material arrives. If a slab pour is Friday, review foundation geometry, embeds, elevations, and wall lines early enough to get an answer.
This does not need to become a meeting that eats half the morning. It can be a short, specific review tied to the next operation. What are we building? Which sheets govern it? What changed? Where do architectural intent and structural support meet? Is there an unanswered RFI that affects release of work?
For mixed English- and Spanish-speaking crews, the finding and RFI need to be understandable in the language of the people doing the work. Translation that ignores construction terminology creates its own coordination problem. “Header,” “hold-down,” “grid line,” and “rough opening” need to mean the right thing in the field, not merely look correct in a generic translation.
The drawings may never match perfectly. That is not an excuse to accept field fixes, buried assumptions, or last-minute calls from the slab. A crew that can identify the exact conflict, document it, and get a real answer before building has leverage. That is what keeps a discrepancy from becoming rework.