1. Decide whether the meeting should be recorded
Convenience is only one consideration. Sensitive personnel conversations, medical information, investigations, or legal advice may call for a different process. Ask the appropriate HR, privacy, or legal owner before a bot joins.
2. Confirm notice and consent
California Penal Code section 632 generally prohibits recording a confidential communication without the consent of all parties, subject to the statute’s scope and exceptions. Other locations have different rules. Confirm how those requirements apply to the tool and participants; do not assume a platform banner settles every issue.
Explain what the tool captures, why it is being used, who can access the result, and what alternatives are available. Check default auto-join settings and invitees who arrive late.
3. Review the vendor and access settings
- What data is stored, and where?
- Can recordings, transcripts, or prompts be used for model training?
- Who can download, share, search, or export the material?
- What retention and deletion controls are available?
- How will legal holds or access requests be handled?
4. Review the summary before relying on it
Check names, decisions, action owners, and omitted context. A fluent summary can still be wrong. Make corrections visible and do not treat the transcript as an unquestionable account of what happened.
5. Agree on the routine
Assign a meeting owner, an approval process, and a review date. Give people a way to report an unwanted recording or inaccurate summary. Revisit the protocol when the vendor changes features.
Questions for the next team meeting
Which meetings can use an assistant? Which cannot? Who approves it? What happens when someone objects? Where do approved notes live?
Educational guidance, not legal advice or a certification of compliance. Requirements depend on location, employer size, industry, and the facts. Consult qualified employment counsel for decisions involving legal obligations.