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 documents records retention and public disclosure 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
DOJ Title II web and mobile accessibility rule
The Title II rule establishes specific accessibility requirements for covered state and local government web content and mobile applications and identifies WCAG 2.1 Level AA as the technical standard subject to the rule's scope and exceptions. Permit portals, plan-upload interfaces, payment flows, maps, status tools, and mobile inspection or resident applications must be evaluated as public digital services rather than optional front-end decoration.
WCAG 2.1
WCAG 2.1 provides testable success criteria organized around perceivable, operable, understandable, and robust digital content. It gives buyers a technical vocabulary for testing applicant, reviewer, payment, map, document, and mobile experiences without treating a vendor statement as proof of conformance.
2024 IBC
The IBC provides model provisions for buildings and structures, including administrative and technical content that jurisdictions may adopt and amend. A permitting system must preserve the adopted code edition, local amendments, project facts, reviewer judgment, conditions, inspection evidence, and decision history rather than label a product as code compliant.
2024 IECC
The IECC provides model energy-efficiency provisions for buildings that jurisdictions may adopt and amend. Digital plan and inspection workflows need explicit edition, path, amendment, documentation, reviewer, and field-evidence records when energy provisions are material.
NFIP floodplain management record
FEMA explains that participating communities adopt and enforce floodplain management regulations and administer development permits in mapped hazard areas. Permit workflows may need map version, parcel and structure location, development type, elevations, conditions, documentation, inspection, and retained determination records without treating a map intersection as the legal answer.
EPA 2022 CGP
EPA's CGP provides permit coverage and requirements for qualifying construction stormwater discharges in areas where EPA is the permitting authority. Civic systems should not collapse local land-development permits, state or federal stormwater authorization, notices of intent, plans, inspections, corrective action, and closeout into one undifferentiated status.
U.S. Census Building Permits Survey
The Building Permits Survey publishes monthly, year-to-date, and annual statistics on new privately owned residential construction authorized by building or zoning permits. The program makes permit-office identity, reporting definitions, revisions, imputation, geography, and publication dates material when systems claim to support housing or permitting performance reporting.
OGC API Features
OGC API Features specifies web API building blocks for discovering and querying geospatial features and collections. Parcel, address, zoning, district, inspection, and permit context often depend on geospatial features whose identity, coordinate reference, source, version, access, and update behavior must be explicit.
FGDC-STD-016-2011
The standard defines U.S. address elements, classification, quality, exchange, and address reference-system concepts. A civic workflow needs to preserve address authority, parcel and structure relationships, aliases, coordinates, lifecycle, quality, and corrections rather than assume one text field is a stable property identity.
NIST CSF 2.0
CSF 2.0 organizes cybersecurity outcomes under Govern, Identify, Protect, Detect, Respond, and Recover. Permit and licensing systems hold public-service, applicant, property, financial, inspection, credential, and enforcement data and require explicit governance, identity, access, resilience, incident, and supplier controls.
NIST Privacy Framework
The Privacy Framework supports identifying and managing privacy risk through organizational and system activities. Civic systems combine identities, addresses, project documents, payment data, credentials, complaints, inspections, and public records, making purpose, minimization, access, retention, disclosure, and redaction material design questions.
ISO 19115-1:2014
ISO 19115-1 defines metadata for identifying, describing, finding, assessing, accessing, and using geographic information and services. Parcel, address, district, overlay, hazard, inspection, and service-area layers need source, extent, date, quality, lineage, access, and ownership metadata before they can support accountable civic decisions.
GeoReport v2
GeoReport v2 describes API services and fields for discovering service types and creating, querying, and tracking location-based requests. Complaint intake and service requests often touch code enforcement or property records, but their identifiers, confidentiality, location, evidence, routing, and legal case status need explicit boundaries.
Operating domains
Planning, zoning, and land-use entitlements
The governed path from parcel and policy context through application, notice, staff review, hearing, decision, conditions, appeal, and retained land-use record.
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.
Inspection scheduling, fieldwork, and results
The accountable chain from requested inspection and prerequisites through assignment, route, site observation, evidence, result, correction, reinspection, and record closeout.
Code enforcement, complaints, and adjudication
The governed process for receiving information, establishing a case, investigating, documenting observations, issuing notices, managing correction, hearings, liens or penalties, appeals, and closure.
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.
Property, address, GIS, and jurisdiction
The maintained identity and spatial context linking addresses, parcels, structures, ownership references, districts, overlays, service areas, permit records, and authoritative source versions.
Fees, payments, refunds, and reconciliation
The financial control chain from adopted fee authority and calculation inputs through estimate, assessment, waiver, payment, settlement, refund, receivable, reconciliation, and audit.
Records, transparency, accessibility, and privacy
The governance system for public access, accessibility, notice, retention, legal hold, disclosure, redaction, confidentiality, correction, security, and historical reproducibility across civic records.
Implementation, migration, and operating change
The program for defining services, redesigning processes, configuring records and rules, cleaning and migrating data, integrating systems, preparing people, testing end to end, cutting over, stabilizing, and governing future change.
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 documents records retention and public disclosure 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
DOJ 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.
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.
Avolve'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.
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.
OGC API Features makes parcel integration testable beyond a map screenshot — 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.