Remodeling discussions and local services.

got denied for a permit - what would you do next?

672 replies
 

Join the conversation

Share your experience or ask a follow-up question.

thomasc12

Getting a permit denied is like the universe’s way of saying, “Not today, buddy.” I swear, I’ve spent more time deciphering city code than actually working on my house. That whole “too industrial” thing cracks me up - like, what does that even mean? Are they expecting me to install chandeliers in my garage?

“Sometimes it’s worth pushing back a little, but yeah, you gotta know when to just let it go or you’ll drive yourself nuts.”

Totally agree with this. I’ve had to learn the hard way that sometimes you just have to pick your battles. Last year, I tried to get a permit for a shed and got denied because the roof pitch was “not in harmony with the neighborhood.” Meanwhile, my neighbor’s got a bright blue tarp for a roof half the year... but sure, my 10x12 shed is the problem.

I did end up calling the city and asking what “harmony” meant in this context. Turns out, they just wanted it to match my house roof color. One trip to the paint store later and suddenly everything was harmonious. Go figure.

I will say though - sometimes I feel like if you act confused enough (which isn’t hard for me), they’ll actually help you out just so you stop calling. Not saying that’s a strategy, but... it kinda works.

At this point, I just try not to take it personally. Permits are like playing bingo - you never know what’s gonna get called out next. If it gets too ridiculous, I just take a break and remind myself why I’m not paying someone else to deal with this headache. Gotta save those pennies for something fun... like replacing all the light bulbs again because apparently 2700K is “too cozy.”


Reply
jack_ghost

Honestly, I get the urge to just let it go sometimes, but I wonder if we give up too easily. You mentioned,

“Sometimes it’s worth pushing back a little, but yeah, you gotta know when to just let it go or you’ll drive yourself nuts.”

I get that - mental health is important - but I’ve actually had some luck pushing back (nicely) when things seemed a little arbitrary. For example, I got flagged for “excessive glazing” on a sunroom addition. I thought about scrapping the whole thing, but instead, I asked for clarification and brought in a few photos of similar builds in the area. They ended up reconsidering after seeing how common it was.

I guess what I’m saying is, sometimes the squeaky wheel does get the grease... or at least a clearer answer. Not saying it always works or that it’s worth the hassle every time, but occasionally you can nudge them into being more reasonable. Maybe it just depends on how much energy you have that week.

And yeah, the “too cozy” light bulb thing is wild. Who knew ambiance could be controversial?


Reply
tylerg21

Pushing back can definitely pay off sometimes, especially when the rules feel like they’re being made up on the spot. I’ve had my fair share of “wait, that’s a rule now?” moments at the permit office. Once got dinged for “excessive egress” on a basement remodel - still not sure what that even means, but after a few polite conversations and a couple of sketches, they let it slide. Sometimes I think they just want to see if you’ll actually show up with a smile and some patience.

That said, I totally get the energy thing. Some weeks you’re ready to go to bat, other times you just want to get the job done and move on. It’s a weird balance between picking your battles and not letting the process steamroll you. I’ve noticed that bringing in photos or examples from the neighborhood works wonders, like you did. It’s almost like they need proof that you’re not trying to build a spaceship in your backyard.

The “too cozy” light bulb thing cracks me up. I once had an inspector tell me my under-cabinet lighting was “too inviting.” Not sure if that’s a compliment or a code violation. Makes you wonder if there’s a secret handbook somewhere: “Section 12B: No excessive coziness.”

At the end of the day, I guess it comes down to how much you care about that particular project. If it’s something you’re passionate about, it’s usually worth pushing a little. If not, sometimes it’s just easier to tweak the plans and call it good. Either way, you end up with a story to tell... and maybe a sunroom with just the right amount of glazing.


Reply
astronomy747

Totally get what you mean about the “is this even a rule?” moments - been there more times than I can count. Sometimes I wonder if half the process is just seeing how persistent you’ll be. Ever tried asking for clarification in writing? I’ve found that when they have to put their reasoning on paper, things magically get clearer (or they back off a bit). But yeah, sometimes it’s just not worth the fight. Curious, did you end up tweaking your plans or are you still pushing back?


Reply

Honestly, I’ve found that pushing back in writing sometimes just drags things out. I usually take a closer look at the code myself - sometimes there’s wiggle room in the interpretation. Once, I caught a reviewer on a technicality and got my permit through. Not saying it always works, but I’d rather dig into specifics than get stuck in endless email chains.


Reply
ryansculptor

