DBFO Tranche 2 and the Client Advice Record: what changes in how advice gets produced

A note on scope. This piece looks at what the reforms mean for the technology behind advice: templates, data, content and the client meeting. It is not legal or compliance advice, and it is not a guide to the obligations themselves. For those, check current regulatory guidance or your licensee's advice.

Most of the discussion about the Delivering Better Financial Outcomes reforms has been about the document: the move from the Statement of Advice to a shorter, more client-focused Client Advice Record. That's the visible change. When put into practice, the downstream change is to everything behind the document: the templates, data, the processes that produce it and even the medium through which it delivered.

We've been through regulatory transitions with practices before. The pattern is always the same: the practices that treat it as a document rewrite struggle; the ones that treat it as a system change come out ahead. Here's what that means in practice.

The document changes, so the templates change. Most if not all of them

A CAR is not an SOA with fewer pages. The structure is different and the emphasis is subtly different too. Every advice template the practice runs will need to be reviewed at a minimum and probably re-engineered, reimagined, not just trimmed.

For a practice with one set of templates, that's a project. For a practice with several (different advice types, multiple brands, legacy versions nobody has retired) it's a programme, and it's where advice production can grind to a halt if the templates are the "nobody dares touch them" kind.

The practices best positioned for this kind of change are the ones whose framework is maintained and centrally managed, where a structural change can be made once and flow through to all its downstream counterparts. If your templates are a collection of disparately patched files, these reforms could be the moment to fix that, not work around it.

"Shorter" can also expose you if the data is not right

A shorter, more focused record has less room to hide problems. When a 60-page SOA contains a stale balance or an outdated contact detail, it's one line among thousands. In a tight, client-focused record, the same error is on the page the client actually reads.

That raises the stakes on data quality. The health of your datafeeds, client record completeness and the routines that keep them trustworthy stop being housekeeping and become part of your brand value compliance positioning. If advisers currently re-check data before every document is presented due to trust issues, the reforms make that cost, and that risk, more visible, not less.

All content needs to be reviewed and potentially re-written, and then maintained

Content like strategy paragraphs and educational material that go into advice documents will need to be reviewed for the new format and the new expectations around client understanding. That's a large body of content for most practices, and it's content that will keep changing as guidance settles.

Practices on our framework have their strategy and education library reviewed and updated for regulatory currency three times a year. Whatever your arrangement, the principle holds: this content is a maintained asset with an owner, not a folder of Word files that gets edited when someone remembers.

The record gets shorter. The meeting should get better

There's an opportunity in the reforms that's easy to miss. The intent behind a more client-focused record is better client understanding. A shorter document helps. But understanding mostly happens in the meeting, and the meeting is where most practices still read the document aloud pointing at complicated tables and passages.

This is a good moment to separate the two jobs: the record does what the regulation requires; the presentation does what the client needs. Tools like AdviceStudio turn the advice document you've produced into a branded, interactive presentation for the meeting, while leaving the document of record untouched. Slides in the presentation footnote reference the original advice document so the client can refer back to it for additional context. The reforms change what you must give the client. They don't stop you from also giving them something they'll remember.

A practical sequence

If you're planning your transition, this is the order we'd suggest:

1. Audit your templates. How many are there, which are actually used, which can be retired before they're converted.
2. Fix the data first. Clean records and healthy feeds before the new templates go live, not after.
3. Re-engineer the framework once. Structural changes made centrally, flowing to every template and brand.
4. Rebuild the content library with an owner and a review cycle.
5. Rethink the meeting while you're rethinking the document.

If you'd like to talk through where your practice sits against that list, a free Advice Tech Health Check is a sensible place to start. We've done this transition before; we'll tell you plainly what we'd prioritise.