ISO 37122 is not a permit-platform performance benchmark

Keep the city indicator separate from the service transaction

ISO’s public abstract places ISO 37122 at the city-indicator level. It supplies definitions and methodologies intended to help measure progress toward a smart city in conjunction with ISO 37120. A building-permit application, planning case, inspection, license, complaint, payment, or public-record request is a different unit of analysis with its own authority, population, states, timestamps, exceptions, and legal effects.

A local government can use a city indicator to frame a public objective without treating the value as a permit-system result. The measurement record should preserve the indicator definition, city boundary, reporting period, population, source systems, calculation, missing-data treatment, revision, and responsible office. The underlying service record should separately preserve the jurisdiction, application or case type, start and end events, pauses, decisions, and accountable roles.

Define permit performance with reproducible local events

Permit turnaround is not one universal measure. A jurisdiction might examine intake-to-completeness, completeness-to-first review, applicant revision time, outside-agency time, resubmission-to-decision, issuance, inspection, correction, or closeout. Each measure needs a named permit population, observation period, business or calendar time, start and end events, paused-time treatment, denominator, exclusions, source, revisions, and missing-data method.

Those definitions must also reflect the public service. A discretionary planning entitlement, ministerial building permit, technical plan review, contractor license, and code-enforcement case cannot be compared as if they were one queue. An issued permit does not establish that construction started or completed, and a faster administrative status does not by itself establish legal quality, accessibility, safety, applicant experience, or housing production.

Do not turn a standards mapping into a vendor score

A provider may document dashboards, workflow timestamps, online services, analytics, or smart-city positioning. Those capabilities can support data collection and public reporting, but they do not prove that the purchased package was configured correctly, that source records are complete, that staff use status codes consistently, or that the platform caused a measured change. ISO 37122 does not certify a permitting product or transfer public authority to it.

A buyer demonstration should reconstruct one metric from raw service records through transformations, exclusions, corrections, publication, and later revision. It should show late entries, duplicate cases, migrated history, reopened work, applicant-held time, changed workflow definitions, and records split across systems. The jurisdiction should be able to reproduce the measure after export and explain every material difference from its official operational record.

Preserve edition, adoption, and local-policy boundaries

ISO lists the first edition as published in May 2019 and records that it was reviewed and confirmed in 2024, so the edition remains current. That lifecycle status does not make the standard binding in every city. A jurisdiction should record whether and how it adopted or referenced the standard through policy, program, contract, reporting practice, or another authority, including the exact edition and review date.

Civic Permit Review relies only on ISO’s public metadata and abstract and does not reproduce protected standard text. The official public record does not establish which indicator a city selected, whether its calculation conforms, whether data are accurate, whether a permit platform supports the method, or whether a service outcome improved. Those unknowns require the city’s adopted policy, full measurement record, technical validation, and accountable public review.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Civic Permit Review will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.