The Code Interpretation Log SOP

Purpose

A building official's interpretation of an unclear code section is binding in that jurisdiction until it is withdrawn, the code changes, or a different official reads it differently. This log keeps the interpretations the shop has been given, in writing, by jurisdiction and by the person who gave them, so a tech on a new job does not re-fight a question the shop already settled, and does not carry one county's answer into the next county. Without it, the shop's knowledge of what each department accepts lives in the head of whoever got failed last, and leaves with them.

Scope

Covers: interpretations of adopted code sections, local amendments and manufacturer-instruction questions given by a building official, plans examiner or inspector, whether volunteered at an inspection or answered on request.

Does not cover: how to ask the question in the first place (see related: How to Ask the Building Department a Code Question); how to document a single interpretation on the job it came from (see related: How to Document a Code Interpretation You Were Given), which this log draws from; and formal approval of an alternative method, which goes through the jurisdiction's own process and produces its own approval document (see related: How to Request Approval for an Alternative Method).

Roles and responsibilities

The handoff that fails is tech to log keeper: an interpretation given at a final inspection, celebrated in the truck, and never written down.

The procedure

1. Capture it on the day, in the official's terms. The tech who received the interpretation writes, before leaving the site, the code section as the official named it, the question, the answer in as close to the official's words as possible, the official's name and role, and the address and permit number. Acceptance: all five fields filled in the job record within the same working day. What wrong looks like: "inspector said we're fine on the vent." Stop rule: a paraphrase with no section number goes to the log keeper marked UNCONFIRMED and is not relied on for any quote until step 3 converts it. No physical hazard at this step; writing it while standing at the open trench or in the attic is the hazard, so the tech writes it in the truck, not on a ladder.

2. Classify the source. The log keeper assigns one of three levels: WRITTEN (an email, a correction notice, a plan review comment, a signed note from the department), VERBAL-CONFIRMED (a verbal answer the shop then confirmed by email to the official without a correction coming back within 10 business days), and VERBAL (nothing in writing). Acceptance: every entry carries exactly one level. What wrong looks like: a VERBAL entry treated as WRITTEN because the inspector was friendly. Stop rule: only WRITTEN and VERBAL-CONFIRMED entries may be cited to an inspector or relied on in pricing; VERBAL entries are reminders to ask, not answers. Whether any of these binds a different official on a later job is a question about that department's practice, not something the log settles.

3. Convert verbal to confirmed. Within 2 business days of a VERBAL entry, the log keeper sends a short email to the official: the address, the section, the question, and "our understanding of your direction is..." with a request to correct it if wrong. Acceptance: email sent and saved to the entry; the 10-business-day clock noted. What wrong looks like: a confirmation email that argues the point, which reads as a dispute rather than a record. Stop rule: if the official corrects the understanding, the entry is rewritten to the correction and the job it came from is checked for conformity the same week; if the correction means installed work does not conform, the owner is told the same day.

4. Make the entry searchable by the three keys techs actually use. Each entry is filed under jurisdiction, code section, and a plain trade phrase ("water heater pan on replacement," "panel bonding at meter base"). Acceptance: a test search on each key finds the entry. What wrong looks like: entries filed only by date or only by inspector's name, which nobody searches. Stop rule: none; a malformed entry is fixed when found.

5. Record the edition and amendment set. Every entry names the code edition the jurisdiction had adopted at the time and whether a local amendment was involved. Acceptance: edition year and amendment reference filled in, taken from the permit or the department's adoption page, never from memory. What wrong looks like: an entry with no edition, which becomes impossible to retire correctly at step 7. Stop rule: if the edition cannot be determined, the entry stays UNCONFIRMED. See related: The Edition on the Permit, Not the Newest Edition.

6. Consult before quoting, and quote the entry's level. Before pricing a job that touches a logged question, the estimator searches the log for that jurisdiction. Acceptance: the quote's internal notes cite the entry number, or "no entry." What wrong looks like: relying on an entry from a different jurisdiction because the question is the same; neighboring departments routinely read the same section differently. Stop rule: an entry from another jurisdiction is a prompt to ask this one, never an answer. If a job must proceed before an answer comes back, the estimator prices the stricter reading and notes it.

