Not an implementation claim. Event studies are among the most leakage-prone research designs in finance; this guide is the methodology for reading and building them without the classic self-deceptions.
Definition. Event-driven research measures returns conditional on discrete occurrences — earnings, index changes, mergers, ratings actions, resolutions in prediction markets. The design’s power (clean identification around a timestamp) is exactly its fragility: everything depends on the event’s definition, its timestamp, and the window’s tradability, and each hides a failure mode.
Problem 1: Defining events without hindsight
An “event” must be identifiable at the time, by the rule stated. The violations are systematic: conditioning on outcomes (“merger announcements that completed” — completion is future information; the tradeable set includes the deals that broke, the survivorship of events); retroactive taxonomies (“major” earnings surprises defined by thresholds fit on the full sample — normalization leakage in event clothing); and database backfill (event databases add, correct, and reclassify events after the fact — the point-in-time event list differs from today’s download, and vendors rarely preserve the vintage). The discipline: write the event rule as an algorithm over point-in-time data, then ask what its live false-positive rate would have been.
Problem 2: The timestamp is the methodology
Event day is not event time: earnings drop pre-open or post-close; news bodies timestamp distribution, not information creation; regulatory filings have acceptance vs dissemination times. Being wrong by hours flips which bar “reacts” — and a “predictive” result that evaporates under correct timestamps is the genre’s signature failure. Worse is pre-event drift: information leaks (analyst chatter, order flow) mean the announcement window captures only the residual; a strategy “trading the event” competes with everyone who traded the leak. Papers must state the timestamp source and its precision — and results at daily resolution for intraday events deserve default suspicion.
Problem 3: Abnormal returns and the clustered-events trap
Event returns need a counterfactual: subtract expected returns via a factor model over the window. Two standing traps: model choice moves results for long windows (a 60-day “drift” is exquisitely sensitive to the benchmark’s factor set); and event clustering breaks independence — earnings seasons, sector-wide ratings waves, and index reconstitutions land together, so N events ≠ N observations, and cross-sectional t-stats on clustered events overstate wildly. Cluster by calendar date at minimum; the honest papers do.
Problem 4: The execution window
The paper measures close-to-close; the information arrived at 4:05pm. What’s actually available is the overnight gap plus the tradable session — and event returns concentrate in the gap you couldn’t trade. The checklist: does the entry price postdate the information’s availability (open-after-announcement, not close-before)? Are event-window spreads used, not calm-market ones — liquidity around events is exactly when spreads triple? For merger-style strategies: is the borrow available, and what does the deal-break tail cost? Post-announcement-drift claims that survive open-entry, event-spread costing are rare — and the ones that do are the genre’s real findings.
Common ways event strategies fail in production
- The event feed differs from the research database: live detection latency, misclassifications, and coverage gaps mean the production event stream is a noisier, slower version of the backtest’s — a data-vendor question papers never address.
- The gap captures the edge: live P&L concentrates in fills you can’t get; realized returns are the paper’s minus the gap.
- Crowding at the timestamp: everyone’s algo reacts to the same feed; the microstructure around events is a queue race the backtest didn’t model.
- Event-rule drift: the definition that backtested cleanly gets “improved” in production — each improvement a new trial.
Questions to ask an event paper
- Was the event set constructible, as defined, on the event date?
- What timestamp source, at what precision — and do results survive open-entry?
- How is clustering handled in the standard errors?
- What are costs in the event window, and does the edge survive them?
What our scoring captures
Event studies score across the full rigor range, and the discriminators are exactly this guide’s four problems — timestamp discipline and clustered-error handling are visible in a paper’s text and scored accordingly. The NLP/LLM hub is the genre’s current frontier (text-defined events), where the training-cutoff leak stacks on top of everything above; read that hub with this guide open.
The leakage taxonomy: look-ahead & PIT → · The window’s costs: transaction costs → · The text frontier: alternative-data map →