documentation is gold.
That’s a fair point about documentation—saved me more than once when two inspectors gave conflicting instructions. Curious, have you ever escalated to a supervisor when you hit that kind of contradiction? Sometimes I wonder if it’s worth the extra friction or just muddies things further.
Had that happen once—two inspectors, two totally different takes. I did end up talking to their supervisor, and honestly, it helped clear things up. Bit awkward, but better than redoing work later. Documentation definitely saved my bacon there. Don’t be afraid to push back a little.
Honestly, I get what you’re saying about talking to the supervisor, but in my experience that can sometimes backfire. Had a situation where I tried going up the chain after getting conflicting feedback, and somehow it just made the inspector more rigid the next time around. Maybe it was pride? Hard to say.
Documentation definitely saved my bacon there.
Totally agree on keeping records, though. That’s saved me more than once when things got messy. Still, sometimes pushing back—especially if you catch them on a bad day—just drags things out or makes them dig in their heels. Lately, I’ve found it works better to just ask a ton of questions right there on site, even if it feels annoying. Like, “Can you show me exactly what’s wrong according to code?” Usually they’ll walk you through it and you can get a clearer picture without escalating.
Maybe it’s luck of the draw with inspectors, but I’m starting to think building a good rapport from the start pays off more than going over their heads... at least until you really hit a wall.
Yeah, I’ve learned the hard way that going over an inspector’s head can turn a small headache into a full-blown migraine. Here’s my usual playbook: 1) Take notes on everything they say, even if it feels nitpicky. 2) Ask for code references—sometimes they’ll even pull out the book and show you. 3) If you get denied, don’t argue right there. Go home, read up, and come back with specific questions. I swear, half the time just showing you’re willing to do your homework gets them on your side. And if you’re working on an old house like mine, sometimes you just have to laugh at how many “exceptions” there are...
Title: Got Denied For A Permit—What Would You Do Next?
Go home, read up, and come back with specific questions. I swear, half the time just showing you’re willing to do your homework gets them on your side.
That’s been my experience too—most inspectors seem allergic to arguments but warm up if you show you’re not just winging it. I used to think getting defensive would help (“But that’s not how it’s done on YouTube!”), but all that did was buy me a one-way ticket to Rejection Town.
One thing I’ll add: sometimes the inspector is actually saving you from a bigger headache down the line. I had a buddy who tried to sneak a bathroom vent through an old chimney chase (don’t ask). Inspector nixed it, and he grumbled for weeks... until we found out the chase was full of squirrel nests. Could’ve been a real horror show if he’d just pushed through.
And yeah, old houses are basically held together with code exceptions and hope. My kitchen wiring looked like a spaghetti monster from 1942. The inspector just shook his head and said, “Well, as long as it doesn’t catch fire.” Not exactly reassuring, but at least he was honest.
If I get denied now, I just treat it like a pop quiz I didn’t study for—go home, hit the books, and come back ready to show my work. Sometimes I’ll even bring photos or sketches of what I’m planning next time. Seems to help them see I’m not trying to cut corners, just trying to keep my house from falling down... or up to code, whichever comes first.
