Most Common Permit Rejections & Fixes

Almost always for one of three reasons: missing site information, drawings that contradict each other from sheet to sheet, or missing structural and energy documentation. Building departments run a completeness check before technical review, so if a key piece is absent or the numbers do not agree, the file comes back with comments. It is rarely “your project is bad” – it is “I can’t verify this from what you sent.” Submit a complete, consistent package and you avoid the large majority of rejections. The reviewer is refusing to guess, not being difficult.

A weak or missing site plan is the most common, closely followed by drawings that do not match – a ceiling height, window size, or roof pitch that reads differently on the plan than on the elevation or section. Reviewers cannot approve numbers that disagree, so any contradiction is an automatic kickback. The fix is a clear site plan with real dimensions (no “approx”) and one coordinated drawing set where every sheet tells the same story. Most other kickbacks – foundation detail, structural proof, energy docs – are variations on “show me, don’t make me guess.”

It means the same dimension or detail shows up differently in different places – the floor plan says one ceiling height, the section says another; the elevation shows a window the schedule does not list; the roof pitch differs page to page. A reviewer cannot tell which is correct, so the file gets returned. This usually happens when someone changes one sheet without updating the others. The cure is to keep a single source-of-truth set and propagate every change everywhere it appears, then resubmit the whole coordinated package at once rather than a few revised pages.

Turn it into a checklist. Copy each comment into its own row, note exactly which sheet you will revise to satisfy it, make the change, and use revision clouds with a revision date so it is obvious to the reviewer. The critical step most people miss: if you fix something on one sheet, update every other sheet it touches, because the number-one reason resubmissions get re-kicked is the same issue still appearing elsewhere. Then resubmit as one clean coordinated set. The goal is to resubmit once, not five times – a complete, consistent response is what gets a file closed out.

It depends on how fast you turn the comments around and whether your resubmission is actually complete. A clean, one-and-done resubmission might add a week or two; a file that bounces repeatedly because each fix introduces a new inconsistency can add months. The review clock effectively pauses while the file is in your court, so most of the delay is on the applicant’s side. That is why a complete, consistent first submission – or a pre-check before you file – is the cheapest time you will ever buy on a build.

You cannot guarantee zero comments, but you can eliminate the predictable ones, which are the vast majority. Confirm zoning before you draw, submit a dimensioned site plan, keep one coordinated set so the sheets never disagree, specify the foundation, include structural proof where the design leaves prescriptive limits, align the energy documents with the drawings, sort rural servicing and any outside-agency clearance early, and complete the admin items exactly as the municipality requires. Do that and you have closed off all eight common kickbacks. Pre-checking the package against the town’s completeness standard before filing is the surest way to a clean review.

They will tell you what is deficient, but they are not your design team – they review what you submit, they do not draw or correct it for you. The comment letter identifies the issues; resolving them is on you and your designer or engineer. Staff can clarify what a comment means if you ask politely, but expecting them to design the fix is the wrong move and slows everyone down. If you do not want to manage the back-and-forth, that is where having a builder or designer pre-check and assemble the package pays for itself.