7. Review quarterly, and retire on every edition change. Each quarter the log keeper lists entries older than 3 years and entries whose official has left the department; the owner confirms, re-asks or retires each. On the effective date of a new edition in a jurisdiction, every entry for that jurisdiction is marked UNDER REVIEW and is not relied on until someone has checked whether the new edition's text resolves, changes or deletes the question. Acceptance: review dated and initialed; every UNDER REVIEW entry resolved within 60 days of the effective date. What wrong looks like: a 2018-edition interpretation still being cited three years after the 2021 adoption. Stop rule: an entry not resolved in 60 days is retired, not left hanging. See related: The New Code Edition Adoption SOP.

8. Retire, do not delete. A retired entry is kept, marked with the date and reason, because it still explains why work done during its life looks the way it does. Acceptance: no entry is ever removed. What wrong looks like: a cleaned-out log that cannot answer why the 2022 jobs were vented differently. Stop rule: none.

Exception path. If an inspector's interpretation contradicts a WRITTEN entry from the same department, the tech does not argue on site. The tech notes it, the job proceeds to the inspector's reading if that is cheap or safe to do, and the log keeper raises the conflict with the department's building official in writing, citing both. If the conflict is expensive, the owner decides whether to request the official's ruling or the department's appeal process before rework. See related: How to Handle an Inspector Who's Stricter Than the Code.

The record this produces

CODE INTERPRETATION LOG          Entry 0112
--------------------------------------------
Jurisdiction:  [county] building dept
Edition:       IRC 2021 + local amend. [ref]
Section:       P2801.6 (water heater pan)
Trade phrase:  water heater pan on replacement
Question:      Pan needed, finished basement,
               heater on slab?
Answer:        Yes. Pan with drain to an
               approved location required
               in any finished space.
Given by:      [name], inspector
Job / permit:  [address] / [permit no.]
Level:         VERBAL-CONFIRMED (email 3/4,
               no correction by 3/18)
Status:        ACTIVE   Next review: Q3

Estimators read it before quoting. Techs read it from the truck before a first inspection in an unfamiliar department. The owner reads the UNDER REVIEW list at every adoption.

A worked pass

A plumbing and remodel shop works in three jurisdictions. In March, an inspector in the county tells a tech at a final on a water heater replacement that a pan with a drain is required in a finished basement, even with the heater sitting on the slab.

• Step 1: the tech writes the section as the inspector named it, P2801.6, the answer, the inspector's name, address and permit, in the truck the same afternoon. Pass.
• Step 2: classified VERBAL. Pass.
• Step 3: confirmation email sent 2 days later, on March 4. No correction by March 18, 10 business days later. Upgraded to VERBAL-CONFIRMED. Pass.
• Step 4 and 5: filed under the county, P2801.6, "water heater pan on replacement," edition 2021 with the county's amendment package. Pass.
• Step 6: FAILED. In May, an estimator quoting a water heater replacement in a finished basement in the neighboring city found entry 0112 and priced a pan and a drain line to the floor drain. But the estimator wrote "per entry 0112" as if it applied in the city. The log keeper's spot check caught it. Stop rule taken: the entry is the county's, so it is a prompt to ask the city. The log keeper emailed the city's department; the city answered in writing that on a basement slab with a floor drain in the same room, it does not consider leakage to cause damage and does not require the pan. New entry 0119, WRITTEN, for the city.
• Result: the city quote was revised without the pan, which removed roughly an hour of labor plus the pan and drain materials. Had the estimator's note gone unchecked, the shop would have priced the stricter reading on every city job indefinitely, or worse, a tech would later have cited a county entry to a city inspector.
• Step 7: in the next January, the county announced adoption of a newer edition effective in April. Both county entries were marked UNDER REVIEW on the effective date and resolved within 60 days.

References

• International Residential Code, administrative chapter, as adopted by your jurisdiction: the building official's authority to render interpretations of the code (R104.1 in the 2021 edition).
• Your jurisdiction's adoption ordinance and local amendment package, which fix the edition an entry belongs to.
• See related: Building Codes Hierarchy Reference; Staying Current on Code Changes Without a Full-Time Job of It.
• See related: How to Read a Code Section, Exceptions and All.