Residential Construction and Building Trades Library
|
Book 25 — Building Codes, Permits, and Inspections: Residential Compliance and Best Practices

Project 01

Build a Residential Code and Permit Reference Binder

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.

Field Cue System

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.

△

Safety Cue

Task-specific guidance for ordinary work hazards, including site visits and record handling.

✋

Critical Safety Cue

A stop-work condition: the learner must not proceed, decide, or represent a requirement without official confirmation.

⛑

Field Safety Cue

Practical handling of official contacts, counters, and records.

▤

Code Alert

Local requirements vary. Verify permit, inspection, and jurisdictional rules directly rather than from memory.

▧

Professional Boundary Cue

Identifies work reserved for the building official, licensed trade, or design professional.

▱

Documentation Cue

Recording, sourcing, and dating guidance for every entry placed in the binder.

Job Overview

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.

Skills You Will Demonstrate

  • CP-001 — Identify governing authorities having jurisdiction over a defined residential property.
  • CP-002 — Locate applicable residential codes and record the adopted edition, local amendments, and official source.
  • CP-003 — Organize permit resources, forms, fee schedules, and submittal requirements by section.
  • CP-004 — Collect inspection contacts, request procedures, and result-access procedures.
  • CP-005 — Document local requirements with source, edition, date verified, and contact of record.
  • CP-006 — Build a code-reference binder that is tested, corrected, and archived under revision control.

Where This Skill Fits

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.

Scope and Intended Use

This project covers:

  • defining the property, parcel, and intended binder users
  • identifying the primary building department and every separate authority that may apply
  • locating the currently adopted codes, local amendments, and administrative rules from official sources
  • locating zoning, parcel, licensing, permit, submittal, fee, and inspection resources
  • organizing the binder into labeled, indexed sections with source dating and secondary-guidance labeling
  • verifying one unresolved item directly with the responsible authority
  • testing the binder against a sample project and archiving the first controlled version

This project does not authorize the learner to:

  • determine whether a specific project requires a permit; that decision is Project 02's scope
  • interpret, apply, or waive a code requirement, or treat this binder as a legal opinion, permit approval, or inspection result
  • rely on memory, an internet summary, an old permit packet, another jurisdiction's rule, or a model code edition that has not been confirmed as locally adopted
  • represent any secondary summary, training material, or industry reference in this binder as an official source

Any resource in the binder that cannot be traced to an authoritative source must be labeled unofficial or removed before the binder is archived.

Reference Conventions

Establish these references before any resource is filed, and apply them consistently across every binder section.

TermDefinition
Authority having jurisdictionThe agency legally empowered to adopt, interpret, or enforce a given requirement for this property
Adopted code editionThe specific code edition and local amendments actually in legal effect, confirmed at the official source rather than assumed from a model code
Official sourceThe agency's own published code, ordinance, form, fee schedule, or written response; not a summary, training material, or another jurisdiction's document
Secondary guidanceUnofficial summaries, industry references, or training materials; useful for orientation but never cited as the controlling requirement
Date verifiedThe date the learner confirmed a resource directly against its official source; the binder is only as current as this date
Unresolved itemA requirement that cannot yet be confirmed from an available official source and must be tracked until the authority responds

Property and Binder Record

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: ____________

Prerequisites

Common Field Fundamentals

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.

AuthoritiesBuilding, zoning, fire, utility, and other applicable agencies
Adopted CodesEdition, local amendments, effective date, official source
Zoning & SiteZoning maps, setback tables, overlays, parcel resources
Licensing & PermitsContractor licensing, permit applications, owner-builder rules
SubmittalsDrawing standards, calculation requirements, energy forms
FeesCurrent fee schedules, valuation methods, deposits, reinspection fees
InspectionsTypes, sequence, request methods, cutoff times, result access
CloseoutCertificate of occupancy, completion, utility-release requirements

Official Sources, Secondary Guidance, and Verification Dates

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.

CP-001 – CP-006

