Rebalancing for small RIAs: calendar, drift bands, or both?
A rebalancing rule is the written condition that tells you when a portfolio goes back to its target allocation. Small RIAs usually use a calendar (for example quarterly), drift bands (trade when an asset class moves a set distance from target), or a hybrid that checks on a calendar and trades only when a band is breached. Any of these can be reasonable; what matters operationally is one rule per model, written into the model and the IPS, with records that show each rebalance followed it.
Someone looks at an account and asks why it went eight months without a rebalance while the rest of the model traded twice. The adviser knows the answer: the client had a large capital gain and asked to wait. But the reason is in the adviser's memory, not in the file, and nothing in the file says what the rule was in the first place.
What are the common rebalancing approaches?
The three common approaches are calendar, drift bands and a hybrid of the two. Each is a different answer to "when do we trade back to target".
| Approach | How it works | Operational note |
|---|---|---|
| Calendar | Rebalance on fixed dates, for example quarterly | Easy to schedule; may trade when little has drifted |
| Drift bands | Rebalance when an asset class moves a set distance from target | Needs regular monitoring of drift |
| Hybrid | Check on a calendar, trade only if bands are breached | A predictable review with fewer trades |
This post doesn't recommend one over another. The choice depends on the strategy, trading costs, taxes and your clients. What it covers is how to write down and run whichever one you pick.
Where should the rule be written?
The rule should be written in three places, and the three should agree.
- In the model: the frequency or the bands, as part of the model's definition and its versions.
- In the IPS: so accounts following the model carry the same rule in the client document.
- In your procedures: who reviews drift, how often, and who approves trades.
The most common gap is between the first two. The model changes, gets a new version, and the IPS still describes the old rule.
A worked example
Take a two-person RIA with about 120 households and a balanced model with a 60% equity, 40% fixed income target. The firm and its numbers are hypothetical. Its rule is a hybrid: check every account in the model on the first business day of each quarter, and trade only where equity is more than 5 percentage points from target.
| Account | Equity weight at check | Outcome | Recorded reason |
|---|---|---|---|
| A | 63% | No trade | Within band |
| B | 66% | Rebalanced to 60% | Band breached by 1 point |
| C | 67% | Skipped | Client request to defer gains until January; reviewed next quarter |
| D | 58% | No trade; new cash deposit directed to equity | Within band; cash flow used |
Every account in the model gets a line, including the ones that didn't trade. Account C is the one that matters later. Without the recorded reason, a skipped account looks like an oversight. With it, it looks like a decision.
What should the rebalancing record show?
The record should show enough for someone to check the trades against the rule without asking the adviser.
- The date of the review.
- What triggered the rebalance: the calendar date, or the drift that breached a band.
- The trades placed, linked to the model and the version in force.
- Any accounts skipped and why: cash needs, tax reasons, client restrictions.
Where does this usually go wrong?
- The rule lives in the adviser's head rather than in the model or IPS.
- The model changes but the IPS still describes the old rebalancing rule.
- Skipped accounts are never recorded, so the exception looks like an oversight.
- Bands are defined loosely, so two people checking the same account reach different answers.
Trade-offs
A pure calendar rule is the easiest to document, because the trigger is a date nobody can dispute. It can mean trading accounts that barely moved. Drift bands trade only when needed but require someone to watch drift between dates, which is real work without a tool that does it. The hybrid sits in between: a fixed review date, with fewer trades. For a one-person firm with a handful of models, a calendar or hybrid rule is usually easier to keep than continuous band monitoring. That is an operational point, not a view on which produces better results.
How Advorra supports it
In Advorra, each versioned model carries its rebalancing rules alongside allocation, benchmark and philosophy; a rebalance tracker and rebalance goals record the work; and trades on the blotter are tied to the strategy they implement. Trade execution stays with your custodian. If you want your next quarterly check recorded against the model's rule, see the product page, or read about the trade blotter.
An operational guide, not investment advice.
Questions advisors ask
Should every model use the same rebalancing method?
Not necessarily, but using one method across all models is simpler to run and to explain. If a model needs a different rule, write down why.
Are drift bands measured in percentage points or as a percentage of the target?
Either, as long as the model says which. A 5-point band on a 60% target and a 20% relative band on the same target trigger at different levels, so the definition has to be explicit.
What about accounts with new cash or withdrawals?
Some firms use cash flows to move toward target before trading. Record it as part of the rebalance if that's your rule, so the trades still trace back to it.
Do I need to rebalance accounts that are within bands at a calendar check?
Under a hybrid rule, no, and the record should say they were checked and left alone. That entry is what shows the rule was followed.
Is this investment advice?
No. It is an operational guide to documenting a rebalancing approach. Investment decisions are the adviser's.
See it on a demo firm
Advorra is practice software for independent RIAs: clients, models, IPS, billing and compliance records in one place, on top of the custodian you already use. Built by The CollabHub.
Get in touch