AI meeting note-takers in client workshops: rules for consultants

Why client workshops are different from internal meetings#

A client workshop is different because an AI note-taker creates a new, verbatim record of the client's confidential information and sends it to a third-party vendor. In an internal meeting the firm controls the people, the content and the policy. In a workshop, client staff who never signed the engagement letter are speaking, and the client's contract terms govern what the firm may do with what it hears.

Workshops also produce candid material: process weaknesses, headcount discussions, supplier complaints and early ideas the client has not approved. A human note-taker filters as they write. A transcript keeps everything, including the aside someone assumed was off the record.

Which consent rules apply to recording a workshop?#

Recording consent rules for a workshop come mainly from state wiretap and eavesdropping laws, which differ: some states allow recording when one party consents, others require the consent of all parties. When participants join from several states, many firms follow the strictest rule that may apply rather than working out which state's law governs. Participants outside the US can bring other laws into play, such as GDPR.

A note-taker that transcribes without keeping audio may still be treated as recording, so do not assume the distinction helps. Which laws apply to a given meeting is a question for counsel; the practical habit is notice to everyone, a clear spoken announcement and an easy way to pause or decline.

Privilege adds a further caution. When client or firm counsel joins a session to give legal advice, a third-party transcript of that discussion can complicate any later claim that the conversation was privileged. Ending the note-taker before counsel speaks is the simple default.

Consent and retention checklist by meeting type#

The checklist below sets a default for each type of meeting a consulting team runs with or about a client. It assumes the client contract permits note-taking tools at all; where it does not, the answer is no for every row.

What to check in the client contract and the vendor's terms#

The client contract and the note-taker vendor's terms decide most of the answer before any state law does. Many consulting MSAs require client approval for new subcontractors or subprocessors, limit where client data may be stored and now include specific AI clauses. The vendor's terms decide whether meeting content can be used to improve its models, how long it keeps recordings and who can see them.

Vendor commitments are specific and worth reading line by line. Zoom's online terms, for example, say it does not use audio, video, chat, screen sharing, attachments or other communications-like customer content to train Zoom or third-party AI models, while Zoom notes that customers on separately negotiated contracts are governed by those contracts. Retention is often a setting rather than a promise: Zoom lets admins delete cloud recordings automatically after a set number of days, and when trash recovery is on, deleted recordings stay recoverable for 30 days. Review both documents before rolling a tool out to client-facing teams, and record the result per client in the engagement file.

• 1Confidentiality clause: does it cover information disclosed orally in meetings?
• 2Subprocessor or subcontractor approval: is the note-taker vendor a new party that needs consent?
• 3Data location: does the vendor store or process data where the contract allows?
• 4Client AI policy: has the client banned or restricted AI tools in its meetings?
• 5Work product terms: would a transcript count as a deliverable or client property?
• 6Vendor training settings: is use of your content to train or improve models switched off?
• 7Auto-sharing: are summaries emailed to every participant, including external ones, by default?
• 8Vendor retention and deletion: can you delete recordings and get confirmation?

Who owns a workshop transcript, and can it be reused?#

Ownership of a workshop transcript depends on the engagement contract, but in practice the content is usually the client's confidential information even when the firm's tool produced the file. Work product clauses may make it a client deliverable; confidentiality clauses typically limit its use to delivering the engagement.

That limits reuse. Feeding client workshop transcripts into an internal knowledge tool or a training set, or including them in a data license, needs a rights review against each client's terms, and often the client's consent. Transcripts of the firm's own internal meetings are a different case, though they still carry employee and client references that need review.

Transcripts also become records the firm may have to produce. If an engagement ends in a fee dispute or a claim, verbatim workshop transcripts can be requested in discovery, and a litigation hold can stop scheduled deletion. A retention period that is set in advance and actually followed is easier to defend than a vendor account that quietly keeps everything.

Illustrative: an operations consulting firm writes its workshop rule#

Illustrative: a fictional operations consulting firm is running a series of process redesign workshops for a manufacturing client with sites in several states. A manager has started using an AI note-taker for internal stand-ups, and the team wants to use it in the workshops too.

The firm's general counsel checks the MSA and finds a subprocessor approval clause, so the engagement partner asks the client sponsor for written approval and gets it, limited to firm-hosted workshops. The team turns off auto-sharing and vendor model training, announces the note-taker at the start of each session and pauses it when the client's HR lead joins to discuss staffing. A consultant reviews each summary before it goes into the engagement folder, and raw transcripts are deleted on the agreed schedule.

How SourceX treats meeting transcripts in a licensing review#

SourceX treats client workshop transcripts as client-controlled material by default. In the Rights step of the SourceX five-step transaction, they are usually carved out unless the contract clearly allows the use and the client agrees. Transcripts of a firm's internal meetings may be considered after de-identification and a review of employee notices.

Where any meeting records proceed, the SourceX Evidence Packet records the consent basis, permitted use, privacy treatment and release authorization, so the buyer and the supplier have the same written account of what was approved and why.