From the Local Government edition of October 25, 2026
Edinburgh councillor's motion seeks counts and resource costs of AI-generated complaints, citing one that took two officer days
The City of Edinburgh Council · Council complaints handling and AI-generated public correspondence · Edinburgh, Scotland, United Kingdom
- Publisher
- The City of Edinburgh Council (committee papers)
- Original publication
- Motion for the 29 October 2026 council meeting; document publication date not stated
- Source retrieved
- 2026-10-26
- Event date
- 2026-10-29
What happened
A motion for Edinburgh's 29 October council meeting asks the Chief Executive to report how many complaints are suspected to be AI-generated, the resource implications, and whether SOLACE or COSLA is coordinating a sector response. It says such complaints can run to thousands of words, may include hallucinated cases and legal references that must be checked, and that one took two officer days to answer, while the council must respond to every point.
Why it matters
Why now: scheduled for the 29 October meeting. Adds a named council seeking measurement of AI-generated complaint volume, the inbound side of local government AI that affects staffing regardless of the council's own AI use. Note an LGC overview of the same issue (22 Oct) is already archived; this is a distinct council action.
Evidence and measured results
Motion text describing officer experience and Information Commissioner guidance; no data yet.
Limitations and uncertainty
A motion, not an adopted decision; anecdotal single case; no counts yet; publication date not stated.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-25; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Complaints teams spend disproportionate officer time on lengthy AI-generated complaints that must be answered point by point.
- Stakeholders
- Chief Executive
- Complaints team
- Policy and Sustainability Committee
- Legal services
- SOLACE and COSLA
- Discovery questions
- How do you identify suspected AI-generated complaints?
- What is average handling time versus other complaints?
- Which points require legal checking?
- Value hypothesis
- Bounded: measurement could inform staffing and process; no evidence that tools reduce effort.
- Potential engagement
- A complaint-handling time study separating suspected AI-generated cases.
- Unsupported claims
- Volume or growth rates
- That AI triage would cut handling time
- Sector-wide figures
Pre-sales engineering
Role takeaway
- Fit
- Councils with statutory duties to answer every point in complaints.
- Architecture and integration
- Limited relevance; possible point-extraction or citation-check aids with human review.
- Prerequisites
- Case management data
- Definition of suspected AI-generated
- Constraints
- Duty to answer all points
- Information Commissioner guidance
- Risk of tool hallucination
- Security
- Complaints contain personal data; any tool must stay within council data controls.
- Proof of value
- Test whether citation checks catch hallucinated references on past cases
- Measure officer time with and without aids
Delivery
Role takeaway
- Work
- Produce the requested report on AI-generated complaint volume and resource needs.
- Dependencies
- Council approval of the motion
- Complaints data
- Sector input
- Ownership
- Chief Executive's office with the complaints team.
- Skills and adoption
- Officers need guidance on handling hallucinated references.
- Governance checkpoints
- Council vote on 29 October
- Report to Policy and Sustainability Committee
- Acceptance criteria
- Proposed: counts of suspected AI-generated complaints reported
- Proposed: handling time compared with other complaints
- Risks
- Misclassifying genuine complaints
- Discouraging legitimate AI-assisted complainants
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?
Limited relevance; possible future triage tooling is not proposed.
Governance
Who approves, reviews and stays accountable for outcomes?
Seeks a formal report and a sector-wide response through SOLACE or COSLA.
Security and privacy
What data, permissions and controls need testing?
Limited relevance.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Officer time is the main cost; one response took two officer days.
Procurement
What should contracts, pricing and exit terms secure?
Limited relevance; any triage tooling would follow the requested report.
Operating model
Which teams own the service once it runs?
Complaints teams must check hallucinated citations and answer every point, changing workload per case.
Publication history
- 2026-10-25Local Government · Issue 507 resources
Stable resource ID: edinburgh-uk-motion-ai-generated-complaints-officer-time-20261029