A calendar invite is not one record that everyone looks at. It is a set of copies, one on each guest's calendar, tied together by a shared identifier, with a single account named as the organizer. Only that account can revise those copies. Most of what goes wrong with showing times traces back to those two facts.
The organizer is a property on the event, fixed when the invite is created
Every mainstream calendar tool reads and writes the same format, iCalendar, defined in RFC 5545. That spec requires an organizer on any invite with guests: the property "MUST be specified in an iCalendar object that specifies a group-scheduled calendar entity", and it "MUST NOT be specified" on a component that sits only on a single user's calendar. The moment you add a guest, the event acquires an owner of record.
That owner is whoever created the invite. Not whoever booked the showing, not your leasing inbox, not the company. If an agent sends a viewing invite from their own mailbox, the agent is the organizer, and the agent's mailbox is where every reply and every future change has to come from.
Each guest holds a separate copy, linked by an identifier
The copies are matched by the UID property, which RFC 5545 defines as "the persistent, globally unique identifier for the calendar component" and describes as "the method for correlating scheduling messages with the referenced" event. UID is how an acceptance or an update finds the right row on a calendar you cannot see.
Revisions ride on a second property, SEQUENCE, and the spec is specific about who moves it: "When a calendar component is created, its sequence number is 0. It is monotonically incremented by the Organizer's CUA each time the Organizer makes a significant revision to the calendar component." CUA means the organizer's calendar software. Read that from the leasing desk: the counter that tells a guest's calendar it is holding an outdated version goes up only when the organizer changes the event.
Three consequences follow. A guest who drags the showing to a new time on their own calendar changes one copy and tells nobody. A guest who forwards the invite hands out a copy still addressed to the original organizer, which is where any reply lands. And an invite created by an agent who has left the company is a pile of copies with a revision counter nobody can advance.
Where this gets misread
Sending a second invite instead of editing the first. A new invite is a new event with a new identifier. It does not supersede anything. The prospect now holds two copies that both look current, including the original at the original time. Editing the existing event is what retires the old time.
Assuming a shared mailbox makes ownership shared. It does not transfer an organizer, and Microsoft's own transfer tool refuses to touch those meetings: "You can't transfer meetings in Group or Shared mailboxes. Instead, add the new organizer to the mailbox." Membership is the continuity mechanism there, not transfer.
Expecting outside guests to be updated quietly. Microsoft documents the split plainly. Attendees in the same organization "don't need to re-RSVP, and the meeting instances on their calendars are silently updated", while attendees outside the organization "receive a meeting message from the old organizer that ends the meeting series, followed by an invitation message from the new organizer for the new series". Prospects, contractors and owners are all outside your organization. They see the cancellation.
The organizer can be changed, under conditions worth knowing
In Google Calendar, an event you own carries a Change owner item under Options. The documented limits: you cannot transfer events with more than 200 guests, and at the calendar level, "You can only transfer ownership of secondary calendars", the primary calendar assigned at sign-up cannot be transferred at all, and "The new owner has 60 days to accept ownership, and you remain the owner until then". Those rules are in Google's transfer calendars or events help page.
In Microsoft 365 there is no button. An Exchange Online administrator runs Invoke-ChangeMeetingOrganizer, which Microsoft states is "available only in the cloud-based service". Its limits are written down: only meetings on the user's default calendar, not Group or Shared mailboxes; the new organizer "must be a user in the same Exchange Online organization"; the effective date "must be a date in the future" because "You can't transfer previous instances"; and once a series has moved, the portion left behind on the original calendar cannot be transferred again. Teams-enabled meetings keep the old Teams organizer regardless.
None of that is a reason to panic. It is a reason to decide who owns showings before you need the answer.
What to settle before the next vacancy
- Pick the account that owns viewings and create every showing invite from it. In Microsoft 365, a shared mailbox whose members change over time survives turnover, because you add people rather than move meetings. In Google, keep showings on a secondary calendar, since those are the only ones whose ownership can be handed over.
- When a time moves, edit the existing event. Treat a second invite for the same showing as an error, not a reminder.
- When a staff member leaves, work through their outstanding invites before the mailbox closes. After that the copies on prospect calendars are frozen.
- Keep the booking time in your own records as well. A guest's copy can drift, and the time you can prove is the one you wrote down.
- Tell prospects to reply rather than edit. A reply reaches the organizer; an edit on their side reaches no one.
The underlying idea carries past calendars. Any record that gets copied out to people you do not control needs one place that counts as authoritative, and a way for everyone else to find out it changed. Calendars publish that mechanism openly, which makes them a good place to see it. The same question is worth asking about the timestamps your deadlines run on.
