Clear client email
Rewrite this email in clear, warm UK English for a financial-advice client. Keep it neutral and professional. Do not add advice or facts: [paste draft].
Useful alongside: AI Client Communications & Disclosure Register
Practical AI governance for UK financial advice firms
64 practical prompts for drafting, organising and reviewing AI-assisted work.
Free resource for UK financial advisers
Practical, copy-and-paste prompts for drafting, organising and reviewing work. They are not financial advice, regulatory advice or a substitute for your firm’s controls.
Before you use one: do not paste client-identifiable, sensitive or confidential information into a public AI tool. Review every output before relying on or sharing it.
Showing 64 of 64 prompts
Rewrite this email in clear, warm UK English for a financial-advice client. Keep it neutral and professional. Do not add advice or facts: [paste draft].
Useful alongside: AI Client Communications & Disclosure Register
Turn these bullet points into a concise post-meeting follow-up email. Separate agreed actions, documents required, and next steps: [paste notes].
Useful alongside: AI Client Communications & Disclosure Register
Explain this process to a client in plain English, using short paragraphs and no jargon: [paste process].
Create three subject-line options for this client email. Make them professional, clear and non-promotional: [paste email].
Check this email for jargon, ambiguity, overconfidence, unsupported claims and wording that could be misunderstood. Return a table of issue, reason and safer wording: [paste email].
Useful alongside: AI Accuracy & Validation Register
Rewrite this communication for a client who may be anxious about market volatility. Keep it calm and factual without giving a recommendation: [paste text].
Create a polite reminder email asking a client for outstanding information. Do not sound demanding: [list information].
Draft a concise email explaining that a member of the team will review the information before any action is taken.
Create a meeting agenda from these topics. Include client priorities, changes since last review, questions, actions and follow-up: [topics].
Turn these rough notes into a neutral internal file note. Separate facts discussed, client questions, actions agreed, outstanding information and matters needing adviser review: [notes].
Useful alongside: AI Advice & Suitability Review Register
Create a pre-meeting checklist for an annual financial-planning review. Do not include specific product recommendations.
Generate neutral questions an adviser could consider asking during a review meeting about changes in circumstances, objectives, income, expenditure and risk tolerance.
Create a checklist of documents or information that may need updating before a client review meeting.
Summarise these meeting notes into no more than 10 factual bullet points. Do not infer missing facts: [notes].
Identify unclear or incomplete items in these meeting notes that should be clarified before a formal record is created: [notes].
Draft a concise internal action list from these meeting notes, with owner, action and deadline columns: [notes].
Explain diversification in plain UK English for a client with limited investment experience. Use an everyday analogy, but do not promise reduced losses.
Explain inflation and its possible effect on spending power in simple language. Do not give investment advice.
Explain investment volatility in plain English, including why values can rise and fall.
Explain the difference between saving and investing in a balanced, neutral way.
Explain the meaning of risk tolerance, capacity for loss and investment objectives in plain English.
Rewrite this technical explanation at approximately a 12-year-old reading level, while keeping it accurate: [text].
Create a short glossary of the technical terms in this document, using client-friendly definitions: [document text].
Give three plain-English ways to explain this financial term without jargon: [term].
Create an agenda for a quarterly AI governance meeting in a UK financial-advice firm. Cover tools in use, risks, incidents, human oversight, suppliers, staff training and actions.
Useful alongside: AI Governance & Accountability Register
Turn this description of an AI use case into a short governance record. Include purpose, users, data involved, human oversight, limitations, risks and actions: [description].
Useful alongside: AI Governance & Accountability Register
Create a list of questions to ask before approving a new AI tool for use in a financial-advice business.
Review this proposed AI use case and identify governance questions that remain unanswered: [description].
Create a simple human-oversight process for this AI-supported task, including who reviews output, what they check and when the AI must not be relied upon: [task].
Useful alongside: AI Human Oversight & Approval Register
Draft a short internal policy statement on using generative AI for drafting only, subject to human review.
Create a checklist to help staff decide whether a proposed AI use should be escalated for management review.
List possible evidence a firm could retain to show that an AI-assisted activity was reviewed by a human.
Create a 10-minute staff briefing on safe use of AI in a financial-advice firm. Cover confidentiality, human review, accuracy, bias and escalation.
Write five short quiz questions for staff about safe use of AI, each with four answer options and an answer explanation.
Create three realistic scenarios where a staff member should not paste information into an AI tool.
Useful alongside: AI Client Data & Confidentiality Register
Create a short training exercise where staff spot potential problems in an AI-generated client email.
Draft a one-page AI do and do not guide for financial-advice staff.
Create a checklist for a manager to use when confirming a staff member has completed AI-awareness training.
Write a short explanation of why an AI answer can sound convincing but still be inaccurate.
Create five discussion questions for a team meeting about responsible use of AI.
Create a due-diligence questionnaire for an AI software supplier used by a UK financial-advice firm. Cover data handling, security, retention, training of models, access controls, accuracy, support and contractual terms.
Useful alongside: AI Client Data & Confidentiality Register
Turn these supplier answers into a concise risk summary. Separate satisfactory points, gaps, unanswered questions and recommended follow-up: [answers].
Create a checklist for reviewing whether an existing AI supplier has changed its terms, privacy notice or product functionality.
Draft questions to ask a supplier about where customer data is stored and whether it is used to train AI models.
Create a comparison table template for assessing three AI tools against privacy, security, cost, controls, support and suitability.
Review this supplier privacy statement and identify plain-English questions we should ask before using the service: [text].
Create a list of contractual points a firm may want to check before subscribing to an AI tool.
Draft an internal record template for approving or declining an AI supplier.
Review this draft for unsupported claims, factual uncertainty, unsuitable certainty, jargon, missing caveats and statements that require adviser approval: [text].
Useful alongside: AI Accuracy & Validation Register
Compare this AI-generated draft against the source material. List every statement that is unsupported, altered or missing: [draft] [source material].
Useful alongside: AI Accuracy & Validation Register
Create a human-review checklist for AI-assisted client communications before they are sent.
Useful alongside: AI Human Oversight & Approval Register
Identify factual claims in this text that need checking against an authoritative source: [text].
Rewrite this wording to make uncertainty clear without making it confusing: [text].
Check this draft for accidental references to the wrong client, dates, products or assumptions: [text].
Create a quality-assurance record from this review. Include content reviewed, checks performed, issues found, corrections made, reviewer and date.
Suggest questions a reviewer should ask before approving an AI-generated internal document.
Turn this account of an AI-related issue into a neutral incident record. Include what happened, when, impact, immediate action, root cause to investigate and follow-up actions: [account].
Create a near-miss record from these notes. Do not assign blame or invent facts: [notes].
Identify possible harms that could arise if this AI-generated output were used without human review: [output].
Useful alongside: AI Consumer Duty & Client Outcomes Register
Create a simple risk assessment for this AI use case. Include risk, possible impact, likelihood, controls, owner and review date: [use case].
Draft questions for a post-incident review after an AI tool produced inaccurate or inappropriate content.
Create a corrective-action tracker from this incident report, with action, owner, target date, progress and evidence of completion: [report].
Rewrite this incident description in neutral, factual language suitable for an internal governance record: [description].
List lessons learned and preventative controls from this AI near miss, without claiming that future incidents are impossible: [near-miss details].
Use the eight free RAIUC AI governance registers to record the activity, checks, decisions and follow-up around AI use in your firm.
Explore the Specialist AI Governance Packs