70/100

Moderate evidence

ProblemPublished recordLaborProblem Space

The impact of fear of automation

Truvace record
TRV-2026-3078raw data (JSON)
Version
v1Published
First published
Evidence type
Randomized controlled trial
Sources
1 sourcePeer-reviewed
sha256
49f6f9767147…check it

In this paper, we study the causal effect of workers’ perceived probability of job loss due to automation on policy preferences and workplace intentions. Using a representative sample of the U.S. workforce, we elicit individuals’ perceived likelihood of losing their job to robots or artificial intelligence within the next decade. We document strong cross-sectional relationships between automation fear and support for higher taxation, more generous government transfers, union membership, retraining, occupational…

The problem

In a randomized survey experiment with a representative sample of US workers, learning that their occupation faced worse automation job-loss odds than expected raised demand for redistribution, government support and unionization, but left intentions to retrain or switch occupations largely unchanged.

What this doesn’t fix

The study measures expressed policy preferences and stated intentions after an information treatment, using a reduced-form approach to perceived downside exposure, not workers' actual later behaviour or job outcomes.

Sources

1 on file
  1. Labour Economicsdoi:10.1016/j.labeco.2026.102979
    Peer-reviewed2026-11-04

Cite this record

v1

Truvace Impact Record TRV-2026-3078, v1: “The impact of fear of automation.” Truvace, 2026-11-20. /record/TRV-2026-3078 (accessed on the day you copy it). sha256 49f6f97671470c2e…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv149f6f9767147…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-3078 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.