Accela's record API needs a type-and-workflow map before status integration

Resolve the record class before interpreting status

Accela's record object spans several civic processes. A row labeled Open, Submitted, Approved, Closed, or Complete is not interpretable until the integration identifies the agency, environment, module, record type, record class, custom identifier, workflow, and governing configuration. The same text can represent a different event in a permit, license, service request, case, or work order.

A durable mapping should preserve both provider identifiers and the public agency's defined meaning. It needs the source field, label, code, effective configuration version, triggering event, responsible department, allowed transitions, public display rule, and destination field. If the agency changes a workflow or record type, the integration should version the mapping rather than silently reinterpret historical records.

Treat successful transport and complete data separately

The API reference says a successful request may return no data matching the filters and may include back-end processing messages. An HTTP success therefore establishes transport and response handling, not the existence or completeness of a permit population. Reconciliation needs the query, environment, timestamp, pagination, total returned records, filters, field selection, warnings, retries, and known comparison population.

Partial-response features also create a governance choice. Selecting fewer fields can improve efficiency, but a downstream user may mistake an omitted value for an empty source value. The integration contract should distinguish not requested, not returned, null, unavailable, redacted, invalid, and truly absent. Counts and checksums should expose dropped pages, duplicate records, and changes during a long extraction.

Keep the main record and related objects connected

Accela's documentation describes related resources such as addresses, parcels, owners, documents, workflow tasks, inspections, fees, activities, and conditions. The Create Record endpoint also says custom forms and tables require later update operations. A record created successfully can therefore remain incomplete for the agency's actual intake or decision workflow.

Integrations should retain the relationship among the main record, custom data, attachments, reviews, inspections, conditions, payments, and decisions without implying that every object has the same authority. A document upload is not plan acceptance, an inspection appointment is not a passed inspection, a fee balance is not payment settlement, and a workflow update is not necessarily final permit issuance.

Preserve agency authority outside the API contract

The API can expose and update configured platform records within documented permissions. The agency's charter, adopted codes, ordinances, delegations, procedures, records rules, and authorized staff determine what those records mean and who may make a public decision. A technical token or update endpoint does not confer permit authority on an application, vendor, contractor, or automated process.

Civic Permit Review treats the current Accela developer reference as primary evidence for the provider's record model, filters, response caveats, and endpoint behavior. It does not infer the configuration of any customer environment, data completeness, public-record status, approval, code compliance, inspection result, payment, safety, or legal effect. Those conclusions require exact agency records and accountable public authority.

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.