Move or Kill: The Start-of-Week Rule for Clearing Recurring Meetings
Treat every standing invite as movable or killable, then batch the decision at the start of the week to protect your focus blocks.
You agreed to the recurring meeting because it sounded reasonable. It has since become a recurring interruption on your mornings, and nobody reviews it. The scheduled length understates the cost: you also lose the focus block before and after it.
Run the start-of-week audit before the week runs you
A full calendar is a ledger of small promises you never signed. Stop treating standing invites as fixed. Treat them as movable or killable, then batch the decision at the start of the week, when your attention is still yours.
Use a drag-or-kill rule: drag it if it can move without changing the relationship or output; kill it if it exists mainly to keep you visible or busy.
Count the hours, not just the title: the slot, the preparation, the follow-up, and the focus block you lose around it. A standing invite can consume more than its scheduled length because it interrupts the work around it.
Write the reason for each invite in a phrase: decision, relationship, visibility, or status. If you cannot name the reason, the invite is a candidate for killing.
- List every standing invite that repeats regularly. You are done when the list is short and the names are clear.
- Ask whether each invite changes the relationship or the output. Finish with a yes or no next to each line.
- Drag the ones that can move without changing the work. Finish when the deep-work block stays intact.
- Kill the ones that exist mainly to keep you visible or busy. You are done when the cancellation is clear and the alternative is written.
- Block the recovered time for deep work, and leave the protected time with a clear boundary.
Drag it if the meeting can move without breaking the work
Outlook drag-and-drop rescheduling is scheduled to begin general availability in late August 2026 under Microsoft 365 Message Center item MC1457230, and the rollout is expected to complete by late September 2026. It will be available in day and multi-day views, will apply only to events you own, and will require no administrator setup.
Use the drag test before you send a message. A meeting is movable when it can change day or time without changing who needs to be there. Do not drag it when the relationship depends on the slot. Do not drag it when the output depends on the slot.
While you drag, keep the message short. Say you are moving the meeting to protect a focus block, and offer a few alternatives. End with a clear next step.
Kill it if the invite is mostly visibility
Kill the invite when its main job is to keep you visible or busy. Ask whether the meeting would still matter if you stopped attending. When the answer is no, send a graceful cancellation. Say you are stepping back from the recurring slot, and offer a written update or a check-in if the topic needs it.
Keep a meeting that is the only place a decision gets made. A standing invite can look like overhead while it is actually the only route to a decision. If it carries a decision, move it or replace it with a clearer process.
Keep the cancellation short and future-facing. Avoid over-explaining. Tell them the recurring slot no longer fits the work, and give an alternative that is easier to accept.
Protect the focus block you just made
Make calendar triage part of your morning routine. Review the standing invites before you open messages. Protect focus time in your calendar by moving the meeting, not by shrinking the block. Block deep work time once the invite is moved or killed, and tell the team what you will not answer.
The recovered time is only useful if it has a job. Put a real task in the block, and give the task a name before the week starts. If the week fills again, return to the audit and ask which invite is doing the damage.