CIVIC PERMITREVIEW

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

Cities and local governments measuring smart-city service development · International smart-city indicator standard

Sustainable cities and communities — Indicators for smart cities

ISO 37122 defines indicator methodologies intended to complement ISO 37120 in measuring smart-city progress.

Published and confirmed international standardVoluntary unless adopted by policy, contract, program, or another authority

What the authority record establishes

ISO 37122 defines indicator methodologies intended to complement ISO 37120 in measuring smart-city progress.

Voluntary unless adopted by policy, contract, program, or another authority

The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.

Why it matters to this market

A digital permit portal should be evaluated through transparent service and operating measures rather than labeled smart solely because an online transaction exists.

Affected operating stages

  • Indicator Design
  • Data Collection
  • Calculation
  • Publication
  • Benchmarking
  • Improvement

Capabilities to examine

Applicant Portal And Guided Intake

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for applicant portal and guided intake.

Public Search Status And Communications

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for public search status and communications.

Review Routing Deadlines And Task Control

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for review routing deadlines and task control.

Workload Turnaround And Service Reporting

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for workload turnaround and service reporting.

APIs Integrations And Data Export

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for APIs integrations and data export.

Mobile And Offline Field Inspections

Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for mobile and offline field inspections.

Affected buyer audiences

  • city executives
  • digital-service leaders
  • performance offices
  • technology teams
  • researchers

Implementation questions

  • Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
  • What is binding, what is guidance, and what is a technical or consensus standard?
  • Which publication, adoption, effective, application, transition, and enforcement dates differ?
  • Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
  • How will a source revision affect open work and historical decisions?

Interpretation boundary

The standard does not certify a smart city, validate a product, prove service improvement, define legal obligations, or set one performance target for every jurisdiction.