Confirm the review issue, trace a member through its plan, schedule, section, connection, and receiving support, then record any disagreement with both source references. Separate document consistency from the engineering verification of loads, stability, capacity, and connections.
Assemble a reviewable structural package
Start with structural general notes, foundation and framing plans, schedules, sections, details, and the current architectural background. Include the referenced geotechnical report, calculation index, equipment loads, and opening requests where they affect your scope. List absent documents before drawing conclusions from the set.
Agree which systems, levels, and design milestones are being reviewed. A partially issued package may intentionally include sheets with different dates. Use the transmittal or document owner’s instruction to establish the governing issue. The drawing register template provides a place to record that decision.
The RAIC structural drawing checklist describes an internal quality-assurance review of information shown on drawings and recognizes consultant responsibilities. It is useful professional context, not a US permit standard. Phoenix’s linked structural checklist is marked July 2013; its code references must not be assumed to govern a current project.
Twelve structural document checks
Use one worksheet row per material condition. For a repeated member type, identify the locations sampled and any exceptions. The CSV adds blank fields for project issue, location, observed evidence, applicable criteria, owner, decision, revised sources, and closure.
| Review area | Sources to compare | Question to resolve |
|---|---|---|
| Design basis | General notes, project criteria, calculation index | Do the stated loads, material assumptions, and referenced design basis describe the same building and issue? |
| Support trace | Framing plans above and below, transfer details | Can each sampled member end be followed to an identified receiving support without an unexplained offset? |
| Member identity | Plan marks, beam/column schedules, sections | Does the same mark resolve to one intended member description and location? |
| Foundation references | Foundation plan, footing schedule, geotechnical report | Are bearing elevations and report references explicit, with changed assumptions referred to the engineer? |
| Lateral connections | Lateral-system plans, diaphragm notes, connection details | Are the documented collectors, connections, and receiving elements traceable through the affected levels? |
| Levels and steps | Slab plans, sections, architectural finish build-ups | Are datums and structural versus finished levels clear at steps, pits, and edges? |
| Detail applicability | Detail callout, local geometry, general details | Does the cited detail describe the actual member, support, orientation, and edge condition? |
| Equipment loads | Roof/framing plan, equipment data, support request | Is the equipment location and stated load basis reconciled with the structural support information? |
| Openings | Opening plan, services request, framing/reinforcement details | Can the proposed penetration be located and traced to an engineer-reviewed structural condition? |
| Delegated elements | General notes, supplier scope, interface criteria | Are the responsible designer, required interface inputs, and outstanding documents identified? |
| Existing construction | Survey records, demolition notes, alteration details | Which existing conditions are verified, which are assumed, and who resolves unverified support information? |
| Revision closure | Response, revised plans/schedules, dependent details | Do all affected representations reflect the accepted decision and identify what still needs engineering review? |
Record “needs clarification” when a reference is missing. Reserve “resolved” for a decision supported by reviewed documents. If a row does not apply, record why; a blank field cannot distinguish an omitted check from a completed one.
Trace a member into its receiving support
Pick a beam at an edge, step, transfer, or other change in condition. Find its mark on the framing plan and open the matching schedule entry. Follow the section and end-connection callouts. Then open the receiving wall, column, beam, or foundation information. Record offsets and level annotations exactly as stated.
The purpose is to establish whether the documents describe a coherent connection. A drawn line between two members does not establish bearing, connection capacity, or a valid load path. Refer missing design information and technical adequacy questions to the responsible engineer. Keep any architectural or services conflict tied to the same grid and level so the team can locate it.
Read the description of a load before comparing numbers. Equipment shipping weight, operating weight, and reactions at individual supports are different inputs. Ask which basis the engineer used and which equipment issue it came from; do not replace it with a convenient value from another schedule.
Worked example: a beam mark changes at a step
Hypothetical example. A framing plan labels an edge beam B-17. The schedule lists B-17, but the section at a slab step labels the same location B-19 and refers to a different end detail. All three sheets belong to the confirmed review issue. The discrepancy is the inconsistent member and connection reference; it does not establish that either design is unsafe.
At the slab step on grid C, the framing plan identifies B-17 while the referenced section identifies B-19. Please confirm the intended member and end condition, and identify the plan, schedule, and connection detail that should govern this location.
Assign the question to the structural engineer. If the response changes the member depth or support condition, include the architect and affected services designer in the follow-up. Backcheck the plan mark, schedule row, section, and detail together. A corrected label alone does not close an unresolved connection question.
Keep engineering decisions visible
Classify each comment by the decision it needs: a drafting correction, missing design input, interface decision, or engineering check. That distinction helps the engineer see which questions require analysis. Record the response reference and any affected calculation or delegated-design package without claiming to validate calculations through this worksheet.
After a revision, review dependent locations as well as the original comment. If a standard detail changes, search for other callouts to it. Retain any unverified existing-condition assumptions and their verification owner. Use the MEP coordination checklist for the wider equipment and opening interfaces.
Review supplied structural PDFs with Groundbook
Groundbook compares supplied drawings, schedules, specifications, reports, and uploaded reference documents to return potential findings with source links. A structural reviewer can use those links to investigate inconsistent member references or missing interfaces, then record the professional decision. It does not certify structural calculations or authorize a structural alteration.
Explore same-discipline consistency review or start a review of your supplied package.