Built for building and planning departments
Every application checked against your code.
Every review clock in view.
Permitting and Inspections takes applications from residents and contractors online and checks each one against the checklists and code sections your jurisdiction has adopted before it enters review. Complete applications are routed to building, planning, fire, and engineering at once, comments come back on one record, and inspections are scheduled and resulted from the field. Every approval is signed by a named reviewer, and the statutory review clock is shown on every application.
- Online applications
- Completeness checked on intake
- Multi-department plan review
- Inspections resulted from the field
What it changes for your office
Most permit delays start before review begins.
An application that arrives without a site plan, a stamped drawing, or the right fee does not get reviewed. It gets returned, often after it has waited in line for days. Permitting and Inspections checks each application against your own requirements the moment it is submitted, so the reviewers start with complete files and the applicant learns what is missing while it is still easy to fix.
For the building official
You see every application by stage, by reviewer, and by how many days remain on its review clock. Applications that are close to their deadline are raised before the deadline passes, and every approval, condition, and denial is signed by the reviewer who made it and tied to the code section it relied on.
For plan reviewers and inspectors
Reviewers receive complete applications with the checklist already worked, the code sections that apply, and the comments from other departments on the same record. Inspectors see their route for the day on a tablet, record results and corrections on site, and attach photos that stay with the permit.
For residents and contractors
Applicants apply online, learn on submission what is missing, pay fees in the same place, and request inspections without calling the counter. They can see where the application stands, which department has it, and what the city needs from them next.
The product
Autessa Permitting and Inspections, what your team works in.
Completeness Review
Your submittal checklists and the code sections behind them are encoded once. Each application is checked against the checklist for its permit type, and every item is marked as met, missing, or needing a reviewer's judgment. The applicant receives a written list of what is missing. Staff confirm the determination before the application is accepted or returned, and the review clock starts only on acceptance.
Plan Review Routing
Accepted applications are routed to every department whose review the permit type requires, at the same time rather than one after another. Each reviewer comments against a code section, comments are combined into one letter for the applicant, and resubmittals return to the reviewers who raised the issues. The review clock pauses and resumes according to the rules your jurisdiction follows.
Inspections
Applicants request inspections online for the next available day. Inspectors receive a route grouped by area, and on site they record pass, partial, or fail against the inspection type, with the code section for each correction and photos attached. A failed item creates a reinspection request, and the next inspection on the permit cannot be scheduled until the prior one has passed.
Clocks and Workload
Every application shows where it sits against the review period your ordinance and your state's rules set, and the department view shows which reviewers are carrying the applications closest to their deadlines. The building official can reassign work before a clock runs out, and the monthly report shows how many applications were completed within their review period and how many inspections were performed within a day of the request.
In practice
The details that decide whether a permit decision holds up.
Three of them, handled the way a careful building department already handles them: which code applies, who makes the call, and when the clock runs.
On the code
Your adopted code is the only standard it applies
Completeness checks and review comments rely on the code editions, local amendments, and checklists your jurisdiction has adopted. Every finding names the section it relies on, and when your council adopts a new edition, applications submitted under the prior edition continue to be reviewed against it.
On decisions
A reviewer signs every approval and every denial
The system checks, drafts, and routes. It does not approve a permit, waive a requirement, or issue a certificate of occupancy. Each of those is done by a named reviewer, inspector, or official, and the record shows who it was and what they relied on.
On the review clock
The clock follows your rules, not the inbox
The review period starts when an application is accepted as complete, pauses when comments go back to the applicant, and resumes on resubmittal, according to the timelines your ordinance and your state set. Each pause and resume is recorded with its reason, so the elapsed time can be shown day by day.
Below: the record a building official reviews before signing a certificate of occupancy.
Defensibility
When a permit decision is challenged, the record already answers it.
Permit decisions are questioned from every side. An applicant asks why the city took so long. A neighbor asks why a variance was not required. An appeals board asks which code section a denial relied on. The answers depend on what the department can show about when each step happened and who decided it.
Permitting and Inspections keeps that record as the work happens. Every completeness finding records the checklist item and code section. Every review comment records the reviewer and the section it cites. Every pause in the review clock records its reason. Every inspection result records the inspector, the photos, and the corrections. The log is append-only, so the record you produce for an appeal is the record that was made at the time.
One application, from submission to issued permit, with every clock event shown.
The same record across a quarter, ready for the council and the annual report.
See it check your own applications.
Bring your submittal checklists, your adopted code and local amendments, and a handful of recent applications. We will show your permit technicians and reviewers how each application would have been checked on intake, routed for review, and tracked against its review clock.
FAQ
Questions we are glad to answer.
Does it approve permits on its own?+
No. The system checks completeness, drafts comments, and routes work. Every approval, denial, condition, inspection result, and certificate of occupancy is signed by a named reviewer, inspector, or official.
Which code does it check against?+
The code editions, local amendments, and submittal checklists your jurisdiction has adopted. Every finding names the section it relied on, and applications stay under the edition in effect when they were submitted.
How does it handle review deadlines?+
We configure the review periods from your ordinance and your state's rules for each permit type, including when the clock starts, pauses, and resumes. Each application shows its elapsed days, and the building official sees which applications are close to their deadline.
Can inspectors use it in the field?+
Yes. Inspectors see their route on a tablet or phone, record results and corrections against code sections, attach photos, and post results from the site. Applicants and contractors are notified of results and reinspection requests right away.
Where does our data go?+
Permitting and Inspections runs in your own Autessa Private Cloud, an environment your jurisdiction controls, with keys your jurisdiction holds. Applications, plans, and inspection records are not used to train models for anyone else.