STRUGGLING WITH VENTILATION INSPECTION REQUIREMENTS LATELY
Yeah, the inconsistency between counties drives me nuts too. One inspector wants baffles every rafter bay, another just shrugs. Had a project last year where we had to redo the whole attic vent layout because the guy suddenly decided he wanted continuous ridge vents instead of what was on the plans. Agree about catching things early—nothing worse than cutting into finished ceilings to fix a missed vent. Still, sometimes it feels like they’re making up rules on the fly...
Still, sometimes it feels like they’re making up rules on the fly...
- Had a site in two neighboring towns—one inspector flagged the same vent setup the next guy approved without blinking.
- Drives up costs and delays. Planning’s almost pointless if the rules change at walkthrough.
- We started sending annotated plan sets to inspectors before rough-in, just to get some kind of written response. Cuts down on “surprise” requirements, but it’s a pain.
- Honestly, feels like half of it depends on what mood they’re in that day.
STRUGGLING WITH VENTILATION INSPECTION REQUIREMENTS LATELY
That’s been my experience too—sometimes it feels like you’re playing code roulette. I’ve had projects where the inspector wanted a specific vent termination height, then the next town over, nobody cared as long as it wasn’t dumping into an attic. The pre-inspection plan review helps, but yeah, it’s a hassle and doesn’t always guarantee consistency.
One thing that’s helped us a bit is keeping a running log of previous inspections, with photos and notes on what passed or failed. When a new inspector comes in, we can show them “Hey, this setup was signed off last month, same jurisdiction.” Doesn’t always sway them, but it’s saved us from a few unnecessary re-dos.
Curious—has anyone tried looping in the mechanical engineer or architect during these walkthroughs? Sometimes having them there to reference code chapters on the spot makes a difference, but maybe that’s just luck...
Curious—has anyone tried looping in the mechanical engineer or architect during these walkthroughs? Sometimes having them there to reference code chapters on the spot makes a difference, but maybe that’s just luck...
We’ve brought our engineer along a couple times, and honestly, it’s been hit or miss. Sometimes the inspector appreciates the backup, other times it feels like it just slows things down. I’m curious—has anyone actually had an inspector change their mind on the spot when shown code language, or do they usually just stick to their guns?
Honestly, I’ve tried having the engineer there, and it’s been a mixed bag for us too. One time, the inspector actually flipped through the codebook with him and agreed to a change, but more often, they just say, “That’s not how we interpret it.” If you’re on a tight budget, I’d say prep your documentation ahead of time—highlight the relevant code sections, maybe have a quick summary sheet ready. That way, you’re not paying for extra hours if the walkthrough drags on. Sometimes less is more, especially if the inspector’s already made up their mind...