The intake form is beautiful. Required fields, drag-and-drop document upload, online payment, a confirmation email with the permit number in the subject line. Meanwhile, down the hall, the fire marshal is replying to plan review comments from an email thread the planner can't see, and site plan version three just arrived with no record of which comments it answers. The applicant finished intake in four minutes. The application has been in review for six weeks. That ratio is the whole story: intake is minutes, review is weeks. The reviewer — the planner, the public works engineer, the fire marshal — is the person the system should be built around, because the reviewer is where the time goes.
Where the Six Weeks Actually Go
Walk any backlog and the open applications are not waiting on forms. They are waiting on routing — does this one need fire review, or just planning and public works, and in what order? They are waiting on comments: written in round one, answered in a resubmittal letter, half-resolved, then reopened in round two because nobody marked them closed. They are waiting on conditions of approval drafted by three different reviewers in three different documents, all of which have to land in one approval. And they are waiting on sign-offs. None of that happens at the counter. All of it happens in the queue, and most permitting software treats the queue as an afterthought behind the form.
What Reviewer-First Design Looks Like
Build for the person doing the review and the requirements stop being abstract:
- A queue that shows what's waiting on you, today. Not a list of every open application — the eleven where you are the holdup, oldest first.
- Comments pinned to the sheet they reference. A drainage comment belongs on sheet C-2 of version 2, not in paragraph four of a PDF letter. When version 3 arrives, the reviewer should see that comment, the applicant's response, and the revised sheet side by side.
- Resubmittals that show what changed. If round two is a full re-review of every sheet, every round costs the same as the first. That's how a three-round review becomes a five-month review.
- Visibility into who's holding. Four of five departments have signed off and nobody knows the fifth reviewer is on vacation until the applicant calls. The system should surface that on day two, not week three.
- Conditions drafted once, carried automatically into the approval. The classic failure: a condition appears in the staff report but never makes it into the approval letter, and six months later nobody can say whether it was required.
- A permanent record of every comment and response. Appeals and records requests will come. The reviewer who wrote the comment may not still work there when they do.
Applicants Don't Suffer From Bad Forms. They Suffer From Silence.
This is the part vendors miss. The applicant's actual questions are: where is my application, who has it, and what do they need from me? Those questions can only be answered if the system models the review itself — reviewers, rounds, comments, holds. A portal that says "In Review" for six weeks is not a status; it's a shrug. A beautiful portal in front of an opaque review process is a complaint generator with good typography.
How to Evaluate the Next System
The form is the front door. The review is the building. When a vendor demos permitting software, give the intake form ten minutes, then spend two hours on the reviewer's day: ask to see the queue, a comment tied to a plan sheet, a resubmittal comparison, and where a condition lives between the staff report and the approval letter. If the demo keeps steering back to the form, you've learned what the product is actually for.