Back to Blog
Best Practice•2026-11-16•11 min read

AI Note Taker Policy Template (Copy and Adapt)

AI Note Taker Policy Template (Copy and Adapt)
TL
Team Laxis
Laxis Team @ Laxis

An AI note taker policy tells employees which recording tools they may use, which meetings are off-limits, how to tell people, and how long transcripts and summaries are kept. Below is a complete AI meeting recording policy template, in 12 short sections with bracketed placeholders. Make the decisions listed first, then copy it and fill in the blanks.

It's deliberately vendor-neutral, so it works whichever tools you approve. It also isn't legal advice: consent and retention rules depend on where your staff and customers are (our explainer on when recording needs consent, state by state and abroad is a starting point), so have counsel review it before you adopt it.

Why companies are writing AI note taker policies now

Companies are writing AI note taker policies because bots now turn up in meetings uninvited, transcripts outlive the conversations they record, and courts and bar associations have started asking who agreed to all this.

In February 2026, Fortune's CHRO newsletter described assistants that stay behind after people leave and email the transcript to the team, and quoted Jackson Lewis attorney Joe Lazzarotti, who advises a full audit of AI use, including deciding which meetings should be recorded. In an order dated August 13, 2026, Judge Eumi K. Lee of the Northern District of California let the core wiretap, California privacy and Illinois biometric claims in the consolidated Otter.ai privacy case go forward, UC Today reported. The order doesn't decide whether Otter broke the law, but the dispute turns on consent, speaker identification and retention, exactly what a policy controls; we follow both cases in our piece on AI note takers in court. Cornell's IT office, for one, places external AI bots in the meeting lobby until the organizer or a presenter admits them.

Decisions to make before you adopt this template

Settle these eight questions first; each one maps to a placeholder in the template, and the policy means little until they're answered.

  • Default stance. Allowed with approved tools, or off unless a meeting owner opts in?
  • Bot-free capture. Allowed? Nothing joins the call, so disclosure rests entirely on the user.
  • Consent standard. Notice plus a chance to object, or explicit agreement from everyone? Does one objection switch it off? (We'd say yes.)
  • Off-limits meetings. Which categories are never recorded?
  • Retention. How long for audio, transcripts and summaries?
  • Default access. Organizer only, all attendees, or the wider team?
  • External meetings. Can staff bring a bot to customer calls? What happens when a customer's bot joins yours?
  • Regulated data. Which tools, if any, may touch health, financial or privileged conversations?

Vetting a tool against these eight? Laxis records without a bot by default, offers a visible bot if your policy prefers one, reminds users to disclose, and its Privacy Policy rules out training on your content without your consent. Test it against your draft policy. 14-day Premium trial, no credit card.

Who should own an AI note taker policy

One named person should own the policy, usually in IT or security, with legal, HR and a business lead each signing off on their part.

  • IT or security: the approved list, platform settings and app permissions.
  • Legal or compliance: consent wording, retention, legal holds and regulated data.
  • HR: off-limits meetings, interviews, training and enforcement.
  • Sales or customer success: external-meeting rules, since they live with them.

At a 30-person company that may be one operations lead wearing every hat. What matters is that a name is on it.

The AI note taker policy template

Copy everything in the box, replace each [bracketed placeholder], delete the options you don't pick, and keep the numbering so people can cite clauses.

AI note taker policy template (copy and adapt)

AI NOTE TAKER AND MEETING RECORDING POLICY

[Company name] | Version [1.0] | Effective [date] | Owner: [name, title]

  1. PURPOSE AND SCOPE

1.1 This policy governs AI tools that record, transcribe or summarize meetings and calls ("AI note takers").

1.2 It applies to all employees, contractors and temporary staff in any meeting where [Company] business is discussed: video calls, phone calls and in-person meetings, on company or personal devices.

1.3 It covers tools that join as a participant ("bots"), tools that capture audio or captions on the user's own device ("bot-free capture"), and AI features built into meeting platforms.

  1. APPROVED TOOLS

2.1 Only tools on the approved list may be used for [Company] meetings: [tools and permitted plans, or link to the list].

2.2 Built-in AI features in [Zoom / Microsoft Teams / Google Meet] are [approved / approved with the settings listed at [link] / not approved].

2.3 To request a new tool, submit [form or ticket] to [IT/Security]. The review covers at least: where audio and data are processed and stored; retention and deletion controls; whether customer content is used to train models; security reports [e.g. SOC 2]; admin controls and SSO; default sharing settings; and whether the vendor will sign a [DPA / BAA] where needed.

2.4 Unapproved tools must not be connected to company calendars, email or accounts. Existing connections must be removed by [date].

  1. WHEN RECORDING IS ALLOWED

3.1 AI note takers may be used for [routine internal meetings / customer calls / training / other].

3.2 AI note takers must not be used for:

a) HR, grievance, disciplinary or investigation meetings [unless HR directs otherwise];

