The pump is booked. The rebar inspection is cleared. Crews are tying the last steel and checking embeds before daylight runs out. Then someone notices that the structural foundation plan calls for a 30-inch-wide grade beam while the architectural wall layout shows a centered wall that only works with a 24-inch beam. That is a concrete pour coordination example every superintendent remembers because the mistake gets expensive the moment concrete leaves the chute.
A pour is not the time to discover that the architectural and structural sets are telling different stories. Yet it happens constantly. Revision dates drift. A foundation detail changes without the matching architectural layout changing with it. A gridline moves. An embed schedule is updated on one sheet and not another. The field crew is left to make a call with a truck waiting.
The right response is not more page-flipping in the trailer. It is a fast, documented check that shows exactly what conflicts, where it conflicts, and who needs to answer before the pour proceeds.
Concrete Pour Coordination Example: A Grade Beam Conflict
Picture a one-story commercial addition with a concrete masonry unit wall running along Grid C. The crew has forms in place for a continuous grade beam and a thickened slab edge. The structural sheet S2.1 shows a 30-inch-wide grade beam from Grid 4 to Grid 8. The beam detail also calls for four #5 longitudinal bars and closed stirrups at 12 inches on center.
On architectural sheet A1.1, the exterior wall is dimensioned from the gridline with a 6-inch CMU backup wall, exterior insulation, air space, and brick veneer. The wall assembly is shown centered over a 24-inch foundation condition. That may sound close enough from the tailgate. It is not.
If the crew pours the 30-inch beam centered on the structural gridline, the brick ledge and wall face can shift from the architectural control dimensions. If they pull the beam in to preserve the wall alignment shown on A1.1, they may reduce required bearing, change reinforcing cover, or create an unapproved eccentric load condition. Neither choice belongs to the foreman alone.
The conflict is not just “the plans do not match.” A usable field finding identifies the exact sheets, revision dates, grid limits, dimensions, and detail references. It should show that S2.1, Revision 3, calls for a 30-inch grade beam at Grid C between Grids 4 and 8, while A1.1, Revision 2, indicates a wall and veneer geometry based on a 24-inch condition. Now the project team has something specific to resolve.
What the crew should verify before stopping the pour
First, confirm that both sheets are current. A mismatch can be a genuine design conflict, or it can be revision drift caused by one trade working from an old printed set. Check the drawing index, issue date, revision cloud, and any addenda that changed foundation geometry or wall types.
Next, verify the physical layout. Pull dimensions from established control lines, not just form edges. Confirm the gridline location, wall face, slab edge, column centerlines, and any offsets shown in sections. A form can be built accurately from the wrong information.
Then check the related documents. The conflict may continue into the structural sections, foundation details, architectural wall sections, civil utility plans, and embed or anchor schedules. The grade beam width might be correct structurally while the architectural wall section has a revised brick ledge detail that never made it into the field set.
Finally, document what is actually built or ready to build. Include photos of the forms and layout stringlines, marked-up dimensions, and the affected grid area. The person answering the RFI needs to see whether this is a drawing question or a concrete truck question.
Draft the RFI Around the Field Decision
Weak RFIs waste time. “Please clarify foundation width at Grid C” gives the design team room to respond with another vague direction or a request for more information. The question needs to state the conflict and the decision the crew cannot safely make.
A field-ready RFI could read like this:
> Structural S2.1, Rev. 3, calls for a 30-inch-wide continuous grade beam at Grid C between Grids 4 and 8. Architectural A1.1, Rev. 2, dimensions the exterior CMU/brick veneer wall assembly based on a 24-inch foundation condition. Forms are installed for the structural 30-inch width. Please confirm required grade beam width, wall location relative to Grid C, brick ledge geometry, and reinforcing requirements before concrete placement.
That language does three jobs. It cites the source sheets. It tells the architect and engineer what condition exists in the field. And it asks for a buildable direction before the irreversible work begins.
Do not bury the schedule impact, either. If the truck is scheduled for 9:00 a.m., say so. That is not pressure for pressure's sake. It tells the design team what is at risk: standby charges, crew downtime, inspection expiration, lost pump time, and a possible cold joint if part of the placement has already started.
The answer may be simple. The engineer may confirm the 30-inch beam and direct the architect to adjust the veneer detail. Or the structural engineer may issue a revised foundation detail. What matters is that the decision is recorded and tied to the drawings, instead of living in a phone call no one can reconstruct later.
The Conflicts That Hide Until Pour Day
Grade beam widths are one common problem, but concrete pours collect every drawing gap upstream. Slabs, footings, piers, curbs, housekeeping pads, and embeds all sit at the intersection of multiple disciplines.
Watch for these recurring conflicts during the pre-pour review:
- Footing sizes that differ between the foundation plan and structural schedule.
- Column, pier, or wall locations that do not land on the same gridlines across sets.
- Slab depressions, thickened edges, or control joints missing from one discipline's drawing.
- Anchor bolts, embeds, sleeve locations, or dowels that conflict with reinforcing or formwork.
- Elevations that use different benchmarks, especially where civil grades meet building slabs.
- Revision changes to storefronts, masonry openings, or equipment pads that affect the concrete footprint.
Not every difference is an error. A structural plan may intentionally use centerline dimensions while an architectural plan controls finish face. The issue is whether the drawings provide enough information to reconcile the two without guessing. If the answer is no, the project needs direction before placement.
Put Coordination at the Right Point in the Workflow
The office can review plans for weeks and still miss the conflict that matters when forms are on the ground. Field conditions expose the real question: Can this be built as drawn, at this location, with the materials and tolerances we have?
That is why the coordination check belongs before steel, before forms are locked, and again before the truck rolls. The first pass catches broad conflicts while changes are cheap. The second pass catches last-minute revisions, layout changes, and details that only become obvious once the crew sees the whole assembly in place.
For a smaller builder, this does not require a full-time VDC department or another enterprise subscription. It requires a repeatable habit. Compare current architectural and structural sheets by grid area. Check dimensions, elevations, wall types, reinforcing, embeds, and revisions. Escalate conflicts with citations, not opinions.
TrueStruct is built for that moment at the slab. It compares architectural and structural drawing sets, flags conflicts with source references, and can turn a finding into a draft RFI from a phone, even where jobsite connectivity is unreliable. The foreman still makes the field call on whether the issue is real and whether work should pause. Software should speed up the evidence, not pretend to replace judgment.
A Pre-Pour Check Is Not Bureaucracy
Some crews hear “coordination” and picture another meeting that keeps them from building. That is fair. Plenty of coordination meetings produce nothing but action items nobody owns.
A good pre-pour check is different. It is a short operational review tied to irreversible work. It protects the crew from being told later that they should have caught a conflict buried across two sheets with different revision dates. It protects the superintendent from explaining why a wall is off layout after masonry is underway. It protects the builder from paying twice for work that should have been decided once.
Before the next foundation or slab pour, choose one control line and trace it across every relevant sheet. Follow it from gridline to form, from form to reinforcing, and from reinforcing to the wall, column, or equipment that lands above it. If the drawings disagree, make the conflict visible while there is still time to fix it with a citation and an answer, not a demolition hammer.