aceModerate evidence
Published recordLaborProblem Space
More
Who Is Afraid of ChatGPT? A Natural Experiment on the Effect of ChatGPT Release on Labour-Market Concerns
- Truvace record
- TRV-2026-2509raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- dbd78c652ab8…check it
The public release of ChatGPT on November 30th, 2022 revived the public debate on technological change and, particularly, on its impact on the labour market. Despite the sudden growth in AI salience after the launch of the new chatbot, to our knowledge, no empirical investigation has assessed the impact of this technological breakthrough on citizens’ first concerns. By means of a unique survey fielded between November and December 2022 in five European countries, we use an Unexpected Event During Survey (UEDS) d…
The problem
A survey study across five European countries found that ChatGPT's release mildly but significantly raised people's concern about unemployment, most among those with low and middling income and education.
What this doesn’t fix
The study measures perceived unemployment risk among survey respondents shortly after the launch, in five European countries, before widespread adoption; it does not measure actual job losses.
Sources
1 on file- Social Science Computer Reviewdoi:10.1177/08944393261493959
Cite this record
v1Truvace Impact Record TRV-2026-2509, v1: “Who Is Afraid of ChatGPT? A Natural Experiment on the Effect of ChatGPT Release on Labour-Market Concerns.” Truvace, 2026-11-12. /record/TRV-2026-2509 (accessed on the day you copy it). sha256 dbd78c652ab8d117…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2509 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.