Define the operating boundary
A useful definition names the triggering event, required inputs, governing source, accountable owner, decision or action, exception path, evidence retained, and downstream handoff. Buyers should adapt those elements to their own population, jurisdictions, policies, systems, and control model before writing requirements.
The most important distinction is between a label and an operational capability. A provider may document review routing deadlines and task control while depending on customer-supplied policy, licensed content, third-party data, integration partners, manual review, or services. The demonstration should expose those dependencies rather than hiding them behind a completed interface.
What a demonstration should prove
- Begin with representative source records and a named policy, standard, or controlled rule.
- Show the normal path, an ambiguous case, missing data, an exception, an override, and a material source change.
- Identify who can change rules, who can approve or reject, and how accountability is preserved.
- Trace every output back to inputs, versions, timestamps, user actions, and governing evidence.
- Export the resulting record and reconcile it with downstream systems and retained obligations.
Authority and operating context
ISO 37120:2018
ISO 37120 defines methodologies for indicators used to measure city services and quality of life. It raises the evidence bar for claims about permit time, service quality, transparency, housing, and development by requiring definitions, population, period, method, and comparability.
ISO 37122:2019
ISO 37122 defines indicator methodologies intended to complement ISO 37120 in measuring smart-city progress. A digital permit portal should be evaluated through transparent service and operating measures rather than labeled smart solely because an online transaction exists.
Operating domains
Building-permit intake and review
The controlled workflow from project scope and applicant identity through application, completeness, fee, technical review, correction, permit decision, conditions, and issuance.
Electronic plan review and version control
The document and decision system for receiving, validating, routing, marking, reconciling, resubmitting, approving, stamping, and retaining plan sets and related review records.
Business, contractor, and property licensing
The recurring regulatory workflow for application, identity, qualification, supporting evidence, fee, review, issuance, renewal, condition, inspection, suspension, and enforcement across distinct license programs.
Evidence and comparison limits
Official provider documentation can establish product positioning. Provider confirmation can clarify package or availability. Independent observation requires a disclosed scenario, environment, date, inputs, and reproducible result. None of those sources alone establishes buyer-specific legal, clinical, regulatory, quality, or operational fitness.
Buyer questions
- What exact outcome and evidence should review routing deadlines and task control produce?
- Which source, version, and customer facts govern the workflow?
- Which decisions remain human and who is accountable for them?
- What is native, configured, integrated, service-delivered, or planned?
- How does a changed source affect open and historical records?
Recent changes
Granicus'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.
EPA's CGP modification highlights why environmental permits need their own jurisdiction boundary — 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.
Permit-operations services need an authority map, not a speed promise — 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.