One permit queue across three departments
Intake is at the counter, plan review is in email, and inspections are in a spreadsheet. Nobody can say where a permit actually is without ringing someone.
For a permit technician and the departments they chase.
One permit queue across three departments
Illustrative sample. Not a client record.
| Case | Item | Status |
|---|---|---|
| B-2026-0441 | Residential addition | At intake |
| B-2026-0442 | Commercial fit-out Held 14 days at Fire. Fire has held 14 of the last 30 past target — this is the pattern, not the case. | At intake |
| B-2026-0443 | Sign permit | At intake |
| B-2026-0444 | Change of use Waiting on a zoning determination nobody was assigned. It has sat unowned for 8 days. | At intake |
| B-2026-0445 | Residential remodel | At intake |
| B-2026-0446 | Demolition | At intake |
Two cases are stuck and neither is stuck for a reason the applicant caused. One is a department running consistently past target; the other has no owner at all. Both are visible here before either becomes a complaint at a council meeting.
Today the applicant finds out by telephoning, and the pattern at Fire is only visible to whoever happens to notice it.
This is a demonstration, not a product. Every record above is invented. The point is not the table — it is that the exception is named, with the field at fault and what it usually means, rather than returned as a code somebody has to decode.
What we would build for you runs on your data, in your environment, and looks like your process rather than this one. More on this category: Permitting and licensing.
The other three
- State reporting, validated before submission A district data manager in a submission window
- One number, from three systems that disagree A finance director assembling a board packet
- Public records requests, against the clock A city secretary or records officer