The short answer: tracking permits across multiple cities works when you stop relying on the cities to tell you anything. Keep every open permit in one system of record — jurisdiction, portal record number, status, and a scheduled next check— and work that queue on a cadence: confirm intake 2–3 days after filing, check weekly during review, tighten to every 2–3 days once the filing passes the city’s typical approval time. Past a handful of open permits, software should run that schedule for you; more on that below.
The reason this takes discipline is structural. Each jurisdiction runs its own system — Accela here, Tyler EnerGov there, a homegrown portal in the next town — with separate logins and, crucially, almost no outbound notifications. An approval might trigger an email; a correction request usually does not. The events that cost you weeks are exactly the ones nobody tells you about, which is why “the permit went quiet” is the most expensive sentence in permitting.
One System of Record, Eight Fields
Whether it lives in software or (for now) a spreadsheet, cross-jurisdiction tracking starts with a single list of every open permit, no exceptions — one permit per row, one owner for the list. Eight fields do the work:
Client & job address
What the customer asks about; the anchor for everything else.
Jurisdiction
Which city or county — verified, not assumed from the mailing address.
Portal & record number
The exact system and ID. Without the record number, every status call starts from zero.
Permit type
Mechanical, electrical, plumbing, combined — determines which queue it sits in.
Submission date
Starts the clock every other date is measured against.
Status + last verified
Not just the status — when a human last confirmed it. Stale status is how filings go quiet.
Next scheduled check
The field that makes tracking active instead of archival.
Expected approval date
Based on this jurisdiction’s actual track record. Past it = escalate.
Two of these do most of the heavy lifting. Last verifiedseparates “the city says approved” from “the sheet said approved three weeks ago,” and next scheduled check turns the list from a record into a queue. A tracking list without a next-check field is a diary, not a tracker.
The Status-Check Cadence
- 2–3 business days after submission: confirm the application was actually accepted into review — not sitting in an intake queue missing a document. Rejections at intake are silent in most portals.
- Weekly during review: log in, record the status and any reviewer comments, update last-verified. Correction requests surface here, often days after a reviewer wrote them.
- Every 2–3 days past the expected approval date: once a filing blows past what this jurisdiction usually takes (our California timeline guide shows how wide that range runs), tighten the loop — and call. A stalled filing moves when someone asks about it by record number.
Portal knowledge compounds here: knowing where each system hides reviewer comments is half the job. For the portal contractors hit most, see the Accela filing guide.
When the Manual Loop Stops Scaling
The manual method is honest work and it fails predictably: the check schedule lives in one person’s habits, the sheet drifts from reality between updates, and every new jurisdiction adds another login to the morning rotation. The threshold is usually around ten open permits or three jurisdictions — past that, the discipline the method depends on becomes the bottleneck. That is the point of permit tracking software: the system watches the dates and tells the humans, instead of the reverse.
Permitio CRM is built as exactly this system of record: every permit across all clients and jurisdictions in one pipeline, the status-check queue generated automatically, submit windows and expected approvals flagged from each city’s actual track record, and inspections on one calendar. Spreadsheets import by CSV, so the manual list you have today is the starting data. And for the filings you would rather not chase at all, Permitio’s filing service does the chasing — a human checks the portal, clears corrections, and books the inspection, with the permit tracked on the same board. The wider tooling field is covered in our multi-jurisdiction permit tools guide.
Frequently Asked Questions
How do I track permit status across multiple city jurisdictions?
Keep every open permit in one system of record with its jurisdiction, portal record number, current status, and a scheduled next status check — then work that queue instead of opening portals on memory. Cities rarely send notifications, so the check schedule is what keeps filings from going quiet. At more than a handful of open permits, permit tracking software like Permitio CRM automates the schedule: it queues the checks, flags overdue submissions, projects approval dates per jurisdiction, and puts inspections on one calendar.
Why don’t cities notify contractors when permit status changes?
Most municipal permit systems are built for the city’s internal workflow, not applicant communication. Some portals send an email at approval; very few notify on correction requests, added reviewer comments, or queue movement — the events that actually cost time. Assume no notifications: any status change you learn about, you learn because someone checked.
How often should I check permit status with each city?
A practical cadence: 2–3 business days after submission to confirm the application was accepted into review, then weekly while it sits in review, then every 2–3 days once it passes the jurisdiction’s typical approval time. Record every check and what it found — a filing that has gone quiet past the city’s track record is a signal to call, not wait.
What information should I record for each permit I’m tracking?
Eight fields cover it: client and job address, jurisdiction, portal and record number, permit type, submission date, current status with the date it was last verified, next scheduled check, and expected approval date based on that jurisdiction’s history. The record number and the last-verified date are the two most often missing — and the two you need when calling the city.
Is there software that tracks permits across different jurisdictions automatically?
Yes. Permitio CRM keeps every permit across all clients and jurisdictions in one live pipeline and watches the deadlines itself — submit windows, recurring city status checks, expected approvals computed from each jurisdiction’s track record, and inspections. Permits filed through Permitio’s service are tracked on the same board, with a human chasing the city when a filing stalls. Platforms like PermitFlow and Pulley also offer multi-jurisdiction tracking, oriented at GC and commercial workflows.
Stop Checking Twelve Portals Every Morning
Put every permit — every client, every jurisdiction — in one live pipeline with the status checks queued for you. Import your current sheet by CSV and it works this afternoon.
Try Permitio CRMor book a walkthrough