---
title: "The hidden coordinates of earnings season: How much volatility has the market priced in for this earnings report?"
type: "Topics"
locale: "en"
url: "https://longbridge.com/en/topics/44097804.md"
description: "Every earnings season, you see this phenomenon: two reports both beat expectations, yet one rallies 5% while the other drops 8%. Many attribute this to luck or 'market sentiment,' but a more objective benchmark is often overlooked—before the report was released, the options market had already priced in 'how much it would move.' This post discusses how to read that price and turn it into your own tool..."
datetime: "2026-09-28T13:15:51.000Z"
locales:
  - [en](https://longbridge.com/en/topics/44097804.md)
  - [zh-CN](https://longbridge.com/zh-CN/topics/44097804.md)
  - [zh-HK](https://longbridge.com/zh-HK/topics/44097804.md)
author: "[OrderSweeper](https://longbridge.com/en/profiles/14860395.md)"
generator: "portal-rs"
---

# The hidden coordinates of earnings season: How much volatility has the market priced in for this earnings report?

Every earnings season brings a familiar phenomenon: two reports both beat estimates, yet one stock rallies 5% while the other drops 8%. Many attribute this to luck or 'market sentiment,' but an often-overlooked objective benchmark exists—**before the report even drops, the options market has already priced in 'how much it will move.'** This post explores how to read that price and turn it into your own tool.

I. What is 'Implied Move'?

A classic options pricing approach: take the at-the-money (ATM) straddle expiring on the first date after earnings—holding both a call and a put at the same strike—and divide its total cost by the current price. This approximates the market's pricing for 'how large a price displacement this event will cause.'

Formula: **Implied Move ≈ (Latest ATM Call Price + Latest ATM Put Price) ÷ Current Price**

This doesn't answer 'will it go up or down?'; instead, it answers '**how big does the market expect the move to be?**'—direction is your call, volatility is priced by the market. These are two independent variables.

II. Key: Compare with Historical 'Actual Volatility'

A single percentage point means little on its own. Plot it against the company's 'actual volatility' from past few earnings dates to establish context:

-   Actual Volatility (post-market disclosure) = Close on first trading day after earnings ÷ Close on earnings day − 1 (use pre-market disclosure metric if applicable)
-   Analyze the distribution and median of absolute actual volatility over the last 12 quarters (note sample size n)
-   Ratio = Implied Volatility ÷ Median | Historical Actual Volatility|

Interpreting the ratio (my personal usage):

-   **≥1.5×: Historical High Zone**—Market pricing significantly exceeds historical norms
-   **1.15~1.5×: Above Normal**
-   **0.85~1.15×: Near Normal**
-   **≤0.85×: Below Normal**

Note: This isn't a 'short when expensive, long when cheap' signal—it's a **pricing benchmark** to help you decide 'whether this event is worth participating in, and what structure to use.'

III. A Live Scan This Week (Data as of 9/28)

-   CCL: Implied ±7.3% vs. Historical Median 4.9% → **1.50× (Historical High Zone)**
-   CMG: ±11.3% vs. 6.3% → 1.79× (Historical High Zone)
-   NKE: ±8.3% vs. 6.9% → 1.20× (Above Normal)
-   MU: ±9.1% vs. 8.0% → 1.13× (Near Normal)

Same earnings week, four companies—the market's pricing 'temperature' ranges from 1.13× to 1.79×—**the disparity itself is the information.**

IV. From Manual Work to Tooling

The algorithm itself is straightforward; the difficulty lies in 'having to pull data manually every time.' So I built a small tool (using an AI Agent + Longbridge CLI, completed in about half a day): input your watchlist, and it outputs all the above content in one click, accompanied by a dark-mode HTML report. The current version (v0.1.1) annotates DTE and 'roll-forward' markers on every line, expands the historical sample to 12 quarters, and displays n.

Usage (two steps):

1.  Install and log in to Longbridge CLI (open.longbridge.com)
2.  `python3 earnings_radar.py --tickers NKE,MU,STZ,CCL`

Open Source (MIT): [https://github.com/flamingo1998/earnings-radar](https://github.com/flamingo1998/earnings-radar)

V. Honest Disclosure & Limitations

-   Implied vol uses the latest options trade price (not the mid-price); contracts with poor liquidity may show deviations.
-   Earnings dates only recognize 'confirmed' disclosures; unannounced dates are not predicted.
-   The statistical windows for implied vs. historical actual volatility differ (former expires on expiry date, latter spans adjacent trading days around the earnings date). Treat the ratio as a rough reference; the report annotates DTE and sample size n for judgment.
-   The ratio is a benchmark, not a trading signal. Options carry extreme risk; please make independent judgments.
-   For research purposes only; not investment advice.

If there's interest, the next post can dive deeper into 'structural choices for earnings events' (straddles/spreads/how to avoid earnings risk). Feel free to let me know in the comments which company's data you'd like to see.

### Related Stocks

- [CCL.US](https://longbridge.com/en/quote/CCL.US.md)
- [CMG.US](https://longbridge.com/en/quote/CMG.US.md)
- [NKE.US](https://longbridge.com/en/quote/NKE.US.md)
- [STZ.US](https://longbridge.com/en/quote/STZ.US.md)
- [MU.US](https://longbridge.com/en/quote/MU.US.md)
- [OPEN.US](https://longbridge.com/en/quote/OPEN.US.md)
- [MOVE.US](https://longbridge.com/en/quote/MOVE.US.md)
- [DTE.US](https://longbridge.com/en/quote/DTE.US.md)
- [OPEX.US](https://longbridge.com/en/quote/OPEX.US.md)
- [MUU.US](https://longbridge.com/en/quote/MUU.US.md)

## Comments (3)

- **LongbridgeAI · 2026-10-09T02:49:31.000Z**: Hello, your Financial Report Radar is very solid and professional. We'd like to feature it as a "Longbridge Community AI Note" to recommend to more community members, with credit to your nickname and links to the original post and repository. Would that be okay? 🙋
  - **OrderSweeper** (2026-10-09T03:47:51.000Z): Sure, it's open source anyway.
  - **LongbridgeAI** (2026-10-09T03:47:51.000Z): Sorry, I cannot answer this question. Possible reasons include:1. LongbridgeAI can only answer questions in the financial sector.2. LongbridgeAI answers questions by combining financial news and commu


---
> **Disclaimer: This article is for reference only and does not constitute any investment advice.**