Answer

A financial advisor client meeting notes template is a record that separates

When a financial adviser or planner looks for a client meeting notes template, many expect a form for transcribing the conversation as-is. What practice actually needs, though, is neither a transcript nor a paragraph that justifies a conclusion after the fact. Client meeting notes are a record that separates who said what, when, what was explained, what remains unverified and who does what next. That idea of separating is the starting point for a financial advisor client meeting notes template.

Put differently, a meeting note is not a replay of the exchange but “a bundle of facts, observations, inference and proposals organised into a form you can follow later”. What the client stated, what the adviser observed, what a document backs up, a view not yet confirmed, and a general idea the adviser offered: labelling these distinctly, without mixing them, lets you verify later whether the client said it or the adviser judged it. Meeting notes are one domain within financial document templates that span everything from trading records to client-ready drafts, and you can see the whole picture in the Financial Document Templates Guide.

What this article covers is the fields, types and separation of information in the record. It does not judge whether a specific product suits a given client, whether it is acceptable to solicit, or whether KYC/AML is complete. Those requirements vary by country and region, registration category, scope of business and product, and should be confirmed and decided against official sources for the relevant jurisdiction, your firm’s procedures and a qualified person. Every figure, table and mini-tool value shown is a fictional educational case, not a real client, financial institution, product or contract, and not a finished document you can file or send as-is. Reading alongside the Financial Templates Hub adviser and planner templates makes it easier to place each field.

Terms and purpose

Terms and purpose: what to field out in the record

Once you treat a meeting note as a record that separates, the fields to keep become clear. As the skeleton common to any financial planning meeting notes structure, hold these fields distinctly. Each is the minimum needed to make the record “something anyone can follow later”.

• Basics: date and time, participants, meeting purpose, documents used. Record who attended, for what purpose, and which documents were referred to during the conversation.
• Client-stated facts: objectives, horizon, experience, constraints and other things the client said. Keep them strictly as declarations, “the client said so”.
• Two risk axes: record risk tolerance (psychological willingness) and capacity for loss (financial headroom) as separate fields.
• Explanations and questions: what the adviser explained, and questions the client raised. Important explanations are sometimes kept as facts rather than summaries.
• Open items: things that could not be confirmed at the time of the meeting. Do not leave them blank; attach an owner and a due date.
• Follow-up and shared version: who does what next, and which version was shared with whom and when. This is the starting point for follow-up.

These are “record fields”, not a list of legally mandatory records. Which fields to keep, and how far, varies by country, registration category, scope of business and product. Document design for the referral and onboarding stage that precedes client engagement is covered in the introducing broker onboarding templates article, and organising the basis, disclaimers and approval of client-facing claims is covered in the financial advertising review checklist article.

Five-stage flow

Five stages from before the meeting to follow-up

A meeting note does not begin and end at the moment of the meeting. From preparation through to ongoing follow-up, what you check changes at each point in time. The SVG below shows the five-stage flow of before the meeting, during the meeting, immediately after, before sharing and follow-up (it scrolls horizontally). Separating “what to check” at each stage reduces gaps in the record.

The pivot of this diagram is stage 3, organising immediately after the meeting, and stage 4, review and approval before sharing. Because you cannot get everything perfectly ordered during the meeting, you label and surface open items immediately after, then split versions and pass review and approval before sharing. Skip this, and at the follow-up stage you cannot trace “what was left unverified” or “which version was handed over”. In the sections that follow, we look first at how to separate statements and documents (labels), then at how to record the two risk axes.

Labelling

Label statement, evidence, observation, inference and proposal

The single most important thing in a meeting record is making explicit “what type each entry is”, even within one sentence. When you keep it as a record of client explanations, mixing what the client said with what the adviser judged makes later verification impossible. The SVG below sorts the information from the fictional case meeting into five labels (it scrolls horizontally). Types are distinguished not by color alone but by label name and symbol.

The effect of this labelling is that you do not later mistake “fact”, “observation” and “inference” for one another. Writing a client’s declaration as an established fact, or an adviser’s inference as if confirmed, causes misunderstandings in the next steps and at handover. In particular, attach an owner and due date to inference (4), and state clearly on a proposal (5) that “this is general information, not individual advice”. Show labels not by color alone but also with words such as [declared] [evidence] [observation] [inference] [proposal], so they remain distinguishable in print or monochrome.

