The embed is tied, the crew is staged, and the pump is coming. Then someone notices the base plate dimension on the structural plan does not land where the architectural grid says it should. This concrete embed coordination example shows what a field team should do next: stop guessing, identify the exact conflict, and get a decision documented before concrete makes the mistake permanent.
The Field Scenario: An Embed That Does Not Land on Grid
Picture a ground-up retail shell with structural steel columns bearing on concrete piers and a continuous grade beam. The concrete crew is setting a four-bolt embed plate at Grid B/4. The structural foundation plan calls out the plate centerline 8 inches east of Grid 4. The latest architectural floor plan shows the storefront mullion centerline, the finished wall layout, and the grid relationship putting that same column centerline 2 inches east of Grid 4.
That is not a small drafting annoyance. It is a 6-inch conflict at a steel column. If the crew follows the structural sheet without asking, the column can land out of line with the storefront, wall framing, or roof steel. If they follow the architectural plan without confirming, they may move a load-bearing support from the engineer's intended location.
Neither sheet gets to win because someone has a hunch. The foreman needs a documented answer.
A Concrete Embed Coordination Example, Step by Step
The work starts by comparing the sheets that control different parts of the same condition. For this example, the superintendent has these drawings in hand:
- S1.1 Foundation Plan, revision 3, issued May 14
- S5.2 Embed Plate Schedule, revision 2, issued May 2
- A1.1 Floor Plan, revision 4, issued May 21
- A6.3 Storefront Details, revision 4, issued May 21
The first problem is revision drift. The structural embed schedule is older than the structural foundation plan, and both structural documents are older than the architectural set. That does not prove the architect moved a column or that the engineer missed the update. It does prove the crew cannot safely treat the pages as one coordinated instruction.
The foreman marks the physical location using the survey control already established for the pour. On S1.1, the callout at B/4 reads: "EP-12, CL 8 inches E. of Grid 4." On A1.1, a dimension chain from the same grid places the storefront column line at 2 inches E. of Grid 4. A6.3 then details the storefront jamb alignment to that column line.
Now the conflict is specific. It is not, "drawings don't match." It is: EP-12 is located 6 inches farther east on the structural foundation plan than the architectural column and storefront alignment at Grid B/4.
That distinction matters. A vague field question gets a vague answer. A cited discrepancy gives the design team something they can review without spending half a day figuring out what the crew is talking about.
Verify the embed before calling it a drawing conflict
Not every mismatch is a design error. Before writing an RFI, the crew needs to rule out field-side causes. Check that the grid designation is the same on every sheet, that the print scale is not being used as a dimension, and that the plate tag EP-12 has not been superseded in a revised schedule.
Then check orientation. On foundation work, east and west can get turned around when a detail is viewed from the opposite side, a reflected plan is involved, or the crew is working off a rotated field print. Confirm the controlling benchmark and stringline. Confirm the plate's bolt pattern and plate orientation against the column base detail. A plate can be on the right centerline and still be wrong if the bolt group is rotated 90 degrees.
In this case, the survey layout confirms the grid. The tag is correct. The structural plan dimension is clearly 8 inches east. The architectural dimension is clearly 2 inches east. The conflict is real.
Build an RFI the Design Team Can Answer
A useful RFI is not a complaint and not a request for someone else to coordinate the project from scratch. It should state the condition, cite the sheets and revisions, explain the field impact, and ask for a decision.
For this condition, the drafted RFI could read:
Subject: EP-12 location conflict at Grid B/4
Conflict: S1.1 Rev. 3 locates EP-12 centerline 8 inches east of Grid 4. A1.1 Rev. 4 locates the storefront/column centerline 2 inches east of Grid 4. A6.3 Rev. 4 aligns the storefront jamb to the architectural column line. Current locations differ by 6 inches.
Field impact: Concrete pier and grade beam pour is scheduled for June 3. Setting EP-12 per S1.1 may misalign the steel column and storefront framing. Setting EP-12 per A1.1 may alter the engineered column support location.
Question: Confirm the required EP-12 centerline dimension from Grid 4 and provide any required revision to the foundation plan, embed schedule, steel column location, or storefront detail.
That is enough. The architect, structural engineer, and steel detailer can see the conflict immediately. The crew has not prescribed an engineering fix. They have protected the pour, the schedule, and the record.
A tool such as TrueStruct can speed up the comparison by flagging the conflicting dimensions, preserving the source-sheet citations, and drafting the first RFI language from the finding. The qualified project team still makes the final call. That is how it should work. Software can catch the mismatch fast; it should not pretend to be the engineer of record.
What Happens If the Crew Pours Anyway
The 6-inch difference might look manageable from the edge of an excavation. It is not manageable after the concrete cures.
If the embed lands wrong, the steel erector may need a field fix. That can mean oversized holes, a welded extension plate, a shifted column, a revised base plate, or a new engineered repair. Each option carries cost, inspection exposure, and schedule impact. If the column line drives storefront framing, the problem can travel through glazing, drywall returns, roofing transitions, and finish dimensions.
There is also a responsibility problem. Once the pour is placed, the discussion shifts from "Which location is correct?" to "Who authorized the deviation?" A marked-up plan, a text message, or a verbal instruction from someone not authorized to issue design direction will not protect the builder when the issue reaches a pay application, a backcharge, or a claim.
The right answer may still be to pour. It depends on the response. If the engineer confirms the structural location controls and the architect revises the storefront condition, the crew can proceed. If the architect confirms a moved column line and the engineer issues a revised embed location, the pour can proceed after layout is updated. The point is not to stop work for every difference. The point is to stop permanent work when the difference affects a load path, opening, trade interface, or code-critical dimension.
Make Embed Coordination Part of the Pour Plan
Embed coordination fails when it is treated as a last-minute task for the person holding the tape measure. The best time to find a mismatch is before the crew starts welding templates, not when the first truck is backing in.
During the pre-pour review, compare the current architectural and structural issue dates. Review every embedded plate, anchor rod group, holdown, sleeve, blockout, and dowel that interfaces with another trade. Focus on gridline dimensions, offsets from face of wall, top-of-concrete elevations, and tag references to schedules. Any condition that depends on steel, storefront, framing, equipment, or MEP rough-in deserves a direct cross-check.
The field team also needs one place to capture the answer. When a revised instruction comes back, attach it to the pour package and make sure the foreman, layout lead, concrete crew, and inspector are working from the same decision. For bilingual crews, the operational direction should be clear in English and Spanish, not buried in an office-only thread that never reaches the slab.
A clean pour is not just concrete placed on time. It is concrete placed with the right embedded work, at the right coordinates, under a decision someone can trace. Find the conflict while it is still lines on a sheet. Once it is cast in place, the job gets expensive fast.