The New Code Edition Adoption SOP

Purpose

When a jurisdiction adopts a new edition of a model code, the work the shop sells changes on a fixed date, and the shop's quotes, templates and habits do not change by themselves. This procedure makes sure that by the effective date someone has read what changed for the shop's trades, the price book and job templates carry the new requirements, the crews have heard about them, and every job in flight is assigned to the right edition. Without it, the first notice of the new edition is a failed inspection on a job quoted under the old one. For the habit of watching for changes in the first place, see related: Staying Current on Code Changes Without a Full-Time Job of It. This SOP starts where that card ends: an adoption has been announced.

Scope

Covers: adoption of a new edition of any code the shop's work is inspected under (residential building, electrical, plumbing, mechanical, fuel gas, energy), and adoption of a local amendment package to an edition already in force.

Does not cover: state licensing rule changes, manufacturer instruction revisions (see related: How to Handle an Instruction Sheet That Changed Since Your Last Install), or federal equipment efficiency standards, which change what can be sold rather than how it is installed and follow their own effective dates. The background on how editions move through state and local adoption is in Building Code Cycles + State Adoption; this SOP does not re-survey it.

Roles and responsibilities

The handoff that fails is reader to office: an impact list that names a code section but not which price-book item or template it changes.

The procedure

1. Log the adoption the day it is announced. The office records the jurisdiction, the code and edition, the effective date, whether a transition or grace period exists, and where the adopting ordinance and amendments are published. Acceptance: all five fields filled, with the source document saved, not a trade newsletter's summary of it. What wrong looks like: "county going to the new electrical code sometime next year." Stop rule: if the effective date or the grace rule cannot be found in an official document, the office emails the department and the entry stays open until answered in writing. No physical hazard; the risk is that a date heard secondhand is wrong by months.

2. Read the changes and the amendments, not just the changes. The change reader for each affected trade reads a section-by-section change summary for the new edition and then the jurisdiction's own amendment package, because a local amendment may delete, delay or tighten a model-code change. Acceptance: a written impact list within 30 days of the announcement or 60 days before the effective date, whichever is sooner, where each line names the section, what changed, and the job types it touches. What wrong looks like: an impact list built from a national summary that never opened the local amendments. Stop rule: the list is not accepted by the owner until the reader confirms the amendment package was read. See related: How to Find Local Code Amendments.

3. Turn every impact line into a concrete change in the shop's system. For each line the office lead names the price-book item, job template, checklist or quote clause that changes, and drafts the change: a new required line item, a changed default quantity, a new checklist step, a new photo requirement. Acceptance: every impact line maps to at least one named item or is marked "no system change" with the reason. What wrong looks like: an impact line with no owner in the system, which is how a requirement gets read, agreed with and never priced. Stop rule: the owner does not approve the list while any line is unmapped.

4. Load the changes before the effective date, tagged by edition. Changed price-book items and templates are built as new versions, not edits to the old, so jobs still under the old edition keep their old template. Acceptance: new versions live in the system at least 14 days before the effective date, each labeled with the edition. What wrong looks like: overwriting the old template on the day, which breaks every in-flight job still quoted under the old edition. Stop rule: if the new versions are not ready 14 days out, the owner decides whether to stop quoting affected job types until they are.

5. Train the crews on the lines that change what they do on site. At a huddle before the effective date, the change reader walks each line that changes field work, with the photo or measurement it now requires. Acceptance: every lead tech in the affected trade attended or read the summary and initialed it; attendance recorded. What wrong looks like: training on the whole change summary, most of which never touches the shop's work, so the three lines that matter get lost. Stop rule: a lead tech who has not initialed does not run the first job under the new edition alone.