I usually take a closer look at the code myself - sometimes there’s wiggle room in the interpretation.

Interesting approach, but do you ever worry about missing something subtle in the code? I get what you mean about endless emails, but sometimes I’ve found that a quick phone call or even dropping by the office can clear things up way faster. Ever tried just asking the reviewer directly what they’d accept? Sometimes they’ll point out a workaround you wouldn’t spot just reading the code.


Reply
dance348

I get where you're coming from - sometimes you can read the code a dozen times and still miss the one thing that trips you up. I actually tried emailing back and forth at first, but it just dragged on forever and got nowhere. Finally, I just called the reviewer directly. Turns out, there was a super simple fix they were looking for, but it wasn't spelled out anywhere in the code or the rejection letter. If I'd stuck to just reading the code, I'd probably still be stuck.

Honestly, I think it's worth just asking them straight up what they're looking for. Worst case, they say no, but at least you know for sure. And yeah, sometimes they'll mention something you never would've guessed from the paperwork alone. It's not always comfortable, but it beats spinning your wheels. Anyone else had luck just showing up at the office? Feels weird but sometimes face-to-face is the only way to get a clear answer...


Reply
sophiesinger

Showing up in person honestly makes a huge difference. I was super nervous about it, but after weeks of back-and-forth emails that went nowhere, I just walked in and asked to talk to someone. It was awkward at first, but the reviewer actually pulled out my file and pointed out exactly what was missing. Way faster than trying to decode their notes or guess what they wanted. I get that not everyone’s comfortable with face-to-face, but sometimes it’s the only way to cut through the red tape. Email just doesn’t cut it for stuff like this, in my experience.


Reply

I get where you’re coming from - face-to-face can definitely clear things up fast. But honestly, I’ve had a few situations where showing up in person didn’t move the needle at all. Sometimes the staff just refer you back to the same checklist or say they’ll “get back to you.” I’ve found that sending a really detailed email, with attachments and specific questions, sometimes gets routed to the right reviewer and leaves a paper trail if there’s confusion later. Not saying it always works, but for folks who can’t get away during office hours, it’s worth trying before taking time off work.


Reply
tea_jeff

I get the appeal of email for the paper trail, but I’ve had mixed luck with that. Sometimes my detailed questions just got a canned response or sat in someone’s inbox for weeks. In-person, at least I know someone’s actually hearing me out, even if it’s not always productive. Maybe it depends on the city?


Reply
jsage27

I hear you on the email front - sometimes it feels like you’re just shouting into the void. But honestly, I’ve had the opposite problem with in-person visits. Last year, I spent half a day waiting around at the city office, only to get bounced between three different people who all gave me slightly different answers. At least with email, I’ve got something in writing when the inspector says one thing and the plan reviewer says another. Saved my butt more than once when someone tried to backtrack.

That said, I do think it depends on the city. Some places, you walk in and they’re super helpful. Others, you’re better off documenting every little thing. I guess I’ve just learned to double up - start with email, then follow up in person if I’m getting nowhere. Not perfect, but it’s kept me out of trouble more times than not.


Reply

I get where you’re coming from about the in-person runaround. Honestly, I’ve had my fair share of those “musical chairs” moments at the permit desk - one guy says yes, the next says no, and suddenly you’re back at square one. What’s worked for me is treating every interaction like a paper trail opportunity. Even if I talk to someone face-to-face, I’ll send a quick follow-up email summarizing what we discussed. That way, if someone tries to change their story later, I can point right back to it.

One time, I had a project where the zoning guy verbally approved a setback variance, but the official paperwork said otherwise. My recap email saved me from having to redo a bunch of site work. It’s not that I don’t trust them, but city staff turnover is real and details get lost.

I do think some cities are way better than others, though. In smaller towns, you might get straight answers and even a little flexibility. In bigger places? Documentation is your only friend. I’d rather spend an extra five minutes writing an email than risk weeks of delays or rework.


Reply
scottcyber782

Title: Got Denied For A Permit - What Would You Do Next?

That paper trail habit is clutch. I’ve run into the same thing - one department says you’re good, then another throws a wrench in it. I’m always surprised by how inconsistent the info can be, even within the same office. I’ve started asking for written responses whenever possible, but sometimes you just get that “it’s policy” shrug.

Have you ever tried pushing back with code references or bringing in an architect/engineer to clarify things? I’ve found that sometimes, if you can point to the exact section of the code or bring in someone with credentials, the staff will reconsider or at least explain their reasoning more clearly. It’s not a guarantee, but it’s helped me avoid blanket denials a couple times.

