The one-page plan, and the binder it replaces.
At the end of a planning meeting, an advisor slides a bound report across the table. It is eighty pages. There is a cover with the client's name on it, a table of contents, a Monte Carlo fan chart, twelve pages of asset-allocation detail, an assumptions appendix, and twenty-odd pages of disclosures.
The client takes it home. They do not open it again. Not because they're incurious — because there is no entry point. Eighty pages of correct information, and not one of them answers the question they came in with.
That report is not a deliverable. It is a transcript of the software. The deliverable is the one page you could have handed them instead.
What the binder is actually for
It's worth being honest about who the binder serves. Most of it exists for the advisor, not the client: it documents that the work was done, it satisfies a compliance instinct, and it looks like value because it's heavy. Weight reads as rigor.
But weight isn't rigor, and the binder quietly fails the one job a deliverable has — to be used. A document that is never opened has not communicated anything. It has filed something. The assumptions appendix and the disclosures should exist and be available on request; they are records, and records belong in a drawer. The problem is handing the client the drawer and calling it a plan.
The one-page test
Here's the test I use. If the plan can't be expressed on a single page that a sixty-five-year-old reads once and understands, the thinking isn't finished — the page is just where the lack of finish becomes visible.
What goes on the page:
- The decisions, dated. Claim Social Security at 70. Convert $90K to Roth in each of 2027 and 2028. Draw from taxable through 2029, then begin tax-deferred. Three or four lines like that — the actual instructions for the next few years.
- The few numbers that carry weight. The guaranteed income floor in late retirement. The lifetime tax delta between this plan and the autopilot version. The first year, line by line: income in, taxes out, what's left. Not every number the model produced — the ones that change a decision.
- The one chart that earns its place. Usually a year-by-year cash-flow view, because that's the shape of the question the client is actually asking. One chart, chosen, not a gallery.
- What we're watching. The two or three things that would change the plan if they move — a tax-law change, a health event, a market drop in the first retirement years.
What gets cut from what they're handed:
- The Monte Carlo fan chart. It's a thermometer for the advisor, not a map for the client — the score is downstream of the plan, not a substitute for it.
- The assumptions appendix and the disclosures. Kept, available, referenced — not stapled to the front of the thing the client reads.
- Every number that doesn't change a decision. Most of them.
Clean is not sparse
This is the misread I want to head off: a one-page deliverable is not a dumbed-down deliverable. The page is thin; the work behind it is not.
A clean deliverable is the truth on as little paper as the truth requires. The computation underneath can be enormous — a full year-by-year tax engine, withdrawal sequencing against marginal cost, a thousand-trial simulation that varies returns and everything downstream of returns. We've written about why that distinction — cash-flow modeling versus portfolio modeling — changes the whole conversation. The one-pager is the distillation of all of it. The depth doesn't disappear; it gets concentrated.
Sparse is leaving things out because you didn't do them. Clean is leaving things out because you did the work and know which three numbers actually matter. They look similar on the page and they are opposites in the room.
Why clutter is usually a tell
After enough plans, you start to read volume as a signal — and not a good one. The eighty-page binder is frequently a sign that the load-bearing decisions were never isolated. When you haven't figured out which three moves matter, you show all of them, because you can't tell the difference. Comprehensiveness becomes a substitute for judgment. Here is everything is what you produce when you can't yet say here is what matters.
The clean version is harder to make, which is exactly why it's worth more. Anyone can export the full report. It takes understanding the household well enough to throw most of it away.
The operational case
There's a practice-management reason to care, beyond the client's experience. A clean deliverable is faster to produce — but only if the engine does the distillation, not the advisor at midnight before the meeting.
If your current process is "run the software, export the binder, then hand-translate the relevant parts into plain language for the meeting," you're doing the tool's job for it. The translation is the work, and it shouldn't be manual. The right tool produces the page, not the drawer. When choosing one, this is the framework I'd use — and the question of what it hands the client should be near the top of it.
We built Foundry Planning so the deliverable is the default output, not a thing you assemble by hand afterward. The page a client takes home is the decisions, the few numbers that move them, and the one chart that fits the question — generated from the same engine that did the modeling. If that's the kind of output you want your clients leaving with, start here.
What's next
This is the middle of three short notes. The first made the case for what a plan is actually for. The last argues they were never separate concerns: the plan is the deliverable.
Working notes on running a planning practice, written for the people who do the work. If there's a workflow question you'd like covered, support@foundryplanning.com.