Three rules keep meeting recordings from becoming a trust liability: explicit consent announced at the start, visibility limited to attendees, and a 30-day retention default. Packed into a one-page team brief, reviewed quarterly.
The short version: A team recording policy only needs to answer five questions — what can be recorded, how people are told, who can access the recording, how long it is kept, and how it gets deleted. If your team records meetings and can't answer all five today, you don't have a policy; you have a habit. This article gives you the reasoning in five short sections, then a complete template you can copy, adapt, and adopt this week.
Consent, visibility, and retention are the small rules that make recording useful without making it a trust liability. (For the consent basics — one-party vs. all-party rules and what to say before you record — start with our guide for individuals. This article is the team-level version.)
Recording a Meeting: Consent Rules, What to Say, and When You Need Permission
1. Scope: Decide What Can Be Recorded — By Meeting Type, Not By Mood
Rule: Routine internal meetings can be recorded by default; sensitive conversations (performance, health, legal, personal one-to-ones) are recorded only with explicit agreement, or not at all.
A single "record everything" or "record nothing" rule both fail. The first scares people out of speaking honestly; the second loses the record of decisions your team actually needs. Classify by the conversation's content: the more personal or consequential the topic, the stronger the consent you need.
2. Notice: Announce Every Recording, Out Loud, Every Time
Rule: The recording is announced verbally before it starts, the purpose is stated in one sentence, and anyone can ask for a pause — no questions asked.
A platform's recording icon is a technical signal, not an announcement. People change what they say when they know they're recorded; they deserve to know, in words, before the first agenda item. Consent law varies by place, and policy never replaces it — announcing clearly is the one practice that satisfies almost every version of the rule.
3. Access: A Recording's Audience Is Named, Not Assumed
Rule: Access follows purpose. The default audience is the meeting's participants; anyone beyond them — a manager, another team, a future hire — is added deliberately, not by default.
A useful record keeps the original words close to the organized result: the decision, the evidence behind it, the open question, and the next action, all traceable back to what was actually said. That traceability is what makes a recording valuable — and it's exactly why access matters. A record anyone can open will eventually be read by someone the speakers never imagined, and the next meeting's honesty is the price.
Practical handoff: when a recording is used, return to the source, confirm what was agreed, identify what still needs attention, and carry that context into the next conversation.
4. Retention: Every Recording Has an Expiry Date
Rule: Set a default retention period (30–90 days covers most working needs), keep specific recordings longer only for a stated reason, and let deletion happen automatically rather than by someone remembering.
"Indefinitely, just in case" is not a retention policy — it's an accumulating liability of searchable, sensitive conversation. Most recordings earn their keep in the first few weeks: settling what was decided, onboarding someone who missed the meeting, resolving a disagreement about a commitment. After that, the summary usually suffices and the raw recording can go.
5. Deletion and Exceptions: Make Leaving Easy
Rule: Anyone recorded can request deletion of a recording they're in; requests are honored quickly, and exceptions (legal hold, formal investigation) are named in the policy rather than invented in the moment.
Deletion that requires three approvals and a ticket teaches people that the policy is decorative. Fast, boring, routine deletion is what makes the rest of the system trustworthy.
Keep the boundary clear: a policy and a tool together still don't replace consent, professional judgment, or the responsibility to verify important decisions. They make the everyday practice consistent enough that judgment is only needed for the genuinely unusual cases. Whatever tool your team uses, its controls should match the policy — who can open, share, export, and delete a recording.
CoHear Security | Recording Privacy & Data Controls
The Template: Copy, Adapt, Adopt
Replace the brackets, delete what's irrelevant, and get it approved like any other team policy.
Meeting Recording Policy — [Team/Company name]
- Purpose. We record meetings to preserve decisions, action items, and context — not to monitor individuals.
- What may be recorded. Routine team meetings, project reviews, and client calls may be recorded. Performance discussions, disciplinary meetings, health-related conversations, and personal one-to-ones are recorded only with the explicit agreement of everyone present, or not at all.
- How consent is announced. The host announces the recording out loud before it begins, states its purpose in one sentence ("This is being recorded so we have accurate notes and action items"), and confirms participants agree. Anyone may ask for the recording to be paused or stopped at any time, without giving a reason. Where the law requires all-party consent, that requirement overrides this policy.
- Who can access recordings. Access is limited to meeting participants by default. Recordings and summaries may be shared beyond the participant list only by the meeting host, for a stated work purpose. Recordings are never used to train AI models except as permitted by our vendor settings [adjust to your tool].
- How long recordings are kept. Recordings are retained for [30/60/90] days and then deleted automatically. A recording may be kept longer only for a documented reason (e.g., project record, legal requirement), noted by the host.
- How deletion works. Any participant may request deletion of a recording they appear in by contacting [owner/channel]. Requests are completed within [5] business days, except where a legal hold applies.
- Exceptions. Legal, HR, or compliance may place specific recordings under hold. Exceptions are documented; they are not decided informally.
Adopted [date]. Owner: [name/role]. Review annually.
FAQ
How long should a team keep meeting recordings?
Long enough to cover their working life — typically 30 to 90 days. Most recordings are consulted in the first few weeks; after that, keep the summary and let the recording expire. Regulated industries and legal requirements can set longer periods.
Does a company recording policy replace consent law?
No. Recording law (including one-party vs. all-party consent rules) applies on top of any internal policy, and where the two conflict, the stricter rule wins. A policy makes behavior consistent; it doesn't make anything legal by itself.
Who owns a meeting recording at work?
Generally the employer owns work records created on company systems — but ownership and access are different questions. A good policy names who may access a recording regardless of who owns it, and gives participants a working deletion-request path.
This article is a practical template for team norms, not legal advice. Have your policy reviewed against the laws and regulations that apply to your organization.