CIVIC PERMITREVIEW

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

Coverage desk

System continuity

Source-backed reporting and analysis connected to the companies, capabilities, authorities, and operating domains it affects.

Portland's AMANDA renewal needs an integration inventory

Portland's passed ordinance calls AMANDA the backbone of its permit system, notes other integrated software and multiple bureau users, and extends maintenance through August 2028. A renewal record should preserve the exact service, interface, bureau, support, and exit dependencies behind that continuity decision.

iWorQ's property history needs parcel-change lineage

iWorQ says every permit can be tied to a property so staff can see past permits, inspections, and code cases, and it describes a parcel-map view. A current property screen does not preserve what happened when parcels split or merged, addresses changed, jurisdiction moved, or a site was demolished and rebuilt. Keep a durable ancestry chain.

Cityworks audit logs need configured scope and retention proof

Cityworks' PLL documentation says permits and cases are audited by user, date, time, and change, while also saying administrators can limit auditing to selected groups or items. A jurisdiction should verify the configured event population, identities, prior values, retention, exports, and custody before relying on the log as a complete public record.

Reconcile permit data classes before a legacy-system cutover

Clariti's 2026 buyer guide tells jurisdictions to inventory, cleanse, sequence, and prepare legacy data before implementation. Acceptance still requires the jurisdiction to prove population, meaning, relationships, retention, attachments, balances, workflow state, and cutover for each record class.

An ePermitHub document handoff is not jurisdiction record custody

ePermitHub describes end-to-end document management for plan review, including integrations with permitting and construction tools. A defensible public record still needs a jurisdiction-owned identifier, authoritative version, transfer receipt, reviewer action, retention rule, public-record treatment, and final approved-set designation across every system boundary.

An e-PlanSoft file check is not plan-review acceptance

e-PlanSoft presents PDF Scout as a pre-review tool that can flag known file issues and reject files before review. A passed technical check still needs to remain separate from intake completeness, substantive plan review, correction disposition, jurisdictional approval, permit issuance, inspection, and occupancy authority.

Los Angeles’s permitting-support extension is not production acceptance

A 2026 City of Los Angeles record proposes extending Gartner project-management and IT consulting for BuildLA and the LA City Permitting System through March 2028. The contract record establishes proposed scope, term, funding, and governance—not go-live, migration completion, configured product behavior, production acceptance, service performance, or Clariti involvement.