Keep calendars through staff exits
Google is rolling out a consequential ownership change for secondary calendars in non-personal Workspace accounts. Deleting an owner will also delete their secondary calendars; suspending the owner will suspend those calendars. Ownership must move before the account action if the calendar needs to remain available. For a district, the risk is an operational calendar tied to a departing staff member: activities, facilities or a team schedule can disappear during otherwise routine offboarding. Google says the extended rollout began October 5 and may take longer than 15 days. The announcement makes calendar ownership a current service-continuity issue, even where the new behavior has not yet appeared.
Why it matters for leaders
Add secondary-calendar ownership to the departure and suspension checklist. Identify high-use calendars, assign a continuing staff owner and test transfer before disabling an account. Include a documented path for urgent suspensions. The immediate cost is staff time to audit ownership and validate the runbook.
Cost, service, risk & adoption
Administrators can transfer secondary calendars through the Admin console or Calendar API; users can transfer them in Calendar Settings. The notice includes Workspace customers and Individual subscribers.
What the evidence cannot tell us
Rollout timing varies. The announcement does not inventory district calendars or establish that existing offboarding automation transfers them correctly.
Read the original sources
Summary and leadership analysis from the Week ending 2026-10-09 brief. The edition’s selection notes explain source access and evidence limitations.