How to Document a Code Interpretation You Were Given
Why this matters
An inspector tells your tech on site that a condition is acceptable, and the job passes. Eight months later a different inspector in the same jurisdiction fails the identical condition on your next job, and your tech says "but last time they told us it was fine." Nobody can say who, when, under which edition, or for which condition. The interpretation existed and it was worth nothing, because it lived in one person's memory. Documenting it takes about ten minutes the same day. It turns a verbal call into a dated record with a name on it, which is what lets you rely on it on the next job, show it to the next inspector, and notice when it stops applying.
How to ask the question in the first place is covered in How to Ask the Building Department a Code Question. This card starts once you have an answer.
Step 1: Capture the six facts before the person leaves
On site or on the phone, get these before the conversation ends. Each one is there because a later reader will need it.
- Who. Full name and title: area inspector, plans examiner, building official. Titles matter because authority differs.
- When and how. Date, and whether it was said on site, by phone or in writing.
- Which code, which edition, which section. "2018 IRC, the dryer exhaust duct length provision" is checkable; "the dryer rule" is not.
- The condition. What was installed or proposed, with the one or two dimensions that decided it.
- The answer. One sentence, in the answerer's words as nearly as you can.
- The job. Address and permit number.
Why all six: an interpretation without the edition dies silently at the next code adoption. Without the condition, it gets stretched to cases it never covered. Without the name, it cannot be confirmed.
Step 2: Send a confirming email the same day
Restate the interpretation to the person who gave it, in plain words, and invite correction. Copy the permit file address if the department has one. Attach the photo or sketch the answer was based on.
Why the same day: the details are fresh for both of you. A confirmation sent a week later reads like a negotiation.
Why invite correction: the email only has value if the answerer had a fair chance to say "that is not what I said." Silence after an explicit invitation is far more useful to you than silence after a statement.
Step 3: Write it so it cannot be stretched
State the condition narrowly and say what the interpretation does not cover. Name the dimension, the product, the model if relevant.
Why: the temptation later is to read "the inspector accepted the longer duct" as "long ducts are fine here." The narrow version protects you from your own crew.
Step 4: File it twice: with the job, and in the jurisdiction log
Save the email and attachments into the job record. Then add a line to the shop's interpretation log for that jurisdiction (the log's structure and upkeep are owned by The Code Interpretation Log SOP).
Why twice: the job file is what you produce if this job is questioned. The jurisdiction log is what the estimator and the next crew read before a similar job, which is the whole reason for keeping the record.
Step 5: Reuse it carefully on the next job
Before relying on a logged interpretation, check three things: the condition on the new job matches the logged one, the jurisdiction is still on the same edition, and you know whether the new job's inspector is the same person. If any of the three has changed, ask again and cite the earlier answer: "In March, Inspector Hale accepted this on 22 Birch under the same section; is that still your read?"
Why: an interpretation is a call on a specific condition by a specific official, not a rule. Many departments do not treat one inspector's field call as binding on another, and nothing obliges them to.
The worked example: the email itself
A crew is roughing in a dryer exhaust in a second-floor laundry, under the 2018 IRC as adopted with no amendment to the dryer provisions. The concealed run is 30 ft of straight 4-inch rigid metal duct with four 90-degree elbows. The fitting allowance table in that provision charges each elbow of the type used at 5 ft, so the equivalent length is 30 plus 4 times 5, which is 50 ft. The code's prescriptive maximum is 35 ft equivalent, but the same provision allows the dryer manufacturer's maximum to govern where the dryer make and model are known and the instructions are provided to the code official before the concealment inspection. The owner's dryer is on site; its instructions allow 64 ft equivalent for this duct type and termination hood. 50 ft is 14 ft under 64.
At rough-in, Inspector Hale reviews the instructions and accepts the manufacturer's length. The lead tech sends this the same afternoon:
To: R. Hale, Building Inspector
Cc: permits@[department]
Subject: 18 Larch St, permit B-2291, dryer duct length
Inspector Hale,
Confirming what you told us on site today, Tuesday
March 4, at rough-in:
Code: 2018 IRC as adopted, dryer exhaust duct length
provision (prescriptive max 35 ft equivalent; maker's
instructions may govern where make and model known).
Condition: 30 ft straight 4 in rigid metal plus four
90 deg elbows at 5 ft each = 50 ft equivalent.
Dryer on site; its instructions allow 64 ft for this
duct and hood. Copy attached and left at the laundry.
Your call: manufacturer's 64 ft governs; 50 ft run
accepted; permanent length label required within 6 ft
of the duct connection; if this dryer is replaced with
a different model, length must be rechecked against
the new instructions.
Does not cover: any other dryer, any longer run, any
booster fan.
If I have any of this wrong, please reply and we will
correct it.
M. Reyes, lead tech, Northline Mechanical
Photos attached: run, elbows, hood, dryer data plate
Why each block is there. The subject line carries address and permit so the department can file it. "Confirming what you told us" names the source and the date in the first sentence. The code block names the edition and paraphrases the provision rather than quoting it, which keeps it accurate to what was discussed. The condition block carries the arithmetic so anyone can check the 50 ft: 30 plus 4 times 5. The call block records the conditions the inspector attached (the label and the recheck on dryer replacement), which are the parts most often forgotten. "Does not cover" is the narrowing from Step 3. The last line is the invitation to correct from Step 2.
The label. The permanent label the provision requires, identifying the equivalent length, goes on within 6 ft of the duct connection where it will be seen when the dryer is pulled out. It is installed before final, and the photo goes in the job file.
What it cost. Writing and sending the email took about 10 minutes; the label took another 5. A failed concealment inspection on this run, by contrast, would have meant either reopening a finished ceiling or rerouting to bring 50 ft under 35, a reduction of 15 ft of equivalent length that this floor plan does not allow without a booster fan.
What the record gives you, and what it does not
The email gives you a dated, named, specific statement of what an official told you, sent to that official with an invitation to correct. That is an operational fact you can bank: it answers "who said so" on the next job, it shows the next inspector the earlier reasoning, and it shows a customer or an insurer that the shop asked and followed the answer.
It does not make the interpretation binding on the department, on a different inspector, or on a later job. Whether a written field interpretation has any legal effect if a dispute arises is a question for your own attorney, and the answer varies by state and by how the department's procedures treat field calls. For a formal, binding determination, ask the building official for a written interpretation under the administrative chapter's provision on the official's authority, as adopted. This is not legal advice.
When the inspector says no to writing
Some inspectors will not put a field call in writing. Send the confirming email anyway, addressed to them, with the invitation to correct. If department policy bars them from replying, note that in the job file. You still have a same-day record with the name, the section and the condition, and you have given the person a chance to object.
When the next inspector disagrees
In September the same crew roughs in a near-identical laundry two streets over, same edition, and a different inspector says the run must come down to 35 ft. The record does its work here, but not by winning the argument on the spot. The tech shows the March email, politely, and asks whether the inspector reads the provision differently or sees a difference in the condition. Often the difference is real: this time the dryer is not on site, so the make and model are not known, and the manufacturer's-length path the March call relied on is not open. The email's own "condition" block shows why March does not reach September.
Where the conditions genuinely match and the two inspectors simply disagree, the record goes to the building official with a request for a written interpretation. That turns two conflicting field calls into one answer for the whole jurisdiction, which then replaces both entries in the log.
When the interpretation stops applying
Flag every log entry with the edition it was given under. When the jurisdiction adopts a new edition, review the entries for that jurisdiction: some provisions are unchanged and the interpretation may still hold (ask again on the first job), some were rewritten and the interpretation is retired. A dryer-length call under the 2018 IRC is a question to re-ask, not an answer to carry, once the 2024 edition is adopted.
References
- International Code Council, International Residential Code (2018 edition), dryer exhaust duct length provisions in Chapter 15, and the administrative chapter on the building official's authority to interpret, as adopted
- Dryer manufacturer's installation instructions, maximum exhaust duct length tables
- See related: How to Ask the Building Department a Code Question; The Code Interpretation Log SOP
- See related: Working With the Authority Having Jurisdiction: The Basics; The Edition on the Permit, Not the Newest Edition