V5.10.1Informed consent before recording meetingsdesign

Recording requires everyone's informed consent beforehand, with a real option to refuse

Aliases: recording consent · right to refuse recording · pre-recording notice

What it is

Consent to record a meeting must be obtained before recording starts, and refusal must be a genuinely available option — not a token "object if you dare," but a low-cost path to not being recorded. The reason: recording changes not the meeting itself but the survival status of every sentence, from ephemeral to permanently replayable. That change's costs fall on every speaker, so the decision must reach their hands before the change occurs.

Why it happens

After-the-fact refusal barely exists, and that is the core of the "beforehand" requirement. Objecting mid-meeting amounts to publicly declaring "what I'm about to say shouldn't go on the record" — socially tantamount to confessing something to hide. The cost of objection is so high that nobody pays it, so a nominal right to refuse at any time is, in effect, no right at all. Likewise, "we record by default; just say so if you mind" shifts the burden of justification onto the weaker party. Effective informed consent requires three conditions at once: timing precedes recording (so refusal can affect whether it happens at all); notice is an active announcement rather than an icon in a corner (the uninformed cannot consent); and a real alternative path exists (skip recording this session, pause for a segment, or take written minutes instead of audio/video). Miss any one, and consent degenerates into post-hoc ratification of a fait accompli.

Where it stops holding

Recording consent in collaborative settings is an interaction-governance matter for teams and products, not the generic privacy-compliance framework — that involves jurisdictional differences and statutory duties with their own authoritative treatments; here only the interaction layer a collaboration tool should implement is in scope. One boundary is external participants: guests and cross-organization attendees cannot be assumed to know local conventions and need a fresh notice every time. Another is who judges what should stay unrecorded: small talk unrelated to the agenda, sudden personnel or family topics — the recorder cannot judge on others' behalf, so a physical pause control must exist rather than relying on after-the-fact editing.

Applying it

  • Keep recording off by default; before starting, the host announces it aloud and confirms no objection, with a globally visible recording state (not just a menu icon).
  • Pre-label invitations with "this session will be recorded" and the purpose (transcript archive / absentee catch-up), so refusal happens at the invitation stage, not after the meeting starts.
  • Provide one-click pause/resume, and let everyone — not only the host — trigger the pause: sensitive segments should not depend on the floor holder's judgment.
  • Make the default refusal path dignified: "we'll use written minutes instead" or "pause here; conclusions confirmed orally go into minutes," never forcing the refuser to weather "why can't this be recorded?"
  • Verification: audit the recording library for a recorded consent action per recording (invitation label or opening announcement); for recordings where someone joined mid-meeting, check whether they received the notice on entry — either gap marks a process hole.

Related

  • Same group: V5.10.2 Being recorded changes what people say and how candidly · V5.10.3 Searchable transcripts extend the reach of original speech · V5.10.4 Automatic transcription errors get quoted as the original words · V5.10.5 Retention period and access scope must be fixed in advance
  • Nearby: V2.09 The Boundary between Awareness Information and Monitoring · V5.08.3 Searchable text records are the long-term value
  • Search terms: recording consent · informed consent · meeting recording · off the record

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/V5.10.1