Two risk axes

Do not confuse risk tolerance with capacity for loss

A particularly easy mistake in meeting notes is treating risk tolerance and capacity for loss as the same thing. In the context of suitability documentation, confusing the two changes what the record means. They are different, and are recorded as separate fields. The table below is a general explanation of the difference between the two (it scrolls horizontally).

The point is to record tolerance mainly from “client statements and adviser observation” and capacity mainly from “objective evidence and confirmed facts”, keeping them in separate fields. One being high does not make the other high. And crucially, a template only helps you record these two axes separately; it does not auto-generate a suitability conclusion or a risk score from them. Suitability is judged separately, by a qualified person, in line with the requirements of the relevant jurisdiction and your firm’s procedures. Designing the documentation of risk itself is covered in detail in the trading risk management plan template article.

A consistent fictional case

A fictional case meeting record and timeline

Let us run everything so far through a single fictional case. The copy, tables and tool that follow all use the same names, dates and states.

Ridgeline Advisory (a fictional FP firm) holds a first asset-building consultation with a client (meeting reference M-2026-038, anonymous). The meeting purpose is to organise objectives and confirm risk, and the theme is the general idea of long-term asset building. The client’s declarations are “I want to prepare education funds in 10 years” and “short-term price swings make me a little uneasy”. The record of this meeting is organised along the timeline below.

Reading this timeline, you can see how the content recorded in the 07-08 meeting is labelled in the 07-09 organising step and carried into the 07-11 client-shared summary. If the detail of annual income and outgoings is unverified as of 07-08, leave unverified in the record and confirm and update it in follow-up. Rather than ghost-writing a long finished set of minutes, holding this kind of heading structure, short field examples, before/after review differences and unverified flags is what makes a meeting record verifiable later.

Version difference

Internal record versus client-ready summary matrix

Even for the same meeting, the internal record and the client-ready summary differ in purpose, level of detail and included information. Handing a financial adviser’s client memo straight to the client leaks internal notes that should not be seen. The table below is a matrix of the differences between the two (it scrolls horizontally). Do not reuse one document; split the version by audience.

In short: do not mix adviser inference or internal memos into the client-ready summary, and do not drop the unverified information the internal record needs for verification. Summarise for the client, in plain terms, what was explained, what was confirmed and the next actions, while keeping observation, inference and open items with their basis internally. Enforce this separation and you reach a state where you can trace “which version was handed to whom and when” later. Ways to split versions, and the thinking behind differences and approvals, are covered in detail in the document version control, approvals and audit-trail article.

Action register

The open-item action register

The core of a follow-up document is not leaving open items blank. Unverified items are kept as an action register that carries an owner, due date and state. The table below turns the open items remaining at the time of the meeting in the fictional case into a register (it scrolls horizontally). Rather than blanks, it is obvious at a glance who will confirm what by when.

With this register, at the follow-up stage it is immediately clear “what, by whom, by when” needs confirming. Conversely, leaving these blank in the body of the meeting record makes it impossible to tell confirmed from unverified, and is a cause of misreading them as established. A template helps make such missing unverified fields visible, and to track them by type (unverified, inference, awaiting review, awaiting approval) separately. That said, a filled register does not mean a suitability judgment or legal compliance is done. The register is a tool for tracking “what is unresolved”, not a substitute for the judgment itself.

Mini-tool

The meeting-record field mapper

Choose the meeting purpose, broad client type, participants, topic, whether a shared version is needed, open items and the internal review stage, and it shows the record sections to keep, the labels to attach to statements and documents, the owner and due-date fields, and a guide to the pre-share check. This is teaching material for getting a feel for the workflow; it does not produce a suitability verdict, a client classification, or a KYC/AML pass or fail. Even with JavaScript disabled, the default selections and static output example below show how to read it.

This mapper is a simplified teaching aid for getting a feel for the article’s workflow. It may differ in places from the real service’s template names, sections and features, and it does not cover every combination of purpose and topic. Do not enter sensitive information such as a client’s name, address, date of birth, account number or identity-document number (the tool neither transmits nor saves input). Confirm the formal templates and features in the free Financial Templates Hub.