b) performance reviews and pay discussions;

c) conversations with legal counsel, or any meeting [Legal] designates as privileged;

d) conversations involving anyone's health information;

e) board meetings and [confidential projects] without approval from [owner];

f) any meeting where a participant objects.

3.3 Capture must stop when the meeting ends. A bot must not attend a meeting its owner does not attend [unless the organizer agrees in advance].

  1. CONSENT AND DISCLOSURE

4.1 The person using an AI note taker is responsible for disclosure, whether or not a bot is visible.

4.2 Internal meetings: say at the start that an AI note taker is running and who will receive the notes. [Optional: add a notice to the calendar invite.]

4.3 External meetings (customers, partners, vendors): ask before or at the start of the meeting and [obtain verbal agreement / note the agreement in the record]. If anyone declines, switch it off.

4.4 Job candidates: ask in writing beforehand, explain who sees the notes and for how long, and confirm that declining will not affect the outcome.

4.5 Where local law requires more, such as agreement from every participant, the stricter rule applies. [Legal] maintains guidance at [link].

  1. BOTS IN EXTERNAL MEETINGS

5.1 Employees may bring an approved bot to meetings hosted by other organizations only if [the host agrees / the customer's own policy allows it].

5.2 When another organization's bot joins a meeting hosted by [Company], the host should [ask whose it is and confirm everyone agrees / admit it for routine meetings only / remove it].

5.3 In meetings covered by section 3.2, hosts must remove outside bots, or have them switched off, before discussion starts. [IT] maintains the platform settings for external bots at [link].

  1. STORAGE, RETENTION AND DELETION

6.1 Recordings, transcripts and AI summaries are stored only in the approved tool or in [approved repository].

6.2 Retention: audio and video [X days]; transcripts [X days]; summaries and action items [X months, or the records schedule for the related business record].

6.3 Automatic deletion must be configured in the tool where available. Archiving or hiding a meeting does not count as deletion.

6.4 When an employee leaves, their meeting records are [transferred to their manager / deleted after X days], subject to section 9.

  1. ACCESS AND SHARING

7.1 Default access is limited to [the organizer / internal attendees].

7.2 Raw transcripts and recordings must not leave [Company] without approval from [manager / Legal].

7.3 Automatic emailing of summaries to all attendees is [off / limited to internal attendees].

7.4 "Anyone with the link" sharing is not permitted.

  1. REVIEW BEFORE FORWARDING

8.1 AI summaries are drafts. Before a summary goes beyond the attendees or outside [Company], the sender checks names, figures, commitments and who said what.

8.2 Transcripts and summaries must not be pasted into AI tools, CRMs or tickets not approved for that data.

  1. LEGAL HOLD AND DISCOVERY

9.1 When [Legal] issues a hold, covered recordings, transcripts and summaries are preserved, and automatic deletion is suspended for them, until [Legal] releases it.

9.2 [IT] must be able to find and export AI meeting records by user and date range within [X business days].

9.3 Employees must not delete, edit or move records covered by a hold.

  1. REGULATED AND SENSITIVE DATA

10.1 Protected health information may be recorded only with tools covered by a signed BAA: [tools, or "none approved"].

10.2 Card numbers, account numbers and government ID numbers must not be read aloud in recorded meetings.

10.3 Meetings subject to [industry rules, e.g. financial record-keeping] use only [approved tools].

10.4 Privileged conversations follow section 3.2(c).

  1. TRAINING AND ENFORCEMENT

11.1 Employees complete [training] before first use and every [12] months.

11.2 Report suspected breaches, such as undisclosed recording or improper sharing, to [contact].

11.3 Breaches may lead to loss of tool access and action under [disciplinary policy].

  1. OWNERSHIP, EXCEPTIONS AND REVIEW

12.1 Owner: [name, title]. Approvers: [Legal, HR, IT/Security].

12.2 Exceptions need written approval from [owner] and [Legal] for a stated period.

12.3 This policy is reviewed every [6/12] months and whenever approved tools or applicable laws change. Next review: [date].

How to roll out an AI meeting recording policy

Roll the policy out in a fixed order: find out what's already in use, match your platform settings to the rules, then announce it with a grace period.

  1. Take inventory. Ask teams what they use, and check which third-party apps have been granted calendar access in your Microsoft 365 or Google Workspace admin tools.
  2. Make the eight decisions and fill in the placeholders.
  3. Get sign-off from legal, HR and IT on their sections.
  4. Configure the platforms to match. Built-in tools keep records where your existing controls reach them: Microsoft Purview retention policies cover Teams recordings and transcripts stored in OneDrive and SharePoint, Google Vault can retain, hold and export Meet recordings, transcripts and Gemini notes, and Zoom admins can auto-delete cloud recordings after a set number of days. Built-in AI has defaults worth checking as well: since September 21, 2026, Google turns Gemini's automatic note-taking on by default for many Business Standard and Plus meetings with three or more guests, unless an admin opts out.
  5. Announce it with a one-paragraph summary and examples of what to say in meetings.
  6. Allow a grace period of [30] days for people to disconnect unapproved tools, then enforce.
  7. Diary the review date.

Companion guides cover the practical steps: blocking outside note-taker bots, removing a note taker that auto-joins, and AI note taker etiquette with disclosure scripts.

Checking any note taker against the policy, including Laxis

Before approving any AI note taker, test it against sections 2, 6 and 10: how it captures, where data goes, how long it keeps records, and what it must never touch. Here's how we answer for the Laxis AI meeting assistant.

Policy questionSectionLaxis's answer
Bot or bot-free?4.1, 5Bot-free by default: device audio on desktop, live captions in the Chrome extension. The Chrome extension lets participants know a recording is running; with desktop capture, the app reminds users to tell participants first, so the disclosure rule in section 4 applies as written. There's also an optional AI Assistant Bot for calendar auto-join, which a user has to enable and which joins as a named participant.
Where is audio processed?2.3, 10In the cloud in the standard apps; Laxis's on-device apps keep recordings on the device.
Health information?10.1Not HIPAA compliant; doesn't sign BAAs. Keep it out of meetings with PHI.
How long are records kept?6Basic shows 30 days of history; older meetings are archived, not deleted. Premium and Business keep unlimited history, so your deletion schedule has to come from you. Enterprise offers custom retention policies.
Admin and sign-in controls?2.3, 7Team admin on Business; SSO and SAML on Enterprise, which also offers data residency.
Where else do notes go?8.2HubSpot and Salesforce sync and Zapier integrations are Business features. Decide whether summaries may flow there.
Is customer content used to train models?2.3Laxis will never use your data to train AI models without your consent. That commitment is in Section 3 of our Privacy Policy and in our No-Training Pledge.
Security reports, subprocessors, deletion timelines2.3, 6Laxis's privacy policy says it is SOC 2 Type I compliant, and the subprocessor list and a Data Processing Addendum are available on request. Get deletion timelines in writing, from us as from any vendor.

So Laxis suits a policy that permits bot-free capture with disclosure, particularly for teams meeting across Zoom, Teams, Meet and Webex, or in person. Where the policy requires on-device processing, look at Laxis's on-device apps; for clinical work it's the wrong choice, because Laxis isn't HIPAA compliant.

Test Laxis against your policy before you approve it. Bot-free by default, with an optional bot only when you turn it on. 14-day Premium trial, no credit card. Start your free trial

Frequently asked questions

What should an AI note taker policy include?

An AI note taker policy should cover scope, approved tools and how new ones are approved, meetings that must not be recorded, consent and disclosure, bots in external meetings, retention and deletion, access to transcripts, review of AI summaries before forwarding, legal holds, regulated data, training and enforcement, and a named owner with a review date.

Should our company allow AI note takers?

Many companies can allow AI note takers if they limit them to approved tools and set clear rules. An outright ban tends to push people toward personal apps nobody has vetted. A practical middle path is approved tools for routine meetings, a short list of meetings that are never recorded, and disclosure every time.

Your policy should require disclosure every time and a real chance to object, whatever the legal minimum is. Recording consent laws vary between jurisdictions, and some demand agreement from all parties, so ask your lawyers which standard applies to your staff and customers and write the stricter rule into the policy.

How long should a company keep AI meeting transcripts?

Keep AI meeting transcripts only as long as you need them, with separate periods for audio, transcripts and summaries. One workable pattern is to delete raw audio soon after the summary is agreed and keep the summary with the related business record. Configure deletion in the tool itself, and suspend it for legal holds.

Can AI meeting transcripts be used in litigation?

Plan as though they could be. An article in the American Bar Association's GPSolo eReport warns that AI note takers create detailed records that can widen what is discoverable. A policy should let legal teams find and preserve meeting records quickly, suspend automatic deletion under a legal hold, and keep privileged conversations from being recorded at all.

Should we block other companies' AI note takers from our meetings?

Block them by default in sensitive meetings and decide case by case for the rest. Your policy should tell hosts what to do when an outside bot joins: ask whose it is, confirm everyone agrees, and remove it if anyone objects. Hosts can remove a bot from Zoom, Teams or Google Meet like any other participant.

Related Product

Laxis Meeting Assistant

Automate your notes today.

  • Bot-free notes for Zoom, Google Meet, Teams and in-person meetings
  • AI summaries, action items and follow-ups in 60+ languages
  • Mac, Windows, iPhone and Android, with a free plan

Start for free, no credit card required.

Learn More ▷