I’m with you on pushing for what’s actually in the code, even if it ruffles a few feathers. I’ve run into similar pushback with newer finishes—sometimes inspectors just aren’t up to speed on what’s allowed. I do still keep a physical folder for backup, though. Not every inspector is tech-savvy, and sometimes it’s just faster to hand over a printout than wait for them to scroll through emails. But yeah, standing your ground is key, especially when you know your stuff.
I do still keep a physical folder for backup, though. Not every inspector is tech-savvy, and sometimes it’s just faster to hand over a printout than wait for them to scroll through emails.
That’s so true. I’ve had an inspector actually thank me for having paper copies—he said his tablet was acting up and he didn’t want to mess with it. I guess it’s old school but it saved us both time. Out of curiosity, have you ever had to push back on something the inspector insisted on, even when you knew the code was on your side? I always worry it’ll drag things out or cost more if I make a fuss, but sometimes you just can’t let it slide...
Pushing back on inspectors is one of those things I always dread, but sometimes it’s just unavoidable. I had a situation last year where the inspector insisted I needed fireblocking in a spot that, according to the code and even the city’s own handout, didn’t actually require it. I tried to keep it friendly—just pulled out the printed code section and the city’s diagram from my folder (which he appreciated, by the way), and calmly explained my reasoning.
Here’s how I usually handle it when I know I’m right but don’t want to make things worse:
1. Stay calm and respectful. Even if you’re frustrated, getting defensive never helps. Most inspectors are just trying to do their job.
2. Have your documentation ready. Like you said, paper copies can be a lifesaver—especially if their tech isn’t cooperating or they’re in a hurry.
3. Ask them to clarify their interpretation. Sometimes they’ll explain something you missed, or you’ll realize you’re both talking about different parts of the code.
4. If you’re still at odds, politely ask if there’s someone else at the office who can review it—like a supervisor or plan reviewer. Usually, they’re fine with that as long as you’re not combative.
In my case, after we looked at the paperwork together, he admitted he might’ve been mixing up two different requirements. He double-checked with his supervisor and ended up signing off without any extra work on my end.
I get what you mean about not wanting to drag things out or risk ticking someone off—sometimes it feels easier to just do what they say and move on. But if it’s going to cost real money or set a precedent for future jobs, I think it’s worth standing your ground (nicely). Most of the time, if you’ve got your ducks in a row and treat them with respect, they’ll at least hear you out.
Funny thing is, after that incident, that same inspector started asking me for copies of certain code sections for his own reference... Guess having that backup folder really does come in handy.
I had a similar run-in last fall—inspector flagged my insulation install, claiming it didn’t meet the city’s “eco” standard, even though I’d used the exact product listed in their guide. I pulled out the spec sheet and, after a bit of back and forth, he realized he’d confused two different R-value requirements. It’s frustrating, but having that paper trail really does save time (and nerves). I’ve noticed some inspectors are just overwhelmed by all the updates—can’t really blame them, but it does put us in a weird spot sometimes.
That sounds all too familiar. I’ve started keeping a binder with every product spec, code reference, and even email exchanges—just in case. It’s wild how quickly the standards change, especially with anything labeled “eco.” Sometimes I wonder if the city even updates their own guides as fast as the codes shift. Have you ever had to appeal a decision, or do you usually get things sorted on-site?
