ChamberOne

Setting up an AI governance group in a small firm

By the ChamberOne team 4 minute read

Big firms have AI committees, working groups and steering boards. A ten-lawyer firm has a managing partner who is also the head of litigation and, on Fridays, the IT department. It still needs someone to decide which tools are approved, to hear what went wrong and to keep the rules current. The answer is not a smaller version of a large-firm structure. It is a lightweight group with a clear job.

Key points

  • Three people, one hour a month and a fixed agenda are enough for a small firm.
  • Approve tools with a standard form, classify the decision and tell everyone.
  • Make incident reporting safe, and escalate serious matters without waiting for the meeting.
  • Keep the policy short, dated and reviewed at least once a year.

Why bother

Without a named owner, AI use in a small firm grows by accident. One partner subscribes to a tool. A trainee uses a free chatbot for research. A paralegal tries a summariser on a client file. No one is sure what is allowed, what has been tried or what happened when it went wrong.

A small group fixes that. It makes decisions visible, gives staff somewhere to ask and creates a record. That record is useful if a client, an insurer or a regulator ever asks how the firm controls its use of AI. Check the guidance from your regulator or bar on supervision and technology, and use it to shape the group's remit.

Who sits on it

Three people is enough, and each should bring a different view.

  • A partner or principal who can make decisions and carry the others. They own the outcome.
  • A practitioner who uses the tools in real work and knows what is practical. Rotate this seat so that different practice areas are heard.
  • Someone responsible for information security, privacy or operations, who can read vendor terms and ask hard questions. In a very small firm, this may be an outside adviser.

One hour a month: a standing agenda

Keep the meeting short and the agenda fixed so it does not drift.

  1. 1

    Requests (15 minutes). Review any new tool or new use that someone wants approved. Decide yes, no or trial.

  2. 2

    Incidents and near misses (15 minutes). What went wrong, what almost did, what was learned. No blame.

  3. 3

    Usage (10 minutes). Which tools are in use, by how many people, and for what. Check against the register.

  4. 4

    Policy (10 minutes). Does anything in the policy need to change in light of the above?

  5. 5

    Actions (10 minutes). Who does what by when. Record and carry forward.

  1. 1Requests: decide yes, no or trial
  2. 2Incidents and near misses, without blame
  3. 3Usage: check tools in use against the register
  4. 4Policy: change anything that needs changing
  5. 5Actions: who does what by when, carried forward
  6. Then back to step 1.
The monthly governance hour

How to approve a tool

Use a short form with the same questions every time. What is the task? What information goes in? Who will use it? What does the vendor do with our data, and where? What happens if the output is wrong? Who reviews it? Is there a cheaper or safer way?

Classify the decision. Approved for general use. Approved for named uses only. Approved for a trial with a named reviewer. Not approved. Record the date, the reasons and a date for review. Tell the whole firm, in plain words, what is allowed and what is not.

Ask the vendor for written answers on data handling. Do not rely on a sales call. Where the answer matters to a client, tell the client.

Reviewing incidents

Define an incident broadly: a wrong citation caught late, client text pasted into an unapproved tool, an unreviewed draft sent. Make it easy to report, and make reporting safe. If people fear blame, they will hide mistakes, and the group will learn nothing.

For each incident, record what happened, what the impact was, why it happened and what changes. Often the cause is a gap in instructions or time pressure, not carelessness. Tell the firm what changed, without naming individuals.

Where an incident touches client information or may need to be reported to a regulator or client, escalate it at once and take advice, without waiting for the monthly meeting.

Keeping the policy alive

A policy of two pages that people have read beats one of twenty that nobody has. Cover the essentials: approved tools, forbidden uses, what must never be entered into public tools, review requirements, how to report problems and who to ask. Put the date and the version on it.

Review it formally at least once a year, and informally at each meeting. Tools, vendor terms and professional guidance change, and so should the policy. Give new joiners a short briefing, and run a refresher for everyone when the policy changes.

What to avoid

  • A group that never meets because everyone is busy. Put the date in the diary for a year.
  • A group that only says no. If every request is refused, staff will use unapproved tools in secret. Offer approved alternatives.
  • A group of senior people only. Include someone who uses the tools daily.
  • Documents that nobody reads. Prefer a one-page summary and an easy way to ask questions.

The goal is not bureaucracy. It is a firm where people know what is allowed, someone is accountable and mistakes lead to learning.

Do
  • Put the meeting dates in the diary for a year
  • Offer approved alternatives when you refuse a request
  • Include someone who uses the tools daily
  • Prefer a one-page summary and an easy way to ask questions
Don't
  • Let the group lapse because everyone is busy
  • Only ever say no
  • Make it senior people only
  • Write documents nobody reads
Keeping a governance group useful

A hypothetical example

Suppose a ten-lawyer firm has a request from an associate to use a summarising tool on witness statements. At the monthly hour, the group reads the vendor's written answers. Data is processed overseas and kept for a limited period. Training use can be switched off. The practitioner member notes that witness statements often contain health details.

The group approves the tool for internal summaries only, with training use off, no use on family or criminal matters, and a named reviewer for every output. It sets a review date three months out and tells the firm in a two-line note. The whole decision took fifteen minutes because the questions were the same ones asked every time.

Reporting to the whole firm

Once a quarter, send everyone a short note from the group: which tools are approved, what changed in the policy and what the group learned from incidents. Invite questions. A firm that hears from its governance group regularly will use it. A firm that never hears from it will assume it does not exist, and go back to doing things privately.

This article is general information about the law, legal practice and technology, current when it was published. It is not legal advice. Laws and guidance change: check the sources linked above and take advice on your own circumstances from a lawyer qualified where you are.

Read next

Setting up an AI governance group in a small firm