Designing a One-Page Client Summary to Accompany the Statement of Advice

11 October 2026·6 min read

Quick answer: A one-page client summary isn't a replacement for the Statement of Advice — it's a plain-English companion that sits alongside it, written so the client signing off can say back, in their own words, what's being recommended and why. It covers what's changing, what it's likely to cost, what it's meant to achieve, and what happens next, in around 400 words a client can read in a few minutes. Used well, it turns sign-off from a paperwork moment into an understanding moment. ✨

Most Statements of Advice are long for a good reason — they carry real disclosure and compliance weight — but that's exactly why almost nobody reads one line by line in the room where they're signing it. That's not a client failing; it's a document-design gap, and a one-page summary sitting in front of the SOA is one of the simplest trust-building habits a practice can build into its sign-off process. 💖

What most practices get wrong

Treating the SOA as the client-facing document — it's built to satisfy disclosure obligations, not to be skimmed in a 45-minute appointment.
Writing the summary in SOA language — if it still reads "the recommended strategy involves...", it hasn't actually been translated.
Only producing one for "complicated" clients — the client with a simple super consolidation deserves a plain-English summary just as much as the client running six strategies at once.
Sending it after the meeting instead of into it — the summary does its best work before the pen comes out, not in a follow-up email three days later.
Letting it drift into marketing copy — a summary that oversells the plan is worse than no summary at all; it has to mirror the SOA faithfully, just in simpler words.

Copy-paste one-pager template (fill in per client):

What we're recommending, in one sentence: [plain-English summary of the core strategy]

Why we're recommending it: [the goal it connects to, in the client's own words from your fact-find]

What it's likely to cost you: [advice fees and any product or platform costs, in dollar terms where you can]

What we're NOT recommending, and why: [one line — this shows judgement, not just a yes]

What happens next: [implementation steps and a rough timeframe]

Three questions worth asking before you sign: [the adviser fills in three genuinely useful prompts]

That's the whole skeleton — six short answers, no SOA jargon, nothing a client has to re-read twice. Here's how it plays out for three different practices.

A 2-adviser practice running back-to-back SOA presentations on Thursdays: they built the one-pager as a template inside their SOA software, pre-filled by the paraplanner straight from the SOA draft, so prep time barely changes. Clients now open it on their phone before the appointment starts and arrive with questions instead of arriving cold.

A sole-practitioner planner billing flat-fee for comprehensive advice: with no paraplanning team, she writes the summary herself as the very last step of drafting the SOA, treating it as a comprehension test for her own strategy — if she can't compress it onto one page without losing the logic, the strategy usually needs simplifying before the client ever sees it.

A practice with mostly pre-retiree clients weighing up transition-to-retirement or account-based pension strategies: because these clients are juggling several moving numbers at once, their one-pager leads with "here's what changes on your pay slip" and "here's what changes in your super" as two short lists, rather than describing the mechanics of the strategy at all — the detail stays in the SOA, the summary just answers the question the client actually came in with.

How to build it without duplicating your SOA

Draft the one-pager after the recommendations section of the SOA is locked, not before, pulling language straight from the client's own stated goals in the fact-find rather than inventing new phrasing. Reference where in the SOA a point is explained in full ("see page 12") rather than restating risk warnings yourself. Keep a paraplanner drafting it as a standard step in the SOA workflow, with the adviser reviewing it alongside the SOA at final sign-off, not as an afterthought. And never let the summary introduce anything — a number, a product name, a timeframe — that isn't already sitting in the SOA. Legally, the SOA is the advice document; the summary is a readability layer on top of it, nothing more.

Please note: general information, not financial advice — check current official guidance before relying on it.

💡 Heads up: keep one line on the summary itself stating it's a plain-English companion to the Statement of Advice and doesn't replace it. That protects the client, who then knows where the full detail and risk disclosures actually live, and it protects you, because the summary is never mistaken for a stand-alone advice document.

Mistakes that undercut the one-pager

Numbers that don't match the SOA — even a rounding difference between the two documents creates confusion at exactly the wrong moment.
A static template nobody updates — when your fee structure or approved product list changes, the summary template needs updating alongside your SOA templates, not six months later.
Skipping compliance review — because it "isn't the advice document", it's tempting to skip sign-off on the summary too; don't. Get it checked the same way you'd check any client-facing material.
Using it to avoid walking through the SOA at all — the summary supports that conversation, it doesn't replace talking the client through the real document.

Frequently asked questions

Does a one-page summary replace our obligation to make sure the client understands the advice?

No — honest answer: a one-pager is a comprehension aid, not a substitute for the adviser actually walking the client through the SOA and checking understanding in the room. It makes that conversation easier, but the obligation to ensure the client understands what they're agreeing to still sits with the adviser, not with the document.

Will this work for a complex, multi-strategy SOA?

It works best as an overview even for complex advice, but a genuinely complex SOA with four or five interacting strategies may need a one-pager that summarises each strategy in a single line rather than trying to explain all of them in full. The goal is orientation, not completeness — don't force every detail onto one page just to keep the format.

Who should write it — the adviser or the paraplanner?

Either can draft it, but whoever signs the SOA should read the final summary against it line by line before it goes to the client. Any mismatch between the two documents is the adviser's to catch, not the paraplanner's alone.

Does this need to go through compliance the same way the SOA does?

Treat it as client-facing advice-related material and run it past whatever review process your practice already uses for SOAs and other advice documents. Because it summarises specific advice given to a specific client, it should get the same level of scrutiny, even if it doesn't need the same sign-off paperwork.

Keep reading 🤍

Written by

Kate, founder of Chronically Online

I help Gold Coast and Brisbane businesses grow with branding, websites and marketing that actually works.

Work with me ✦