A structural addendum review guide is not paperwork for the trailer. It is how a foreman keeps a changed beam callout, footing size, holdown schedule, or slab opening from turning into torn-out work. Addenda often arrive after layout is underway and before the whole crew has heard a word about them. That is when a small revision becomes a field problem.
The drawings never match perfectly. Architectural sheets may move a wall while the structural plan still carries the old post location. The structural engineer may revise a header, but the framing detail on another sheet points to a superseded condition. Nobody wins by pretending a clouded note on one page is enough.
Start With the Work in Front of You
Do not review an addendum as a stack of pages from page one to page last. Start with the work scheduled for the next few days. If the crew is forming footings tomorrow, the priority is civil and structural changes that affect excavation, footing dimensions, rebar, embeds, slab edges, and grid control. If framing is active, start with bearing lines, posts, beams, headers, shear walls, connections, and roof framing.
This approach is not an excuse to ignore the rest of the addendum. It is triage. A complete review still matters, but the details that can stop a pour or send a crew home need answers first.
Before comparing anything, identify the controlling issue date. Write down the original issued-for-construction date, each addendum number, and the revision date shown on the current architectural and structural sheets. A sheet can carry the latest title block date while one detail remains unchanged from an earlier issue. Date alone does not prove coordination.
Build a Clean Addendum Record
An addendum review falls apart when the crew cannot tell which sheet they are looking at. Keep the active set clear and keep replaced sheets out of the working stack. Do not leave an old S1.1 on the gang box because it is “basically the same.” Basically the same is where rework starts.
For every addendum, record the addendum number, received date, sheets added or replaced, and the work areas affected. Then mark whether each item changes field layout, material ordering, inspection requirements, sequencing, or an already-installed condition. That record can be simple, but it needs to be visible to the people doing the work.
A practical field review usually has four outputs: the current sheets, a list of detected conflicts, a short list of confirmed changes the crew must execute, and RFIs for anything that remains unclear. The point is not to create more administration. The point is to stop assumptions from becoming permanent work.
Read Revision Clouds, Then Read Beyond Them
Revision clouds tell you where the designer intended to show a change. They do not tell you every sheet, detail, elevation, schedule, or note affected by that change.
If a cloud moves Grid C or changes a wall opening, follow that location through the architectural floor plan, structural framing plan, foundation plan, building sections, wall sections, and relevant schedules. A shifted wall can change more than framing. It can affect a continuous footing, a grade beam, a slab thickening, anchor bolt placement, a lintel, or a mechanical penetration.
Treat every changed grid reference as high risk. Grid conflicts spread fast because crews use grids for layout, survey control, concrete placement, steel, and framing. If the architectural set calls a column at C/4 and the structural plan shows C/4 in a different location, stop treating it as a drafting nuisance. It is a field decision waiting to go wrong.
The Structural Addendum Review Guide: What to Compare
The highest-value review is a direct comparison between the revised sheet and every related sheet in the issued set. Page flipping can catch obvious changes, but it misses revision drift when information moved across disciplines or sheets.
Focus your comparison on conditions with expensive consequences:
- Dimensions, especially face-of-wall, centerline, edge-of-slab, and opening dimensions.
- Grid lines, building offsets, elevations, and datum references.
- Footings, piers, grade beams, slab thickenings, reinforcement, and embeds.
- Posts, beams, headers, joists, trusses, connection hardware, and bearing conditions.
- Shear walls, holdowns, collectors, straps, nailing schedules, and load-path continuity.
- New or revised penetrations, sleeves, blockouts, and conflicts with architectural openings.
Do not assume the larger structural member governs every conflict. The engineer may control the structural capacity, but the architect may control the required opening, finish elevation, accessibility clearance, or room layout. When documents conflict, the crew needs a written direction that reconciles the condition, not a guess about whose sheet matters more.
Watch for Silent Changes
The dangerous revisions are not always the big red clouds. Watch for a revised keynote, detail number, schedule entry, or general note that changes what happens in the field without changing the plan graphic much at all.
A header schedule can change from two 2x12s to an LVL package. A foundation note can add epoxy dowels at an existing-to-new connection. A section can revise a beam pocket elevation. A shear-wall detail can change fastener spacing. Each one can affect material, labor, inspection, and sequence.
Also compare callouts that point to details. If a plan note changes from “see 5/S4.2” to “see 8/S4.2,” read both details. The new reference may be a corrected condition, or it may have been carried over incorrectly. Either way, the field should not discover the answer after cutting material.
Turn Conflicts Into Usable RFIs
An RFI that says “Please clarify” is weak. It delays the answer because the design team has to recreate the problem. A usable RFI names the exact conflict, shows where it occurs, and asks for a decision that can be built.
State the sheet numbers, revision dates, grid or room location, and conflicting dimensions or notes. Describe the current field status: laid out, excavated, formed, poured, framed, or not started. Then ask the question plainly. For example: “Structural S2.1, Addendum 03, shows a 24-inch-deep grade beam at Grid B/5. Architectural A1.2, revised the same date, shifts the exterior wall 8 inches east. Confirm controlling grade-beam location and provide revised reinforcing and slab-edge detail if required.”
Attach the cited plan snippets or markups when the workflow allows it. The person answering should not need a scavenger hunt to see the issue. Just as important, do not let an RFI draft make the decision for you. Automation can identify the mismatch and organize the evidence. A qualified superintendent, engineer, or architect still adjudicates the buildable answer.
Review With the People Who Will Build It
A foreman should not receive a revised sheet after the morning huddle and be expected to translate it alone while the crew waits. Bring the affected leads into the review. The concrete lead may spot an embed issue. The framing lead may see that a new header conflicts with a truss bearing location. The layout person may recognize that a shifted grid breaks established control.
Keep the huddle tight. Show the old condition, the revised condition, the affected location, and the direction for today. If an answer is pending, say that clearly and identify the hold point. “Do not pour this strip footing past Grid 6 until RFI 14 is answered” is better than letting the crew interpret a vague warning.
For bilingual crews, the instruction needs to travel in the language used on the work face. A translated summary should preserve structural terms, dimensions, sheet references, and hold points. “Cambió” is not enough. The crew needs to know what changed, where, and whether work proceeds.
Use Technology Without Moving the Work Back to the Desk
The old method is printed sheets, highlighters, memory, and somebody trying to compare PDFs after hours. It works until it does not. The failure point is usually not effort. It is that a field crew needs an answer beside the excavation, forms, or wall line, not after a desktop review cycle.
A field-first reconciliation tool can compare architectural and structural sets, flag conflicting dimensions, missing elements, grid mismatches, and revision drift, then cite the source sheets. That changes the conversation from “I think this moved” to “These two issued sheets disagree here.” TrueStruct is built around that jobsite reality, with findings and drafted RFIs available where the work is happening, including offline conditions.
The trade-off is simple: software can surface discrepancies fast, but it cannot replace judgment about constructability, code, means and methods, or design intent. Use it to reduce page flipping and make the evidence clear. Keep the final decision with the people licensed and responsible to make it.
The best addendum review ends with the crew knowing exactly what is safe to build, what has changed, and what is on hold. That clarity protects the schedule, but more than that, it protects the people expected to make a permanent decision with a crew standing beside them.