Writing a Financial Planning Engagement Letter That Sets Expectations, Not Just Fees

15 September 2026·5 min read

Quick answer: A good engagement letter does more than list your fees — it sets out what the client will experience, how often you'll be in touch, what they need to bring, and what "done" looks like at each stage. Structure it in plain English with clear sections, not solicitor-style paragraphs, and use it as a relationship tool, not just a compliance document. Clients who understand what to expect complain less, ghost less, and trust you faster. 📱

Most engagement letters read like they were written to protect the practice, not to welcome the client. Fair enough — they do need to cover fees, scope and your obligations. But if the very first proper document a new client receives from you feels like fine print, you've spent your best trust-building moment on legal hedging instead of clarity. The practices that get referrals talk about their engagement letter differently: it's the moment they set the tone for the whole relationship. Get it right and it becomes something clients actually re-read when they're unsure what happens next, instead of a PDF that gets filed and forgotten. 💖

What most financial planners get wrong

The common mistake is treating the engagement letter purely as a fee disclosure exercise — dense paragraphs about remuneration, general advice warnings, and scope limitations, with almost nothing about the client's actual experience. Clients don't remember the fee clause; they remember whether they knew what was coming next. The second mistake is the opposite problem: letters so friendly and casual they lose the clarity a formal document needs, leaving genuine ambiguity about what's included in the engagement and what isn't — which is exactly what causes disputes later. The best engagement letters do both jobs at once: clear obligations, warm delivery.

The expectations-first engagement letter structure (copy this)

1. Welcome + what happens now — one warm paragraph confirming the engagement and the very next step (e.g. "Your first review meeting is booked for...").
2. What we're doing together — plain-English scope: the specific advice areas covered, written as outcomes ("helping you decide whether to salary sacrifice" not "superannuation contribution strategy advice").
3. What this doesn't cover — the scope boundary, stated plainly, so there's no ambiguity later.
4. How we'll communicate — contact method, expected response time, and how often you'll proactively check in.
5. What we need from you — a short checklist of documents/information, with a realistic deadline.
6. Fees — the actual numbers, clearly laid out, with the "why" briefly explained (what's included at each fee tier).
7. What "done" looks like — the deliverable the client will receive at the end (a written plan, a review summary, etc.) and roughly when.

Solo adviser, first-time clients: A planner working mostly with people in their first proper advice engagement (often referred by their accountant) rewrote her engagement letter to open with "Here's exactly what the next six weeks look like" followed by a simple numbered timeline. Client questions about "what happens next" during onboarding dropped noticeably, because the answer was already sitting in their inbox.

Practice with a longer, multi-stage engagement: A firm doing complex pre-retirement work split their engagement letter's scope section into phases — "Phase 1: Discovery and modelling," "Phase 2: Strategy and recommendations," "Phase 3: Implementation" — each with its own rough timeframe and fee component. Clients stopped assuming the whole process would be done in one meeting, which had previously been their biggest source of frustration.

Practice that had a scope dispute: One firm had a client push back hard when a request outside the original engagement (an unrelated insurance review) wasn't included in the fee already paid. The underlying letter wasn't wrong exactly, but the "what this doesn't cover" section was buried in dense legal language the client had clearly never absorbed. Adding a short, plain-English boundary list up front — not instead of the formal clause, alongside it — was the fix for future engagements.

How to actually write this

Draft the client experience first, the legal language second

Write the plain-English version of each section before you touch your compliance template. Once the client-facing logic is right, layer your required disclosures and warnings around it rather than starting from the legal document and trying to warm it up afterward.

Use headings a client would actually search for

"What we need from you" beats "Client Obligations." "How we'll communicate" beats "Correspondence." Small wording choices like this are the difference between a document that gets read and one that gets skimmed once and filed.

Keep the compliance clauses, just don't lead with them

Your general advice warnings, remuneration disclosures and other required content still need to be there in full — this is about sequencing and plain language, not removing anything you're obliged to include.

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

💡 The engagement letter is your first real "show, don't tell" moment. Clients decide within that first document whether you're organised and easy to work with, or whether they've just signed up for another confusing professional relationship. Treat it like a piece of client communication, not paperwork you copy-pasted from last year's template.

Mistakes to avoid

Opening with fee disclosures before the client knows what they're actually getting.
Vague scope language that sounds thorough but doesn't actually tell the client what's included.
No stated response time or communication cadence, leaving clients to guess whether silence is normal.
Reusing a template that hasn't been reviewed against current requirements — check it's current before every new engagement.
Writing it for the file, not the client — remembering someone actually has to read and understand this.

Frequently asked questions

Do we still need all our standard legal and compliance clauses if we make the letter more plain-English?

Yes, in full. Plain-English framing sections and required disclosure clauses aren't mutually exclusive — you're adding clarity around your existing obligations, not replacing them.

How long should an engagement letter be?

Here's the honest trade-off: shorter feels friendlier and gets read more fully, but if you shorten it by cutting scope detail rather than tightening the language, you're trading clarity now for disputes later. Aim to trim wording, not content — a well-written three-page letter usually beats a vague one-page letter and a vague six-page one equally.

Should the fee structure be a flat number or itemised by phase?

Itemising by phase or deliverable tends to reduce disputes because clients can see what each dollar bought, but it takes more upfront work to structure clearly — worth it for complex, multi-stage engagements more than simple ones.

Can we reuse the same letter for every client?

A consistent template is fine and sensible, but the scope section specifically should be tailored per client — generic scope language is exactly where later disagreements tend to start.

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 ✦