The Minister for Financial Services has said it plainly. DBFO reforms remain a priority, but Shield and First Guardian have made the environment "more complex," and there are no firm timelines for Tranche 2.
In other words, don’t hold your breath; you might be waiting a while. The proposed new class of adviser may not survive in its current form. Remaining reforms, including the best interest duty amendments and SOA replacement, if they proceed, will be integrated into a broader consumer protection package alongside managed investment scheme governance, lead generator regulation, and CSLR redesign. This means they might not receive the focus or changes needed.
That is a long legislative queue. Practices waiting for DBFO before improving their operations are making a bet on political delivery that the Minister himself is unwilling to guarantee.
This shouldn't surprise anyone. Since the Wallis Inquiry in 1997, major regulatory reform in financial advice has taken four to seven years from recommendation to implementation. The QAR was finalised in late 2022. The only reforms fully delivered since then are education standards, which were largely industry-driven, and Tranche 1 fee consent changes, which were procedural (and needed fixing). Everything that requires structural change to the advice process itself has stalled.
The good news is that most of what DBFO promises is already available under current law. Here are four areas where practices can act now.
Area | The Opportunity | What to Do Monday Morning |
|---|
SOA Simplification | Current law (s947B/C) requires just seven elements in an SOA. ASIC's RG 175 requires advice documents to be "clear, concise and effective." Nothing mandates a 120-page document. That is a compliance culture problem, not a legislative one. | Separate client-facing advice from compliance file notes. Design the document around scope, advice, reasoning, and cost. Keep everything else in the file, not in the client's hands. You can do this today. |
Data Collection | Most practices re-enter the same client data across fact finds, file notes, modelling, paraplanning instructions, SOAs, applications, and CRM. Each re-entry is a cost and an error risk. | Map every point where client data is entered or re-entered. Build toward a single-entry model in which a single client interaction generates the fact find, file note, and paraplanning instructions without re-keying. This is where AI and meeting transcription tools deliver their real value. |
Consumer Learning Formats | Clients do not read 120-page documents. They learn through conversation, visual tools, and short-form summaries. The current SOA format is designed for compliance, not comprehension. | Explore how you present advice to clients: video summaries, interactive scenario tools, and one-page advice summaries backed by detailed file records. The law prescribes content, not format. Use that flexibility now. |
Professional Year Integration | The Professional Year is an underused practice development tool. Most practices treat PY candidates as a compliance obligation rather than a capacity multiplier. | Design PY roles around your advice process bottlenecks. A well-structured PY programme builds your next generation of advisers while freeing experienced practitioners to focus on client relationships and complex advice. |
None of these need new laws. None depend on regulatory certainty. They require a decision to stop considering the current practice as fixed until parliament says otherwise.
What links all four areas is a problem the Quality of Advice Review clearly identified: practices have been creating their advice documents to satisfy compliance, not to assist clients in making decisions. AFCA told the Review that SOAs are "primarily drafted with an eye to legal requirements and the needs of the advisory firm's compliance department, rather than a consumer-centric document." Michelle Levy went further, concluding that current law already allows for clear, concise advice documents, and that it is the conflation of client communication with compliance evidence that causes the issue, not the legislation itself.
That distinction, between what a client needs to understand and what an adviser needs to keep on file, is not a DBFO reform. It is a design choice available to every practice today. The same logic applies to data collection, client communication formats, and how PY candidates are deployed. Practices already implementing these changes are not waiting for permission. They treat DBFO as validation of a direction they've already taken, not as a starting signal.
The important question isn't "When will DBFO arrive?" but rather "What would my practice look like if I stopped waiting for it?"
