Transfer recurring meetings before a leaver's account is deleted

A manager opens a team calendar and sees a weekly invite owned by someone who left. For non-personal Google Workspace accounts, deleting the account removes the secondary calendars that the deleted user owned. The invite still appears every week, the owner field still points to a departed account, and nobody wants to cancel it.

A recurring meeting is calendar debt until it has a named owner, a review date, and a clean handoff path. If the owner leaves, the debt moves to the next person who opens the calendar and sees the invite still standing.

Deletion closes the transfer window

Google Workspace is deploying a lifecycle rule that ties secondary calendars to their owning non-personal account. Account suspension suspends the secondary calendars that a suspended non-personal account owned. Group calendars and Classroom calendars are part of the Google Workspace secondary calendar lifecycle update.

Move the calendars while the account still exists. The Google Admin console route lets an admin move an undeleted user's secondary calendars to a user in the same organization. One Google Admin console option automatically cancels a deleted user's future events 21 days after deletion. Put the audit in the offboarding checklist, not in a later cleanup.

The hours show which invites are dead

A productivity audit identifies recurring meetings that outlived their purpose as structural drag, alongside stalled handoffs and forgotten review steps. A one-hour meeting with 10 participants earning $50 per hour is a $500 investment, and without an agenda and clear outcome, that $500 is characterized as waste. If the meeting has no owner, the cost spreads into repeated interruptions, unclear next steps, and the assumption that someone else will clean it up.

A four-step audit closes the handoff

Run the four-step calendar-debt audit before the offboarding ticket closes. Do it while the leaver can still answer questions.

• A productivity audit counts recurring meetings older than three months as part of the calendar evidence it examines, so list every recurring invite owned by the leaver or the team calendar and flag the older ones.
• In DACI-based decision-log practice, one owner is assigned per decision to prevent accountability gaps, so name one owner per recurring meeting. To keep the record defensible, a decision log should note when the choice was closed, which session produced it, and who was in the room.
• Set a review date in the meeting description or calendar notes, and note what outcome will justify the next occurrence.
• Google Calendar stops allowing further transfers after the owner account has been deleted, so transfer ownership before the account is deleted or suspended, or cancel the invite if no owner can be named.

A decision recorded without a named owner or rationale can be re-litigated six months later because the original reasoning is missing. A review date turns a standing invite into a dated commitment instead of a permanent fixture. Transfer or cancel before the account disappears.

A factual note cancels the dead meeting

When the meeting has no owner and no review date, cancel it. A short note is enough: the original purpose has ended, the owner is leaving, and the next review date is set. Keep the note factual. Say what is ending and where the team can go if the topic resurfaces. If the work is still active, point to the new owner. Fellow's carry-over feature for recurring meetings moves unfinished talking points and action items to the next agenda, reducing the chance that decisions are lost. If the meeting still has value, transfer it to a named owner before the leaver leaves.