AI can compress a transcript, translate an interview, propose a headline or create a rough illustration in seconds. None of those actions proves that the resulting publication is accurate, lawful or fair. The useful unit of media automation is therefore not “a generated article”. It is a publication packet that lets an editor trace every material claim, quote, asset, right and disclosure.
This distinction matters most when speed is valuable: breaking news, live blogs, election coverage and high-volume local publishing. A model can make a newsroom faster at producing both corrections and errors. The operating design must make unsupported material harder to publish, not merely easier to generate.
This guide reflects the position on 31 July 2026. It distinguishes current rules from consultations and proposals; it is not legal advice.
Start With the Standards That Survive a Tool Change
For IPSO-regulated publishers, editorial accountability does not move to the vendor. IPSO’s AI guidance says editors remain accountable, human oversight remains central and publications must still take care over accuracy. Clause 1 of the Editors’ Code requires care not to publish inaccurate, misleading or distorted information or images, distinguishes fact from comment and conjecture, and requires prompt, appropriately prominent correction of significant inaccuracies.
Broadcast news has its own regime. Rule 5.1 of Ofcom’s Broadcasting Code requires due accuracy and due impartiality; significant mistakes should normally be acknowledged and corrected quickly. A model-written script, synthetic voice or AI-selected clip does not change that test.
Translate the applicable standard into workflow controls rather than a generic “human in the loop”. Name the editor, define what evidence they inspect, record the decision and make the stop button real.
Use a Publication Manifest
Create a manifest alongside each story, episode or asset. It need not be public in full, but it should be exportable for complaints, legal review and corrections.
| Manifest field | Minimum evidence |
|---|---|
| Commission | Purpose, audience, format, deadline and risk rating |
| Sources | URL/file, publisher, date accessed, relevant passage and reporter note |
| Claims | Claim ID linked to supporting sources and confidence status |
| Quotes | Recording/transcript location, speaker confirmation where needed, edits |
| Assets | Creator, licence, consent/model release, permitted territories and expiry |
| AI use | Tool, model/version, task, input restrictions and output retained |
| Review | Accuracy, legal, rights, safety and accessibility sign-offs |
| Publication | Final version, timestamp, labels, syndication destinations |
| Corrections | Complaint, decision, change, reason and propagation status |
The published copy should be generated from or checked against this packet. A URL in a model response is not a source until a person or trusted retrieval process opens it, confirms that it exists and verifies that it supports the specific claim.
Put Tasks Into Green, Amber and Red Lanes
Risk depends on the task and the subject, not on whether the vendor calls its system a copilot.
Green tasks are reversible and do not add facts: timestamping an owned recording, formatting structured data, tagging an approved archive or creating transcription candidates. Sample them for quality and protect confidential inputs.
Amber tasks can change meaning: summarisation, translation, headline suggestions, image clean-up, clip selection and personalisation. Require comparison with the source, visible uncertainty and an editor who understands the language or context.
Red tasks can cause serious harm: generating allegations about a named person, inventing or reconstructing quotes, depicting a real person doing something they did not do, publishing medical or financial instructions, or autonomously reporting a public emergency. These need original-source verification, specialist review where appropriate and often a prohibition on synthetic substitution.
The lanes should attach to content types in the CMS. A reporter should not be able to bypass a red-lane gate by pasting the same output into a different field.
Verify Claims at Sentence Level
A practical verification pass extracts material factual claims before publication. For each, the editor sees the exact supporting passage, its date and source type. Primary records—judgments, filings, legislation, official data and the original interview—should be distinguished from commentary that merely repeats them.
Require a second independent source where newsroom policy calls for one; do not let the model manufacture apparent corroboration by citing multiple pages that all repeat one release. Dates, units, locations and named entities deserve deterministic checks. Quotes must resolve to an audio/video timestamp or the reporter’s contemporaneous record, not a polished reconstruction.
When evidence conflicts, the system should expose the conflict. “Unable to verify” is a valid state. A blank paragraph is safer than an invented bridge. The deeper local-news application is covered in AI for journalism and local reporting.
Clear Rights Before Polishing Output
Generated does not mean rights-cleared. The UK government’s 2024–25 copyright and AI consultation described the current framework: copying copyright works for model training requires permission unless an exception applies, and an output can infringe where it reproduces a substantial part of a protected work. The government then published its report and impact assessment on 18 March 2026 under the Data (Use and Access) Act. That report did not itself create a blanket permission for publishers or settle every disputed question.
Maintain a rights ledger for training, retrieval and publication separately. Record the licence or exception relied upon, permitted uses, attribution, territory, term, sublicensing and whether content may be sent to a third-party model. Vendor assurances belong in the file, but they do not answer whether the newsroom had permission to upload an unpublished manuscript, archive photo or freelance recording.
Screen outputs for recognisable passages, logos, characters and compositions before release. If a generated image is only “in the style of” a living artist, a narrow infringement check may still miss contractual, passing-off, reputational and editorial risks. Commissioning or licensing original work is often the cleaner route.
Label Synthetic Media According to Use and Territory
The label decision is not one universal “made with AI” badge. Record what was altered, whether the change affects meaning, whether a real person or event is depicted, and where the content will be offered.
Article 50 of the EU AI Act applies from 2 August 2026. The European Commission’s current transparency summary describes machine-readable marking obligations for providers of systems that generate or manipulate synthetic content, and disclosure duties for deployers publishing deepfakes or AI-generated public-interest text without human review or editorial control. A UK publisher is not automatically in scope merely because it is online; assess the Act’s territorial and role-specific application to the service and EU audience.
Do not use the public-interest-text exception as a checkbox. If relying on substantive human review and editorial responsibility, the manifest should show who reviewed the content, against which sources, and who is accountable for publication. For a synthetic image, audio or video that could be mistaken for an authentic person, place a clear disclosure near the content and preserve provenance metadata through resizing and syndication.
UK policy is still developing. The March 2026 report announced further work on digital replicas, content labelling and creator control. Treat consultations, taskforces and proposed codes as future-facing work until they are final and applicable; do not present them as enacted UK duties.
For a dedicated implementation checklist, see EU AI Act transparency rules for UK teams.
Keep Advertising Visibly Separate From Editorial
AI can produce a native-looking sponsor article at the same time as editorial copy, which makes provenance controls essential. ASA/CAP guidance on advertisement features says paid content subject to editorial control must be obviously identifiable. Labels such as “Ad” or “Advertisement Feature” should be prominent and upfront; “Sponsored” can be ambiguous.
Carry the commercial label into cards, search results, newsletters, feeds, snippets and social posts—not only the article page. Store who paid, what control they had and which claims were substantiated. An AI rewrite must not erase qualifications or make a regulated product claim stronger than the approved evidence.
Treat Audience Features as a Separate Regulated Product
Publishing articles does not by itself make every newsroom an Online Safety Act service. But comments, community posting or a public search feature may bring a service or part of it into scope. Ofcom’s illegal-content duties guidance requires in-scope services to assess risk, implement protections and keep records, including a new assessment before a significant service change.
Assess scope explicitly before adding AI replies, comment summaries or recommendation features. A moderation model is one control, not the risk assessment. Keep appeal, reporting and escalation paths usable when automation fails. Similar practical controls appear in AI content moderation and social media.
A Breaking-Story Workflow
Consider an incoming video that appears to show a public figure at an unfolding incident. A safe workflow is:
- quarantine the original and preserve file metadata;
- identify the uploader and obtain the highest-quality source;
- check time, location, shadows, weather and independent footage;
- run forensic tools as indicators, not verdicts;
- contact the subject or representative where appropriate;
- write only claims supported by the verified evidence;
- label uncertainty and any synthetic reconstruction explicitly;
- obtain the required editorial and legal sign-offs;
- publish with the manifest version attached internally; and
- monitor new evidence and propagate any correction to every channel.
The model may organise those checks. It must not convert an uncertain authenticity score into a factual allegation.
Measure Trust Operations
Track the rate and severity of corrections, unsupported-claim blocks, quote mismatches, rights exceptions, missing disclosures, editor overrides, complaint outcomes and time to propagate a correction. Break results down by desk, format, tool and risk lane. Engagement and production volume are business measures, not evidence that the content is sound.
A release gate for any AI-assisted publishing route should require:
- every material claim to be supported, attributed or clearly framed as unverified;
- every quote to resolve to an original record;
- every external asset to have a recorded right, consent and permitted use;
- named-person allegations and high-risk advice to receive the defined specialist review;
- synthetic-media and advertising labels to survive all distribution channels;
- confidential sources and embargoed material to be excluded from unapproved models;
- corrections to update the canonical page, feeds, newsletters and syndication partners;
- accessibility checks for captions, alt text and reading order;
- logging of tool, version, reviewer and final decision; and
- a tested ability to disable generation while normal publishing continues.
Re-run these gates when a model, vendor, prompt, distribution channel or editorial policy changes.
The strongest newsroom automation does not imitate an editor. It gives the editor better evidence, clearer uncertainty and a reliable correction path. Publish faster only when the proof can keep up. For audio-specific rights, voice and transcript controls, continue with AI in podcast production.