Authority Research / Documentation / Organization Qualification

Residential Code and Permit Reference Binder

Difficulty: Beginner

Estimated Time: 4–6 hours, plus wait time for one agency response

Estimated Cost: $0–$40

Finished Work: One indexed, source-verified, tested, and archived reference binder

A. Finished-Project Specification

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.

B. Binder Section Schedule (Component Schedule)

SectionQuantitySource TypeRequired ContentVerification / Purpose
Authorities1OfficialAgency name, responsibility, address, website, phone, email, hours, portalConfirmed jurisdiction over the defined property
Adopted Codes1OfficialBuilding, residential, existing-building, plumbing, electrical, mechanical, fuel-gas, fire, energy, accessibility codesEdition, amendment, effective date, source recorded for each
Local Amendments1OfficialAdministrative ordinances, permit rules, bulletins, interpretations, standard detailsDistinguished from unadopted model-code language
Zoning1OfficialZoning maps, use tables, setback tables, height limits, lot coverage, overlaysMatched to the defined parcel
Property Mapping1OfficialParcel, addressing, property-record, flood, wildfire, seismic, snow, wind, coastal, historic, environmental maps as applicableMatched to the defined parcel
Licensing1OfficialContractor-license, trade-license, registration, owner-builder, insurance, bond requirementsCurrent requirement text, not a summary
Permit Applications1OfficialBuilding, zoning, demolition, grading, plumbing, electrical, mechanical, gas, fire, driveway, right-of-way, utility, well, septic, and specialty formsCurrent published form version
Submittals1OfficialPlan-submittal checklists, drawing standards, calculation requirements, energy forms, product-approval requirements, electronic-file rulesCurrent published requirement
Fees1OfficialFee schedules, valuation methods, deposits, reinspection fees, extension fees, payment methodsCurrent published rate
Review Procedures1OfficialPlan-review turnaround, expedited-review policies, correction-response procedures, revision-submittal rulesCurrent published procedure
Inspections1OfficialInspection types, sequence, request methods, cutoff times, cancellation policies, contact requirements, result-access proceduresCurrent published procedure
Closeout1OfficialFinal approval, certificate of occupancy, certificate of completion, utility-release, closeout requirementsCurrent published requirement
Utilities and Special Districts1OfficialUtility, well, septic, floodplain, historic-preservation, HOA-adjacent contacts where applicableConfirmed separately from government authorities
Revisions and Corrections1Blank templateRevision log and correction-tracking template for use in later projectsReady for use, not yet populated
Source Verification and Local Questions1Working documentSource-verification page and local-questions logPopulated with at least one contacted and answered item

C. Resource Takeoff

  • Property data: one defined residential property address, parcel number, municipality, county, and state, confirmed against an official property record.
  • Binder hardware: one three-ring binder, fifteen tab dividers, and section-divider labels, or an equivalent digital folder structure with fifteen labeled folders.
  • Source documents: saved copies or stable official links, with access dates, for every technical entry; printed or scanned copies where the agency does not provide a stable digital link.
  • Verification allowance: at least one completed contact with a responsible authority for an item that could not be confirmed from published sources alone, with the response recorded on the source-verification page.

D. Acceptance Standards

CheckStandard
Authority register completenessEvery applicable authority listed with responsibility, contact information, and date verified
Code and amendment sourcingEvery adopted code and amendment entry includes edition, effective date, section, and official source
Official vs. secondary labelingEvery non-official resource is clearly labeled as secondary guidance, with no unofficial summary presented as a controlling requirement
Section completenessAll fifteen binder sections listed in the Component Schedule are present, populated, and correctly labeled
Verification testThe 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 handlingAt least one unresolved item is contacted, answered, and recorded with agency, contact, date, question, and response
Revision controlThe first controlled binder version is archived with a revision date and change log

