Skip to content
All library documents

Portfolio Rebalancing Corridors and Dynamic Allocation

Article Quant Q&A · Author: Stefan Voigt
Read the original

Summary

The document compares calendar-based portfolio rebalancing with threshold-based corridors. Fixed schedules such as monthly rebalancing are simple, but weights may drift substantially between dates. A corridor approach monitors deviations from target weights and trades when they exceed a chosen band. Corridor width depends on trading costs, asset correlations, and volatility: higher costs or correlation support wider bands, while greater volatility supports narrower ones.

It also describes limitations of setting independent thresholds for each asset. Portfolio holdings move together, so a trade decision may depend on other assets’ movements, and a single-period corridor choice can ignore the chance of further trading soon after. Dynamic programming can address this multi-period balance between tracking the target and minimizing costs. The discussion argues that transaction-cost and correlation inputs may be more stable than return forecasts, and mentions a method for scaling dynamic programming to larger portfolios. No empirical results or implementation details are supplied.

Key ideas

  • Calendar rebalancing risks allowing portfolio weights to drift between scheduled trades.
  • Corridor rebalancing triggers trades when allocations move outside chosen bands.
  • Higher transaction costs and stronger asset correlations generally support wider corridors.
  • Higher volatility generally supports narrower corridors.
  • Dynamic programming can model multi-period tradeoffs between allocation drift and trading costs.

Tags

Portfolio constructionRisk managementExecution
Full text
# When to adjust portfolio weights?


# When to adjust portfolio weights?












In portfolio allocation literature there is lot of effort made in obtaining 'better' portfolio weights, for example via improving parameter estimates, introducing Bayesian approaches, incorporating constraints in the optimization procedure or by incorporating other predictive variables. However, in most empirical horse races (for example the famous work of DeMiguel et al) monthly reallocation is considered. Especially when taking transaction costs into account, most of the models fail as they loose performance due to estimation risk and the extreme weights cause high turnover. Therefore I am primarily interested in approaches that specify when to rebalance your portfolio instead of searching for fancier optimization techniques. What approaches do you know that monitor portfolio weights for 'structural breaks' in the allocation and help to specify the timing of reallocation?

## Answer by rhaskett (score 2, accepted)

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

vega captures the two most common solutions to this problem.

There are some valid criticisms of corridors as well. Because assets are correlated within a portfolio the decision to trade a particular asset should actually depend on the movements of other assets rather than having a corridor per asset. Also, finding the right corridor is often done using various forms of single period analysis, but this is really a multi-period problem (if I trade now what are the chances I'll have to trade next period).

Multi period dynamic balancing problems can be solved using dynamic programming. This solution really gets at the main tradeoff between tracking and costs. I realize this is to some extent this sounds like trading one "fancy optimization" for another, but the cost and correlations inputs are much more stable than return estimates so optimization can be expected to perform closer to the goal. Kritzman et. al. found a great trick to make dynamic programming scalable for larger portfolios as well.

## Answer by vega (score 3)

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

I think generally there are two approaches: "calendar rebalancing" (such as monthly as you mention) and "optimal corridor width".

For the first option, the danger is the portfolio could stray considerably from your benchmark between rebalancing dates.

For the second option, track tactical deviation on a continuous basis. When you are outside the corridor, then rebalance. The corridor size depends on:

- Transaction cost (higher cost -> wider corridor)

- Correlations (higher correlation amongst portfolio assets -> wider corridor)

- Volatility (higher volatility -> narrower corridor)

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.