AI notetakers and client confidentiality at a small law firm

Short answer: A small law firm should approve an AI notetaker for a specific account, plan and type of client call before admitting it. Our recommendation is to keep a notetaker out of a confidential call until the responsible lawyer has reviewed data handling and decided what to tell the client. ABA Formal Opinion 512 makes the confidentiality analysis depend on the particular tool and representation, rather than giving a product-wide approval. Ask your counsel to settle applicable professional rules, recording requirements and the client-consent decision before a pilot uses client information.

Obsidian Ridge offers the assessment below. The approval worksheet and test sequence are our practical recommendations; the ABA opinion is the cited professional-responsibility source.

Key facts

• Can an AI notetaker join a client call? Our recommendation is conditional approval for a named use, not automatic admission because an employee installed it. Use the decision checklist below.
• The ABA's starting point: Opinion 512 ties the analysis to “the client, the matter, the task, and the GAI tool used to perform it.” ABA Formal Opinion 512, page 6, issued July 29, 2024; checked November 3, 2026.
• Consent has substance: The opinion says, “When consent is required, it must be informed.” ABA, page 7, checked November 3, 2026. Have counsel decide what that requires for the proposed call.
• A product name is not an approval record: Our worksheet records the plan, account owner, participants, storage and sharing decisions. Compare the questions with the existing AI-tool evidence pages.
• The decision needs an owner: Assign a lawyer to approve use and an administrator to demonstrate the settings. Put the resulting staff instruction in the AI policy builder.

Which notetaker, on which plan, for which calls?

Start with one ordinary task: producing a draft note for the lawyer who attended a client meeting. Write that task down before choosing a product. A transcript, a short summary and an automatically sent follow-up are different proposed outputs. Approve each output and destination explicitly, even if a single setup screen offers all three.

Our recommended approval unit is the combination of tool, plan, work account and meeting type. Record the exact subscription shown in the firm's account, who administers it and which features the pilot will use. Leave unknown settings marked as unknown. A colleague's recollection of what a vendor promised on another plan is not evidence for this one.

For a first review, use the existing evidence pages for Otter.ai, Fireflies.ai, Read AI and Zoom AI Companion as routes to their dated vendor sources. Those pages are starting points for questions, not a list of notetakers approved for your firm. Ask the vendor to confirm the exact account and features in writing where the published documents leave a gap.

The assistants already inside the firm's own software are a different question from a notetaker that joins a call, and they belong in the same register. Clio's AI is built into Clio Manage and reads the matters that are in it. CoCounsel works on the matter file a firm uploads to it. Lexis+ with Protégé can also be pointed at the firm's own documents and prior work, which is the setting that decides how much client material it touches. Each of those pages records what the vendor publishes for each plan, with the date the page was read.

Separate an internal meeting about public marketing copy from a prospective-client intake, a privileged strategy discussion and a call involving several matters. Our recommendation is to start with invented material and a narrow task. If the firm cannot explain why the tool needs access to a particular call, do not make that call the pilot.

What does Opinion 512 settle, and what remains your decision?

The July 2024 opinion discusses generative AI under the ABA Model Rules. Its confidentiality section addresses disclosure risks inside and outside a firm, and its communication section makes disclosure depend on the circumstances. It calls for informed consent before relevant client information enters the self-learning tools described in its analysis, and says generic engagement-letter authorization is insufficient where informed consent is needed. These are the opinion's conclusions, not a ruling that every notetaker has the same capabilities or consent requirements. Opinion 512, sections B and C, checked November 3, 2026.

Take three separate questions to counsel: which professional obligations govern the lawyer, what recording and privacy requirements apply to the participants, and what the client engagement permits. Do not use this article to resolve privilege, consent or jurisdiction. Bring the actual proposed workflow so the answer can be about a real decision.

For that discussion, describe what goes into the service before describing what comes out. Include audio, any transcript, screen material if capture is proposed, prompts and the final note. Then list every intended recipient. A concise diagram on paper is enough: call to service, service to reviewer, approved note to matter file. Add any other transfer the vendor or administrator identifies.

What should the firm tell the client?