E. Preparation — Define Property, Authorities, and Users

  1. Define the property address, parcel, municipality, county, state, project types, and intended users of the binder. Record this information on the Property and Binder Record above before locating any resource.
  2. Identify the primary building department and confirm its jurisdiction over the property. Confirm the department's name and jurisdiction directly from an official source rather than assumption.
  3. Identify separate planning, zoning, fire, public-works, health, environmental, floodplain, utility, well, septic, historic, and transportation authorities that may apply. Record each authority that has any bearing on the defined property, even if its role will not be used immediately.
  4. Identify homeowners-association or other private review bodies separately from government authorities. Keep private review requirements in a clearly labeled section distinct from government permits.
  5. Create an authority register with agency name, responsibility, address, website, telephone, email, counter hours, submission portal, and date verified. Complete one register row for every authority identified in Steps 2 through 4.

F. Locate Adopted Codes, Amendments, and Zoning Resources

  1. Locate the authoritative list of adopted building, residential, existing-building, plumbing, electrical, mechanical, fuel-gas, fire, energy, accessibility, and other applicable codes. Use the official agency's published adoption list, not a model-code publisher's default edition.
  2. Record the adopted edition, local amendments, effective date, and official source for each code. File each entry in the Adopted Codes section with its supporting source link or saved document.
  3. Locate administrative ordinances, permit rules, enforcement policies, bulletins, interpretations, and standard details. File these in the Local Amendments section, separated from the adopted code text itself.
  4. Locate zoning maps, zoning code, use tables, setback tables, height limits, lot-coverage rules, accessory-structure rules, and overlay requirements. Confirm these resources are matched to the defined parcel's zoning district.
  5. Locate parcel, addressing, property-record, flood, wildfire, seismic, snow, wind, coastal, historic, and environmental mapping resources where applicable. File these in the Property Mapping section with the date each map layer was checked.

G. Locate Licensing, Permit, Submittal, Fee, and Inspection Resources

  1. Locate contractor-license, trade-license, registration, owner-builder, insurance, and bond requirements. File the current requirement text in the Licensing section.
  2. Locate permit applications for building, zoning, demolition, grading, plumbing, electrical, mechanical, gas, fire, driveway, right-of-way, utility, well, septic, and specialty work. Save the current published form for each applicable permit type.
  3. Locate plan-submittal checklists, drawing standards, calculation requirements, energy forms, product-approval requirements, and electronic-file rules. File these in the Submittals section.
  4. Locate current permit fee schedules, valuation methods, deposits, reinspection fees, extension fees, and payment methods. File these in the Fees section with the effective date of the schedule.
  5. Locate plan-review turnaround information, expedited-review policies, correction-response procedures, and revision-submittal rules. File these in the Review Procedures section.
  6. Locate inspection types, sequence, request methods, cutoff times, cancellation policies, contact requirements, and result-access procedures. File these in the Inspections section.
  7. Locate final approval, certificate of occupancy, certificate of completion, utility-release, and closeout requirements. File these in the Closeout section.
  8. Collect contact information for plans examiners, inspectors, zoning staff, utilities, and other official resources without relying on personal informal contacts. Use published agency directories rather than a single individual's private contact information.

H. Assemble, Label, and Verify the Binder

  1. Create binder sections for authorities, adopted codes, local amendments, zoning, licensing, permits, submittals, inspections, energy, life safety, standard details, fees, utilities, revisions, corrections, and closeout. Match the section order to the Component Schedule above.
  2. Save authoritative source documents or stable official links with access dates. Record the date accessed alongside every saved document or link.
  3. Label unofficial summaries, training materials, and industry references as secondary guidance. Do not place any unlabeled secondary resource next to an official source where it could be mistaken for one.
  4. Remove outdated forms and mark superseded code editions as archive-only. Do not leave a superseded form or edition in active use without a clear archive label.
  5. Create a source-verification page requiring recheck before each new project. State the recheck interval and the person responsible for it.
  6. Create a local-questions log for requirements that remain unclear. Record each unresolved requirement identified while assembling the binder.
  7. Contact the responsible authority for one unresolved item and record the response and verification date. Use the Field Safety Cue above when making this contact.

