Why the file note is the proof of process
Section 961B(1) requires a provider to act in the best interests of the client when giving personal advice to a retail client. Section 961B(2) sets out the safe harbour: a series of steps that, if followed, satisfy that obligation. The steps include identifying the client's needs and objectives, making reasonable inquiries, conducting a reasonable investigation into relevant products, and basing all judgements on the client's circumstances.
None of that process is visible from the SOA alone. An AFSL compliance review, an AFCA complaint, or an ASIC investigation will look at the file note to find out what actually happened in the conversation. If the note does not show the process, the process may as well not have occurred. The scenarios below all share the same core problem: the process was weak, missing, or inadequately recorded. For the full list of safe harbour steps, see s961B safe harbour steps explained.
Scenario 1 - no investigation of alternatives on the file
What happened
An adviser recommends a platform-based superannuation product to a client who is consolidating three old super funds. The recommendation is documented in the SOA. The file note records the client's objectives and the recommended product's features. It does not record which alternative products were considered, or why they were less suitable.
What went wrong
Safe harbour step (e) in s961B(2) requires the adviser to conduct a reasonable investigation into the financial products that might achieve the client's objectives and meet their needs. If that investigation occurred but was not recorded, the file cannot show it happened. If it did not occur, the step was skipped entirely. Either way, the file fails to answer the question a reviewer will ask: what else did you look at, and why is this the best option for this client?
What good looks like
The file note records the investigation, not just the conclusion. It names the product categories or specific products that were considered, the criteria applied (cost, investment options, insurance availability, admin features), and the reason the recommended product was preferred on those criteria for this client's circumstances. Even a brief, structured entry covers this: "Considered three platform options. Option B and C excluded because of higher ongoing fees relative to the client's balance and no access to direct equities, which the client requested." That is a defensible file.
Scenario 2 - scope quietly wider than the note
What happened
A client comes in to discuss life insurance. During the meeting, the conversation drifts into estate planning and whether the client's existing will reflects their current wishes. The adviser makes comments about estate planning structure. The file note covers only the insurance discussion. The SOA is limited to insurance.
What went wrong
Any part of the conversation that constitutes personal advice on a financial product or financial situation is covered by the best interests duty. Advice given outside the stated scope but within the meeting is still advice. If the file does not record it, there is no documented process to support it. The client may later act on what was said, or a complaint may arise from it, and the file will show nothing.
What good looks like
The note captures what was actually discussed, not just the pre-agreed scope. Where the conversation moved beyond the original scope, that is noted explicitly - whether advice was given or deferred, and what follow-up is required. If the estate planning discussion was exploratory only and no personal advice was given, note that too. The record should reflect the meeting, not an idealised version of it.
Scenario 3 - assumptions instead of reasonable inquiries
What happened
A new client completes a fact find. The employment section lists their occupation as "self-employed" with no further detail about income stability or business structure. The adviser does not follow up on these gaps. The note records the client's annual income from the fact find and proceeds to recommend income protection insurance at a benefit amount and wait period based on that figure.
What went wrong
Safe harbour step (c) in s961B(2) requires the adviser to make reasonable inquiries about the client's relevant circumstances. For a self-employed client, income stability, business continuity, existing business expenses insurance, and cash reserves are all relevant to the appropriateness of income protection design. Without those inquiries, the recommendation is built on an incomplete picture. The s961G appropriate advice duty also fails - you cannot reasonably conclude the advice is appropriate to circumstances you did not properly establish.
What good looks like
The note records the gap and what was done about it. "Client identified as self-employed. Follow-up questions asked during meeting: business type (sole trader), annual revenue range, existing business overhead insurance (none), whether income fluctuates significantly (yes, Q4 higher). Income figure of $X confirmed as approximate average. Wait period set at 90 days to reflect the client's stated cash buffer of approximately 3 months." That note answers the inquiry question. It also shows the recommendation was calibrated to what was actually found out.
Scenario 4 - a conflict disclosed but not prioritised
What happened
An adviser recommends a managed investment product that pays a higher trail commission than two comparable alternatives. The FSG discloses that the adviser's licensee receives commissions from product issuers. The file note records the recommendation and notes the disclosure was made. It does not record how the conflict was managed or why the recommended product was chosen despite the conflict.
What went wrong
Section 961J requires that where a conflict exists between the interests of the client and the interests of the provider or an associate, the provider must give priority to the client's interests. Disclosure alone does not satisfy s961J. The obligation is to act in a way that prioritises the client, and to be able to show that the conflict did not drive the recommendation. A file that records the disclosure but not the management of the conflict leaves open the question of whether the client's interests actually came first. See best interests duty for financial advisers for more on how conflicts must be handled across the whole engagement.
What good looks like
The note records the conflict explicitly and explains how it was managed. "A conflict was identified: the recommended product pays a higher trail than alternatives A and B. The product was recommended because [specific client-centred reasons: investment menu breadth, lower buy-sell spread, better alignment with client's stated preference for direct equities exposure]. The conflict did not drive the recommendation. Alternatives A and B were assessed and excluded for [reasons]. The client was informed of the conflict and the basis for the recommendation." That entry addresses s961J directly and shows the client's interests were prioritised on the merits.
Scenario 5 - advice appropriate on paper but the reasoning is missing
What happened
A client in their mid-50s asks for advice on transitioning to retirement. The SOA recommends a transition to retirement income stream and a shift in the portfolio to a balanced risk profile. The file note records the client's age, account balance, and that a TTR was recommended. It does not record why a balanced profile was selected rather than a growth or conservative profile, or what the client said about their risk tolerance and retirement timeline during the meeting.
What went wrong
The advice may well be appropriate. But appropriate under s961G means a reasonable person could conclude it is appropriate to this client, given the best interests process was followed. If the file does not show the reasoning connecting the client's circumstances to the recommendation, the appropriateness cannot be demonstrated from the record. The recommendation looks reasonable in the abstract; it is not evidenced as reasonable for this client.
What good looks like
The note captures the client's stated risk tolerance, their investment horizon, their income needs in the transition period, and any constraints they mentioned. Then it connects those facts to the recommendation: "Client stated they are uncomfortable with large short-term losses and expect to draw on the TTR income stream within 2 years. Growth profile assessed - higher volatility inconsistent with the client's stated risk appetite at this stage. Conservative profile considered - likely insufficient growth to maintain real value over a 10+ year remaining investment horizon. Balanced profile selected as best fit given the client's tolerance, timeline, and income objectives." That is the reasoning s961G is looking for, and the what to record in a financial advice file note article covers how to structure these entries.
Scenario 6 - the note written from memory days later
What happened
An adviser sees four clients in a day. Notes are written at the end of the week from memory. By then, two of the meetings have blurred together and the notes for one client include a detail that belongs to another. The note for the third client does not record the client's specific concern about a previous investment loss, which was the context for the risk profile discussion during the meeting.
What went wrong
A file note written days after the meeting is not a contemporaneous record. Under RG 175, ASIC expects notes to be made as close to the meeting as possible. A delayed note is harder to defend as accurate. If a complaint arises, the client's recollection and the note may differ, and a note written days later carries less weight than one created on the day. The missing detail about the previous investment loss is also a substantive gap: it is the kind of client circumstance that bears directly on the risk recommendation, and its absence from the file leaves the reasoning incomplete.
What good looks like
The note is created the same day, ideally immediately after the meeting while the conversation is fresh. It captures what the client said - including concerns, preferences, and constraints they raised - not just the factual data the adviser collected. A contemporaneous note written from the actual transcript of the conversation is the most defensible record, because it reflects what was said rather than what the adviser recalls was said.
Summary: failure patterns at a glance
| Failure pattern | Which duty or step | What the note should show |
|---|---|---|
| No investigation of alternatives on the file | s961B(2)(e) - reasonable investigation | Products considered, criteria applied, why the recommended product was preferred for this client |
| Scope quietly wider than the note | s961B(1) - best interests across the full engagement | What was actually discussed, whether personal advice was given outside the stated scope, and any follow-up required |
| Assumptions instead of reasonable inquiries | s961B(2)(c) - reasonable inquiries; s961G - appropriate advice | Gaps identified, follow-up questions asked, what was established and how it shaped the recommendation |
| Conflict disclosed but not prioritised | s961J - conflicts priority rule | The conflict named, how it was managed, the client-centred reasons the product was recommended despite it |
| Advice appropriate on paper but reasoning missing | s961G - appropriate advice | The client's circumstances, the explicit reasoning linking those circumstances to the recommendation, why alternatives were less appropriate |
| Note written from memory days later | RG 175 contemporaneous record expectation; accuracy of s961B(2)(c) fact-finding on file | A note created the same day, reflecting what the client actually said, not a reconstructed summary |
For the complete list of safe harbour steps and what each one requires on the file, see s961B safe harbour steps explained. The best interests duty file note checklist gives you a practical reference for every client meeting.
How CallNote turns near-misses into defensible files
Most of the failures above are not failures of knowledge. The adviser knew what they were doing. The problem was the file did not capture it: the inquiry that happened but was not recorded, the reasoning that was sound but never written down, the note that was accurate but constructed days too late. The file note is the proof of process, and a process that was not documented is a process that cannot be defended.
CallNote receives a call transcript - from Dialpad, Aircall, a voice memo, a paste, or an email - and generates a structured file note from it. It never records your call. Your phone system or meeting platform produces the transcript; CallNote turns it into a draft note built around the elements that matter for best interests compliance: client circumstances and objectives, the subject matter discussed, alternatives considered, the recommendation and the reasoning behind it, conflicts noted.
Because the draft is generated from the actual transcript, the note reflects what was said in the meeting, not a reconstruction from memory hours or days later. You review the draft, refine the reasoning where needed, then lodge and lock. The locked note is timestamped, SHA-256 sealed, and added to an append-only audit log. Any later addition is recorded as an amendment, not an overwrite. The scenarios above - no alternatives on the file, missing inquiry details, reasoning absent - become visible in review before the note is lodged, when there is still time to fill the gap rather than after a complaint has been filed.
CallNote is hosted in AWS Sydney, uses AES-256 encryption, and never trains AI on your data. For how the same note satisfies the broader best interests framework, see best interests duty for financial advisers. For the full scope of what to capture on every file, see what to record in a financial advice file note. The for financial advisers hub has the full context.
Common questions
What is the best interests duty in s961B of the Corporations Act?
Section 961B(1) of the Corporations Act 2001 requires a provider to act in the best interests of a retail client when giving personal advice. Section 961B(2) sets out the safe harbour steps - a series of specific actions (identifying needs, making reasonable inquiries, investigating products, basing judgements on the client's circumstances) that, if followed, satisfy the obligation. The steps are the process; the file note is how you prove the process happened.
What does "reasonable investigation" mean under s961B(2)(e)?
Safe harbour step (e) requires the adviser to conduct a reasonable investigation into the financial products that might achieve the client's objectives and meet their needs. In practice, this means considering alternatives, applying relevant criteria (cost, features, suitability), and being able to explain why the recommended product was preferred over others for this specific client. The investigation needs to appear on the file, not just in the adviser's mind.
Does disclosing a conflict satisfy the obligations under s961J?
No. Section 961J requires the adviser to give priority to the client's interests where a conflict exists between those interests and the interests of the provider or an associate. Disclosure is required, but it does not satisfy the obligation to act in a way that prioritises the client. The file note needs to show how the conflict was managed and why the recommendation was driven by the client's circumstances, not the conflict.
How long after a meeting should a file note be written?
ASIC's RG 175 expects notes to be made as close to the meeting as possible - ideally the same day. A note written days later from memory is harder to defend as accurate if a complaint arises. A note created from the actual transcript of the conversation is the most defensible record, because it reflects what was said rather than a reconstruction of it.
What is the difference between the SOA and the file note for best interests purposes?
The SOA is the advice document - it tells the client what you recommend. The file note is the process document - it captures why the recommendation is appropriate to this client's circumstances, what was investigated, what the client said, and how conflicts were handled. Regulators and AFCA read both. A thorough SOA with a thin file note is a weak file, because the process behind the recommendation cannot be demonstrated from the SOA alone.