The most under-used IPS section is the REBALANCING POLICY clause -- the rule for when and how to restore target weights. A good rebalancing clause has three components. (1) A trigger -- either time-based (rebalance every quarter / every year), threshold-based (rebalance when any asset class drifts more than X percentage points or Y percent of its target weight), or hybrid (annual rebalance plus interim threshold trigger). Threshold-based is operationally more efficient because it skips rebalances when nothing has drifted; time-based is simpler to communicate. (2) A tolerance band -- how big the deviation must be before the trigger fires (5 percentage points is a common default for major asset classes; 25% of target weight is the common percent-based equivalent). (3) A tax-awareness clause -- prefer rebalancing with new contributions and dividend reinvestment first (zero-cost), use tax-loss harvesting opportunities, and only sell taxable winners when the threshold demands it. The clause is short -- 4-6 sentences -- but doing without it leaves rebalancing to discretion, and discretion is exactly what the IPS exists to override.
Required nominal return = ((1 + required_real_return) * (1 + inflation)) - 1
The defaults above ($80K spending / $2M portfolio / 2.5% inflation) recreate the canonical 4% rule case. Real return required = 80,000 / 2,000,000 = 4.00%. Nominal return required = ((1.04 * 1.025) - 1) = 6.60%. This is the calculation that anchors the IPS return-objectives section -- before any discussion of equity-vs-bond weights, the required nominal return tells you what the portfolio must earn to fund the plan. Drag spending up to $120K and watch the verdict shift to STRESSED: real return required becomes 6.00%, nominal 8.65%, which is well above what a 60/40 portfolio has historically earned -- meaning the IPS must surface this gap to the client and force a trade-off conversation (lower spending, work longer, accept higher risk of plan failure, or shift to higher equity allocation with larger drawdown risk). The math is the prompt for the conversation.
Going Deeper -- four IPS failure modes that show up in practice. (1) Written and never re-read: the IPS gets signed at account opening and lives in a drawer; the advisor never references it during quarterly reviews; it has zero behavioral protection value. Fix: re-read at every review, even for 60 seconds. (2) Missing rebalancing clause: the policy says nothing about when to rebalance, so rebalancing becomes ad-hoc discretion; over time the portfolio drifts and the advisor has no objective basis to push back on client reluctance. Fix: write the clause; trigger + tolerance + tax-awareness. (3) Returns-revised, not life-revised: the IPS gets updated chasing recent performance instead of in response to actual life events; the document becomes a lagging indicator of bias instead of a leading indicator of commitment. Fix: separate revision triggers ('life event' vs 'preference change') and require the second category to come with a written reason. (4) Cross-link with portfolio module: corpval and portfolio paths (port-3, port-4 if present) cover the asset-allocation math that the IPS commits to; the IPS is the policy, the asset-allocation work is the implementation. Treat them as two sides of one job. AI prompt for self-review: 'Given this client KYC summary, draft a one-page IPS covering all six RR-LTLU sections plus a rebalancing-policy clause, in 250 words or fewer.' Next module turns from the document to the end-to-end onboarding workflow that operationalizes everything we have built so far.
Sit with the ideas.
A client's IPS specifies a 60% equity / 40% fixed-income target allocation, with a 'rebalance when any asset class drifts more than 5 percentage points from target' rule. After a strong equity year the portfolio is 70% equity / 30% fixed income. The client says they are reluctant to sell winners and would rather wait for fixed income to catch up. Under the disciplined IPS framework, what should the advisor do?