The claim lands and the sum insured falls short. Your client is a couple of hundred grand short of what they needed, and the conversation happening across the desk right now isn’t the one you were expecting. You recommended a higher amount. You noted it in the file. They asked you to keep the premium down instead, and you arranged what they asked for.
None of that changes what’s happening in this room right now. The question isn’t whether you remember warning them. It’s what someone else, reading your file in six months or two years, can actually understand from it. Memory fades and gets argued over. A file note either shows what you recommended, why, and what the client chose, or it doesn’t. If a complaint reaches AFCA, that file is the only witness you have.
Why “properly” matters
AFCA’s published approach to broker complaints sets out what a broker’s duty of care actually covers: appropriate practices to canvass and record a client’s needs, reasonable efforts to arrange suitable cover, and properly informing the client where the sum insured falls short of what they need.
Simply sending a policy schedule with the shortfall sitting in the paperwork usually isn’t enough on its own. Verbal advice backed by written correspondence, file notes, and proof of dispatch is generally treated as sufficient under AFCA’s approach.
Translate that into what actually sits in most CRMs. A note reading “client wants lower sum insured, agreed” tells nobody what you recommended, what you said would happen if a loss exceeded that amount, or that the client understood any of it. AFCA isn’t asking every broker to collect a signed waiver. It’s asking whether the file shows an informed decision rather than an instruction taken at face value.
The six questions your file should answer
A defensible file answers six questions:
- What did your client disclose? Current values, business changes, assumptions, and any obvious gaps in what they gave you.
- What did you recommend? Name the actual sum insured or the method for reaching it, not just “increase cover.”
- Why did you recommend it? Tie the figure to the client’s circumstances and the specific risk you were addressing.
- What consequence did you explain? Record what an inadequate sum insured actually does, including any underinsurance or average provision that applies under that policy’s wording.
- What did your client decide? Capture the instruction they gave you, the reason behind it, and the cover they chose in the end.
- How did you confirm it? Follow the conversation up in writing, keep proof you sent it, and file it somewhere you can find it again.
When a complaint like this actually lands, AFCA typically wants to see the terms of engagement, any needs analysis, correspondence, file notes, and the policy documents themselves. Build the file with that list in mind, not after a complaint is already open.
A stronger record
Compare two versions of the same conversation.
A thin file reads: “Client wants to keep premium down. Agreed to lower sum insured.”
A stronger one covers the recommended position and the basis for it, the lower amount your client asked for instead, the specific consequence you discussed if a loss occurred, any questions they asked and what you told them, a clear instruction to proceed despite your advice, and a written follow-up asking them to flag anything you’d summarised incorrectly.
A signature can support that record. It can’t rescue advice nobody understood. The point isn’t a disclaimer collected for the file. It’s evidence that your client made a decision with the consequence in front of them.
This is a content framework, not a substitute for your licensee’s approved advice, disclosure, and record-keeping procedures. What’s required will vary with the client, the product, and the advice being given.
Renewal is a new checkpoint
A declined recommendation from two years ago doesn’t protect anyone at this year’s renewal. Revisit the sum insured every time, rather than rolling over the figure your client accepted last time round.
Ask what’s changed. Asset values, stock, turnover, fit-out, plant, new contracts, new locations, and the general drift in rebuild and replacement costs all move the number, usually upward.
The NIBA Code of Practice requires brokers to contact clients well before, and at least fourteen days before, their cover expires, and to take proper, timely steps to source terms and set out the client’s options. Use that contact to reissue the recommendation and record whether your client’s answer has changed.
If dissatisfaction appears
An expression of dissatisfaction can be a complaint even when your client never uses that word. ASIC’s guidance on internal dispute resolution defines a complaint broadly: dissatisfaction expressed to or about your business, where a response is expected, whether or not that’s stated outright.
Don’t argue the point from memory or reconstruct notes once someone’s unhappy with what happened. Preserve the file as it stands and escalate it through your licensee’s internal dispute resolution process straight away. Keep communicating professionally, and leave any admission or promise about the outcome to whoever holds the authority to make it.
A habit, not a one-off form
Good documentation isn’t one perfect template filled in once and forgotten. It’s a habit: clear advice, consistent records, a second set of eyes on files before a gap becomes a complaint, and someone experienced to call when a decision sits outside the usual playbook.
That’s the shape of Better Broker’s compliance and documentation support for the brokers in its network: guidance on policy wording and record-keeping, regular file audits that catch gaps before a client does, and direct help when a complaint or regulatory enquiry lands. It sits alongside a wider point about why compliance is core to long-term broker success.
How would your file read if this client challenged your advice in six months? If the answer isn’t obvious, get in touch and talk through what a stronger process looks like for your book.