Safety Cue
Task-specific guidance for ordinary work hazards, including site visits and record handling.
Project 01
Build one current, jurisdiction-specific reference binder containing authoritative code, zoning, permit, licensing, inspection, utility, and closeout resources for a defined residential property, verified against official sources rather than memory or informal summaries.
These cues appear at the point of work. They identify safety, code, professional-boundary, and documentation issues before they become an unverified assumption or a compliance gap.
Task-specific guidance for ordinary work hazards, including site visits and record handling.
A stop-work condition: the learner must not proceed, decide, or represent a requirement without official confirmation.
Practical handling of official contacts, counters, and records.
Local requirements vary. Verify permit, inspection, and jurisdictional rules directly rather than from memory.
Identifies work reserved for the building official, licensed trade, or design professional.
Recording, sourcing, and dating guidance for every entry placed in the binder.
This project qualifies you to identify governing authorities, locate the currently adopted codes and local amendments, and organize a verified, jurisdiction-specific reference binder before any permit decision is made. The finished work product is one complete, indexed binder covering authorities, adopted codes, zoning, licensing, permits, submittals, inspections, energy, life safety, fees, utilities, revisions, corrections, and closeout for one defined residential property.
You will define the property and its intended users, build an authority register, locate and record the adopted codes and local amendments, locate zoning and parcel resources, locate licensing and permit resources, locate fee and inspection procedures, organize the binder into labeled sections, verify one unresolved item directly with the responsible authority, and test the binder against a sample project before archiving the first controlled version.
This is the first project in the book. Every later project in this book — the permit decision in Project 02, the application packet in Project 03, every inspection-readiness project, and the Chapter 20 capstone — depends on the authority register and verified sources built here. Nothing in this book replaces the building official, plans examiner, inspector, or design professional as the final authority.
Every project in this book begins with the same question: which authority controls this requirement, and where is the current official version of it? Project 02 cannot classify a scope item as permit-required or exempt without this binder's authority register and permit-exemption sources. Project 03 cannot assemble an application packet without this binder's forms, checklists, and fee information. Every rough-in and final-inspection project depends on the inspection-request procedures recorded here.
The verification discipline in this chapter — recording source, edition, amendment date, effective date, section, and date verified for every requirement — is the same discipline used throughout the rest of the book, including the Chapter 20 capstone's authority-to-closeout compliance archive.
This project covers:
This project does not authorize the learner to:
Any resource in the binder that cannot be traced to an authoritative source must be labeled unofficial or removed before the binder is archived.
Establish these references before any resource is filed, and apply them consistently across every binder section.
| Term | Definition |
|---|---|
| Authority having jurisdiction | The agency legally empowered to adopt, interpret, or enforce a given requirement for this property |
| Adopted code edition | The specific code edition and local amendments actually in legal effect, confirmed at the official source rather than assumed from a model code |
| Official source | The agency's own published code, ordinance, form, fee schedule, or written response; not a summary, training material, or another jurisdiction's document |
| Secondary guidance | Unofficial summaries, industry references, or training materials; useful for orientation but never cited as the controlling requirement |
| Date verified | The date the learner confirmed a resource directly against its official source; the binder is only as current as this date |
| Unresolved item | A requirement that cannot yet be confirmed from an available official source and must be tracked until the authority responds |
Before locating any resource, record the property, users, and binder scope directly on the authority register:
Property address: ______ Parcel number: ______ Municipality: ______ County: ______ State: ______
Project types this binder must cover: ____________ Intended users: ____________
Date started: ____________ Builder or preparer name: ____________
Every compliance task in this book, from this chapter's authority register to the Chapter 20 capstone's authority-to-closeout archive, follows the same five-part sequence: identify the authority, locate the official source, record it with a verified date, organize it for use, and recheck it before it controls a real decision. Learning that sequence here, on one property's reference resources, means every later project starts from a method you already trust.
Every entry placed in the binder is either an official source or clearly labeled secondary guidance. Record the source, title, edition, amendment date, effective date, section, webpage or office, contact, and date verified for every governing requirement placed in the binder. An entry without a recorded date verified cannot be treated as current.
Do not carry a code edition, fee, or form forward from memory or a prior project's binder. Confirm it directly at the official source and record the date verified before filing it. Carrying an unverified entry forward allows outdated requirements to compound across future projects in this book.
This binder is an educational reference, not a permit approval, inspection report, code-compliance certification, or legal opinion. Do not represent any checklist, summary, or organized resource in this binder as authorization to build, permit, or occupy. Stop and direct the learner to the authority having jurisdiction whenever a requirement cannot be confirmed from an official source.
When contacting an agency counter or staff member, ask a specific, focused question tied to the property and requirement. Record the agency, contact name or identifier where offered, date, question, and response exactly as given. Do not argue with, mislead, or pressure agency staff, and do not represent a verbal comment as a final determination without written confirmation where the agency requires it.
Zoning variances, code interpretations, structural sizing, and formal permit determinations are made by the zoning official, building official, plans examiner, or design professional, not by this binder or its preparer. Where the binder identifies an unresolved or ambiguous requirement, label it unresolved and record the official source that must answer it rather than selecting the least costly interpretation.
CP-001 – CP-006
Authority Research / Documentation / Organization Qualification
Scope: one physical or digital binder, organized into the fifteen labeled sections listed in the Component Schedule below, covering one defined residential property, with every technical entry sourced, dated, and verified against an official authority.
| Section | Quantity | Source Type | Required Content | Verification / Purpose |
|---|---|---|---|---|
| Authorities | 1 | Official | Agency name, responsibility, address, website, phone, email, hours, portal | Confirmed jurisdiction over the defined property |
| Adopted Codes | 1 | Official | Building, residential, existing-building, plumbing, electrical, mechanical, fuel-gas, fire, energy, accessibility codes | Edition, amendment, effective date, source recorded for each |
| Local Amendments | 1 | Official | Administrative ordinances, permit rules, bulletins, interpretations, standard details | Distinguished from unadopted model-code language |
| Zoning | 1 | Official | Zoning maps, use tables, setback tables, height limits, lot coverage, overlays | Matched to the defined parcel |
| Property Mapping | 1 | Official | Parcel, addressing, property-record, flood, wildfire, seismic, snow, wind, coastal, historic, environmental maps as applicable | Matched to the defined parcel |
| Licensing | 1 | Official | Contractor-license, trade-license, registration, owner-builder, insurance, bond requirements | Current requirement text, not a summary |
| Permit Applications | 1 | Official | Building, zoning, demolition, grading, plumbing, electrical, mechanical, gas, fire, driveway, right-of-way, utility, well, septic, and specialty forms | Current published form version |
| Submittals | 1 | Official | Plan-submittal checklists, drawing standards, calculation requirements, energy forms, product-approval requirements, electronic-file rules | Current published requirement |
| Fees | 1 | Official | Fee schedules, valuation methods, deposits, reinspection fees, extension fees, payment methods | Current published rate |
| Review Procedures | 1 | Official | Plan-review turnaround, expedited-review policies, correction-response procedures, revision-submittal rules | Current published procedure |
| Inspections | 1 | Official | Inspection types, sequence, request methods, cutoff times, cancellation policies, contact requirements, result-access procedures | Current published procedure |
| Closeout | 1 | Official | Final approval, certificate of occupancy, certificate of completion, utility-release, closeout requirements | Current published requirement |
| Utilities and Special Districts | 1 | Official | Utility, well, septic, floodplain, historic-preservation, HOA-adjacent contacts where applicable | Confirmed separately from government authorities |
| Revisions and Corrections | 1 | Blank template | Revision log and correction-tracking template for use in later projects | Ready for use, not yet populated |
| Source Verification and Local Questions | 1 | Working document | Source-verification page and local-questions log | Populated with at least one contacted and answered item |
| Check | Standard |
|---|---|
| Authority register completeness | Every applicable authority listed with responsibility, contact information, and date verified |
| Code and amendment sourcing | Every adopted code and amendment entry includes edition, effective date, section, and official source |
| Official vs. secondary labeling | Every non-official resource is clearly labeled as secondary guidance, with no unofficial summary presented as a controlling requirement |
| Section completeness | All fifteen binder sections listed in the Component Schedule are present, populated, and correctly labeled |
| Verification test | The permit application, adopted code edition, inspection request procedure, and final-approval requirement for one sample project can be located in the binder within a reasonable search |
| Unresolved-item handling | At least one unresolved item is contacted, answered, and recorded with agency, contact, date, question, and response |
| Revision control | The first controlled binder version is archived with a revision date and change log |
Inspect the finished binder using the same checks regardless of which section is being reviewed.
Complete the Source Verification Worksheet in the Inspection Checklist section below before beginning Project 02.
Probable cause: the edition was copied from a model-code publisher's default page, a prior project's binder, or an informal summary instead of the agency's own adoption list.
Confirmation: recheck the agency's official adoption page or contact the building department directly and compare the stated edition and amendment date to the binder entry.
Correction: replace the entry with the confirmed edition, amendment date, and official source, and mark the superseded entry as archive-only.
Reinspection: repeat the sourcing check on the corrected entry.
Probable cause: a training reference, industry article, or informal checklist was filed next to official sources without a secondary-guidance label.
Confirmation: review each entry in the section and confirm whether it links to the agency's own publication or to a third-party summary.
Correction: label the resource as secondary guidance, relocate it away from official entries if needed, and locate the corresponding official source if one exists.
Reinspection: repeat the labeling check for the affected section.
Probable cause: a section from the Component Schedule was skipped, combined with another section, or left partially populated during assembly.
Confirmation: compare the finished binder's section list against the fifteen sections required in the Component Schedule.
Correction: create or complete the missing section using the locating steps in Sections F and G.
Reinspection: repeat the completeness check on the full binder.
Probable cause: a resource is filed in the wrong section, is missing a stable link, or was never actually collected during Sections F and G.
Confirmation: repeat the sample-project search in Section I, Step 1, and note the exact resource and section that could not be found.
Correction: relocate, replace, or newly collect the missing resource and refile it in the correct section.
Reinspection: repeat the verification-test check with the same sample project.
Probable cause: a question was logged on the local-questions log but the contact was never completed, or a verbal answer was recorded without a name, date, or agency.
Confirmation: review the local-questions log for entries missing a recorded response, contact, or date.
Correction: complete the contact through the agency's approved channel and record the full response with contact, date, and any stated limitations.
Reinspection: repeat the unresolved-item check on the completed log.
Probable cause: the binder was assembled and used without formally closing out the first controlled version.
Confirmation: check the archive record for a version number, date, and change-log summary.
Correction: assign a version number, record the archive date, and summarize what was verified as of that date.
Reinspection: repeat the revision-control check on the archived binder.
This project ends with the first controlled binder version archived and ready for reuse, not left as a working draft.
| Competency | Independent Pass Standard | Not Demonstrated | With Assistance | Independently |
|---|---|---|---|---|
| CP-001 | Identifies every authority having jurisdiction over the defined property, including private review bodies recorded separately from government authorities | |||
| CP-002 | Locates applicable residential codes and records the adopted edition, local amendments, and official source for each | |||
| CP-003 | Organizes permit resources, forms, fee schedules, and submittal requirements into correctly labeled binder sections | |||
| CP-004 | Collects inspection contacts, request procedures, and result-access procedures matching the current official publication | |||
| CP-005 | Documents every local requirement with source, edition, date verified, and contact of record, and correctly labels secondary guidance | |||
| CP-006 | Builds, tests against a sample project, corrects, and archives the binder under recorded revision control |
Mark one column per competency. Only Demonstrated Independently awards the competency; Demonstrated with Assistance authorizes additional supervised practice but does not complete the requirement.
| Section | Source Type | Edition / Effective Date | Date Verified | Contact of Record | Correction (if any) |
|---|---|---|---|---|---|
| Authorities | |||||
| Adopted Codes | |||||
| Local Amendments | |||||
| Zoning | |||||
| Property Mapping | |||||
| Licensing | |||||
| Permit Applications | |||||
| Submittals | |||||
| Fees | |||||
| Review Procedures | |||||
| Inspections | |||||
| Closeout | |||||
| Utilities and Special Districts |
Unresolved item contacted: ____________ Response and date: ____________
Sample-project test result: ______ (Pass/Fail) Binder version archived: ______ Date: ____________ Reviewer name: ____________
With all fifteen binder sections assembled and recorded, review the finished binder against the Acceptance Standards table and confirm every technical entry has a source, edition or effective date, and date verified, every secondary resource is labeled, the sample-project test locates every required resource, at least one unresolved item has a recorded agency response, and the archived version carries a revision date and change log. Complete the Source Verification Worksheet and correct any failed item before beginning Project 02. If an entry fails, identify whether the error occurred in sourcing, labeling, section placement, verification, or archiving before correcting and re-running the affected check.
You have completed the first project in the building codes, permits, and inspections sequence: building a residential code and permit reference binder. This project required you to identify governing authorities having jurisdiction over a defined residential property (CP-001), locate applicable residential codes and record the adopted edition, local amendments, and official source (CP-002), organize permit resources, forms, fee schedules, and submittal requirements by section (CP-003), collect inspection contacts, request procedures, and result-access procedures (CP-004), document local requirements with source, edition, date verified, and contact of record (CP-005), and build a code-reference binder that is tested, corrected, and archived under revision control (CP-006).
You now have a verified, source-dated reference binder and a repeatable authority-research method you can apply to any future residential property. That system carries directly into the next project: determining whether a specific residential project actually requires a permit.
Store the archived binder version where it remains available to every later project in this book. You will recheck and reuse this exact authority-research method throughout the rest of this book.