CIVIC PERMITREVIEW

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

GIS interoperability · Standards-and-platform comparison

Lead story: OGC API Features and ArcGIS feature services differ

OGC API Features defines a modular open interface for discovering and querying feature data, while an ArcGIS Feature Service exposes an ArcGIS service's layers, tables, capabilities, queries, and optional edits. Teams should select the contract they can govern and test, then make any adapter explicit.

Civic permitting, planning, and regulatory systems intelligence

View newsroom

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.

MuniLogic’s shared property record needs field-level authority

MuniLogic presents MuniLogicCE across property, GIS, permitting, licensing, code enforcement, documents, payments, and constituent services. A shared property view is useful only when each parcel, address, ownership, use, permit, license, inspection, and enforcement field keeps its source, effective date, jurisdictional meaning, correction path, and public authority.

NFIP participation needs a local administration record

FEMA describes floodplain management as a community-based function and sets minimum standards for communities participating in the National Flood Insurance Program. A jurisdiction still needs a maintained record connecting participation, adopted rules, responsible officials, maps, permits, inspections, enforcement, variances, corrections, and public communication.

Gridics code-to-parcel updates need effective-date parity

Gridics says its platform combines digitized zoning-code text, parcel-level data, GIS layers, maps, and self-service tools. A jurisdiction should activate those surfaces against one governed effective-date record so a resident, planner, and reviewer do not receive different answers during an ordinance or map change.

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.

A NIST CSF profile needs a permitting-system boundary

NIST presents CSF 2.0 profiles as a way to describe cybersecurity outcomes. A local permitting profile still needs a named service boundary, systems and interfaces, public responsibilities, evidence owners, exceptions, and recovery conditions.

How the market is organized

Explore all
Public authority

The platform routes work; the jurisdiction makes the decision

A defensible civic record keeps the governing source, authorized role, applicant, property, submission, review, condition, notice, inspection, payment, and final decision distinct—even when one suite displays them together.

Read the market record →
Land use

A map answer is not a zoning determination

Parcel, district, overlay, code text, use, nonconformity, entitlement, hearing, condition, and appeal can share geography while retaining different evidence and decision rights.

Read the market record →
Plan review

Version integrity matters before automated checking

Plan intelligence is useful only when the system can identify sheets, versions, authors, comments, responses, approvals, amendments, and the exact issued set without erasing reviewer judgment.

Read the market record →
Implementation

Data migration is an operating decision, not a row count

Historical permits, parcels, people, fees, documents, statuses, inspections, conditions, notices, and links need explicit disposition and acceptance before a new portal can be trusted.

Read the market record →

Codes, rules, and public-program record

Explore all
DOJ Title II web and mobile accessibility rule
WCAG 2.1
2024 IBC
2024 IECC
NFIP floodplain management record
Civic operating and decision domains
Planning, zoning, and land-use entitlements
Building-permit intake and review
Electronic plan review and version control
Inspection scheduling, fieldwork, and results
Code enforcement, complaints, and adjudication

Platforms and service organizations in review

Explore all

Civic systems change ledger

Explore all
Municipal process changeMinneapolis removes plan review for specified permit scopes

Municipal teams can streamline a defined administrative path while preserving a versioned eligibility record, applicable code obligations, separate payment and issuance states, later inspections, exceptions, and accountable City authority.

RegulationDOJ shifts Title II web-rule dates, but permit portals still need an operating accessibility plan

Civic permitting intelligence becomes useful when a sourced change can be connected to a named public service, jurisdiction, accountable decision, evidence chain, and interpretation boundary without implying compliance or approval.

Model codeThe 2024 IBC keeps software outside the code decision

Civic permitting intelligence becomes useful when a sourced change can be connected to a named public service, jurisdiction, accountable decision, evidence chain, and interpretation boundary without implying compliance or approval.

Official dataCensus final 2025 permit estimates change the housing-authorization baseline

Civic permitting intelligence becomes useful when a sourced change can be connected to a named public service, jurisdiction, accountable decision, evidence chain, and interpretation boundary without implying compliance or approval.

AcquisitionGranicus's SmartGov acquisition reframes the midmarket permitting decision

Civic permitting intelligence becomes useful when a sourced change can be connected to a named public service, jurisdiction, accountable decision, evidence chain, and interpretation boundary without implying compliance or approval.

Corporate changeAvolve's DigEplan merger makes plan review a two-product question

Civic permitting intelligence becomes useful when a sourced change can be connected to a named public service, jurisdiction, accountable decision, evidence chain, and interpretation boundary without implying compliance or approval.

Civic Record Research

Explore all
CIVIC PERMIT REVIEW · 2026Civic permitting market architectureIndependent market research
Original analysis

How enterprise suites, municipal platforms, plan-review products, planning intelligence, GIS layers, payment services, permit operations, and implementation firms divide the market.

The research connects the provider market, normalized capabilities, authority records, operating domains, and source limitations rather than presenting a score or universal winner.

Read the report →
Conditional comparisons

Compare operating fit, not popularity

Accela Civic Platform vs Tyler Technologies Enterprise Permitting & Licensing
OpenGov Permitting & Licensing vs Clariti
Granicus Permitting & Licensing vs CentralSquare Community Development
Computronix POSSE PLS vs CityView
Cloudpermit vs Citizenserve