Turn a banking meeting into reviewed actions, with consent first

A worked approach to AI notes that separates what was discussed, what was agreed and what still requires a decision.

The most dangerous sentence in a meeting summary may be a small one: the customer agreed. A conversation can include questions, possibilities and unfinished thoughts that never become instructions. AI notes can help staff remember a meeting, but the workflow must preserve those distinctions.

Morgan Stanley announced a consent-based meeting summariser that drafts follow-up material. JPMorganChase describes employee drafting through LLM Suite. UK authorities' survey shows AI is used across financial services. These sources establish real institutional activity; they do not validate the fictional note-taking process that follows. [Meeting tool](https://www.morganstanley.com/press-releases/ai-at-morgan-stanley-debrief-launch), [employee platform](https://www.jpmorganchase.com/about/technology/blog/llmsuite-ab-award), [survey](https://www.bankofengland.co.uk/report/2024/artificial-intelligence-in-uk-financial-services-2024).

In this teaching example, a banking relationship manager meets the owner of a fictional bakery. The owner wants to understand documents needed for a business service. Recording is optional. Before the meeting, the manager explains what will be captured, who can access it and the review process. If the owner declines, the manager takes ordinary notes. Consent is a real step, rather than a sentence added after a recording already exists.

The AI draft uses separate headings: information supplied, questions raised, actions agreed and unresolved points. The bakery owner says they might expand next year. The assistant can place that under context. It must not turn it into an approved finance application or a firm borrowing requirement. Another statement, I can send the registration document on Thursday, can become a proposed follow-up action for the manager to confirm.

Every action includes a responsible person and, when actually discussed, a date. Where the date is absent, the assistant leaves it blank. It should not fill Friday into a neat table because empty cells look unfinished. If several people spoke, a reviewer checks attribution against the transcript. Incorrectly assigning a commitment can be more harmful than omitting a decorative summary sentence.

The relationship manager compares the draft with their own notes and the recording where appropriate. They correct misunderstandings and remove irrelevant personal details. The reviewed summary is then shown to the customer through an approved communication process. A draft email remains a draft until the manager approves it. A model's suggested attachment is not sufficient authority to send confidential documents.

One difficult test involves a conditional statement. The owner says they will send a document if their accountant approves. A useful note retains the condition. Another test uses overlapping speakers and a poor connection; the assistant should mark unclear speech instead of guessing. Include names that sound alike, amounts said in different currencies and a date corrected later in the conversation. These are evaluation cases the organisation can construct with consenting volunteers and fictional content.

A note-taking system must also handle failure politely. If transcription stops halfway, tell the manager that the draft covers only part of the meeting and allow manual completion. Preserve any safe work already reviewed. Do not label the meeting fully summarised when important passages are missing. A support reference can help operations staff investigate without exposing internal service errors to the customer.

Set retention deliberately. A recording, an unreviewed draft and a final approved record need not have identical access or lifetime. The bank's responsible teams should establish the rules appropriate to its obligations. A reviewer should be able to tell which version was approved and whether a later edit changed the agreed action. Removing unnecessary copies reduces confusion as well as exposure.

Evaluate the process by checking action accuracy, conditional statements preserved, attribution errors and corrections required. Also ask whether staff can spend more attention on the customer without missing important facts. Do not use a vendor's adoption number as a substitute for that evaluation. An internal rollout may have different data, controls and staff training from another organisation.

The cited tools are institution-specific. Their announcements do not establish public subscriptions, current prices or permission to upload customer meetings to another provider. A local pilot needs approved infrastructure and a clear cost for recording, storage, transcription and review. Manual notes remain a valid option where these conditions are absent.

The best result is a record that both parties recognise: this was discussed, these actions were agreed, and these questions remain open. AI helps prepare that record. It earns trust through careful review and meaningful consent, rather than through the apparent completeness of the first draft.