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 applicant portal and guided intake 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.
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.
HUD PRO Housing
PRO Housing funds eligible governments to identify and remove barriers to affordable housing production and preservation, including policy, land-use, infrastructure, process, and permitting barriers. Digital permitting projects should connect technology work to defined barriers, process evidence, equity, participation, housing outcomes, displacement safeguards, and grant obligations rather than promise that software alone creates housing.
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.
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
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.
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.
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.
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 applicant portal and guided intake 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.
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.
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.