I. Test, Correct, and Archive

  1. Test the binder by locating the permit application, adopted code edition, inspection request procedure, and final-approval requirement for one sample project. Time the search and note any section that could not be located within a reasonable effort.
  2. Correct missing, duplicate, conflicting, inaccessible, or outdated resources. Replace or relabel every item identified as a failure during the test in Step 1.
  3. Assign responsibility for periodic binder review and update. Record the responsible reviewer and the review interval on the source-verification page.
  4. Archive the first controlled binder version with a revision date and change log. Record the archive date, version number, and a summary of what was verified at that date.

Common Binder Inspection

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.

Image Placeholder
Recommended image: a labeled binder with fifteen tab dividers visible, matching the Component Schedule section names.
Image Placeholder
Recommended image: a sample authority-register page showing agency name, responsibility, contact information, and a date-verified column.
Image Placeholder
Recommended image: a source-verification page contrasting an official-source entry with a clearly labeled secondary-guidance entry.
Image Placeholder
Recommended image: a local-questions log with one row completed, showing agency, contact, date, question, and response.

Failure Points and Troubleshooting

Cleanup

This project ends with the first controlled binder version archived and ready for reuse, not left as a working draft.

Field Terms

Authority Having Jurisdiction
The agency legally empowered to adopt, interpret, or enforce a given requirement for a defined property.
Adopted Code Edition
The specific code edition and local amendments actually in legal effect for the property, confirmed at the official source.
Official Source
An agency's own published code, ordinance, form, fee schedule, or written response.
Secondary Guidance
Unofficial summaries, industry references, or training materials that are never cited as a controlling requirement.
Date Verified
The date a resource was confirmed directly against its official source.
Authority Register
The document recording every applicable agency's name, responsibility, contact information, and date verified.
Unresolved Item
A requirement that cannot yet be confirmed from an available official source and must be tracked until answered.
Source-Verification Page
The binder page recording the recheck interval and responsible reviewer for every section.
Local-Questions Log
The document recording agency, contact, date, question, and response for unresolved items.
Revision Control
Tracking the binder's version number, archive date, and change log so outdated resources are not mistaken for current ones.

Skill Check

  1. Why must every code edition recorded in the binder be confirmed at the agency's own adoption list rather than a model-code publisher's default page?
  2. What is the difference between an official source and secondary guidance, and why must secondary guidance be clearly labeled?
  3. What information must be recorded for every governing requirement placed in the binder?
  4. Why does a binder entry without a recorded date verified fail the sourcing check?
  5. What must the learner do before treating an agency's verbal comment as a final determination?
  6. What is the purpose of the sample-project test in Section I, and what does a failed test indicate?
  7. Why must private homeowners-association or covenant requirements be kept in a section separate from government permits?
  8. What are three possible causes of an outdated resource remaining in active use, and how does the learner confirm which one occurred?
  9. What must the learner do before archiving the first controlled binder version?
  10. Why does this chapter require the learner to contact a responsible authority for at least one unresolved item rather than leaving it undetermined?

Competency Rubric

CompetencyIndependent Pass StandardNot DemonstratedWith AssistanceIndependently
CP-001Identifies every authority having jurisdiction over the defined property, including private review bodies recorded separately from government authorities
CP-002Locates applicable residential codes and records the adopted edition, local amendments, and official source for each
CP-003Organizes permit resources, forms, fee schedules, and submittal requirements into correctly labeled binder sections
CP-004Collects inspection contacts, request procedures, and result-access procedures matching the current official publication
CP-005Documents every local requirement with source, edition, date verified, and contact of record, and correctly labels secondary guidance
CP-006Builds, 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.

Inspection Checklist — Source Verification Worksheet

SectionSource TypeEdition / Effective DateDate VerifiedContact of RecordCorrection (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: ____________

Performance Check

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.

Project Closeout

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.