Cut recurring meetings before five-year AI memories
Audit standing invites for decision, required people, and skip impact, then cancel, shorten, or move them async before Teams AI memory archives them.

List the standing obligations before they count you
Your calendar is full of standing invites that ask for time, attention, and follow-up work, often without an end date. Audit the recurring meetings you own before they become records.
List everything that competes for attention in a weekly schedule, including recurring responsibilities. The finished list names every standing meeting, its time, and its purpose.
Track recurring work for one week before locking it into a schedule. The log shows which meetings produce decisions, which produce only updates, and which produce work for another meeting.
Lucid's meeting taxonomy treats meetings as a system where each session creates follow-up work for later sessions. A recurring meeting can generate notes, tasks, and a next meeting, even when the original decision is stale.
Treat each recurring invite as a contract with a review date
For every standing invite, answer four questions:
- What decision does it make?
- Who must be present?
- What happens if it is skipped?
- Should it be canceled, shortened, made async, or kept with a stated purpose and retention limit?
Record the answers beside the meeting, then put the chosen action in the invite, with the reason for the change. The audit note gives the admin a clear set of questions.
Check 1:1s against the recommended cadence: weekly or biweekly, 30 to 60 minutes. Frequent 1:1s also affect performance: Google Project Oxygen found that managers who hold frequent 1:1s tend to earn better performance scores than managers without frequent 1:1s. Then shorten the conversation, with status moved to a written update.
Check the archive setting before you cut. Microsoft Teams meeting memory files use the .meeting extension and hold the meeting metadata, plus a summary of key insights and discussion. Teams turns on AI archive generation for every tenant by default. Ask IT to set the retention limit. Unless an admin changes it, the default expiration is five years, or 1,825 days.
Those files sit in a Teams-owned SharePoint Embedded container, not a user's space, and organization users cannot view or access them. That invisibility is a warning: a meeting you never review can still become a long-term record.
Ask IT for the start date, because Microsoft Teams AI meeting memory file generation rolls out in November 2026. Admin controls for AI meeting memory files appear in the Teams admin center about four weeks before file generation starts. Teams admins can stop AI archive generation in the Teams Admin Center by disabling the AI meeting archive generation setting under AI Memory & Archive.
Cut the meetings that stop making decisions
Cancel the invite when the decision it made is no longer active, the required people are no longer needed, or the skip consequence is only a missed update. Add a short note explaining the replacement, such as a written update or a standing document.
Shorten the meeting when it still makes a decision but no longer needs the full block. Move the status to async and keep only the part that requires live judgment.
Make the meeting async when the real work is review, comment, or approval. The work lives in a document, ticket, or channel thread where people can respond without a shared time slot.
Keep the meeting only when it has a stated purpose, a required audience, and a retention limit. The invite states the purpose, required audience, and a date to revisit it.
Do not cancel a meeting only because it feels long. Cut it when the decision, required people, or skip consequence fails the test. A meeting that still makes a hard decision may deserve a smaller block, not a full removal.
An interruption takes roughly 23 minutes before full concentration returns. Switching tasks quickly can cut useful output by as much as 40 percent. Those numbers explain why a calendar full of short, recurring meetings can feel like focused work even when it produces little.
Put the next review date in the invite, and assign the owner who will check whether the meeting still makes a decision.