From the Local Government edition of October 19, 2026
East Devon District Council cannot yet quantify Copilot benefits or targets and keeps its AI policy internal, after a councillor's challenge at full council
East Devon District Council · District council corporate services and digital · East Devon, England, United Kingdom
- Publisher
- Exmouth Journal
- Original publication
- 19 October 2026 (Exmouth Journal); council meeting 14 October 2026
- Source retrieved
- 2026-10-20
- Event date
- 2026-10-14
What happened
The Exmouth Journal reported on 19 October 2026 that at East Devon District Council's full council on 14 October, Cllr Mike Goodman asked what AI had achieved in staff time, response times, customer satisfaction and savings, and what targets were set for the next two years. Written answers said 67 staff had the paid version of Copilot as of July 2026 and all office-based staff could use the free version, that a digital-team action plan was still identifying uses, and that the council could not comment on expected improvements until that work was complete. The AI policy is an internal staff-use document on the intranet, updated on 21 September and to be reviewed every four months. Goodman cited an external audit finding that the AI acceptable use policy had not been reviewed since June 2024 and argued public-sector AI policies should be public; with the portfolio holder absent, his supplementary questions got no substantive answer.
Why it matters
A clear counterweight to vendor success stories: a council with Copilot in use could not show measured benefits or targets, and its policy was neither public nor, per an audit cited by a member, recently reviewed.
Evidence and measured results
Full news article opened. The council's written answers and the external audit report were not opened; findings rely on the article's account.
Limitations and uncertainty
Single meeting account; the audit claim is second-hand; the council may publish figures once the action plan concludes.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-19; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Members are asking for proof of AI value and a public policy, and officers cannot yet supply either.
- Stakeholders
- Portfolio holder for digital
- Digital team
- Internal and external audit
- Elected members
- HR and training
- Discovery questions
- What baseline task data exists from before Copilot?
- Who owns the response to member questions on AI value?
- Can the staff AI policy be published?
- How was the cited audit finding closed?
- Value hypothesis
- A measurement framework could let the council show, or rule out, value from existing seats; no benefit is evidenced yet.
- Potential engagement
- Eight-week Copilot benefits baseline and public AI policy review.
- Unsupported claims
- Any time or cost saving
- Improved response times or satisfaction
- Compliance with audit recommendations
Pre-sales engineering
Role takeaway
- Fit
- Measurement and governance for an existing Microsoft 365 Copilot deployment.
- Architecture and integration
- Copilot usage telemetry joined to task logs or service metrics; no new platform needed.
- Prerequisites
- Usage telemetry access
- Baseline task timings
- Current reviewed policy
- Constraints
- Small paid-seat base (67)
- Policy kept internal
- Four-month review cycle
- Security
- Check the updated policy covers sensitive data in prompts and retention of Copilot outputs.
- Proof of value
- Matched-task timing study
- Before/after response-time metrics in one service
- Staff survey tied to specific tasks
Delivery
Role takeaway
- Work
- Complete action plan, set baselines and targets, publish policy, report to full council.
- Dependencies
- Digital team capacity
- Service managers for baselines
- Audit for finding closure
- Ownership
- Digital team under the relevant portfolio holder.
- Skills and adoption
- Use-case design per role beyond initial training.
- Governance checkpoints
- Publish AI policy
- Confirm audit finding closed
- Report targets to members
- Acceptance criteria
- Proposed: two-year targets published for staff time and response times
- Proposed: policy reviewed on its four-month cycle with dates logged
- Proposed: first benefits report to council within six months
- Risks
- Spend without evidence
- Member distrust
- Policy review lapses again
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?
Microsoft 365 Copilot (paid for 67 users) plus free Copilot Chat for office staff; no other tooling described.
Governance
Who approves, reviews and stays accountable for outcomes?
Internal-only AI policy with a four-month review cycle; audit finding (as cited) of a lapsed review; elected-member demand for public policy and measurable targets.
Security and privacy
What data, permissions and controls need testing?
Not addressed beyond the existence of a staff-use policy.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Staff training followed by an action plan; no workforce outcomes reported.
Procurement
What should contracts, pricing and exit terms secure?
Licence count disclosed (67 paid seats); cost not reported.
Operating model
Which teams own the service once it runs?
Benefits measurement deferred until use cases are identified, after licences were already deployed.
Publication history
- 2026-10-19Local Government · Issue 444 resources
Stable resource ID: east-devon-dc-copilot-benefits-policy-transparency-challenge-20261019