TrueStruct

Field Notes

Jobsite Drawing Reconciliation Review That Works

September 13, 2026 · Kevin Patrick · 7 min read

A footing is staked. The concrete crew is ready. Then someone notices the architectural dimension does not match the structural plan. Now the crew is standing by, the pour window is shrinking, and somebody is flipping through PDFs trying to figure out which sheet controls. A jobsite drawing reconciliation review is how you catch that conflict before it becomes fresh concrete, cut lumber, or a field fix nobody wants to own.

The drawings never match perfectly. That is not a complaint. It is a jobsite fact. Architectural, structural, civil, MEP, and revised sheets move at different speeds. A minor change in one discipline can create a major problem for the crew building the work. The risk is not just a bad drawing. The risk is a bad drawing reaching the point of installation without anyone seeing the conflict.

What a Jobsite Drawing Reconciliation Review Should Do

A real review is not a document-control exercise completed in an office and filed away. It is a field check that asks one hard question: can the crew build this work correctly from the drawings in hand?

That means comparing related sheets, revisions, callouts, details, dimensions, notes, and grid references. It means checking the structural set against the architectural set before layout, checking sections against plans before framing, and checking the latest revision against what was issued last week. The goal is not to generate more paperwork. The goal is to stop rework before it starts.

A useful reconciliation review should identify the exact location of the mismatch and preserve the evidence. “Plans conflict” is not enough when the superintendent needs an answer before a pour. The finding needs the relevant sheet numbers, detail references, grid lines, dimensions, and revision information. If the question goes to the architect or engineer, that source trail becomes the backbone of a usable RFI.

The person in the field still makes the final call. Software can compare sheets quickly and surface a conflict. It cannot replace the qualified superintendent, engineer, architect, or foreman who understands the sequence of work, the site conditions, and the consequences of a decision. Automation should shorten the hunt, not pretend to adjudicate construction.

Where Drawing Conflicts Hit the Field Hardest

Not every discrepancy has the same impact. A typo in a finish note may be annoying. A missing structural element or a conflicting footing dimension can shut down a crew or create expensive corrective work.

Layout is one of the first pressure points. Grid references may shift between an architectural floor plan and a structural foundation plan. Column locations can be offset. A dimension string may be revised on one sheet but not carried through to the other. Once control lines are snapped and forms are built, even a small mismatch has labor attached to it.

Concrete work has little patience for unresolved plans. Before a slab or footing pour, the field team needs confidence in elevations, reinforcing requirements, embeds, blockouts, piers, thickened slabs, and openings. If a structural section calls for an element that is absent from the plan view, that is not a cleanup item for later. It needs an answer while there is still time to act.

Framing creates another common collision point. The architectural plan may show an opening, while the structural sheets do not show the required header or point load path. A wall may be tagged differently across sets. A beam may conflict with ceiling height, duct routing, or an architectural feature. The field team should not have to discover that after studs are up and material has been cut.

Revision drift is the quiet version of the same problem. One team has a current architectural sheet. Another is working from an older structural PDF saved to a phone. The title blocks may look close enough to pass a quick glance, but the revision dates do not match. That is how a job gets built from multiple versions of the truth.

Review Before the Work Is Committed

The best time for a jobsite drawing reconciliation review depends on the scope, but it should always happen before the work becomes hard to change. For foundation work, review before layout and again before the pour. For framing, review before walls are stood and before major headers, beams, or trusses are installed. For openings, embeds, sleeves, and penetrations, reconcile the drawings before crews commit labor and materials.

This is not an argument for holding a two-hour meeting every time someone picks up a tape measure. The review should match the risk. A small interior partition change may need a fast confirmation. A transfer beam, stepped footing, or revised opening on a load-bearing wall deserves a deeper check and a documented answer.

A disciplined field workflow is simple. Start with the current drawing sets. Compare sheets that govern the same physical work. Flag the discrepancies that affect layout, sequencing, safety, inspection, cost, or schedule. Then determine whether the issue is clear enough to resolve from the contract documents or whether it requires an RFI.

The key is to keep the issue attached to the work location. A crew does not need a vague message saying, “Please review structural conflict.” They need, “At Grid C/4, S2.1 Detail 6 shows a 24-inch grade beam, while A1.2 dimensions the wall line 8 inches off that beam centerline.” That gives the office a question they can answer and gives the crew a record of why work paused or changed.

Why Page-Flipping Fails Under Jobsite Pressure

Manual comparison works until it does not. A good foreman can catch a lot, but no one reliably compares hundreds of callouts, dimensions, details, and revision clouds while managing deliveries, inspections, weather, manpower, and active work.

Office-centered platforms often assume the review happens at a desktop before the crew mobilizes. That helps preconstruction, but it misses the moment when field risk is highest: when a worker is at the layout point with a phone, a set of plans, and a decision that cannot wait until the next coordination meeting.

The jobsite also has real connectivity problems. Basements, remote sites, new developments, and active concrete or steel work do not always offer reliable signal. A drawing review tool that only works when the internet behaves is not field-first. Crews need access where the work is happening, including offline when necessary.

Language matters, too. An RFI that is clear to an English-speaking project manager but vague to the crew carrying out the work has not solved the communication problem. Clear construction terminology and native English and Spanish output help keep the issue, the question, and the instruction aligned across the team.

Turn the Finding Into an RFI, Not Another Delay

A discrepancy only becomes valuable when it moves toward resolution. The RFI should state the conflict, identify the exact source sheets, explain the field condition or pending work, and ask for a specific direction. It should not force the architect or engineer to repeat the detective work the field team already completed.

For example, a weak RFI says: “Please clarify footing location.” A field-ready RFI says that the architectural plan dimensions the exterior wall at one location, the structural plan locates the footing differently, the conflict occurs at identified grids, and forms are scheduled for a stated date. The question then asks which location governs and whether related structural elements need revision.

That level of clarity protects everybody. The foreman has a documented reason not to guess. The superintendent can track schedule exposure. The design team sees the exact conflict without a vague back-and-forth. The owner gets fewer surprise change events caused by preventable drawing drift.

TrueStruct is built around this jobsite reality. It compares architectural and structural drawing sets, flags conflicts such as missing elements, dimension mismatches, grid conflicts, and revision drift, then attaches citations to the finding. From there, the team can draft an RFI without starting from a blank screen. The field gets faster answers, while the qualified people remain responsible for the final decision.

Make Accountability Easier Than Guessing

A good review process does not slow production. It removes the false speed of building first and arguing later. There will always be gray areas in construction, and not every mismatch requires an RFI. Sometimes the governing note is clear. Sometimes the latest addendum answers the question. Sometimes the superintendent can verify the intent with the design team in minutes.

But when the documents genuinely conflict, guessing is not productivity. It is an undocumented design decision made by the person with the least time and often the least authority to make it.

Put reconciliation at the point where work is about to happen. Give the crew the sheets, citations, and language needed to raise the right question. The best field teams do not wait for rework to reveal a conflict. They catch it while it is still just ink on a drawing.

Catch the drawing conflict before the crew builds it

TrueStruct reconciles architectural and structural sets, flags every discrepancy with a citation, and drafts the RFI. On your phone, in the field.

Start free in the app

← Back to the blog