Scheduled, inspected, finaled.
Permitect Inspect runs the permit after approval. Applicants schedule inspections online under the city’s own cutoffs and windows, the city assigns the inspector, results land the same day, and every failed item comes back with the code section behind it. When the last required inspection passes, the permit is finaled — closeout letter and all.
Pick a date. We handle the rules.
Cutoff times, AM/PM windows, advance-notice rules, daily capacity, holiday calendars — every city’s scheduling policy is configuration the city sets once, enforced everywhere the applicant looks. Full days simply don’t appear in the picker, and an inspection that isn’t ready to request yet says why, right on the row.
One scheduling experience across every Permitect city, no matter how differently each one runs its counter.
One board for the day’s inspections.
Requests come in; the dispatcher confirms, assigns, and balances the day — every inspector’s stops, every unassigned visit, capacity in plain view.
Checklist, photos, result. Done from the driveway.
A mobile-first surface built for the tailgate, not the desk: today’s stops, a per-stop checklist tied to the code, photo capture, and one-tap results — pass, partial, fail, not ready, no access.
Failed items carry over to the reinspection automatically, so nothing gets re-litigated.
Guard measures 34″ at the east rail — KZC-adopted IRC R312.1.2requires 36″ minimum.
Every failure cites the section it failed.
The inspector states the defect in plain words — ‘guard is 34 inches, needs 36’ — and Kirk drafts the correction item with the jurisdiction’s exact code section, validated against the adopted code before it can be sent. The inspector approves every word.
The correction letter is in the applicant’s portal and inbox the same day, each item linked to the code text it cites.
Guard measures 34″ at the east rail — KZC-adopted IRC R312.1.2 requires 36″ minimum.
Know what the inspector will look for.
Every inspection type carries a prep checklist generated from the adopted code — live and jurisdiction-specific, not a stale PDF. Crews show up ready, not-ready reinspections (and the fees that follow) get rarer.
Finaled, on the record.
When the last required inspection passes, the permit finals: closeout letter generated, applicant and city notified, the record complete. The 180-day activity clock is tracked the whole way, with warnings before anything lapses — Permitect flags; your building official decides.
Configuration, not customization.
Inspection types, required-inspection templates, and scheduling policy are all data the city owns — set up in plain-language forms, or described in your own words to the built-in assistant, which drafts the configuration from your city’s existing rules for your staff to review and approve.
State-authority inspections (electrical through WA L&I or MN DLI, fire-district inspections) are flagged and routed with the right guidance instead of a dead end.
Notifications reach everyone who needs them — GC, sub, owner, site contact — not one inbox per permit. And the whole inspection record exports as open data in the BLDS standard.
See a permit go from issued to finaled, live.
Bring a permit, or use one of ours. No cost, no commitment, nothing to install.