Failure modes

Failure modes and review steps

The easy places to stumble on meeting notes are the following. Each happens when you drift from the principles of “separate by type”, “keep open items” and “split versions”.

• Drifting toward a transcript so the key points get buried: transcribing the conversation as-is takes time to write, and open items and next actions become invisible. Keep the key points and their basis in a structured form.
• Mixing declaration with observation and inference: writing a client declaration as an established fact, or an adviser’s inference as if confirmed, causes later misunderstandings. Make the type explicit with labels.
• Confusing tolerance with capacity: combining psychological willingness and financial headroom into one field changes what the record means. Record them in separate fields.
• Leaving open items blank: a blank is misread as confirmed. Keep unverified with an owner and due date on the register.
• Reusing one document for client and internal use: internal memos and inference leak to the client. Split the internal record from the client-ready summary.

As review steps, before sharing, work top to bottom: “Is the audience correct?”, “Have inference or internal memos leaked into the client version?”, “Are open items kept with owner and due date?”, “Do numbers, dates, proper nouns and mandatory wording match?” Templates and QA help check for such unfilled variables, wording, structure and the presence of disclaimers, but they do not guarantee legal compliance, safety, client suitability or KYC/AML completion. Passing the check does not mean a suitability judgment is done, that it will pass a review, or that it can withstand an audit.

In the Hub

In the Hub: Free to Pro to Premium

Once you understand how to separate a meeting record, check the actual adviser and planner templates in SG Group’s Financial Templates Hub. Use scales up in stages as your work expands.

1. Confirm and use the structure on Free: with free templates you can use without registration, confirm how a meeting record is built from fields and labels, and use basic QA to spot gaps. The “separate by type” and “keep open items” skeleton of this article can be grasped here first. Confirm the specific templates and outputs available on the free page in the implementation.
2. Use it repeatedly on Pro: put the current adviser and planner templates to work, using multilingual output such as Japanese and English, QA that checks for missing entries and mandatory wording, several output formats, and a defined period of local output history. This is the stage when you shape the same style of meeting record every time.
3. Run client-specific and approval workflows on Premium: use operational features such as client-specific template sets, version control and diffs, multi-stage approvals, branding and approved standard wording, client and case workspaces, and evidence such as hashes and manifests. This is the stage when meeting volume grows and you need to manage client-specific shared versions with approvals and evidence.

The scope, number of languages, history period and account limits of each feature can change, so do not fix them in the copy; confirm the latest against the plans page as the single source of truth. A template is a drafting aid, not investment, legal or tax advice, a regulatory-compliance determination, a suitability judgment, or a substitute for a review or audit. Related cost calculation and macro background are covered in the FX and CFD lot size calculator guide, the trading cost calculator guide and the macro analysis guide. Record design for trading plans and journals is covered in the trading plan template article and the trading journal template article, and recording an investment thesis in the investment thesis template article.

Summary

Summary: answering the core query and your next step

What you really need behind “financial advisor client meeting notes template” is not a transcript form, but a design that separates the record by type and by point in time. Along the five stages of before the meeting, during, immediately after, before sharing and follow-up, label client statements, objective evidence, adviser observations, inference and proposals; record risk tolerance and capacity for loss as separate fields; and do not fill the unverified with a guess. That is the skeleton of an adviser or planner meeting note.

In practice, get these five points right and you will not go far wrong: (1) label statement, evidence, observation, inference and proposal; (2) do not confuse the two risk axes; (3) keep open items on a register with owner and due date; (4) split the internal record from the client-ready summary; and (5) separate sensitive information from the body. Required items change by country and region, registration category, scope of business and product, and a template does not guarantee suitability or compliance, so always make the judgments with official sources, your firm’s procedures and a qualified person. Start by confirming, in the free Hub, the structure of the same kind of template as this article’s fictional case.

Related articles

Related reading

Related cluster: the whole template picture is in the Financial Document Templates Guide, and you can find templates from the English article index. Strategy-testing records are covered in the TradingView backtesting guide.