What a paused shot clock actually means, and why most systems compute it wrong
The clock is a legal instrument, not a metric
In a growing number of states, a building department that misses its statutory review deadline does not merely look slow. Depending on the statute, the application may be deemed approved, the permit fee may have to be refunded in part, or the applicant may acquire a cause of action. The deadline is therefore not a service-level target your office sets. It is a date computed from the record, and someone may eventually ask you to prove how you computed it.
That proof requirement is what separates a compliance engine from a countdown. A countdown tells your staff how many days are left. A compliance engine can reconstruct, on any past date, which days counted, which did not, and why — and can show who paused the clock and on what basis.[1]
If your system cannot say which days it excluded and who excluded them, you do not have a shot-clock feature. You have a countdown with a legal opinion attached.
Where the arithmetic breaks
Almost every implementation handles the simple case correctly: an application is accepted, a timer counts business days, a permit issues. The failure modes cluster in four places, and all four appear in the corrections cycle.
- The pause boundary. Does the clock stop when the correction letter is generated, when it is sent, or when the applicant opens it? A day of difference, multiplied across a year of permits, is a pattern an attorney will find.
- Partial resubmittals. An applicant answers four of six items. Most systems either resume the clock as though the package were complete, or leave it paused indefinitely. Neither is what the statute says.
- Parallel departments. If Fire is waiting on the applicant and Zoning is still reviewing, the case clock and the department clock diverge. Systems that model one timer per case cannot represent this at all.
- Calendars. Business days depend on the jurisdiction's own holiday calendar, which changes by council action and is rarely modelled as data.
Four states, four definitions
The deadline, the unit of counting, and the consequence of missing it all vary. The table below is the summary; the full state-by-state guide carries the citation and the amendment history for each.
| State | Deadline | Source status |
|---|---|---|
| Florida | 30 business days to approve or issue a written correction notice, with fee-reduction consequences on delay | Cited · Fla. Stat. §553.792[2] |
| California | 15 business days to determine completeness, then 30 business days to review projects of 25 units or fewer and 60 for larger ones; a lapse is a Housing Accountability Act violation | Cited · Cal. Gov. Code §65913.3[4] |
| Georgia | 30 days to issue the permit or identify the non-complying plan features; on silence the application is approved as a matter of law | Cited · O.C.G.A. §8-2-26[5] |
| Texas | 45 days to grant or deny, or give written notice and take 30 more; on lapse the city may not collect permit fees and must refund them | Cited · Tex. Loc. Gov’t Code §214.904[6] |
Every row carries its citation, per our own rule: we publish a statutory figure only with the statute attached. Nothing on this site should be read as legal advice, and statutes move — verify against current text with your city attorney.
What to require of a vendor
Four requirements, written so that a demonstration either satisfies them or does not. They are worth putting in the RFP verbatim.
- Show a case whose clock paused and resumed twice, and reproduce the day count as it stood on a date I choose.
- Show a case where one department is waiting on the applicant while another is actively reviewing.
- Change the jurisdiction holiday calendar in front of me and show the affected deadlines recompute.
- Export the audit record of every pause, resume, and manual override for a single permit, with actor and reason.
Notes & sources
- On reconstruction as an evidentiary requirement rather than a reporting convenience — see the audit and tamper-evidence section of our security posture. ↩
- Fla. Stat. §553.792, building permit application review timeframes. Verify the current text and any amendment subsequent to publication of this piece. ↩
- Cycle-time figures in the data callout are drawn from a single illustrative case record, not from an aggregate. Aggregate figures appear in the cycle-time benchmark report. ↩
- Cal. Gov. Code §65913.3, post-entitlement phase permits, added by AB 2234 (2022). Applies to developments where at least two-thirds of the square footage is residential; failure to meet the timeframes is a violation of the Housing Accountability Act, Cal. Gov. Code §65589.5. Verify the current text and any subsequent amendment. ↩
- O.C.G.A. §8-2-26, local enforcement, inspectors, and building permits. The 30-day period is tolled where an application is rejected as incomplete, and later revisions carry an additional five business days. Verify the current text and any subsequent amendment. ↩
- Tex. Loc. Gov’t Code §214.904, time for issuance of a municipal building permit. The city may instead reach a written agreement with the applicant setting its own deadline. Verify the current text and any subsequent amendment. ↩