Document-Control Cue
Identity, issue, revision, and status verification for the current structural document.
Chapter 7
Interpret one residential structural framing package and produce a framing-scope checklist identifying load paths, member tags, layouts, bearing, openings, connectors, bracing, and inspection points without performing unauthorized engineering.
These cues appear at the point of use. They identify document-control, scale, cross-reference, code, and clarification issues before they become misread information in the field.
Identity, issue, revision, and status verification for the current structural document.
A misread of this information can cause unsafe, non-compliant, or costly field work.
Guidance for using the structural set safely and correctly on site.
Verify adopted jurisdiction, design criteria, and permit status before relying on a code citation.
Never scale a reproduced, resized, or displayed structural drawing without verification.
Follow a member tag to its schedule or detail and back to confirm coordination.
Stop and record a clarification item instead of resizing, relocating, or substituting a structural member.
This chapter qualifies you to receive a residential structural framing package and convert its members, bearing, connectors, and notes into a framing-scope checklist without redesigning, resizing, or relocating any structural component. The finished work product is one framing checklist organized by layout, material verification, bearing, openings, blocking, connectors, bracing, penetrations, inspection, and concealment, built from the current approved structural documents received for one project.
You will confirm structural sheet identity and design criteria, compare structural grids and dimensions with the architectural set, locate and tag beams, girders, headers, posts, and bearing walls, trace bearing from roof through foundation, identify openings and required framing around them, match connector tags to schedules and details, identify delegated-design items, and compare framing with architectural, plumbing, electrical, and HVAC information without resolving any conflict through an unauthorized field decision.
This chapter depends directly on Chapter 3 (foundation), Chapter 4 (floor plan), Chapter 5 (elevations), and Chapter 6 (sections), and it supplies the load-path and bearing information Chapter 8 needs before opening schedules can be finalized against structural rough framing.
Structural framing plans convert the geometry established in the floor plan, elevations, and sections into an actual load path from roof to footing. Chapter 3 established the foundation this load path bears on. Chapter 6 traced the assembly layers the framing carries. This chapter reads the framing itself: the members, their bearing, their connectors, and the openings cut through them. Chapter 8 depends on this chapter's header and opening information before door and window rough openings can be released, and Chapter 17 depends on this chapter's framing checklist when cross-trade penetrations through joists, beams, and shear walls are compared against plumbing, electrical, and HVAC routes.
The document-control habits from Chapter 1, the site and foundation controls from Chapters 2 and 3, and the assembly-tracing discipline from Chapter 6 all continue in this chapter without exception.
This chapter covers:
This chapter does not authorize the learner to:
Any missing member tag, unmatched schedule, unclear bearing condition, or connector ambiguity found while building the checklist must be recorded as an RFI-style question rather than resolved by the learner.
Establish these definitions before beginning the framing checklist, and apply them consistently across every structural sheet in the package.
| Term | Definition |
|---|---|
| Bearing | The point or line where a structural member transfers its load to the member, wall, or foundation below it |
| Load path | The continuous route a load follows from its point of application down through structural members to the foundation and soil |
| Member tag | The label on a framing plan identifying a specific beam, header, post, joist, or truss and pointing to its schedule or detail |
| Delegated design | A structural component, such as a truss or engineered-lumber member, designed by a separate licensed engineer under a performance criteria stated in the documents |
| Connector | A manufactured or fabricated hardware item, such as a hold-down, strap, or post base, that transfers load between two structural members |
| Shear wall / braced wall | A wall identified on the structural documents as resisting lateral (wind or seismic) force in addition to any gravity load |
| Blocking | Short framing members installed between larger members to maintain spacing, transfer load, or provide backing, as documented |
Before building the member and connector registers, record the following directly on the document-control log:
Structural sheet set issue / revision: ______________________ Engineer of record: ______________________
Design criteria referenced (loads, wind, seismic): ______________________
Coordinated architectural set revision: ______________________ Date received: ____________ Reviewer name: ____________
Every framing plan is only useful once it is traced back to a load path that terminates at the foundation. Learning to trace that path before tagging individual members prevents the common error of treating a framing plan as a set of isolated symbols rather than a coordinated structural system.
An architectural elevation or roof plan shows the finished roof geometry the design intends to achieve. A structural roof-framing plan shows the actual members, bearing points, and connections required to build that geometry. When the two appear to disagree on slope, bearing, or geometry, record the conflict as a coordination item rather than assuming either document controls without confirmation.
Truss-web layout, reactions, connector capacities, and beam sizes are engineering decisions. Do not infer them from architectural roof lines, ceiling heights, or apparent geometry. Use only the structural framing plan, truss layout, schedules, and connector details, and record any missing information as a clarification item.
Structural general notes state the design loads, wind, seismic, and code basis the engineer used. Confirm these criteria correspond to the approved project basis and permit documents before relying on any structural note, and do not use a code citation to fill a missing design detail without clarification.
Record any missing member tag, unmatched schedule entry, incomplete detail, or inconsistent grid as a clarification item during this chapter. Do not resize, relocate, notch, drill, reinforce, or substitute a structural member to resolve what you find.
BP-037 – BP-042
Document-Control / Structural Interpretation Qualification
Deliverable set: one member register covering every tagged beam, girder, header, post, column, bearing wall, and shear wall in the received structural package; one load-path map tracing bearing from roof through foundation; one connector register covering every tagged hold-down, strap, anchor bolt, and post base; one framing-scope checklist organized by layout, material verification, bearing, openings, blocking, connectors, bracing, penetrations, inspection, and concealment; and one RFI-style question list for missing sizes, conflicts, unclear bearing, connector ambiguity, or trade penetrations.
| Component | Quantity | Source | Required Fields | Preparation / Purpose |
|---|---|---|---|---|
| Structural document identity record | 1 | Structural general notes, design criteria, engineer information | Sheet set issue, engineer of record, design criteria, coordinated architectural revision | Establishes the design basis every other component is built against |
| Member register | 1 | Every tagged structural member | Tag, type, location, material/size as documented, schedule reference, status | Confirms every member is matched to its governing schedule or detail |
| Load-path map | 1 | Bearing walls, beams, posts, foundations, footings | Bearing point, member above, member below, foundation reference | Traces gravity load continuously from roof to footing |
| Connector register | 1 | Every tagged connector | Tag, location, connected members, schedule reference, manufacturer reference | Confirms every connector is matched to its governing schedule or manufacturer data |
| Framing-scope checklist | 1 | All prior components plus architectural, plumbing, electrical, and HVAC coordination | Category, item, reference, verification status, conflict flag | Converts document information into a build-readiness checklist |
| RFI-style question list | 1 | Discrepancies found while building the above | Item, description, affected sheet, requested action, required-by date | Records unresolved items for the document-control process |
| Check | Standard |
|---|---|
| Member register completeness | Every member tag appearing on a structural plan is entered in the register and matched to a schedule, note, or detail, or logged as unmatched |
| Load-path continuity | Every bearing point traced in the load-path map connects to a member above, a member or foundation below, and does not terminate without a documented support |
| Connector matching | Every connector tag is matched to its schedule, detail, or manufacturer reference, or logged as unmatched |
| Architectural coordination | Structural grids, dimensions, and openings are compared against the architectural set and every mismatch is logged |
| No unauthorized design | No member has been resized, relocated, notched, drilled, reinforced, or substituted to resolve a conflict found during the chapter |
| RFI completeness | Every missing size, unmatched tag, unclear bearing condition, or connector ambiguity is recorded as a neutral RFI-style question |
Inspect the finished checklist using the same checks regardless of which member type or bearing condition is involved.
Complete the Framing Checklist Worksheet in the Inspection Checklist section below before beginning Chapter 8.
Probable cause: the schedule was not fully reviewed, the tag belongs to a schedule on a different sheet, or the schedule entry was omitted from the issued set.
Confirmation: check every structural schedule in the package, including sheets not adjacent to the framing plan, before concluding the tag is unmatched.
Correction: log the unmatched tag on the RFI-style question list with its exact sheet and grid location; do not assign a size or material from a similar member elsewhere in the set.
Reinspection: repeat the matching check on the member register once a response is received.
Probable cause: a bearing point was traced to a wall or member not shown as continuing to the foundation, or a level change was misread.
Confirmation: compare the terminating point against the foundation plan from Chapter 3 and the section information from Chapter 6.
Correction: log the discontinuous load path as a conflict; do not assume an unstated support exists.
Reinspection: repeat the continuity check on the load-path map once a response is received.
Probable cause: the connector schedule was issued separately and not included in the received package, or the tag references a manufacturer catalog not provided.
Confirmation: check the document-control register from Chapter 1 to confirm whether the connector schedule or manufacturer catalog was received.
Correction: log the missing schedule or catalog as a document-request item; do not select a substitute connector based on apparent similarity.
Reinspection: repeat the matching check on the connector register once the missing document is received.
Probable cause: the architectural and structural sets were developed on different coordination cycles, or a later architectural revision was not reflected in the structural set.
Confirmation: compare the revision dates of the affected architectural and structural sheets against the document-control register.
Correction: log the conflict with its exact location and both source references; do not relocate the opening or modify the structural member to resolve it.
Reinspection: repeat the coordination check once an approved response is incorporated into both sets.
Probable cause: the architectural roof line represents design intent that was later revised structurally, or a truss layout was value-engineered after the elevations were issued.
Confirmation: compare the current revision of the elevation sheet against the current revision of the structural roof-framing plan.
Correction: log the geometry conflict; do not average, split the difference, or select the version that appears more buildable.
Reinspection: repeat the coordination check once an approved response reconciles both sheets.
This chapter ends with a controlled, coordinated framing-scope checklist ready for use, not a set of isolated member notes.
| Competency | Independent Pass Standard | Not Demonstrated | With Assistance | Independently |
|---|---|---|---|---|
| BP-037 | Correctly identifies every beam and girder on the structural plans and matches each to its schedule or detail reference | |||
| BP-038 | Correctly reads joist layouts, including framing direction, spacing, and documented span limits | |||
| BP-039 | Correctly locates headers and traces every framed opening to its architectural and structural information | |||
| BP-040 | Correctly interprets roof-framing notes, including bearing points and uplift connections, without inferring truss design from architectural lines | |||
| BP-041 | Correctly identifies structural connectors and matches each to its schedule or manufacturer reference | |||
| BP-042 | Produces a complete framing-scope checklist organized by layout, bearing, openings, connectors, bracing, and inspection points |
Mark one column per competency. Only Demonstrated Independently awards the competency; Demonstrated with Assistance authorizes additional supervised practice but does not complete the requirement.
| Deliverable | Status | Items Logged | Verified By | Date | Notes |
|---|---|---|---|---|---|
| Structural document identity record | |||||
| Member register | |||||
| Load-path map | |||||
| Connector register | |||||
| Framing-scope checklist | |||||
| RFI-style question list |
Total members tagged: ____________ Total connectors tagged: ____________ Discrepancies logged: ____________
Framing-scope checklist declared complete: ______ (Pass/Fail) Date: ____________ Reviewer name: ____________
With all six deliverable components complete, review the finished framing package against the Acceptance Standards table and confirm every tagged member and connector is registered and matched to a schedule or reference, the load path is traced continuously from roof to foundation with no unsupported termination, structural grids and openings have been compared against the architectural set with every mismatch logged, no structural member has been resized, relocated, notched, drilled, reinforced, or substituted anywhere in the checklist, and every missing size, unmatched tag, unclear bearing condition, or connector ambiguity has been recorded as a neutral RFI-style question. Complete the Framing Checklist Worksheet and resolve any failed item, through the project's document-control process, before beginning Chapter 8.
You have completed the seventh chapter in the blueprint-reading sequence: reading structural framing plans. This chapter required you to identify beams and girders and match each to its schedule (BP-037), read joist layouts including framing direction, spacing, and span limits (BP-038), locate headers and trace framed openings back to architectural and structural information (BP-039), interpret roof-framing notes including bearing points and uplift connections (BP-040), identify structural connectors and match each to its schedule or manufacturer reference (BP-041), and create a complete framing-scope checklist (BP-042).
You now have a verified member register, load-path map, connector register, and framing-scope checklist for one residential project. That checklist carries directly into the next chapter: coordinating door, window, and specialty-opening schedules with the structural rough-opening information you have just recorded.
Retain your completed framing-scope checklist. You will reuse this exact load-path and bearing information in Chapter 8, Chapter 17, and the Chapter 20 capstone.