OpenGov workflow configuration does not confer permit authority

Map each configured step to the jurisdiction’s authority

A permitting platform can represent intake, completeness review, routing, plan examination, fees, approvals, issuance, inspections, corrections, closeout, and public communication. Each step still needs a named jurisdiction, government function, adopted authority, accountable role, decision right, record, status, effective date, exception, and appeal or correction path.

The configuration should distinguish ministerial intake from discretionary findings, model codes from locally adopted requirements, staff recommendations from authorized decisions, and administrative status from legal effect. A workflow can coordinate these boundaries only if the jurisdiction defines and governs them.

Treat automated flags as review inputs

A guided form or assisted check may help identify missing fields, document types, routing conditions, or potential issues. It does not establish that an application is legally complete, a design complies with an adopted code, a parcel has a particular legal status, a fee is lawfully due, or a permit should issue. Those conclusions require current local authority and accountable review.

Jurisdictions should retain the input, rule or model version, source records, timestamp, output, confidence or reason, reviewer, override, correction, and final authorized decision. Applicants also need clear notice of what the system checked, what it did not check, and how to correct or challenge a record through the jurisdiction’s established process.

Test the implemented record chain, not the product-page breadth

The OpenGov page documents a product family and intended workflow coverage. It does not establish which modules, forms, integrations, codes, fee schedules, maps, accessibility controls, retention rules, security controls, or service levels a customer purchased and configured. Nor does it prove migration quality, staff adoption, turnaround time, approval rate, or public outcome.

A useful demonstration follows one local application through revision, outside-agency referral, payment exception, plan comment, inspection correction, expiration, public-record request, and appeal or supervisor review. The jurisdiction should identify the authoritative source at each handoff and prove that history, versions, permissions, and decisions remain reconstructable.

Keep provider claims and government decisions visibly separate

OpenGov is the authoritative source for its current public product positioning. The jurisdiction remains the authority for its adopted rules, configured operating process, official records, and permit or licensing decisions. Customer-specific outcomes require records with population, period, event definitions, denominator, exclusions, and method—not provider language alone.

Civic Permit Review rechecked the official product record on August 9, 2026; no post-July 30 material product change was identified. The page currently resolves to OpenGov’s Permitting and Licensing product surface. Buyers should verify the contracted product, current documentation, jurisdiction-specific implementation, and accountable authority map.

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.