Back to the blog

Writing your firm’s AI use policy: what to include

Which tools staff may use, for which tasks, with what information, and who checks the result: a practical AI use policy people can follow.

Three law firm colleagues reviewing a short printed guidance document together at a meeting table

People in your firm may already be using AI, whether through a firm account or a personal tool on their phone. If nobody has set clear rules, they may be making their own decisions about what is suitable for work.

An AI use policy addresses that gap. It tells staff which tools they may use, for which tasks, with what information, and who checks the result. It need not be long. A short, practical document that people read is more useful than a lengthy one filed away.

The Law Society’s guide Generative AI: the essentials recommends setting out what each tool is for and what data can go into it. That is a sensible place to begin.

Start with what people are already doing

Before you write anything, find out how AI is being used in your firm today. Ask each team a short set of questions. Keep the tone neutral, so people answer truthfully rather than defensively.

  • Which AI tools have you used for work in the last three months?
  • Were they firm accounts or personal ones?
  • What tasks did you use them for?
  • Did any client names, documents or personal data go in?
  • Who checked the output before it was used?

The answers tell you what the policy needs to cover. They may also reveal a confidentiality or data protection issue that needs to be escalated under the firm’s existing incident process.

What the policy should cover

Keep the structure simple. Each section should answer a practical question a fee earner or assistant might ask.

Approved tools

List the tools staff may use for firm work, by name, account type and approved configuration. Say that unapproved tools and accounts must not be used for client work. Assess the actual terms and settings; the account’s price alone does not establish whether it is suitable.

Check whether software the firm already pays for, such as Microsoft 365, includes a suitable AI feature. For each approved tool, record who vetted it and when. Check confidentiality terms, retention and deletion, access controls, where data is processed, and whether inputs may be used to train models. Our article on keeping client information safe when using AI covers these questions in more detail.

Permitted and prohibited uses

Be specific. “Use AI responsibly” gives nobody much to act on. A short task list works better than general principles. For example, a firm might adopt these rules:

  • Permitted with reviewFirst drafts of client update letters, document summaries, chronologies and meeting notes, using approved tools and permitted information.
  • Additional approval requiredAI-assisted work to be filed at court or sent to an opponent might require a supervising partner’s approval.
  • Not permittedGiving AI-generated advice to a client without a competent person checking it, or uploading client documents to an unapproved tool.

These are examples of internal controls, not a universal list of regulatory requirements. Your firm’s rules should reflect the work, the risks and any applicable court or client requirements. A trainee should be able to read them and know whether a task is allowed.

Information rules

Say what may and may not go into each tool. Use fictional examples when testing tools or building templates. Removing names alone may not make a document anonymous.

Check confidentiality, privilege, data protection obligations and the client’s engagement terms before using client information. Some clients restrict AI use in their outside counsel guidelines. A supplier’s promise not to train on inputs does not settle these other questions.

Ask the person responsible for data protection to assess each proposed use. A data protection impact assessment is required before processing begins where the processing is likely to create a high risk to people’s rights and freedoms. Record the assessment and the reasons for deciding whether a DPIA is needed.

Review and responsibility

Treat AI-assisted work as unchecked until an appropriate person has reviewed it. Name the role responsible for that check, not just “the user”. Using AI does not remove a solicitor’s professional responsibility, including responsibility for work they supervise.

Spell out what checking involves. Open and read the sources. Compare facts with the file. Verify legal propositions, citations and dates before relying on them. Our guide to checking AI outputs sets out a reviewer’s checklist you can adapt.

Records

Set a proportionate record-keeping rule for substantive AI-assisted work. Record the tool, what it was used for, who reviewed the result and the outcome of that review. A brief note may be enough for a simple task; higher-risk work may need a fuller record.

Follow the firm’s retention and security rules, preserving the evidence needed to explain how the work was prepared and checked. Avoid unnecessary duplicate copies of confidential prompts or outputs, while retaining anything required for supervision, legal obligations or a dispute.

Telling clients

Decide what to tell clients about AI use and where to say it. The Law Society recommends clear communication, where appropriate, about when and how AI tools are used. Client care letters or terms of business may be appropriate, but a general clause may not address a particular client’s instructions or a specific use.

Agree the approach with whoever owns those documents. Check when further explanation or permission is needed, rather than assuming that generic wording resolves every confidentiality or contractual question.

Making the policy stick

A policy that sits on the intranet changes very little. Plan how people will learn it and how you will know it is working.

  • Name an owner. Choose someone with the authority to maintain the policy and approved tools list, working with the firm’s compliance, IT and data protection leads.
  • Show people how it applies. Walk each team through the rules in a short session, using fictional examples of tasks from their own work.
  • Make approval requests straightforward. Give staff a clear way to ask about a tool or proposed use, and tell them who will respond.
  • Set a review timetable. Six-monthly reviews may be a starting point. Review sooner when tools, settings, supplier terms, work or relevant guidance change.
  • Check what happens in practice. A quarterly sample of files may help you see whether AI use and review are recorded. Adjust the frequency and scope to the risk.

Cover both practical skills and professional responsibilities in training. A short exercise where people find the mistake in an AI draft can show whether they understand the checks, not just the software.

Keep it proportionate

A ten-person firm does not need the same document as a national practice. Start with the tools you actually use and the tasks people actually do. Add to the policy as you approve more uses.

If you are piloting AI with one team, keep the pilot’s permissions and checks specific to that work, alongside clear rules for everyone else. Test the approach before extending it. The examples on our AI uses page can help you decide which tasks to cover first.

Common questions

Should we simply ban AI until the policy is ready?

Pause unapproved uses, particularly where client information is involved. An interim note can explain the restrictions, how to ask questions and which uses, if any, have already been assessed and approved. If no suitable tool has been approved, do not approve one merely to fill the gap. Keep staff informed while the assessment is completed.

Does the policy need to cover support staff?

Yes. Secretaries, paralegals and finance staff handle client information too. Write the policy so it applies to everyone working on firm matters, including contractors, with rules suited to their access and responsibilities.

Is this the same as our information security policy?

It should sit alongside it and refer to it. Keep the AI policy focused on tools, tasks, information, review and records, so staff can find the answer quickly. Make sure the documents agree on access, retention and incident reporting.

Put agreed AI rules into daily practice.

Legal Edge can help you understand how AI is being used, assess and implement suitable tools, and train your teams to use them with appropriate checks. Scope and fees are agreed before work starts.

Talk to Atif

Sources and further reading

Last reviewed: 1 November 2026. The professional guidance cited is for England and Wales; firms should check the requirements that apply to their jurisdiction and work.