57/100

Moderate evidence

GainPublished recordBusinessGood Space

Generative AI, Managerial Expectations, and Economic Activity

Truvace record
TRV-2026-2496raw data (JSON)
Version
v1Published
First published
Evidence type
Observational studyPreprint, not yet peer reviewed
Sources
1 sourcePeer-reviewed
sha256
37c6ba21e093…check it

Using generative AI, we extract managers’ economic expectations from over 120,000 corporate conference call transcripts. The resulting AI Economy Score predicts GDP growth, production, employment, and wages five or more quarters ahead, beyond survey forecasts and other existing measures. Industry- and firm-level scores capture sector- and firm-specific activity, and a composite of firm, industry, and macroeconomic expectations further improves forecasting power and horizon. Predictability concentrates among hist…

The gain

In a working paper analysing 125,830 earnings calls, an AI-derived score of manager optimism raised the share of next-quarter GDP growth explained from 43.8% to 48.6% and kept predicting GDP for five quarters.

What this doesn’t fix

The authors say that telling the model the call date does not eliminate look-ahead bias, since its training data extend past that point, and the score failed to anticipate the early-2020 pandemic collapse.

Sources

1 on file
  1. NBER Working Paperdoi:10.3386/w35949
    Peer-reviewed2026-10-01

Cite this record

v1

Truvace Impact Record TRV-2026-2496, v1: “Generative AI, Managerial Expectations, and Economic Activity.” Truvace, 2026-11-12. /record/TRV-2026-2496 (accessed on the day you copy it). sha256 37c6ba21e0935c09…

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. Publishedv137c6ba21e093…

    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-2496 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.