Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the Local Government edition of September 8, 2026

Government evaluationMixedRecent

PlanAI pilot separates rapid summarisation from weeks of preparation and quality assurance

Ministry of Housing, Communities and Local Government; participating English planning authorities · Local-plan consultation analysis · England; transferable workflow questions, not U.S. planning rules or savings estimates

Publisher
MHCLG Digital
Original publication
July 30, 2026
Source retrieved
2026-09-09
Read original source

What happened

The official pilot account reports large analysis-stage efficiencies alongside preparation costs and inaccurate policy tagging.

Why it matters

Relevant to municipal consultation teams processing resident comments; summarisation must preserve participation and minority concerns.

Evidence and measured results

Five authorities extended the pilot. MHCLG reports around 90% efficiency gains but says preparation and iteration took two to three weeks for some authorities. Greenwich encountered inaccurate policy tags. The account does not provide comparable denominators, total workflow costs or an independent quality benchmark.

Limitations and uncertainty

Programme-authored narrative rather than a controlled study. The reported efficiency applies to a component. No demonstrated end-to-end causal benefit or accessibility evaluation.

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

Engage the consultation lead, information governance team and community-engagement staff around whether analysis capacity is delaying plan development. Ask how submissions arrive, how minority views are represented and what a corrected thematic report costs to produce. Offer a bounded comparison on a completed consultation, with the existing manual analysis retained as a reference. A credible hypothesis is less repetitive grouping while preserving accurate representation; it is not a promise of a 90% shorter consultation. Establish whether the buyer can fund preparation and review. Clarify that an assistant's thematic output does not replace the municipality's policy judgement or engagement obligations.

Pre-sales engineering

Role takeaway

Build a test corpus spanning short, long, multilingual and overlapping-policy responses. Keep original identifiers through redaction, segmentation, tagging and summary generation. Prerequisites include an agreed policy taxonomy, lawful data access and reviewer-labelled examples. Evaluate omitted concerns, incorrect policy assignments and distortion of response volume, not just processing speed. Include adversarial instructions embedded in comments as untrusted data. Proposed validation should compare error rates and total analyst effort with the manual baseline, then repeat after configuration changes. Hosting and agent capabilities were not evaluated here; avoid autonomous updates to official consultation conclusions until the authority has validated a controlled approval boundary.

Delivery

Role takeaway

The consultation service manager should own completeness and fairness, supported by records staff, analysts and privacy reviewers. First establish a manual reference sample and an accessible alternative route; then rehearse redaction, correction and publication. Dependencies include policy clarity and sufficient review capacity. Train staff to inspect underlying responses when a summary is ambiguous. Proposed acceptance requires every sampled theme to be traceable, all high-impact omissions to be resolved, and the manual route to receive equivalent review. Track elapsed time from receipt through approved analysis. These are proposed checks. Risks include undercounting preparation, amplifying frequent views and unintentionally excluding residents who avoid AI.

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?

Separate input preparation, tagging, summarisation and reviewer approval in both the pipeline and performance logs.

Governance

Who approves, reviews and stays accountable for outcomes?

Require a trace from thematic conclusions to resident submissions, with a route to challenge omitted or misrepresented views.

Security and privacy

What data, permissions and controls need testing?

Redact personal data before processing and verify whether deleted source text persists in prompts, caches or logs.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

The account describes an AI opt-out with manual analysis. Interpretation: test equal treatment across both routes.

Procurement

What should contracts, pricing and exit terms secure?

Include preparation, human checking and support costs in quotations; require exportable response-to-summary links.

Operating model

Which teams own the service once it runs?

Fund consultation analysts' verification work and escalation, not merely the model runtime.

What changed

New-to-archive July source; newly relevant as direct evidence of preparation and tagging limits in municipal knowledge work. No newer release or outcome claimed.

Publication history

  1. 2026-09-08Local Government · Issue 034 resources
Read preserved resource versions (JSON)

Stable resource ID: mhclg-planai-consultation-preparation-2026