Search permit management and almost everything you find is a software company explaining why you need software. Some of it is good. Almost none of it says the thing a buyer most needs to hear, which is that tracking permits and getting permits is not the same job.
Get a free quote
What the term actually means
Pulling a permit is a task with a beginning and an end. Permit management is the function that surrounds it and does not end until the last permit on the job is closed.
Concretely, it covers researching what each jurisdiction requires, assembling and submitting packages, verifying licensing and registration before filing, tracking status across every permit and every reviewing department, routing returned comments to whoever can answer them, following up when a file goes quiet, scheduling inspections, and closing every permit out so the building permit can final.
Pulling a permit is a task. Permit management is what happens on the other forty.
The distinction matters because the two halves fail differently. The front half — research, assembly, filing — fails loudly and immediately. You get a rejection. The back half fails silently: a file sitting in a queue nobody checked, a trade permit nobody closed, an inspection that was never rescheduled after a fail.
Recognize the back half? That is most of what we do. Request a free quote.
What has to be tracked per permit
"Status" is not one field, which is why permit tracking in a spreadsheet degrades faster than people expect. Each permit carries:
- Jurisdiction and portal, with its own login, submission format and status vocabulary
- The license it was pulled under, and whether that license and registration are still current
- Fee status — calculated, invoiced, paid, and whether issuance is waiting on it
- Review status per department, not per permit, because building, fire, zoning and public works move independently
- Outstanding comments and their owner, split between administrative items and technical ones only the design professional can answer
- Inspection milestones and results, including any that failed and were never rescheduled
- Expiration and extension dates, because a permit pulled early and then idled can go void before that trade returns
Now multiply. A job with a building permit plus electrical, plumbing and mechanical is four permits, and trade permits file separately with their own licensing and inspections. Ten live jobs is forty permits, each carrying the seven attributes above.
Tracking more of those than you can comfortably see? Tell us your volume and we will take the tracking off you.
Where it breaks, and it is not permit count
The intuitive answer is volume. The real answer is jurisdiction count, and it is worth being precise about why.
Forty permits in one county is a routine. The forms are the same, the portal is the same, the fee basis is the same, the reviewers are the same, and a person learns it once. Ten permits across four counties is four sets of everything — four portals with four logins, four fee bases, four registration regimes, four status vocabularies where "in review" means something different in each.
The cost is not filing the permits. It is maintaining current knowledge of every jurisdiction you file in.
Three failure points cluster there, and all three are back-half failures:
The file nobody checked. Portals rarely notify. A submittal can sit in an intake queue for weeks with nothing wrong and nobody asking. We cover what active follow-up actually does, and does not do, in permit runner vs permit expediter.
The trade permit nobody closed. The building permit cannot final until the permits beneath it have. This surfaces at the end of the job, when there is no slack left.
The deadline nobody was watching. Several states attach statutory windows to correction responses — under Fla. Stat. § 553.792, an applicant has 10 business days to submit revisions after written notice, and missing it results in denial rather than delay. We set those out in how long does a building permit take.
Running permits across several jurisdictions? That is the case where this stops being a spreadsheet problem. We prepare, file, track and close out in all 50 states across seven trades. Check requirements in the county permit guides, see what we cover on the Alliance Permitting home page, or tell us your markets and volume.
What permit management software does, and what it does not
Permit management software is genuinely useful and we are not going to pretend otherwise. It centralizes documents, gives a team one source of truth, standardizes process by jurisdiction, and puts status in one view instead of eight browser tabs.
The question worth asking before you buy is narrower than "software or service." It is whether the platform files, and whether it files where you work.
The category splits, and the split is not obvious from the marketing
In a September 2026 review of the published comparison content and vendor product pages in this category, the platforms sort into two groups.
Mercator's roundup of permit tracking tools states it directly: most permit tracking platforms are built to organize, monitor and manage the submission process but do not handle the actual filing — while noting that some specialized services do. Projul's 2026 roundup describes one platform as focused on tracking and management "without trying to handle the actual submission process."
Others clearly do file. PermitFlow's own product page describes submitting, tracking and pulling permits in one platform, and Projul credits it with connecting directly to permitting offices in many major metro areas and submitting applications electronically on the customer's behalf.
So the real question is not software versus service. It is: does this one file, and does it file in my jurisdictions?
The limit that matters most
Where submission automation exists, it is generally bounded by supported jurisdictions. Projul's guidance on the strongest submission platform in its roundup is explicitly scoped to "high-volume permit work in supported jurisdictions," and to major metro areas.
That is a reasonable engineering constraint — building and maintaining an integration against a municipal portal is real work, and there are roughly 20,100 permit-issuing places nationally. But it has a direct consequence for a buyer. A platform that files beautifully in six metros does nothing for the county job that is actually holding your schedule, and the jurisdictions most likely to be unsupported are the small ones where the process is least standardized and the manual effort is highest.
Three questions that separate the options, whatever a platform calls itself:
- Does it submit, or does it track a submission I make? Both are legitimate products. They are not the same purchase.
- Which jurisdictions does it submit in, by name? Ask for the list, then check it against your actual pipeline rather than your biggest market.
- What happens in the jurisdictions it does not cover? This is usually where the honest answer is "your team does it," which is fine as long as you knew.
Which reframes the decision. Software is the right purchase when you have the people and the jurisdiction knowledge and what you lack is visibility. It is the wrong purchase when the constraint is that nobody has time to chase four portals on a Tuesday — because a dashboard showing four stalled permits is not the same as four permits that are not stalled.
Bought visibility and still short on hands? We file in all 50 states, with no supported-jurisdiction list. Request a free quote or call 1-855-478-4290.
Multi-site is a different problem
Rollouts and multi-location programs get treated as one process repeated. They are not, and this is the part of permit management with the widest gap between how it is planned and how it runs.
Design is repeatable. Permitting is not.
The same prototype produces a different filing in every market. Five things vary per site even when the drawings do not.
1. The submittal package itself
Each jurisdiction publishes its own required document set, its own forms on its own current versions, and its own rules about what must be sealed. A prototype package assembled for one market is a starting point elsewhere, not a submission.
2. Which trades pull separately, and under whose license
Trade permits file on their own in most places, but the rules differ — some jurisdictions require a master permit before any trade sub-permit can be obtained, and the permit attaches to the trade contractor's license rather than the GC's. Your national electrical sub needs separate registration in each market, and that registration is a prerequisite to filing rather than part of it. We cover the structure in who pulls the electrical permit.
3. Filing structure and phasing
Whether the work files as a single permit, a master permit with subsidiaries, or a stand-alone trade permit changes by jurisdiction and by scope. Where the schedule demands it, some jurisdictions issue foundation-only or early-start permits so site work can begin while the full package is still in review — and some do not. That is a per-market scheduling variable, not a program-wide one. More in commercial building permits explained.
4. Review timing, and whether any clock applies at all
A handful of states set statutory review deadlines with real remedies; most do not. Two sites in a twelve-market rollout can have legally enforceable turnaround on one and nothing but local practice on the other. We set out which states have clocks in how long does a building permit take.
5. Landlord and applicant-of-record coordination
On tenant work, who is named as applicant varies with the lease and the jurisdiction, and many leases require landlord review and written approval before filing. Sequencing that against the filing date is pure coordination with no technical content, and it delays more multi-site programs than any code issue.
What that does to a schedule
Two consequences follow, and both are commonly mispriced.
A per-site average is wrong at both ends. Some sites clear faster than the average and some take twice it. The fast ones bank no value, because the program opens when the slowest site opens. Planning on the mean means planning to miss.
Knowledge does not compound the way it does in one market. In a single jurisdiction the tenth permit is genuinely easier than the first. Across a rollout, the twelfth jurisdiction is as unfamiliar as the first, because nothing learned in market three transfers to market twelve.
What does compound is the administrative pattern — the document discipline, the licensing checks before filing, the tracking cadence, the habit of confirming receipt rather than assuming it. That is the part worth standardizing across a program even when nothing else can be, and it is the part that survives moving to a new market.
Running a multi-site program? This is the case we are built for, and there is no supported-jurisdiction list. Tell us the markets and the schedule.
Spreadsheet, software, or outsourced
Three real options, and they solve different problems.
| Option | What it gives you | Fits when |
|---|---|---|
| Spreadsheet | Zero cost, total flexibility, and a record only as good as whoever last updated it. | One or two jurisdictions, a modest number of live permits, and one person who genuinely owns it. |
| Software | Visibility, a shared source of truth, document centralization, and process standardized per jurisdiction. Usually not submission. | You have the people and the jurisdiction knowledge, and the constraint is that nobody can see the whole picture. |
| Outsourced filing | The work done rather than displayed — research, assembly, filing, tracking, follow-up, comment routing, closeout. | Jurisdiction count is rising, or permitting is spread across project managers who each do a little of it. |
The honest note on that last row: outsourcing is not automatically right. If you work one market consistently and someone owns it properly, keeping it in-house is the better answer and we will say so. The failure mode we see most is not too little software — it is permitting distributed across four project managers as a background task, where nobody owns it and every gap is somebody else's.
Not sure which row you are in? Tell us your jurisdiction count and who owns permitting today, and we will tell you straight. Request a free quote.
How we run it
Plainly, since the article argues the term is used loosely.
We take the function rather than the task. For every permit on a job: research what that jurisdiction requires, assemble the package on current forms, verify licensing and registration before filing rather than at filing, calculate and pay fees, submit to the correct office, track each reviewing department separately, route returned comments to whoever must answer them, follow up when a file goes quiet, and watch the closeout sequence so no trade permit is left open.
What we do not do is review plans, interpret code, determine whether a project needs a permit, perform inspections, or influence review decisions. Those belong to your design professional and the building official. The full scope is in what permit expediting actually covers, and what it costs in how much does a permit expediter cost.
Want the function rather than another dashboard? Request a free quote and we will scope it against your actual markets.
Permit management FAQ
What is permit management in construction?
The ongoing work of getting permits filed correctly and keeping them moving to closeout across a portfolio of projects. It covers researching jurisdiction requirements, assembling and submitting packages, tracking status across every permit and every reviewing department, routing returned comments, following up when a file goes quiet, scheduling inspections, and closing out every permit so the building permit can final. Pulling a single permit is a task. Permit management is the function around it.
Does permit management software submit permits?
Some do and some do not, and it is the first thing to establish. Published comparisons of the category note that most permit tracking platforms organize and monitor the submission process without handling the actual filing, while some specialized platforms submit applications electronically on the customer's behalf. Where submission exists it is generally limited to supported jurisdictions and major metro areas, so ask for the covered list by name and check it against your real pipeline rather than your biggest market.
What has to be tracked for each permit?
More than a status field. Each permit carries its jurisdiction and portal, the license it was pulled under, the fee and whether it is paid, current review status per reviewing department, any outstanding comments and who owns each one, inspection milestones and results, and expiration or extension dates. On a job with a building permit plus three trade permits, that is four of everything.
When does permit management stop working in a spreadsheet?
Usually at the point where jurisdiction count rises rather than permit count. A spreadsheet handles many permits in one jurisdiction reasonably well because the process is uniform. It degrades quickly across several jurisdictions, because each has its own forms, portals, status vocabulary, fee basis and registration requirements, and none of that fits in a status column.
What is different about permit management for multi-site projects?
The same scope produces different filings in every market. A rollout that is identical in design will face different submittal requirements, different portals, different trade permit rules and different review timelines at each location. The work is not repeating one process across sites, it is running a different process at each site toward the same opening date.
Should permit management be in-house or outsourced?
It depends on jurisdiction count and on whether someone genuinely owns permitting rather than fitting it around other duties. One or two jurisdictions with a dedicated owner works in-house. Several jurisdictions, or permitting spread across project managers who each do a little of it, is where the failures cluster and where outsourcing usually pays for itself.
Current as of September 2026. Software capabilities change and vendors add submission features over time — confirm what any platform actually does before buying on the strength of a category description, including this one. This is general information about administrative process, not legal advice.