Georgia's new shot clock law, SB 447, sets firm review deadlines for permits. Many planning departments already run short of staff, and the law brings no new staff or budget. Clariti builds permitting and community development software for local governments. Teams can meet these deadlines with the staff they have by fixing problems before a file reaches review. Mark Wedge, who spent eight years on the Chamblee City Council before joining Clariti, has heard from developers whose permits sat for weeks.
The clock runs out at the completeness check. Staff who run out of time face two poor choices. They can send a rushed notice that may be incomplete or wrong, or let the file move on before anyone reviews it.
Catching the problem before filing keeps the queue clean. When staff hunt down missing documents after submission, each correction round adds to the review cycle. The pre-check runs before formal submission, so the applicant's time in the tool does not count against the review clock.
Reviewers make the call. They can accept, modify, or override any finding. The tool flags issues in plain language and shows a finding only when it is confident in it. AI does not replace licensed judgment, because permit decisions carry public safety stakes.
Clariti’s CivCheck shows a jurisdiction's own amendments alongside state standards. Reviewers work from the most current adopted ordinances without constant manual lookup.
They look only at what changed. CivCheck highlights only what changed between revisions.
The applicant starts with an address, and the tool pulls GIS and zoning data for that parcel. A residential lot shows its own setback and height limits. The applicant describes the project and uploads the plan set. The tool confirms each document belongs to the right project, so a geotech study for a different address gets flagged.
Each code check explains why staff look for the item, gives a time estimate, and links to the code book. CivCheck highlights what it finds on the plans. If it cannot find an item, such as a smoke alarm distance, the applicant supplies the measurement and the tool checks it.
Before submission, the applicant sees a readiness score. Some jurisdictions require a set level before a file can go in. Applicants can override an item, but they must state a reason.
Intake reviewers confirm highlights in one pass. CivCheck jumps to the scale bar, north arrow, and street names it located, so staff confirm or reject each one in turn instead of scrolling a long plan set.
Building and zoning reviewers check the calculations. The sample configuration shows the measured floor area ratio, then reviewers can re-measure, and the CivCheck sends a correction report back to the applicant.
Plan reviewers often answer the same check in different ways. A single digital checklist gives applicants and staff one method to follow.
No. Homeowners see the document and intake checks. Design professionals also see the code compliance checks, since they are better placed to supply the information those checks need.
A residential rollout takes months, not years, when a department's checklists are already in good order. Many departments start with document and intake review and add code compliance later. Teams with less organized checklists need longer to agree on how each check should work, and the jurisdiction's size also shapes the timeline.
It runs alone or connects to your permit system of record. Standalone, applicants get an ID and a watermarked project summary to show staff. Which connection fits depends on the system your city uses, so start with the integration list for that system.
Answer three questions with your own numbers before you talk to a vendor. Where does this save reviewer time? How does it help us meet the clock? How will applicants experience it?
Book a demo to see the applicant and staff views for yourself. Then watch the full session, including the live demonstration here.