Prepare the explanation before the meeting invitation. Our suggested outline covers the purpose of the notetaker, what it would capture, who would receive the result, where the firm proposes to keep it and how the meeting can proceed without it. Have counsel turn that outline into the appropriate notice or consent process for the particular use.

Avoid a general assurance that the software is private. A useful explanation names the actual workflow. If the firm does not know whether a transcript remains in the vendor account, resolve that question before claiming otherwise. If the client asks for a restriction, put it where the person hosting the call will see it.

Do not treat a bot's display name, a recording indicator or a calendar invitation as the firm's completed legal analysis. Those interface details can be part of the process counsel approves, but the firm still needs to know what its staff should do when a client declines. Give the host a practical fallback: remove the notetaker, verify it has left and take ordinary notes through the approved process.

For a recurring meeting, record who checks that approval still applies when participants, subject matter or features change. A standing invitation should not become a standing exception that nobody owns. This is our operational recommendation, not a universal requirement to obtain fresh consent at a particular interval.

What evidence belongs in the approval record?

Keep the record short enough that the managing partner can use it. Our suggested fields are below. Save vendor answers and configuration evidence with a date; do not put client meeting content into the approval worksheet itself.

Review model-training terms separately from storage and sharing. Asking whether content is used for training does not answer who can open the transcript, whether a recap link can be forwarded, or how the firm retrieves its records. Ask each question plainly rather than treating a favorable answer to one as approval of the whole workflow.

Our suggested handling rule is to put draft output in a restricted review location. The lawyer checks names, attribution, dates, commitments and omissions against what actually happened before the note becomes part of the working matter record. Mark the reviewer and review date. Decide with counsel how to preserve corrections and any underlying material; do not silently overwrite evidence or delete a recording just to simplify the tool inventory.

What can the firm decide this week?

Use this checklist as a bounded approval exercise. It is our recommended process, not a claim that completing six steps establishes professional compliance.

1. Name the owner and use. Choose one responsible lawyer, one proposed notetaker and one permitted meeting type. List calls that remain excluded.
2. Collect the account facts. Record the plan, workspace owner, vendor terms and answers about capture, training, retention, sharing and export. Ask for missing details in writing.
3. Resolve the client discussion. Ask counsel to approve the notice or consent approach and the no-notetaker alternative. Record any matter-specific restrictions.
4. Test with invented content. Hold a short internal call, then inspect where the audio, transcript and summary appear. Test a participant without permission and the proposed sharing route.
5. Test the ending. Check what happens when a meeting finishes, an employee leaves the workspace and the firm needs to retrieve an approved note. Have counsel approve retention and deletion rules before testing them.
6. Issue the decision. Approve the exact scope, restrict it or hold it pending evidence. Tell staff who can authorize an exception and when the decision will be reviewed.

A successful test includes a blocked case. Ask the administrator to show that an unapproved colleague cannot open the invented matter's note. If that test fails, record the actual access and fix it before a client call. Do not interpret a summary that looks accurate as proof that the sharing controls work.

If a notetaker has already joined an unapproved call, stop further use and follow the firm's incident process. Preserve the product, account, meeting and sharing details for the authorized reviewer. Ask counsel what preservation, client communication or other response is required. Avoid experimenting with the real recording to find out how widely it can be shared.

How does this fit the firm's wider AI policy?

The call decision should become a short rule staff can find before a meeting starts. Include the approved tool and account, who can invite it, excluded calls, required client discussion, output reviewer and reporting route. The broader law-firm AI policy guide helps put that decision beside rules for documents and chat assistants.

Use the AI tool risk checker to organize unanswered questions. The law-firm industry page describes the wider security context. An assessment can help identify tools and access within its agreed scope; the firm and its counsel still make the professional and client decisions.

Sources

• ABA Formal Opinion 512, Generative Artificial Intelligence Tools, July 29, 2024, especially pages 6–9. Opened November 3, 2026.
• Obsidian Ridge's AI-tool evidence index: links to plan-specific vendor statements; an index, not a firm approval list.
• Obsidian Ridge assessment scope: approved offer terms supplied by the shared constants below.