Yeah, inspectors can be wild cards—one guy flagged my shower valve for being 1/4" off center, while the next just wanted to talk about his fishing trip. I keep a spreadsheet of code notes, too. It’s a pain, but it’s bailed me out more than once. Honestly, half the time it feels like you’re prepping for a pop quiz with no study guide...
Man, I swear inspectors have their own secret dice they roll before every visit. One guy measured my pipe spacing with a laser level, the next just peeked in and said, “Looks good, kid.” I’ve started keeping a notebook of random stuff they mention—half of it’s probably not even code, but you never know. It’s like prepping for Jeopardy, except the categories are always a surprise...
It’s like prepping for Jeopardy, except the categories are always a surprise...
That’s honestly the perfect way to put it. I’ve had inspectors get hung up on things like the direction of vent pipe runs—stuff that’s not even spelled out in the codebook, just “best practice” from their last job. Keeping notes is smart. I usually cross-reference what they mention with the actual code later, just to be sure I’m not chasing ghosts. Some of it’s legit, but sometimes it’s just personal preference. The inconsistency can be frustrating, but at least you’re covered if you document everything.
Did you ever push back when an inspector flagged something that wasn’t actually in the code? I get that they’ve got experience, but sometimes it feels like you’re supposed to just read their mind. I’m curious if anyone’s ever had luck getting them to clarify or back down a bit, or is it just easier to go along and fix whatever they want?
Had this happen more than once, actually. There was a time I was redoing a laundry room and the inspector flagged the dryer vent for not being “accessible enough.” I’d double-checked the code, and there was nothing about that—just requirements for length, material, and termination. I asked him to show me the section he was referencing, and he kind of danced around it, saying it was “best practice.”
I get that they want things done right, but I don’t think it’s unreasonable to ask for specifics. If it’s not in the code, it shouldn’t be a fail. I’ve found that if you’re respectful but persistent, most inspectors will at least explain their reasoning. Sometimes they’ll admit it’s just their personal preference, and in those cases, I’ll push back a bit more. I’ll even print out the code section if I have to.
That said, there are times when it’s just easier to do the fix, especially if it’s minor. If it’s something that’ll take an hour and doesn’t mess with the project, I’ll just do it and move on. But if it’s a big change or adds cost, I’m not shy about standing my ground.
Honestly, I think a lot of folks just go along because they don’t want to risk delays, but if nobody ever questions these “interpretations,” inspectors start thinking their preferences are the law. That’s how you end up with a patchwork of unofficial rules.
It’s a balancing act—pick your battles, but don’t be afraid to ask for clarification. You’re not being difficult, you’re just making sure everyone’s playing by the same rulebook.