Deloitte admits AI wrote parts of Wellington council report — but stands by findings
Wellington mayor Andrew Little has publicly stated that “large chunks” of a $435,000 Deloitte report on council staffing were written by artificial intelligence. The admission adds to mounting criticism of the Future Fit Pōneke report, which recommended cutting 330 staff — a figure now revealed to be based on flawed data.
Key errors found in the report
The council's own review uncovered multiple data-handling mistakes:
- Deloitte double-counted current employees alongside vacant roles.
- Employment data was three years old, sourced from the Taxpayers' Union.
- All employees were counted at their full-time salary, regardless of actual hours worked.
- Staffing expenses were overstated by $21.5 million.
- Roles with “project” in the title were automatically assumed to be duplicates.
Because of these inaccuracies, the council concluded that the recommendation to cut 330 FTE roles was “inherently flawed.” A more accurate figure might be 284, though even that does not account for other potential errors.
AI disclosure remains vague
Mayor Little told Newstalk ZB that the AI-generated sections were “just a waste of time” compared to the chapter on contract management systems, which he described as a “disaster” but useful. Deloitte has not specified which sections were AI-produced or how the AI was used.
In a prepared statement, Deloitte said: “Deloitte uses a range of tools and technologies across its work, including AI-enabled tools where appropriate,” while requiring that “a human needed to sign off any analysis, findings and conclusions.” They maintain the report's conclusions are sound.
Implications for AI use in consulting
This case highlights the risk of using AI without rigorous verification — especially in high-stakes public-sector reports. For developers and teams building AI-assisted workflows, the lesson is clear: AI can draft, but humans must validate every data point and assumption. The Wellington council's experience is a cautionary tale about the reputational cost when AI-generated content is accepted without thorough audit.
📖 Read the full source: HN LLM Tools
👀 See Also

Claude Code Bug Replaces German Umlauts with ASCII Substitutes
Claude Code and Claude.ai app have been randomly replacing German umlauts (ä, ö, ü, ß) with ASCII substitutes (ae, oe, ue, ss) since December 2025. The bug persists despite explicit instructions and has gone unfixed for over 3 months with no response from Anthropic support.
The Mundane Risk: Why AI Safety's Biggest Threats Are Boring, Not Dramatic
An essay argues that mundane AI failures are already causing damage at scale, current alignment approaches depend too heavily on sandboxed environments, and capability convergence makes accidental open-world exposure increasingly plausible.

The double standard in AI-assisted creation: coding vs. writing
A Reddit discussion highlights the contrasting reception between AI-assisted coding (vibe coding) and AI-assisted writing, noting identical workflows but different cultural perceptions.

Andrej Karpathy Joins Anthropic's Pre-Training Team to Drive Recursive Self-Improvement Using Claude
Andrej Karpathy, former OpenAI cofounder, joins Anthropic's pre-training team under Nick Josef to build a new team focused on using Claude to accelerate pre-training research, enabling recursive self-improvement.