Safety Cue
Task-specific guidance for handling plan sets, marked-up sheets, and office or field review conditions.
Project 04
Review one residential plan set and produce a sheet-referenced code-note summary that links project data, fire and life safety, energy, structural, MEP, and inspection notes to field responsibilities, using only the approved documents and confirmed jurisdictional sources.
These cues appear at the point of work. They identify safety, code, professional-boundary, and documentation issues before an unread note becomes a missed inspection hold point or an unauthorized field assumption.
Task-specific guidance for handling plan sets, marked-up sheets, and office or field review conditions.
A stop-work condition: the learner must not proceed, decide, or represent a note's meaning without confirming the controlling document.
Practical handling of plan revisions, superseded sheets, and clarification requests during field use.
Plan notes reference codes and amendments that vary by jurisdiction. Verify listed editions against the Chapter 1 authority register.
Identifies note content reserved for interpretation by the design professional, plans examiner, or building official.
Recording, sourcing, and revision-tracking guidance for every note entered in the register.
This project qualifies you to locate, read, and organize the code notes printed on a residential plan set into one sheet-referenced code-note summary that a field crew can actually use. The finished work product is one complete note register and code-note summary tied to a specific plan revision, covering project data, fire and life safety, structural, MEP, and energy notes, with every note linked to its controlling sheet, detail, or specification.
You will confirm the plan date and approval status, build a note register keyed to sheet and subject, identify occupancy, construction-type, and fire-separation notes, identify alarm, egress, and emergency-escape notes, identify structural design-criteria and framing notes, identify plumbing, electrical, HVAC, and energy notes, compare notes against the actual drawings for conflicts, convert unresolved items into formal clarification questions, and issue a controlled summary for field planning while the approved documents remain controlling.
This project depends directly on the authority register and adopted-code sources built in Project 01. The code-note summary produced here becomes a working reference for every later inspection-readiness project in this book, including the foundation, framing, envelope, and MEP rough-in inspections and the Chapter 20 capstone.
A plan set carries the project's actual design decisions in its notes, not only in its drawn geometry. A learner who skips the notes and reads only the drawing risks missing a fire-separation requirement, an energy assembly value, or a structural design criterion that never appears as a dimension line. This project teaches the discipline of reading every note, tracing it to its supporting detail or specification, and recording it where the field crew and later inspection-readiness projects can find it.
The site and zoning checklist in Project 05, the foundation-inspection preparation in Project 06, and every later rough-in and envelope project in this book reuse the code-note summary built here as their starting reference for project-specific requirements. The Chapter 20 capstone repeats this exact review with the final issued plan set.
This project covers:
This project does not authorize the learner to:
Any note that cannot be reconciled with the drawings, specifications, or authority register must be recorded as an open clarification question rather than resolved by assumption.
Establish these references before any note is entered in the register, and apply them consistently across every note-register entry.
| Term | Definition |
|---|---|
| Code note | A printed statement on a plan sheet that states a code, design, or administrative requirement applicable to the shown work |
| General note | A note applying broadly across the sheet or project rather than to one specific detail or location |
| Controlling sheet | The specific plan sheet, detail, or specification section that a note refers to for its full implementation requirement |
| Note register | The working document recording note number, sheet, subject, affected trade, project stage, and verification method for every note reviewed |
| Plan revision | A specific dated and numbered version of a plan sheet; only the current, approved revision controls field work |
| Clarification question | A formal question sent to the design professional or plans examiner when a note is unclear, conflicting, or missing implementation detail |
Before reading any note, record the plan set and review scope directly on the note register cover page:
Project address: ______ Plan set title: ______ Plan date: ______ Revision number: ______
Approval status: ______ Authority having jurisdiction: ______ Number of sheets in set: ______
Reviewer name: ____________ Date review started: ____________
Every plan set carries requirements in three places: the drawn geometry, the printed notes, and the referenced specifications or details. A note that says a wall is rated, an assembly meets an energy value, or a stair meets a code dimension is only as good as the detail or specification it points to. This project teaches the habit of tracing every note to its controlling reference before treating it as understood, the same habit used when reading approved documents throughout the rest of this book.
Every note that references a detail, section, schedule, or specification must be traced to that reference before the note is considered read. A note stating a requirement without a traceable controlling reference, or a note using generic language requiring local confirmation, must be recorded as an item requiring clarification rather than resolved by assumption.
Do not enter a note in the register without recording its sheet number, its subject, and the specific detail, section, or specification it points to. A note recorded without a traceable reference cannot be verified later and must be flagged for clarification.
When a code note conflicts with the drawings, with another note, or with the Chapter 1 authority register, stop and record the conflict as a formal clarification question. Do not select the least costly interpretation, and do not instruct a trade to proceed on an assumed resolution.
Before entering any note in the register, confirm against the revision log that the sheet is the current controlling revision. Remove or clearly mark any note pulled from a superseded sheet, and do not distribute a code-note summary built from a mixture of current and superseded sheets.
The design professional, plans examiner, or building official interprets ambiguous or conflicting plan notes, not the learner or this summary. Record unresolved notes as open clarification questions and route them through the responsible party rather than interpreting them independently.
CP-019 – CP-024
Plan Review / Documentation / Field-Reference Qualification
Scope: one note register and one code-note summary, both covering a single defined residential plan set at a single confirmed revision, organized into the eight review areas listed in the Component Schedule below, with every note traced to its controlling sheet, detail, or specification.
| Register Section | Quantity | Source | Required Content | Verification / Purpose |
|---|---|---|---|---|
| Project Data | 1 | Cover sheet | Code editions, occupancy, construction type, building area, height, stories | Compared against Chapter 1 authority register |
| Life Safety | 1 | Life-safety plan, electrical plan | Smoke alarm, carbon-monoxide alarm, egress, emergency escape, exit notes | Traced to code-required locations and product notes |
| Structural | 1 | Structural, foundation, framing sheets | Design criteria, foundation, anchor, hold-down, bracing, connector, nailing notes | Traced to structural details without redoing engineering |
| MEP | 1 | Plumbing, electrical, mechanical sheets | Plumbing, electrical, gas, HVAC, ventilation, combustion, equipment-clearance notes | Traced to schedules and equipment specifications |
| Energy | 1 | Energy documents, specifications | Insulation, fenestration, air sealing, ducts, equipment, controls, ventilation, testing | Traced to energy compliance forms |
| Zoning and Site | 1 | Site plan, cover sheet | Setback, height, lot coverage, parking, flood, wildfire, site notes shown on plans | Compared against Project 05 zoning checklist scope |
| Product Approvals | 1 | Specifications, details | Product-approval, listed-system, manufacturer-instruction, testing, commissioning, deferred-submittal notes | Traced to manufacturer or listing documents |
| Conflicts and Clarifications | 1 | Working log | Contradictions, generic language, missing implementation detail | Converted to formal clarification questions with recorded responses |
| Check | Standard |
|---|---|
| Plan-revision confirmation | The reviewed plan date, revision number, and approval status are recorded and match the current controlling set |
| Register completeness | Every note register section in the Component Schedule is populated with note number, sheet, subject, trade, and stage |
| Traceability | Every register entry is traced to a controlling detail, section, schedule, or specification, or flagged as unresolved |
| Code-edition cross-check | Every code edition or amendment cited on the plans is compared against the Chapter 1 authority register with any discrepancy recorded |
| Conflict handling | Every identified conflict between notes, drawings, or trades is recorded and converted into a clarification question rather than resolved by assumption |
| Clarification closure | At least one clarification question is answered and the response is recorded in the register |
| Summary usability | The finished code-note summary is organized by project stage and trade and links each item to its controlling reference |
Inspect the finished note register and code-note summary using the same checks regardless of which section is being reviewed.
Complete the Code-Note Verification Worksheet in the Inspection Checklist section below before beginning Project 05.
Probable cause: the note was copied into the register without following its detail, section, or specification callout back to the actual referenced content.
Confirmation: locate the referenced detail, section, or specification and confirm it actually contains the implementation information the note promises.
Correction: update the register entry with the confirmed reference, or flag the note as a clarification item if no supporting reference exists.
Reinspection: repeat the traceability check on the corrected entry.
Probable cause: the plan set's cover sheet or general notes reference a code edition that has since been superseded, or the plans were drafted using a different jurisdiction's default edition.
Confirmation: compare the plan's stated edition and amendment date directly against the Chapter 1 authority register entry for the same code.
Correction: record the discrepancy as a formal clarification question to the design professional or plans examiner rather than assuming either source controls.
Reinspection: repeat the code-edition cross-check after the clarification response is recorded.
Probable cause: a conflicting or generic note was interpreted in the field or office to keep the review moving, rather than being logged and routed to the design professional or plans examiner.
Confirmation: review the Conflicts and Clarifications section for entries missing a recorded question and response.
Correction: remove the assumed interpretation from the summary, submit the formal clarification question, and update the register once the response is recorded.
Reinspection: repeat the conflict check on the corrected register.
Probable cause: a revised sheet was issued after the register was built, and the summary was not rechecked against the current revision log before distribution.
Confirmation: compare the revision date recorded in the summary against the current revision log for the plan set.
Correction: rebuild or revise the affected register entries using the current sheet, and reissue the summary with the corrected revision date.
Reinspection: repeat the revision check on the reissued summary.
Probable cause: the summary retained the register's raw sheet-by-sheet order instead of being organized by project stage and trade.
Confirmation: ask a responsible trade representative to locate their applicable notes and time the search.
Correction: reorganize the summary by stage and trade grouping as required in Section J.
Reinspection: repeat the usability check with the same trade representative.
This project ends with the code-note summary issued and archived at a confirmed plan revision, not left as a working draft.
| Competency | Independent Pass Standard | Not Demonstrated | With Assistance | Independently |
|---|---|---|---|---|
| CP-019 | Locates code notes on the plan set and organizes them into a complete sheet-referenced register | |||
| CP-020 | Identifies occupancy information stated on the plans, including accessory or mixed-use conditions | |||
| CP-021 | Interprets construction-type, fire-resistance, and separation notes as printed, tracing each to its supporting detail | |||
| CP-022 | Identifies fire-safety, alarm, and egress notes and links them to their controlling sheet or detail | |||
| CP-023 | Identifies energy-code notes and traces them to their supporting energy documents | |||
| CP-024 | Produces a code-note summary organized by stage and trade, with every item traced to a controlling reference and issued at a confirmed plan revision |
Mark one column per competency. Only Demonstrated Independently awards the competency; Demonstrated with Assistance authorizes additional supervised practice but does not complete the requirement.
| Register Section | Note Count | Traced to Reference | Cross-Checked to Authority Register | Open Clarifications | Correction (if any) |
|---|---|---|---|---|---|
| Project Data | |||||
| Life Safety | |||||
| Structural | |||||
| MEP | |||||
| Energy | |||||
| Zoning and Site | |||||
| Product Approvals | |||||
| Conflicts and Clarifications |
Plan revision reviewed: ____________ Clarification contacted: ____________ Response and date: ____________
Summary reviewed with: ______ Summary issued (date): ______ Archived by: ____________
With all eight note-register sections populated and cross-referenced, review the finished register and code-note summary against the Acceptance Standards table and confirm the reviewed plan revision is recorded, every entry is traced to a controlling reference, every cited code edition is cross-checked against the Chapter 1 authority register, every conflict was routed through a formal clarification question, at least one clarification has a recorded response, and the summary is organized by stage and trade. Complete the Code-Note Verification Worksheet and correct any failed item before beginning Project 05. If an entry fails, identify whether the error occurred in traceability, cross-checking, conflict handling, clarification closure, or summary organization before correcting and re-running the affected check.
You have completed the fourth project in the building codes, permits, and inspections sequence: reading code notes on residential plans. This project required you to locate code notes on a residential plan set and organize them into a sheet-referenced register (CP-019), identify occupancy information stated on the plans (CP-020), interpret construction-type notes as printed on the approved documents (CP-021), identify fire-safety notes, including separation, alarm, and egress requirements (CP-022), identify energy-code notes shown on the plans and supporting documents (CP-023), and create a code-note summary linking every note to its controlling sheet, detail, or specification (CP-024).
You now have a verified, revision-dated code-note summary and a repeatable plan-reading method you can apply to any future residential plan set. That system carries directly into the next project: building a site, setback, and zoning compliance checklist from the parcel's official survey, zoning, and overlay resources.
Store the archived note register and code-note summary where they remain available to every later inspection-readiness project in this book. You will recheck and reuse this exact plan-reading method throughout the rest of this book.