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

Read the record as a proposed consulting extension

The official Los Angeles record supports a narrow and useful conclusion: city officials documented a continuing need for Gartner project-management and information-technology consulting connected to BuildLA and the LA City Permitting System, and recommended a contract amendment with a stated term and compensation ceiling. The transmittal presents the matter for consideration. It is not a production-acceptance certificate, project completion report, product announcement, performance audit, or universal implementation model.

A reliable program ledger should preserve the council file and contract numbers, document and transmittal dates, requesting department, contractor, purpose, original and proposed term, prior and proposed compensation, funding sources, recommendation status, approval path, attached scope, and later execution or council records. Proposed, authorized, executed, invoiced, delivered, accepted, operational, and closed are separate states and should never be collapsed into one implementation status.

Separate consulting scope from system and service outcomes

Project management and IT consulting can support planning, governance, requirements, procurement, coordination, quality review, risk management, implementation, maintenance, or support without owning the underlying platform or proving any production result. The source does not establish which features are configured, which records have migrated, which integrations operate, which users are trained, which services are live, or which acceptance criteria have been met.

For each workstream, the city program record should identify the accountable department, consultant role, product and integrator boundaries, current phase, approved baseline, deliverable, acceptance criteria, evidence owner, decision authority, issue, dependency, change, payment relationship, and next gate. A contract ceiling or extended term is financial and governance evidence; it is not a measure of permit cycle time, backlog, accessibility, data quality, staff adoption, applicant experience, or approval outcome.

Build acceptance from records, not labels

Production acceptance should be tied to an approved scope and environment, traceable requirements, test population, defects and severity, security and privacy review, accessibility conformance, data-migration reconciliation, interface testing, role and permission testing, records and retention behavior, operational procedures, training, support readiness, rollback or continuity plan, decision authority, and signed disposition. A go-live date alone does not supply that evidence.

The buyer test should ask for one end-to-end civic transaction and its difficult exceptions: incomplete intake, revised plans, cross-department routing, fee change, failed payment, inspection correction, public notice, appeal, public-record request, accessibility barrier, duplicate parcel, migrated history, and outage. Each state should identify the source system, authoritative record, responsible role, timestamp, correction path, and retained evidence.

Correct the entity boundary before publication

During this review, Civic Permit Review found that an internal source registry had mislabeled this PDF as a Clariti implementation record and linked it to the Clariti provider record. The PDF names Gartner and the City of Los Angeles projects; it does not name Clariti. The registry label and provider linkage were corrected on August 28, 2026, while the prior label, exact URL, and correction reason were preserved in the source-maintenance record.

No material development after the August 27 daily cutoff was established. This article is durable analysis of an existing official record and a correction to evidence attribution, not a claim that the proposed amendment was newly approved or that implementation status changed today. Readers should consult later official council, contract, project, audit, and operating records before drawing any current program conclusion.

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.