Portfolio Rebalance Exception Log
Last verified: 2026-07-07
A portfolio rebalance exception log is a simple record of the times you did not rebalance even though your plan said you were close to doing it.
That sounds boring. It is also useful. Most portfolio drift does not happen because one decision was obviously reckless. It happens because a few reasonable-sounding exceptions stack on top of each other until the account no longer matches the plan.
The goal is not to rebalance mechanically at all costs. Taxes, spreads, cash needs, position size, and changing facts can all matter. The goal is to stop undocumented exceptions from becoming a hidden strategy.
What a rebalance exception is
A rebalance exception is any decision where the portfolio crossed a review trigger, but you chose not to trade yet.
Examples:
- ▸A stock sleeve target is 20%, the review band is 25%, and the sleeve is now 27%.
- ▸A single position grew above the written concentration cap.
- ▸Cash fell below the planned buffer, but you did not refill it.
- ▸A taxable sale would create friction, so you delayed the rebalance.
- ▸A new deposit is coming soon, so you plan to rebalance with cash flow instead of selling.
None of those are automatically wrong. The problem is when the reason lives only in your head.
Why exceptions need their own log
A portfolio plan is only useful if you can tell the difference between discipline and drift.
Without a log, every exception can sound smart in the moment:
- ▸“I will wait for a better price.”
- ▸“The tax impact is annoying.”
- ▸“This position is still working.”
- ▸“I will fix it next month.”
Some of those reasons may be valid. Some may be avoidance. The exception log makes the difference visible later.
The five fields to capture
Keep the log short enough that you will actually use it.
| Field | What to write |
|---|---|
| Trigger | Which rule or band was crossed? |
| Current weight | What is the portfolio exposure now? |
| Planned action | What would the normal rule suggest reviewing? |
| Exception reason | Why are you delaying or changing the action? |
| Recheck date | When will this exception expire? |
The recheck date is the most important part. An exception without an expiration date can quietly become the new plan.
Example: concentration exception
Assume a portfolio has a rule that no single stock should stay above 12% without review. One position rises to 15% after a strong move.
A weak note says:
Holding for now.
A better exception log says:
| Field | Example |
|---|---|
| Trigger | Single-stock weight above 12% review band |
| Current weight | 15% |
| Planned action | Review trim, new cash allocation, or updated cap |
| Exception reason | Upcoming earnings call may update thesis; no immediate cash need |
| Recheck date | Review after earnings call transcript and updated position weight |
That note does not tell you what to do. It tells future-you why the rule was paused.
Separate tax friction from thesis drift
Taxable accounts can make rebalancing messy. Selling appreciated positions may create realized gains. Selling losing positions may involve tax-loss harvesting considerations. Those details are source-sensitive and should be checked with current tax rules and a qualified tax professional when needed.
For the exception log, keep the distinction clean:
- ▸Tax friction means the rebalance action has a cost.
- ▸Thesis drift means you are changing the reason for holding.
- ▸Behavior drift means you do not want to make the decision.
Those are not the same thing. If the real reason is tax friction, write that. If the real reason is “I am emotionally attached to the winner,” write that too.
Use cash flow before forced selling when possible
Many long-term investors can rebalance partly with new deposits, dividends, or withdrawals instead of immediate selling.
Example:
- ▸Target: 60% stock, 30% bonds, 10% cash.
- ▸Current: 66% stock, 26% bonds, 8% cash.
- ▸Monthly contribution: $1,000.
Instead of selling stock immediately, the investor may direct the next deposits toward bonds and cash until the weights move closer to target. That can reduce friction, but it still needs a written review date. Otherwise “rebalance with future deposits” becomes “never rebalance.”
Exception rules that keep the plan honest
Use these guardrails:
- ▸Every exception gets an expiration date.
- ▸No exception can be renewed without a fresh written reason.
- ▸If the same exception repeats three times, the original rule needs review.
- ▸If a position crosses a hard risk limit, the exception log is not a loophole.
- ▸Review the exception list before adding new risk.
This keeps the log from becoming a permission slip for ignoring the plan.
Common mistakes
The biggest mistake is writing the exception after the outcome is already known. That turns the log into a story instead of a control.
Other mistakes:
- ▸Using vague reasons like “market conditions.”
- ▸Forgetting to record the actual weight or dollar exposure.
- ▸Leaving exceptions open-ended.
- ▸Treating tax friction as a reason to ignore concentration forever.
- ▸Changing the portfolio target without labeling it as a plan change.
How Bucko fits
Bucko can help you keep rebalance bands, exception notes, screenshots, cash-flow plans, and review dates in one educational research workspace. The point is not for Bucko to make allocation decisions for you. The point is to make your own rules, exceptions, and follow-up reviews visible.