6. Apply the cutover rule to every job in flight. The default rule: the edition that governs a job is the one in force on the date its permit application was submitted, unless the jurisdiction's adopting ordinance says otherwise or offers a grace period in which the applicant may choose. The office tags every open job with its governing edition. Acceptance: every job with a permit pending or not yet applied for carries an edition tag. What wrong looks like: a job quoted before the effective date and applied for after it, priced under the old edition. Stop rule: for any job whose quote and permit straddle the date, the office reprices against the new edition and the owner decides, under the quote's own terms, whether to issue a change order or absorb the difference; the customer is told before work starts, not at inspection. See related: The Edition on the Permit, Not the Newest Edition.

7. Freeze the interpretation log for that jurisdiction. On the effective date every log entry for that jurisdiction is marked UNDER REVIEW. Acceptance: done on the date. What wrong looks like: an estimator citing an old-edition interpretation to price a new-edition job. Stop rule: no UNDER REVIEW entry is relied on until it is resolved. See related: The Code Interpretation Log SOP, which owns the review.

8. Debrief the first three inspections. The lead tech on each of the first three inspected jobs under the new edition reports any correction notice or comment to the change reader. Acceptance: three reports, or a note that fewer than three happened within 90 days. What wrong looks like: a correction on the first job that the second and third crews repeat. Stop rule: any correction tied to a new-edition requirement goes back through step 3 within a week. Resume hazard: where a correction requires reopening energized or gas work, the crew de-energizes and verifies dead, or shuts and leak-tests the gas, exactly as on the original job before touching it.

The record this produces

An adoption file per jurisdiction per edition, holding the step 1 log, the source documents, the impact list with its mapping to price-book items and templates, the training sign-off, the cutover tag list of in-flight jobs, and the three debrief reports. The owner reads it at sign-off. A year later it answers the question a customer or an inspector asks: why was this job priced or built this way.

A worked pass

An HVAC and electrical shop works mostly in one county. The county announces adoption of a newer edition of the electrical code (NFPA 70, the NEC), replacing one two cycles older, effective in six months, with a local amendment package.

• Step 1: jurisdiction, code, edition, effective date and source ordinance logged; the ordinance stated no grace period. Pass.
• Step 2: the electrical change reader listed eleven sections touching the shop's work. Two mattered most: ground-fault protection extended to outdoor outlets serving dwelling equipment, which reaches condenser circuits, and new service-level requirements for surge protection and an outdoor emergency disconnect on service upgrades. Reading the amendment package, the reader found the county had delayed the outdoor-outlet ground-fault requirement for HVAC equipment for one cycle, as a number of jurisdictions did after nuisance-tripping complaints with some inverter equipment. Pass, and that one paragraph saved repricing every condenser job.
• Step 3: eleven lines mapped. Surge protection became a required line on the service-upgrade template; the emergency disconnect became a required line plus a photo step on the same template. The outdoor-outlet line was mapped to "no system change, delayed by amendment," with a calendar reminder at the next adoption. Pass.
• Step 4: new template versions live 21 days before the effective date. Pass.
• Step 5: huddle held; all four lead techs initialed. Pass.
• Step 6: FAILED. A service upgrade quoted 10 days before the effective date had its permit application submitted 3 days after it, because the customer delayed signing. The quote had been built on the old template with no surge protection and no outdoor disconnect. The office's tag sweep caught it. Stop rule taken: the job was repriced under the new edition, adding about 3 hours of labor plus the two devices. The quote's terms said pricing assumed the code in force at permit application, so the owner issued a change order, and the office called the customer before scheduling, not at the meter.
• Step 8: the first three inspected upgrades passed; the debrief noted one inspector asking for the surge device's listing to be visible, and the photo step was updated to include the label.

References

• NFPA 70, National Electrical Code, in the edition and with the amendments your jurisdiction has adopted; the change summary published with each edition is the starting point for step 2.
• Your jurisdiction's adopting ordinance, which sets the effective date, any grace period and the local amendments.
• See related: Staying Current on Code Changes Without a Full-Time Job of It; Building Code Cycles + State Adoption.
• See related: Reading Which Code Book Governs This Job.