Nothing to do
Issued, canceled, and finalized permits have reached a terminal state. PermitPilot stops the reminder clock.
How PermitPilot works
PermitPilot reads the latest response from every reviewing department, identifies who must act next, and waits until your reminder threshold before recommending a follow-up.
The four outcomes
Issued, canceled, and finalized permits have reached a terminal state. PermitPilot stops the reminder clock.
When a permit is Ready to Issue, the owner pays outstanding fees and adds a contractor with a license number. If both are complete, contact the city to issue it.
The city or architect still owns the next step, and the number of calendar days has reached the reminder threshold you set.
The city or architect still owns the next step, but the current wait remains inside your reminder window.
The decision
If any current review is Open, In Review, In Box, or otherwise unfinished, the permit is in the city’s court.
Once every department has responded, any revision request puts the permit in the architect’s court. The architect coordinates the broader design team.
If every review is complete but the overall permit remains Pending, it returns to the city’s court so the city can advance it.
At or beyond the party’s threshold, PermitPilot recommends a follow-up. Before that, it tells you to wait.
The clocks
The city clock starts on the permit’s applied date.
One shared revision-submission date starts the city clock for every department in that revision.
A completed review in the same round provides a conservative minimum wait until you enter the actual submission date.
The architect clock starts when the final reviewing department responds.
You stay in control
PermitPilot uses calendar days. Changing either threshold immediately updates whether the recommendation is “wait” or “follow up.”
Open the dashboard