ASIC File Notes: The 4 Elements AU Advisers Miss

File notes are usually treated like admin. That is the mistake.

In practice, file notes are the operational backbone of defensible advice. When advice is reviewed, challenged, remediated, or handed over, the file note is often the clearest record of what happened, why it happened, and what the adviser relied on at the time.

That matters more now than it did a few years ago. Adviser numbers have fallen from 28,900 in 2018 to around 15,135 in March 2026, a 48% reduction. The FAAA has been clear that adviser and paraplanner shortages are structural, not cyclical. Firms are carrying more work with fewer experienced hands, and documentation is where that pressure shows up first.

Across the firms we work with, the pattern is consistent. Advice teams know record-keeping matters. They also have inconsistent habits, different templates, patchy meeting capture, and file notes that depend too heavily on individual judgement.

That inconsistency is the real problem.

A weak file note is rarely the result of adviser laziness. More often, the rationale, client context, disclosures, and evidence trail were simply never captured in a repeatable way. One adviser records three paragraphs. Another records three lines. A paraplanner fills the gaps from memory. Compliance tries to interpret intent after the fact.

That is where risk creeps in.

ASIC has been clear for years that record-keeping is part of the advice obligation, not separate from it. ASIC RG 175 governs conduct and disclosure for financial product advisers. For personal advice, RG 175.307 to 175.311 and 175.333 to 175.338 set out key expectations around records and the basis on which advice is given.

More recently, ASIC Corporations Instrument 2024/508 updated record-keeping requirements. Section 912G(7) requires records of the information relied on to demonstrate client interest priority. That wording matters. Showing the recommendation alone is insufficient. You need to show what information was relied on in getting there.

This is where firms need a more operational view of compliance. A file note should be a structured business record, not a free-text diary entry.

The simplest way to think about it is through four elements. If your file note consistently captures these four, you are in a much stronger position with compliance, supervision, remediation, and client servicing.

The Four Elements of ASIC-compliant file notes

1. Client circumstances

Start with the client's relevant circumstances at the time the advice was given.

This sounds obvious, but it is where many file notes become too generic. "Discussed retirement goals" is a useless record. "Client intends to retire at 62, expects $85,000 p.a. net spending, has no debt, and wants to retain access to capital for aged care contingencies" is a useful one.

Capture the facts that actually shaped the advice. That usually includes:

If it is further advice, record what has and has not changed. That is especially important where a Record of Advice, or ROA, is used instead of an SOA.

An ROA can substitute for an SOA in three situations:

Teams often know these scenarios in principle, but the file note fails to evidence why the ROA pathway was appropriate. If you are relying on an ROA, the file note should state the basis for that reliance in plain terms.

2. Basis for advice

The second element is the reasoning behind the advice.

This is where you connect the client's circumstances to the recommendation. Many file notes jump from meeting discussion straight to action items. That leaves out the most important part: the adviser's judgement.

Capture:

This does not need to be a long essay. It does need to show a rational chain.

For example, if a client is moving from accumulation to pension phase, the file note should record more than "recommended account-based pension". It should capture the factors considered: income needs, tax treatment, estate planning preferences, liquidity needs, social security impacts, and whether alternatives were assessed.

The same applies to insurance, debt recycling, contribution strategies, platform changes, and portfolio adjustments. The basis for advice should be visible to someone reviewing the file later who was not in the room.

Here is the test I use with firms. Could a competent reviewer understand the recommendation and the reasoning without asking the adviser to reconstruct it from memory six months later.

If the answer is no, the file note is unfinished.

3. Disclosure obligations

The third element is disclosure. This is where firms often rely too much on templates and too little on evidence.

Templates matter. They create consistency. They do not prove a disclosure occurred.

Your file note should record relevant disclosures made to the client, including:

If the client made a decision after a discussion about trade-offs, record that discussion. If the client chose a lower cover amount after affordability concerns were explained, record it. If implementation was delayed because the client wanted time to consider tax consequences, record it.

A defensible file shows what was explained, what the client understood, and how that affected the next step. Attaching a document and assuming it speaks for itself is a different thing entirely.

4. Information relied on

The fourth element has become more important with the updated record-keeping focus, especially under s912G(7).

You need to capture the information relied on to demonstrate client interest priority. In practice, that means keeping a clear record of the inputs that informed the advice and the selection process.

