CIVIC PERMITREVIEW

The systems, rules, and operating record behind civic approvals.

Coverage desk

Permit authority

Source-backed reporting and analysis connected to the companies, capabilities, authorities, and operating domains it affects.

San Diego permit use needs inspection and expiration evidence

San Diego Information Bulletin 117 ties permit utilization and continued validity to specific timing and inspection conditions for covered building permits. Owners and reviewers need to distinguish an inspection request, a qualifying completed inspection, an approved extension, final-only eligibility and actual permit closure.

Minneapolis plan-review exemptions need an eligibility record

Minneapolis says specified roof, siding, window, and door projects no longer require applicants to upload plans for building plan review, while its Express Limited Permit path can allow eligible applicants to complete payment online with less staff review. The operating control is a versioned eligibility record that proves why a particular project entered the streamlined path without implying that plan-review exemption equals code compliance, inspection completion, or authority beyond the named city process.

Permit.com forecasts need jurisdiction-stage assumptions

Permit.com says it provides milestone tracking, approval forecasting, and preliminary timeline forecasts informed by jurisdiction trends and historical data. A useful forecast must name the permit stage, jurisdiction, review path, starting event, assumptions, and revision history without implying control over agency action.

Accela task routing needs a jurisdictional clock rule

Accela's current Civic Platform page describes cross-department tasks, routing, approvals, and SLA management. A municipality must still define which clock starts, pauses, transfers, or ends for each public-service decision and who holds the authority at handoff.

Cityworks audit logs need configured scope and retention proof

Cityworks' PLL documentation says permits and cases are audited by user, date, time, and change, while also saying administrators can limit auditing to selected groups or items. A jurisdiction should verify the configured event population, identities, prior values, retention, exports, and custody before relying on the log as a complete public record.

A Granicus portal update is not the jurisdiction's official notice record

Granicus documents permitting and licensing platforms with self-service access, workflow communication, real-time data, and mobile tools. A portal update can improve service, but the jurisdiction still needs a controlled record of what notice was issued, by whom, through which authorized channel, when service occurred, and which deadline followed.

Treat a ZoningHub parcel result as research, not a determination

ZoningHub describes a public-facing zoning research service that communities populate with code content and may pair with GIS. A parcel result can organize a first inquiry, but it is not an authoritative zoning determination for a specific property or proposal.

A BS&A license-status alert is not contractor authorization

BS&A documents permit workflows that link contractor and licensee records and notify staff about expiration, registration, money owed, and stop-work conditions. Those checks can focus review, but the jurisdiction's current source records and authorized official still determine whether a contractor may perform the named work.

Clariti keeps staff review between CivCheck and a plan-review finding

Clariti describes CivCheck as guided AI plan-review software and states that every AI interpretation requires staff review and approval. That boundary should remain visible in the case record: an automated interpretation can focus reviewer attention, but the jurisdiction's authorized reviewer owns the finding.

A Symbium compliance check does not confer permit approval

Symbium presents computational-law software for property and permitting workflows, including automated checks against configured rules. A passing result can inform intake or review, but only the authorized jurisdiction can determine completeness, exercise discretion, impose conditions, and issue a permit.

A Tyler plan markup is not the approved permit set

Tyler documents electronic plan submission, concurrent review, markups, approval stamps, version control, workflow, and field access within Enterprise Permitting & Licensing. Civic teams still need one authority-controlled chain from applicant revision through discipline review, conditions, approval, issuance, field set, later revision, and final record.

Accela's record API needs a type-and-workflow map before status integration

Accela documents one transactional record object across applications, permits, cases, licenses, service requests, and work orders. An integration that copies a status without the agency's record type, workflow, related objects, and history can turn different civic processes into a misleading common field.

OpenGov workflow configuration does not confer permit authority

OpenGov documents configurable forms, fees, routing, approvals, inspections, and applicant-facing workflows for permitting and licensing. Those provider-documented capabilities can support a jurisdiction’s process; they do not create legal authority, adopt a code, make findings, approve a plan, issue a permit, or decide an inspection result.