What My Dad Said When I Told Him the Permit Got Rejected

What My Dad Said When I Told Him the Permit Got Rejected

“Did you talk to anyone before you submitted?”

I hadn’t. And the look on his face told me he already knew that.

My dad spent thirty years in commercial construction. He’s seen projects go sideways in every possible way. And according to him the single most common reason first-time builders run into trouble isn’t money or contractors or bad weather. It’s site development permits. Specifically, it’s people who don’t understand them treating them like a formality.

“They’re not a formality,” he told me. Twice. Possibly three times.

He was right.

What I Submitted and Why It Came Back

The rejection letter used language I had to read four times before I understood it. Something about inadequate stormwater documentation and insufficient demonstration of compliance with the county’s impervious surface thresholds.

Plain English version: my site plan didn’t properly show where rainwater would go after my proposed structure covered a significant portion of the lot. The county needed to know that my development wouldn’t contribute to runoff problems downstream. My application didn’t answer that question clearly enough.

Site development permits exist precisely for situations like this. Someone who knows what downstream drainage problems actually cost — in infrastructure damage, in flooded properties, in public liability — designed a review process that catches these issues early. My submission skipped past that concern without addressing it.

Resubmission took three weeks to prepare and another five weeks to review. Eight weeks minimum wage gone from my timeline because I didn’t talk to anyone before I submitted.

The Conversation I Should Have Had

Most planning departments will meet with you before you submit anything formal. A pre-application meeting. Usually free. Sometimes required. Always useful.

In that meeting a planner looks at your project concept and tells you what they’ll need to approve it. They flag the things that commonly cause problems. They tell you which departments will review your application and what each one is specifically looking at. They give you a realistic timeline instead of the optimistic one you’ve been telling your contractor.

For site development permits specifically this conversation matters more than most people realize. Because the documentation requirements aren’t always obvious from the application checklist alone. Stormwater calculations. Grading plans. Erosion control details. Tree removal assessments. Utility conflict reports. Depending on your site and your project some of these matter a lot and some don’t apply at all. A pre-application meeting tells you which is which.

I skipped that meeting because I thought I understood the process. My dad still brings it up occasionally.

The Part About Timing

Here’s something that genuinely surprised me. Site development permits and building permits operate on separate tracks. Getting one doesn’t automatically advance the other. They can run concurrently in some jurisdictions. In others one has to clear before the other can even be submitted.

Not knowing which situation applies to your project and your location can cost you months. Not days. Months.

The contractor I’d planned to use had a window available that fit my original timeline perfectly. By the time the site development permits cleared that window was gone. He’d taken other projects. I went on a waiting list. Waiting lists have their own timelines.

By the time everything aligned and actual construction started I was eleven months past my original target date. Eleven months.

What I Tell People Now

Get the pre-application meeting. Even if you think you don’t need it. Especially if you think you don’t need it.

Find out specifically what your project triggers in your specific jurisdiction. Not what a similar project required somewhere else. Your site. Your county. Your project type. The variation between neighboring municipalities is larger than most people expect.

Hire a civil engineer before you think you need one. Their job is knowing exactly what site development permits reviewers want to see and preparing documents that don’t come back for corrections.

And build the permit timeline into your schedule first. Before contractor availability. Before material lead times. Before everything else. Because everything else waits for site development permits. Not the other way around.

My dad said all of this to me before I started. I nodded and didn’t really listen.

Expensive nod.