From the Local Government edition of September 8, 2026
Independent planning scorecard establishes a baseline without claiming an AI effect
PlanningLens Ltd · Municipal planning evaluation · England; evaluation design has limited transfer to U.S. permitting
- Publisher
- PlanningLens
- Original publication
- August 3, 2026; data snapshot July 22, 2026
- Source retrieved
- 2026-09-09
- Event date
- 2026-07-22
What happened
PlanningLens publishes a pre-trial decision-time baseline and comparator panels; it explicitly declines to attribute early changes to AI.
Why it matters
Helps localities define evidence needed before accepting throughput claims. Different planning laws and case mixes preclude importing the English baseline.
Evidence and measured results
The analysis reports 7,663 pilot-council decisions, a pooled median of 7.71 weeks, and 16 control councils. Baseline window: May 2024–April 2026. Timing runs from validation to decision, ignores deadline extensions and excludes cases over 364 days. May–July observations are explicitly noncausal.
Limitations and uncertainty
Commercial publisher, not part of the trial. Raw decision rows were not independently recomputed. Incomplete recent feeds, imperfect Camden matching and excluded long cases limit inference. Baseline is not an effectiveness verdict.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-09; this does not change the original publication date. Labels below come from the analysis itself.
Sales
Role takeaway
Ask a permitting director, performance analyst and procurement officer what evidence would justify scaling an assistant. Clarify whether the problem is staff workload, applicant waiting time or missed deadlines, since these require different measures. Offer a bounded baseline-and-evaluation design using the customer's records. The value hypothesis is a better informed purchase or continuation decision, not immediate productivity. Do not use the 7.71-week English baseline as a customer benchmark. Confirm that case definitions and timestamps are reliable enough for comparison, and that someone independent of the supplier can challenge exclusions, missing records and an apparently favourable result.
Pre-sales engineering
Role takeaway
Assemble a versioned dataset linking case stage, application class, reviewer and actual AI exposure. Retain missingness flags and capture changes in staffing or policy. Prerequisites include stable identifiers, authorized records access and a pre-agreed comparison design. Test timestamp semantics and matching sensitivity before generating dashboards. Proposed validation should reproduce a sampled record's elapsed time from the source and show results with and without long-case exclusions. Treat a matched panel as observational evidence with residual confounding. The scorecard does not validate an agent, model or deployment architecture; any application integration requires its own security and reliability testing.
Delivery
Role takeaway
A municipal performance lead should own the evaluation with planning staff and data engineering support. Freeze the initial protocol, record exclusions and establish a schedule for data refresh and discrepancy resolution. Dependencies include access to complete records and visibility into operational changes. Train stakeholders to distinguish component efficiency, resident waiting time and causal attribution. Proposed acceptance requires reproducible sampled calculations, visible data gaps and documented review of comparator suitability before any benefits claim. These are proposed controls, not measured improvements. Risks include selective follow-up, changing denominators and attributing concurrent process reforms to AI. Keep unresolved uncertainty in the published findings.
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Capture stage timestamps and model exposure separately; elapsed-time records alone cannot establish that a case used an assistant.
Governance
Who approves, reviews and stays accountable for outcomes?
Predefine comparison rules and publish methodological changes before interpreting results.
Security and privacy
What data, permissions and controls need testing?
Use minimal case identifiers for reproducibility and suppress personal details in public evaluation outputs.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Add applicant experience and staff rework to timing data; neither is established by portal timestamps.
Procurement
What should contracts, pricing and exit terms secure?
Require independently reproducible evaluation definitions, not just a supplier's chosen success metric.
Operating model
Which teams own the service once it runs?
Assign an analyst outside the deployment team to maintain comparators and record service changes.
What changed
New-to-archive August baseline; contributes an independent evaluation design to planning coverage. No September outcome or post-trial causal result claimed.
Publication history
- 2026-09-08Local Government · Issue 034 resources
Stable resource ID: planninglens-ai-planning-baseline-2026