Skip to content
All library documents

Annualizing Volatility from Monthly Returns and Trading Days

Article Quant Q&A · Author: Andrey

Summary

The document considers the usual estimate that annualized volatility equals monthly return standard deviation multiplied by the square root of twelve, and asks whether different month lengths should change the calculation. It explains that the relevant variation is in trading days, which differ across months and years because of weekends and market holidays, rather than simply the number of calendar days.

One proposed adjustment is to estimate a daily return from each monthly return using that month’s trading-day count, then pool variance estimates while accounting for the different sample sizes. The answer argues that the added effort is unlikely to change results materially given the noise in market returns. More fundamentally, monthly returns can conceal large within-month moves that cancel out; estimating that volatility properly requires higher-frequency observations. The discussion offers no empirical comparison of the adjusted estimate and the standard convention, so it leaves the practical size of the difference unquantified.

Key ideas

  • The common monthly volatility estimate annualizes by multiplying monthly standard deviation by the square root of twelve.
  • Trading-day counts vary across months and years, which complicates a day-count adjustment.
  • A proposed adjustment estimates daily returns by month and pools variance with sample sizes in view.
  • Monthly returns can hide substantial within-month volatility when gains and losses offset.
  • Higher-frequency observations are needed to measure volatility that monthly endpoints conceal.

Tags

Full text
# Calculating "annualized" standard deviation from monthly returns and the different month lengths


# Calculating "annualized" standard deviation from monthly returns and the different month lengths












I have the monthly returns and want to estimate an "annualized" standard deviation.

An industry-standard way seems to be the following:

$$ \sigma_a = \sqrt{12} \sigma_m, $$

where $\sigma_m$ is "monthly" standard deviation calculated from the monthly returns $r_i$:

$$ \sigma_m = \sqrt{\frac{1}{n - 1} \sum_{i=1}^n (r_i - \bar{r})^2}. $$

My question: the formulae above do not take into account the different lengths of the calendar months. It's clear that 1% returns in January and in February are a bit different effective returns.

Is there a commonly used way that takes into account the number of days per month?

## Answer by demully (score 4)

https://quant.stackexchange.com/a/48919

Yes, there is... BUT... it’s a ton of effort, that is very unlikely to ever make any material difference.

The problem here isn’t so much that different calendar months have different numbers of calendar days. From any year to the next, different years will have a different number of trading days, depending on the accident of when weekends and public holidays fall that year. Whatever the “correct” adjustment, it will different for 2019 than for 2018, which is different than for 2017, and so on :-(

So if you’re happy to count the actual trading days every month every year, and you’re confident it will ever make a difference, here goes...

Each monthly return is obviously a sample subset of similar but slightly different sample size. From this, divide the monthly return by the number of trading days that month to give you a daily return sample estimate for that month. Given that plus the number of trading days that month, you can create a “pooled” variance estimate for multiple sample subsets combined, that takes into account the sample size that each month contributes to the aggregate.

I struggle with why anyone would bother trying, and struggle to believe it would make any noticeable difference given the inherent noise in market returns.

This plus the root 12 times monthly sigma equally miss the basic point. Imagine a month where the market was up or down 10% every day that month, but ending up flat. That zero monthly return would dampen your vol estimate, when 10% per day “coin flip” should represent 160% annualised vol over that period. To do this properly, you need higher-frequency data!

Shown in full with attribution under the source's licence. Licence: CC BY-SA 4.0 (Stack Exchange)

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.