What is forward volatility?

The core idea

Forward volatility is implied volatility for a future time bucket.

A quoted implied volatility belongs to one expiry. Forward volatility asks a different question: given the total variance implied to an earlier expiry and a later expiry, what volatility is implied for the interval between them?

That forward bucket is often where event premium, liquidity stress, and calendar dislocations show up before they are obvious in a single headline IV number.

This is why forward volatility belongs inside a volatility surfaceworkflow. The calculation uses the term structure of implied volatility, then checks whether the resulting forward bucket is plausible.

Formula

Forward volatility comes from the difference in total variance.

Let T1 and T2 be year fractions for two expiries, and let sigma1 and sigma2 be the annualized implied volatilities for those expiries. The forward variance between T1 and T2 is the incremental total variance divided by the time gap.

Worked example

A 30D IV of 58% and a 90D IV of 64% imply a 66.8% 30D-90D forward vol.

The 30-day total variance is 0.58² x 30/365 = 0.0276. The 90-day total variance is 0.64² x 90/365 = 0.1010. The forward variance for the 30D-90D window is (0.1010 - 0.0276) / (60/365), so the forward volatility is about 66.8%.

The same total-variance arithmetic is why variance swaps belong beside forward-volatility analysis. Forward volatility isolates an implied future variance bucket, while a variance swap compares realized variance over a contract window with the fixed variance strike.

Production construction

Forward volatility should be built from accepted total-variance surface state.

In a production crypto options stack, forward volatility is not a separate indicator bolted onto the dashboard. It is derived from the accepted SVI or SSVI expiry states after quote cleaning, forward selection, smile fitting, and guardrails have already run. That keeps the term-structure panel tied to the same market state as risk reversals, flies, and Greeks.

accepted expiry smiles -> total variance curve -> monotonicity check -> forward buckets -> dashboard/API state

Dashboard monitoring

Forward buckets make term-structure dislocations easier to inspect.

A live crypto options dashboard should not only show expiry IV levels. It should show whether the incremental volatility between expiries is consistent with venue marks, fitted smiles, and surface diagnostics.

Surface diagnostics

Forward volatility is only reliable when the expiry smiles underneath it are reliable.

The calculation starts from accepted expiry slices. If the volatility smile for either expiry is stale, overfit, or built from weak wing marks, the derived forward bucket can look precise while carrying bad market state. This is why forward volatility should be checked beside SVI fit diagnostics, risk nodes, and term-structure continuity.

The same total-variance arithmetic appears in variance swaps, but the operational job is different: forward volatility explains an implied future bucket, while variance-swap tooling compares realized and implied variance over a contract window.

Calendar checks

Negative forward variance is a data-quality and arbitrage signal, not a value to smooth away.

Calendar-arbitrage checks are the main reason to keep forward volatility close to the surface builder. If the total variance curve is not increasing with expiry, the derived forward bucket should be held back and traced to its source smiles. A SABR curve can help explain a single expiry, while local volatility and SSVI-style views make the cross-expiry consistency problem more explicit.

Event windows

Forward volatility is useful when the market prices a specific future interval.

Crypto term structures often move around ETF decisions, unlocks, macro prints, exchange incidents, or protocol events. Forward buckets isolate the market-implied variance for the interval around the event, but they still need the surrounding smile context. A sharp ATM bucket may be less important than a change in downside skew, fly curvature, or a sticky-deltascenario after the forward moves.

API output

A forward-volatility API should expose the two variance points behind the bucket.

A single annualized number is not enough for downstream risk systems. API consumers need to know which expiries were used, whether the coordinate was ATM or fixed delta, which surface versions supplied the total variance inputs, and whether the bucket is live, scenario, or held back.

{
  "metric": "forward_volatility",
  "asset": "BTC",
  "coordinate": "atm",
  "front_expiry": "2026-08-28",
  "back_expiry": "2026-09-25",
  "front_total_variance": 0.0412,
  "back_total_variance": 0.0728,
  "forward_window_days": 28,
  "forward_volatility": 0.641,
  "source_surface_versions": ["btc_svi_2026-08-28_14:02:10Z", "btc_svi_2026-09-25_14:02:10Z"],
  "status": "accepted"
}

Dashboard screenshots

Term structure, smiles, and risk nodes need to be visible together.

Forward volatility is a derived view, so the dashboard should show the source surface, accepted smiles, and risk diagnostics close to the forward bucket. Otherwise a clean-looking term structure can hide a rejected smile or a sparse wing.

Topical path

Move from IV into the surface and dashboard workflow.

• Implied volatility: Start with the option-price-to-IV conversion.
• Volatility surface: Place forward volatility inside the full strike and tenor surface.
• SVI: Fit each expiry smile before comparing tenor buckets.
• Volatility smile: Inspect the one-expiry smile that feeds each total-variance point.
• Variance swaps: Use the same total-variance logic in realized-versus-implied variance payoffs.
• SSVI: Check whether the full tenor parameterization explains repeated forward-bucket breaks.
• SABR: Compare dynamic smile assumptions with direct total-variance surface construction.
• Local volatility: Connect arbitrage-aware surfaces to spot-and-time dynamics.
• Risk reversals: Inspect whether event premium lives in skew rather than only ATM term structure.
• Volatility flies: Track curvature changes when a forward bucket moves.
• Option Greeks: Translate forward-bucket moves into risk reports and sensitivity changes.
• Sticky strike vs sticky delta: Understand how forward moves change strike and delta-based interpretations.
• Technical articles: Read the engineering notes behind the live surface pipeline.
• Dashboard: Monitor live term structure and surface diagnostics.

References

Related Derivasys guides.

• Derivasys implied volatility guide
• Derivasys volatility surface guide
• Derivasys SVI guide
• Derivasys volatility smile guide
• Derivasys variance swaps guide
• Derivasys SSVI guide
• Derivasys SABR guide
• Derivasys local volatility guide
• Sticky strike vs sticky delta
• Derivasys risk reversal guide
• Derivasys volatility fly guide
• Derivasys option Greeks guide
• Derivasys technical articles