Curious if you’ve noticed any difference between departments - like, is planning usually the stickler, or is it more often building? For me, zoning’s been the wild card. Just wondering if that’s universal or just my luck...


Reply
sky_carpenter

I’ve run into the same thing - one department says you’re good, then another throws a wrench in it. I’m always surprised by how inconsistent the info can be, even within the same office.

Totally get where you’re coming from. That back-and-forth between departments is brutal - feels like playing whack-a-mole half the time.

- Keeping everything in writing is key, like you said. Even just a quick email recap after a phone call can save headaches.
- I’ve had some luck showing up with printed code sections highlighted. Sometimes they’ll actually listen, sometimes not, but at least it shows you’re not just winging it.
- Bringing in an architect or engineer does seem to carry more weight, especially if you’re dealing with structural stuff. Had a project once where the city was adamant about setback rules until my engineer pointed out an exception in the code... suddenly it was fine.

On your question about departments - I’d say for me, planning is usually the slowest but zoning’s definitely the wildcard. One time zoning told me something was fine, then months later, a different staffer flagged it as an issue on final inspection. Ended up costing me weeks and a couple grand to fix. It’s wild how much depends on who’s at the desk that day.

I do think pushing back (politely) helps more than people expect. Even if you don’t win that round, sometimes they’ll at least explain their logic better or suggest workarounds you wouldn’t get otherwise.

Hang in there - half this game is just persistence and paperwork. If it was easy, everyone would do it...


Reply

Man, the “depends who’s at the desk” thing is way too real. I swear, sometimes I feel like I should bring donuts just to see if it helps my odds. Had a permit get bounced back once because the reviewer “didn’t like” the window placement - no code issue, just vibes, apparently. Ended up getting it through with a different staffer two weeks later, same plans. Persistence and paperwork, for sure... and maybe a little luck.


Reply

Had a permit get bounced back once because the reviewer “didn’t like” the window placement - no code issue, just vibes, apparently.

That’s frustrating but honestly, I’ve run into the same thing. One time, I had a lighting plan held up because the reviewer thought it was “too modern” for the neighborhood. No code violation, just personal taste. Ended up resubmitting with the exact same specs and it went through. It really does come down to who’s reviewing your file that day... Persistence is key, but sometimes it feels like a coin toss.


Reply
aarond55

Honestly, this is the kind of stuff that makes me want to pull my hair out. Here’s how I try to keep my sanity:

- Remind myself: reviewers are just people, and sometimes they’re just having a weird day.
- If it’s not a code issue, I’ll resubmit and cross my fingers. Sometimes it really is just luck.
- I keep a “rejection” folder for all the random reasons I’ve been denied - makes for good laughs later.
- If it’s costing me money, I’ll push back (nicely). Otherwise, I just roll with it.

Hang in there... you’re definitely not alone in this circus.


Reply
richardc25

Honestly, I’ve had my fair share of permit headaches too. Sometimes I wonder if the reviewers even read the whole application or just skim and stamp “no.” Your “rejection” folder idea is gold - wish I’d thought of that years ago. It really does feel like a circus some days, but you’re right, pushing back (nicely) when it matters is key. Ever notice how sometimes a different reviewer will approve the exact same thing? Makes you question the whole process...


Reply

Ever notice how sometimes a different reviewer will approve the exact same thing? Makes you question the whole process...

That’s been my experience more times than I’d like to admit. I had a deck project last year - first reviewer flagged it for “insufficient railing detail,” even though I’d attached the manufacturer’s specs and a diagram. Resubmitted with the exact same documents, just reordered them, and the next person signed off without a single comment. It’s frustrating, but I’ve learned to treat rejections as part of the process rather than a final answer.

I keep detailed notes on every submittal and response, which helps if I need to reference something later or escalate. Sometimes it’s just about persistence and making sure your application is as clear as possible. But yeah, it does feel arbitrary at times. The “rejection” folder idea is smart - wish I’d started that sooner too. It saves a lot of time when you’re trying to spot patterns in what gets flagged.


Reply
riverwalker

Honestly, I get what you’re saying, but I’m not sure it’s always as random as it feels. Sometimes I think it comes down to how each reviewer interprets the code, or maybe even just how much coffee they’ve had that day. I’ve had plans kicked back for tiny things, but when I called and asked for clarification, they actually walked me through what they wanted. Not saying the system’s perfect, but sometimes a quick phone call clears up more than just resubmitting.


Reply
Scroll to Top