Truace
Subscribe
TRV-2026-1579Certified recordPeer-reviewed

Associations of artificial intelligence use at work with psychological distress, loneliness, and life satisfaction among employed US adults

Objective: To quantify the associations between artificial intelligence use at work and psychosocial well-being among employed adults in the United States. Methods: Nationally representative data come from the Household Trends and Outlook Pulse Survey (United States, March 2026). Artificial intelligence use at work was measured as the number of distinct assisted work tasks. Outcomes included psychological distress, loneliness, and life satisfaction. Regression models adjusted for sociodemographic characteristics…

Labor · The Trace — both readings · certified 2026-10-16 · v1 · article view · machine-readable

Current reading — gain

Among employed US adults in March 2026, doing more distinct work tasks with AI was associated with higher life satisfaction.

Current reading — problem

Among the same employed US adults, greater AI use at work was associated with a higher prevalence of feeling lonely.

What this doesn’t fix

The findings are associations from survey data, and the authors state that longitudinal studies are needed to examine the impact of increasing AI use on employee well-being.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1579, v1: “Associations of artificial intelligence use at work with psychological distress, loneliness, and life satisfaction among employed US adults.” Truvace, 2026-10-16. /record/TRV-2026-1579 (accessed at citation time). sha256 a4d588989e8f45db…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1a4d588989e8f…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1579 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.