/4 min read/Promatic
The six reasons permits actually get kicked back
Plan-check corrections are boring and repetitive, which is good news — almost every rejection we see comes from one of six causes, and five of them are avoidable before you submit.
A rejected permit does not feel like a paperwork problem. It feels like a scheduling problem: the crew was booked, the equipment was ordered, and now everything slides by a week because a reviewer wrote three lines in a portal.
The useful thing about corrections is how repetitive they are. Across the residential permits we file, the overwhelming majority of first-round rejections come down to six causes. Five of them you can eliminate before you ever hit submit.
1. The scope on the application does not match the scope on the plans
This is the single most common one, and it is almost always an artefact of speed. The application says "replace furnace." The equipment cut sheet attached to it is a heat pump. Or the application lists mechanical only, and the plan set shows a new circuit and a disconnect.
Reviewers are not being difficult here. They are matching the described work to the work shown, and when the two disagree they cannot tell which one is going to be built.
The fix: write the scope from the plan set, not from the sales order. If the job includes electrical work, say so on the application even when the electrical is trivial. Adding a trade to an application is free. Adding it after a rejection costs a round trip.
2. Missing contractor registration in that jurisdiction
A state licence is not the same as being registered with a city. Plenty of jurisdictions maintain their own contractor registry, want a current certificate of insurance on file, and will reject an application from an unregistered contractor without reading past the first field.
The frustrating part is that this has nothing to do with the job. It is an account problem masquerading as a permit problem, and it typically only bites you the first time you work in a new city.
The fix: check registration before the application, not after the rejection. This is exactly the kind of thing worth recording per jurisdiction, because the answer never changes and you only have to find it once.
3. Energy compliance forms are absent or unsigned
Depending on the state and the scope, a change-out can pull in energy code documentation — compliance forms, load calculations, duct leakage testing, or a certificate that has to be signed by someone specific.
Two failure modes here. The first is not including the form at all. The second, more annoying one, is including it unsigned or signed by the wrong party. A form that needs a HERS rater's signature is not satisfied by the contractor's.
The fix: treat the energy documentation as part of the submittal package, not as an attachment you can send later. If it needs a third-party signature, start it when you book the job, not when you file.
4. The property owner information is wrong
Permits are issued against a property, and jurisdictions validate the owner name and parcel against their own records. If the homeowner bought the house last year and the county record has not caught up, or the property is held in a trust, or the name on your contract is a spouse who is not on title, the application gets flagged.
The fix: pull the owner name from the assessor record rather than from the customer. Where the two disagree, that is a conversation to have before submitting, not a correction to receive afterwards.
5. Illegible or incomplete attachments
A photo of a nameplate taken at an angle, in shadow, with a thumb over the model number. A plan set exported at a resolution where the dimensions are unreadable. A site plan without a north arrow or a scale.
Reviewers reject what they cannot read. This is the least interesting cause of rejection and one of the most common.
The fix: look at every attachment at 100% before it goes out. If you cannot read the model number, neither can the reviewer.
6. The reviewer wants something the code does not obviously require
This is the one you cannot eliminate. Every jurisdiction has local amendments, house preferences, and reviewers with particular concerns. One city wants seismic strapping details on a water heater swap. Another wants a specific clearance dimension called out even when the equipment listing covers it.
There is no way to anticipate all of these from the code alone. The only defence is a record: once a jurisdiction asks for something, it will ask again on the next one.
The fix: write it down, per jurisdiction, and apply it pre-emptively next time. This is the part of permitting that actually compounds, and it is the reason a second permit in a city should be meaningfully faster than the first.
What this means for scheduling
If you take nothing else from this: a first-round rejection is not a random event. It has a cause, that cause is usually one of six things, and five of them are checkable in the ten minutes before you submit.
The reason we price corrections inside a flat fee rather than billing them separately is precisely this. If corrections were a revenue line, there would be no incentive to run the ten-minute check. Charging one fee regardless of how many rounds it takes puts the cost of a sloppy submittal on us, which is the only arrangement where our incentives and yours actually agree.