TrueStruct

Field Notes

What Causes Field Rework on Active Jobsites?

August 18, 2026 · Kevin Patrick · 7 min read

A crew has forms set, rebar tied, and a pour window closing. Then someone catches it: the architectural plan calls for an opening that the structural sheet does not support. That is what causes field rework in its most expensive form - work built from information that never lined up in the first place.

Rework is not just a labor problem. It is usually a decision problem that reached the field too late. The crew gets blamed for tearing out work, but the root cause often started with conflicting sheets, an uncommunicated revision, a vague handoff, or an RFI that stayed stuck in someone’s inbox.

The cost hits fast. Labor gets burned twice. Material is wasted. Inspections move. The next trade loses its access. A one-hour drawing question can turn into a three-day schedule problem when it is discovered after concrete is placed or framing is closed up.

What Causes Field Rework? Usually Bad Information at the Point of Work

Most rework starts before anyone picks up a tool. The field receives a set of drawings that looks complete until the crew compares the sheets needed for the actual task. The conflict may be small on paper: a dimension that differs by a few inches, a grid line that shifts between disciplines, a missing header, or a detail referenced from the wrong revision.

On an active jobsite, small conflicts are not small. A concrete crew needs exact locations before a pour. A framing crew needs openings, bearing points, and headers resolved before walls go up. If the answer is buried in a 300-page PDF set or split between an architect’s update and an engineer’s older sheet, the crew is forced to make a call with incomplete information.

Sometimes that call is reasonable. The foreman cannot stop every task over a minor ambiguity. But when the drawing issue affects layout, structure, embeds, penetrations, or required clearance, building first and asking later is a gamble. Rework is what happens when the jobsite loses that gamble.

Drawing Conflicts Between Architectural and Structural Sets

Architectural and structural drawings serve different purposes. They should coordinate, but they do not always match. The architect may show the intended layout, finished dimensions, door or window locations, and ceiling conditions. The structural engineer defines the elements that hold the building up. When those sheets disagree, the conflict does not disappear because the crew is under pressure.

Common field conflicts include an architectural opening with no structural header, a structural beam that cuts through an architectural layout, column locations that do not match grids, or slab thickening that is absent from the architectural background. Conflicting dimensions are especially dangerous because both numbers can look believable when a crew is laying out with tape, chalk, or a total station.

The hard part is that neither set should be treated as automatically superior. Structural requirements control structural safety, but architects may have issued a later coordination change. The right answer depends on revision dates, notes, addenda, approved changes, and the specific condition. The field needs to see the conflict clearly, cite the source sheets, and get a decision from the responsible party before work becomes permanent.

Revision Drift: The Quiet Cause of Expensive Redo

Revision drift happens when different people are working from different versions of the plan set. The office may have the latest bulletin. The superintendent may have downloaded it last week. The foreman may have printed an older sheet in the trailer. A subcontractor may be using a marked-up PDF sent by text.

Everybody thinks they have the current drawing. Nobody has the same drawing.

This is how a crew installs an old door schedule, places embeds to a superseded grid, or frames an opening that was moved two revisions ago. The problem is not that people cannot read drawings. The problem is that revision control breaks down when the job depends on manual uploads, email chains, printed sets, and page-by-page checking.

Revision clouds help, but they are not a field-control system. They only help if the person reviewing the sheet knows which related sheets changed too. A revised architectural floor plan can affect structural framing, reflected ceiling plans, MEP routing, elevations, and details. If that connection is missed, the job builds revision drift into the work.

RFIs That Start Too Late or Ask the Wrong Question

An RFI is supposed to stop assumptions from turning into installed mistakes. In practice, many RFIs lose time because they are created after the crew has already hit the conflict at the workface. Others are too vague to get a usable answer.

“Please clarify” is not a field-ready RFI. It forces the architect or engineer to hunt through the set, interpret the condition, and ask for more information. The crew is still waiting.

A useful RFI identifies the exact sheets, grid references, dimensions, revision dates, and conflicting callouts. It states what the field found and asks for a direct decision. For example, if architectural Sheet A2.1 locates a framed opening at Grid C/4 while structural Sheet S3.2 shows a shear wall at that location, the RFI should cite both conditions and request the required framing and structural direction.

Speed matters, but so does authority. A quick verbal answer from the wrong person can create another round of rework. The field needs a documented answer from the party authorized to decide. That protects the crew and gives the next trade something reliable to build from.

Handoffs Lose Context Between Office and Field

Projects do not fail because no one communicated. They fail because critical information gets communicated without context, confirmation, or a clear owner.

A project manager may tell the superintendent that a change is coming. The superintendent may mention it during a morning huddle. The foreman may understand the general intent but not have the revised detail. By the time the crew reaches that area, the message has become, “I think they moved that wall.” That is not enough to lay out work.

Language gaps can make the problem worse. On many crews, the person interpreting a technical drawing detail for Spanish-speaking workers is also managing production. A vague mark-up, shorthand note, or office-only explanation can be misunderstood even when everyone is skilled and trying to get it right. Clear citations, plain language, and terminology that works in English and Spanish reduce the chance that a drawing conflict turns into a wrong installation.

The best handoff is not a meeting. It is a confirmed field condition: here is the current sheet, here is what changed, here is the approved answer, and here is the work it affects.

Schedule Pressure Turns Uncertainty Into Rework

Schedule pressure does not create drawing errors, but it changes how crews respond to them. When a pump truck is booked, inspections are stacked, or another trade is waiting on the area, stopping work feels expensive. So the crew uses the best available interpretation and keeps moving.

Sometimes that is the right move. If the condition is low-risk, reversible, and clearly supported by the documents, waiting may cost more than proceeding. But that decision should be deliberate. The moment the issue affects structural capacity, code compliance, waterproofing, fire rating, layout control, or another trade’s work, production pressure is a poor substitute for an answer.

Good superintendents create a simple escalation rule: crews can solve ordinary means-and-methods questions, but drawing conflicts with downstream consequences get flagged before installation. That keeps foremen from carrying designer-level risk just because they are closest to the work.

The Field Often Finds the Problem First

The people laying out the slab, setting steel, and framing walls are the first people to see where drawings collide with physical reality. They are not asking for more bureaucracy. They need a faster way to compare relevant sheets, pinpoint the mismatch, and turn it into an RFI before it becomes buried work.

That is the field-first problem TrueStruct is built to address. It compares architectural and structural drawing sets, identifies conflicts such as mismatched dimensions, missing structural elements, grid issues, and revision drift, then ties each finding back to the source sheets. It can draft the RFI, but a qualified person still makes the final call. That is the right division of labor: let the tool find the discrepancy, and let accountable construction professionals decide what gets built.

Rework will never disappear completely. Existing conditions change, design teams revise, and jobsites are messy by nature. But crews should not have to discover a preventable conflict after the pour, after drywall, or after an inspector has already walked the area. Catch the mismatch while it is still a question on a screen, not a demolition ticket in the field.

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