Change the owner of a Google Calendar event before you hand over a meeting
When you change roles, the meetings you organise do not follow your job title. Until someone else owns them, you remain the organiser, and a Meet link can depend on you staying in the organisation. Arte Soft, the developer of Cloud Calendars, wrote this checklist; the transfer itself happens in Google Calendar on a computer.
Handover options compared
| Action | Organiser changes? | Meet features after | Risk if you leave |
|---|---|---|---|
| Change owner, accepted, to colleague’s primary calendar | Yes | Follow the new organiser’s policies | Verify saved organiser, access and required Meet features; acceptance alone is not a guarantee of every host capability |
| Change owner sent, not yet accepted | You remain the owner until acceptance; the recipient has a 60-day acceptance window | Unchanged | High; meeting still depends on you |
| Move to a non-primary calendar | No | Unchanged | Google says the Meet link stops working if you leave the organisation |
| Event with more than 200 guests | Cannot be transferred | — | Coordinate an appropriate successor-owned replacement and supported cancellation scope; preserve relevant history |
What most people assume
Sending a colleague “Change owner” hands the meeting over immediately.
What a transfer does and does not do
Google’s steps are: select an event you own, open Options, choose Change owner, enter the new owner and a message. The new owner receives an email with a link. Google states they have 60 days to accept and that you remain the owner until then.
Google says events with more than 200 guests cannot be transferred to another owner or calendar. Its same-organisation requirement is stated under whole-calendar ownership transfer, not the separate event Change owner procedure. For an individual event, inspect the actual Change owner options and your organisation’s policy; this guide does not promise that every proposed recipient is eligible. Moving an event between calendars and changing its owner are separate operations.
The Google Meet consequence
Google’s Meet documentation says that when an event is created on or transferred to someone else’s primary calendar, that person becomes the calendar event organiser, and the meeting’s features depend on the video-conferencing policies that apply to them. Its example: if the new organiser’s edition or admin settings do not allow recording, they will not be able to record the meeting.
If an event is instead put on a non-primary calendar, Google says the organiser does not change, so Meet features stay the same — and if you then leave the organisation before the meeting, the link stops working. Parking meetings on a team calendar is therefore not a safe substitute for a real owner transfer when you are leaving.
Worked example: a handover list
A fictional programme coordinator moving teams on 30 November organises three items: a weekly partner check-in, a one-off quarterly review with a Meet link that is usually recorded, and an all-hands briefing with 240 guests.
The coordinator checks the actual Change owner options for the check-in and review and confirms the intended recipient before sending. Before the review’s transfer, they ask whether the successor’s account supports Meet recording. The 240-guest all-hands exceeds Google’s documented transfer limit, so they coordinate a supported replacement owned by the successor and inform attendees how the original will be retired. A recurring meeting needs deliberate future-occurrence scope and preservation of useful history; do not delete an entire historical series as a handoff shortcut.
For illustration, the coordinator starts a week before leaving and follows up on pending requests. That is a planning example, not a required or sufficient lead time. Completion depends on the recipient actually accepting; afterwards, inspect the saved event’s organiser and required Meet features before closing the old account.
Checks after acceptance
Open the event as the new owner and confirm the organiser, guest list, time zone and Meet link. Ask the new owner to start the Meet call briefly before the first real session if recording or other host features matter. For a recurring meeting, look at several future occurrences, not only the next one, before assuming the whole series moved.
If the transfer has not been accepted when you leave, you are still the owner. Do not let the 60-day window run out silently: chase the recipient or plan a replacement event with the attendees informed.
What this page does not cover
Transferring ownership of a whole secondary calendar is a different decision with its own consequences and is handled in a separate guide. Cloud Calendars can display Google events but does not perform Google’s ownership transfer; use Google Calendar for that step.
What it looks like
Cloud Calendars overview, using our product images. Provider settings and protocol examples described in this guide are separate from the screens shown here.
What to do
- List every event you organise that will outlive your role.
- Check the proposed recipient in the event’s actual Change owner workflow and ask whether the successor’s account supports the Meet features you rely on.
- Send Change owner with a message well before your last day.
- For events over 200 guests, coordinate a successor-owned replacement and clearly communicate the appropriate retirement or cancellation scope for the original.
- Chase acceptances; you remain owner until each is accepted.
- After acceptance, check the organiser, several recurring occurrences and the Meet link.
Questions
- Is the meeting transferred as soon as I click Change owner?
- No. Google says the new owner gets an email link, has 60 days to accept, and you stay owner until then.
- Can I transfer a meeting to someone at a client company?
- Do not infer the answer from the whole-calendar ownership rule. Google states a same-organisation requirement under calendar transfer, while documenting Change owner separately for events. Check the event’s available controls and organisation policy; neither universal eligibility nor universal rejection across domains is established here.
- Will recording still work after the transfer?
- Only if the new organiser’s edition and admin settings allow it. Google says Meet features follow the policies of the calendar event organiser.