234 incidents on record · 2026HeadlightsIncident reports by Ellie Harris · Melbourne
5 new this weekLibrary last updated 14 October 2026
← The incident library
HD-INC-225
Workplace relations · Japan · 2024 · An AI tool that proposed pay changes to managers was used in pay reviews while the employer, according to the union, refused to disclose what it considered or what it proposed

IBM Japan Settled a Union Complaint by Agreeing to Disclose What Its AI Weighed in Pay

By Ellie Harris · Filed IBM Japan announced in August 2019, according to the union, that it had introduced Watson into pay reviews; complaint filed 3 April 2020 (case 令和2年都委不第31号)

Alleged: IBM Japan, Ltd. developed or deployed the AI system implicated in this incident. Details are drawn from public reports; parties are presumed innocent of any wrongdoing not established by an official finding.

IBM Japan Settled a Union Complaint by Agreeing to Disclose What Its AI Weighed in Pay

What happened

It was reported by JMITU’s IBM Japan branch that IBM Japan told group employees in August 2019 that it had introduced its own AI, Watson, into pay assessments. The union says it asked IBM Japan to explain what the AI considered and what it showed managers.

It was reported by the union that IBM Japan refused those requests. On 3 April 2020, the union says it applied to the Tokyo Metropolitan Labour Relations Commission, alleging unfair labour practices under Article 7 of the Labour Union Act: bargaining in bad faith and interference.

According to the union, IBM Japan said the AI was only a tool to support managers’ judgement. The union reports that IBM Japan also said the information shown to managers was not intended to be disclosed to employees as it stood.

What an auditable version would have shown

It was reported by the union that company material described about 40 kinds of data considered by the AI and pay proposals shown to managers, including by what percentage to raise pay. The union also says IBM’s sales material said managers tend to follow its recommendations.

The union reports that IBM Japan’s position was that managers made the judgement. The sources reviewed do not show how managers actually used the AI’s proposals or whether anyone’s pay was set differently because of them.

Where the gap was

It was reported by the union that the parties reached a settlement before the commission on 1 August 2024. Under the settlement published by the union, IBM Japan agreed to disclose to the unions the titles of all items the AI was made to consider in the 2019 and future pay adjustments. The unions agreed not to disclose those titles to third parties indiscriminately.

The settlement records that when a member’s pay review is disputed for specific reasons, such as a cut, zero raise or low rating, IBM Japan will present and explain the AI’s proposal. It will also explain how the items considered by the AI relate to its grading rules and discuss future questions about the AI’s pay evaluation method in good faith.

The settlement contains no finding that IBM Japan acted unlawfully. It was reported by the union that Kyndryl Japan, which took over part of IBM Japan’s business after the complaint, does not currently use AI in pay assessments.

A ConductRecord keeps, for each pay review, what the AI considered, what it proposed and what the manager decided.

A MetricRecord is designed to produce signed figures, such as how often managers followed the AI’s proposal, that a union or regulator can verify.

ConductRecord and MetricRecord are Headlights designs.

What governance should have looked like

It was reported by the union that the settlement gave it a way to see the AI’s proposal when a member’s pay review was disputed, about five years after IBM Japan announced it had introduced the AI. No statement by IBM Japan on the settlement was found as of 3 October 2026.

Where an AI proposes pay, best practice would be to tell employees what it considers, keep its proposal and the manager’s decision for each review, and show both to an employee who disputes the outcome.

Failure Pattern: according to the union, an employer used its own AI to propose pay changes to managers and refused to disclose what the AI considered until a settlement required it.

Governance Principle: when an AI proposes pay for a person, the employer should be able to show what it considered and what it proposed for that person.

The reference implementation of ConductRecord and MetricRecord is open source. It lives at github.com/saffronandindia/headlights-oss, Apache 2.0 licensed and free to install. The repository is public now.

Sources

The mailing list

Fresh incident reports every week. One email to match.

We add new incidents to the library regularly, and send a single short email each week with what's new. The library stays free and open; this is just how you keep up with it.

Sent through Substack. Unsubscribe in one click.

The record

An auditable system would have produced a signed, tamper-evident record the moment this happened: what the system did, the version that did it, the basis it acted on, and the action taken, and IBM Japan, Ltd. could have produced it on demand.

This is the record the system as deployed did not produce in a signed, auditable form.

What this teaches
Capture what happened when it happens
What the system did, the version that did it, the basis it acted on, and the action taken, recorded at the moment, not reconstructed after.
Sign it, so no one has to trust the record-keeper
A tamper-evident entry. Edit it later and the signature breaks. The record does not ask for the benefit of the doubt.
Make it verifiable by anyone
A court, a regulator, a customer's lawyer can check the record themselves, without taking the company, or us, at our word.

Headlights summarises publicly reported AI incidents. All summaries are independently written, attributed to their original sources, and intended for research and educational purposes. Allegations are identified as such until established through official findings.

Last reviewed October 2026. This report is based on the sources listed above and reflects information available at the time of review; later developments may not be captured. Where a person is described as charged with or alleged to have done something, that allegation is unproven unless a conviction or a court or regulatory finding is stated. Headlights publishes journalism and commentary, not legal advice.

Want to write back?

Direct to my inbox.

ellie@useheadlights.com →