A note from the workshop
The bot joined. Ask where the transcript goes.
An automatic note-taker may be useful, but the people in the meeting should understand what is being captured and where it goes. Before enabling a transcription or summary feature, find the owner, audience, retention controls, and an ordinary way to decline or use manual notes.
Three useful checks
- Identify the actual service: Built-in transcription and an external meeting bot can have different policies.
- Ask who can access it: Check the recording, transcript, summary, and sharing settings separately.
- Agree before enabling it: Use the approved process for your organization and the people in the meeting.
Put it into practice
Use a fictional meeting agenda to plan the workflow. List which parts of a real discussion could be sensitive and whether a short human-written action list would do the job. Capturing every sentence is not automatically necessary to remember who agreed to repair a printer.
Microsoft documents Teams notifications and administrator controls for recording and transcription. Those controls are specific to that product and organization. Do not assume a notification from one application describes every external bot, storage service, or AI summary tool in the call.
Ask the organizer how to review access and retention, and where a participant can raise a concern. Check summaries against the original agreed actions before treating them as decisions. If you cannot establish the recording rules, use the organization’s approved alternative instead of quietly experimenting with people’s conversation.
The meeting ends before the record does
A recording tool introduces a second audience: whoever can access the transcript, recording, summary, or exports afterward. That audience may differ from the people currently visible on the call. Before enabling capture, identify the actual service, who invited it, where the output goes, and what controls exist over access and retention.
Microsoft’s Teams documentation describes recording and transcription notifications, including organization-managed behavior. A visible notification tells you something about the platform’s workflow; it does not by itself answer every question about consent, legal requirements, downstream copies, or an independently connected bot. Keep the product feature and the organization’s recording policy separate.
Design a smaller record for a fictional meeting
Imagine a short meeting about repairing a shared printer. The useful outcome might be three lines: Sam will order the part, Lee will schedule the visit, and the group will check progress on Friday. Ask whether a full transcript is necessary to preserve that result. A concise agreed action list may do the job with less material to store and distribute.
If transcription is needed, plan the record before the call. Write down the owner of the output, its intended audience, and when the record should be reviewed or removed under the relevant policy. Use fictional agenda items for this exercise, and do not upload a private past meeting to investigate the tool.
- Identify the meeting platform and any separate capture service.
- Agree on the purpose of the record and whether a shorter action list is sufficient.
- Check participant notice, consent requirements, and organizational rules through the proper channels.
- Confirm where outputs are stored and who can access or share them.
- Name the person responsible for reviewing the output and its retention.
If an unfamiliar bot appears
Ask the organizer who added it and which service it represents before proceeding with sensitive discussion. A display name is not a complete explanation of the service behind it. If the organizer cannot establish the workflow, resolve the uncertainty before including material you would not want retained.
Check the output as well as the capture settings. An automatic summary can misattribute a decision or turn a suggestion into an assigned task. Review the agreed action list with the participants rather than treating the transcript as an infallible memory. If copies have already been exported, deleting one visible record may not remove every copy elsewhere.
A useful meeting record has an accountable owner
Finish with a short policy for the actual workflow: purpose, service, audience, retention, and reviewer. Leave legal conclusions to the relevant qualified or organizational guidance; this is a planning exercise. The practical win is a meeting where people know what is being captured and why, and where someone remains responsible for the record after the bot has left the room.
Know the limits
This is a workflow checklist, not legal advice or a statement that a notification alone satisfies recording laws. Requirements depend on circumstances and organization policy.
Identify the owner and audience of one meeting-notes workflow before turning it on.
Print the private field sheet. Record actions and observations, not passwords, recovery codes, or private documents.
Keep exploring: the offline AI experiment, lost-phone recovery, or the Recovery Drill.
About this field note
Original CRYPT1K editorial guidance. Sources reviewed October 21, 2026. Procedures are reader exercises; no unperformed hardware, account, or AI test results are claimed. Character and artwork are fictional and AI-assisted.