Permitting software gets sold by showing you a permit. A clean intake form, a record with a number, a printable document at the end. The demo is twenty minutes of intake and thirty seconds of everything else. But the permit is the output — what falls out the end when everything went right. The workflow is everything else, and the workflow is where these systems live or die.
What Sits Between Application and Permit
Between application received and permit issued is the actual job, and most of it is the part that bites:
- Completeness review — the application that can't even be reviewed yet, and the completeness letter telling the applicant why
- Corrections and resubmittals — site plan v3, and which comments it actually answered
- Routing to multiple reviewers, each with their own queue and their own idea of what done means
- Fees — calculated, invoiced, adjusted when the valuation changes, occasionally refunded
- Inspections — scheduled, failed, rescheduled, failed again
- Closeout — the step every backlog report is secretly about
A system that models the permit but not these steps hasn't modeled the work. It's modeled the souvenir.
The States With No Status
The in-between states are the heart of the problem. An application is complete, planning has signed off, and it's been sitting eleven days waiting on the public works reviewer. What status is that? Most systems say "in review," which is true and useless. Another permit is approved but unpaid — the applicant got the good news and went quiet. Another is issued and on its third failed framing inspection, which means the project is in trouble but the permit record looks fine. And then there are the permits marked closed that were never finaled — no final inspection, no certificate of occupancy — that surface years later when a title company calls during a home sale and a clerk has to reconstruct what happened from a microfiched inspection card.
Every one of those is a real state of the work. If the software has no place to put them, staff put them somewhere else. Usually it's specific: the counter clerk keeps the real status list taped to the monitor, because the system can't answer the question people walk up and ask. At that point the official system is a filing cabinet, and the actual workflow has gone underground where no report, no audit, and no new hire can find it.
Closeout deserves its own sentence, because it's the failure nobody budgets for. Permits don't close themselves. An issued permit with no final inspection isn't done — it's a liability with a number on it, and it will wait patiently until the property changes hands.
One Question
Here is the whole evaluation, compressed: pick any open application and ask the system, where is this stuck, and who does it wait on? Not what stage is it in — who is it waiting on, and since when. If the system can answer that for every open application without anyone checking email or walking down the hall, it models the workflow. If the answer requires a meeting, you've bought a document generator.
Run that test before signing anything. Agencies don't have a permit problem; they have a throughput problem and a closeout problem. The permit is a document. The workflow is the program. Buy software for the program, and make the vendor answer the stuck question live, on their own demo data.