This may include:

A good file note can reference the source documents relied on, provided the links are clear and the records are retrievable. The point is not duplication. It is evidentiary integrity.

If someone asks, "What information did you rely on in concluding this was in the client's interests and prioritised appropriately", the answer should be available from the file itself.

This is the free consulting bit

Once teams understand the four elements, the next issue is operational. What should go into the note every time.

Here is a practical minimum standard I recommend.

Record the meeting context. Date, time, attendees, adviser, and whether the interaction was in person, by phone, or video.

Record the purpose of the interaction. Annual review, further advice, insurance needs analysis, contribution strategy, pension commencement, implementation follow-up, or something else specific.

Record the client's current position and any change since the last advice interaction. Be precise. If nothing material has changed, say that and note the basis for that conclusion.

Record the decisions under consideration. This keeps the file note anchored to the actual advice issue.

Record the recommendation and the reasoning. Include assumptions, alternatives considered if relevant, and any scope limits.

Record disclosures and warnings provided. Especially where advice is limited, product replacement is involved, or the client declines part of a recommendation.

Record the information relied on. Reference the documents, modelling, research, or client instructions used.

Record the client response. Agreed, requested time, declined, asked for revision, or approved implementation.

Record next steps and responsibility. Who is doing what, by when.

That sounds simple because it is. The difficulty is consistency across every adviser and support team member, every time.

Why inconsistency gets worse under pressure

The adviser shortage has changed the economics of documentation.

When a practice is stretched, file notes get delegated, delayed, shortened, or completed from fragments. That is understandable. It is also where quality drops fastest.

Paraplanners feel this pressure acutely. They are often reconstructing advice intent from meeting recordings, emails, CRM entries, and half-finished notes. Compliance teams then inherit variability that is hard to supervise at scale.

This is one reason AI adoption has accelerated so quickly in advice businesses. Current data shows 74% of Australian practices are using or planning to use AI, and 59% are already using it. Among use cases, file notes have the highest AI penetration at 86%.

That pattern makes sense. File note generation is time-intensive, repetitive, and structure-dependent. AI is well suited to turning a transcript or meeting summary into a first draft.

Used properly, it can standardise output and reduce the blank page problem. Used poorly, it can create polished records that are incomplete, inaccurate, or impossible to defend.

ASIC is increasingly warning about unregulated AI use in financial decisions. That should be taken seriously. A generated file note is still your record. If the AI inferred facts that were never said, omitted a disclosure, or mischaracterised the client's priorities, the risk sits with the firm.

This gets even more important as consumer trust in AI rises. CALI research from March 2026 found that three in five Australians would trust AI-generated financial advice. Consumer trust does not reduce the obligation on firms to supervise how AI is used in advice processes.

Where AI fits in file note production

AI can help produce better file notes. It does not remove the need for adviser judgement.

The right use of AI in this context is narrow and practical:

The wrong use is treating AI output as a finished compliance record without review.

In most firms, the best model is human-led, AI-assisted. The adviser or authorised staff member remains responsible for verifying that the note accurately reflects the interaction, the basis for advice, and the information relied on.

That review step should be explicit in your process.

I also recommend firms avoid generic prompting for file notes. Generic prompts produce generic records. Build a standard structure aligned to your advice process, your approved wording, and your supervision expectations.

For example, if your team regularly uses ROAs, make the AI workflow require an explicit field for why the ROA path is available. If your compliance reviews focus heavily on client interest priority, require the workflow to capture the source information relied on and any alternatives considered.

This is where firms often need more than a tool. They need operational design.

At AdviseWell, that is the part we spend most time on: helping firms turn compliance expectations into repeatable workflows and AI-assisted processes that still preserve review, accountability, and evidence quality. The technology matters. The process design matters more.

related: Automate the full SoA

A practical standard for defensible file notes

If you want a simple test for your current file notes, use this.

Take ten recent client files across different advisers. Remove the adviser's personal context and read the notes cold.

Can a reviewer identify:

If those answers come easily and consistently, your process is working. If they depend on who wrote the note, your firm has a process design problem.

File notes are the record that holds the advice process together when memory fades, staff change, clients complain, or ASIC asks for evidence.

The firms that do this well tend to treat file notes as part of advice production. The shift from "admin after the meeting" to "part of the advice workflow" sounds small. Operationally, it changes everything.