Moving a meeting is an edit to something that already exists. The people, the purpose, the length and the joining link all survive it, and one field changes. Treat it as an edit and it costs one message. Treat it as a fresh request and you pay for the whole negotiation a second time.
- A move has a precise definition in the calendar standard, and it is exactly this: the same event, at a higher revision. Change the identifier and you have not moved a meeting, you have cancelled one and booked another.
- What a time change does invalidate is every acceptance you were holding. That is by design rather than by accident, and it is the one thing a move genuinely destroys.
- You do not need to ask when they are free. The constraints that produced the original time are still sitting in the thread and mostly still true.
- The remaining work is telling people, and some of the people who need telling are not on the invitation.
One field changes and the rest survives
The instinct, when something booked has to move, is to go back to the beginning. “So sorry, something has come up at my end. Are you around at all next week?” That message reopens everything, including the parts that were never in dispute.
After a meeting has been agreed, very little about it is in dispute. Both of you still want it. It is still about the same thing, still the same length, still with the same people on it, still using the same link. One property has stopped being true.
The standard that calendars use to talk to each other is unusually clear about the difference, and it is worth knowing because it separates a two second edit from a fresh thread. An event carries a UID, a globally unique identifier, and a SEQUENCE, a revision number. RFC 5546, the iCalendar Transport-Independent Interoperability Protocol, describes how a receiving calendar works out what it has just been sent: “If the recipient CUA of a ‘REQUEST’ method finds that the ‘UID’ property value already exists on the calendar but that the ‘SEQUENCE’ (or ‘DTSTAMP’) property value in the ‘REQUEST’ method is greater than the value for the existing event, then the ‘REQUEST’ method describes a rescheduling of the event.”
Same identifier and a higher revision is a move. A new identifier is a different meeting that happens to be about the same subject. Everything that makes moving cheap follows from staying on the first path. The description you wrote stays written. The attachment stays attached. The guest list stays intact, including the colleague you added late and would forget. The event keeps its place in every reference that already points at it.
Cancel and rebook and none of that comes with you. You have also sent two emails where one would do: a cancellation, which reads as the meeting being off, followed by an invitation, which reads as a new request. People answer the first and let the second sit.
So the working shape is small. Change the time on the event that already exists, and write one short message saying what happened. The rest of this is what that leaves you to think about.
What one move actually disturbs
A meeting is not a single block. It is a block with things attached to it, and the calendar moves the block.
Every acceptance you were holding. This is the real loss, and the standard states it plainly. RFC 5546 lists the properties whose change obliges the organiser to bump the revision number: “When the ‘Organizer’ makes changes to one of the following properties, the sequence number MUST be incremented: o ‘DTSTART’ o ‘DTEND’ o ‘DURATION’ o ‘DUE’ o ‘RRULE’ o ‘RDATE’ o ‘EXDATE’ o ‘STATUS’”. The reason given is the useful part: an organiser must increment it “whenever it makes changes to properties in the calendar component that the ‘Organizer’ deems will jeopardize the validity of the participation status of the ‘Attendees’”. A time change is defined, by the protocol itself, as the kind of change that puts every yes in doubt. Whatever your tracking column said before the move, read it as blank afterwards.
The hour you gave back. Usually you want it released, and if you publish availability it will be released fast, because a booking page answers the question again at the instant somebody looks at it. That is the behaviour you asked for, and booking links covers what the page is claiming on your behalf. What catches people is the other case: you moved the meeting because that morning was needed for something else, and the something else never got put in the calendar, so the hour is sold twice over by Wednesday.
The hour you took. A slot that looks empty on the calendar in front of you is not necessarily empty. If your availability is spread across a work account and a personal one, a move made in a hurry is exactly the moment the second calendar gets skipped, and two calendars is about closing that gap for good rather than checking twice.
Everything that was anchored to it. The half hour of preparation before. The travel. The debrief after. The follow-up you promised somebody for that afternoon, on the assumption the meeting would already have happened. The filing deadline the meeting exists to serve, which has not moved at all. A calendar moves one block and leaves the rest standing where it was, which is why a meeting moved by two days sometimes produces four things to fix. Dated commitments that are nobody’s hour belong on a list rather than in the diary, which is email task management, without writing it down.
The rest of the series, if there is one. Moving one occurrence of a recurring meeting asks a question with three answers: this one, this one and everything after it, or all of them. The single occurrence is the right answer to a clash and the wrong answer to a permanent change, and choosing wrongly is invisible until the following week, when the old time comes round again. Note also that the standard only ranges forward. RFC 5545, the Internet Calendaring and Scheduling Core Object Specification, defines a RANGE parameter that takes one value, THISANDFUTURE, meaning “a range defined by the recurrence identifier and all subsequent instances”, and says of the alternative that “The value ‘THISANDPRIOR’ is deprecated by this revision of iCalendar and MUST NOT be generated by applications”. A series can be redirected from here on. It cannot be rewritten behind you.
The other person’s clock. Moving a meeting ninety minutes can push it past the end of somebody’s working day two zones over, and moving it three weeks can carry it across a clock change, so the local time they wrote down is not the local time it now happens at. Both are ordinary and neither announces itself, and scheduling across time zones is where the habits that catch them live.
The joining detail. Video conferencing attached to the event travels with the event, which is the common case and the reason a move usually needs no new link. A meeting created by booking software has a second record of itself, and whether your drag reaches that record depends on the plumbing. Calendly’s help documents the version that works and the conditions on it: “If you connect your Google Calendar, you can reschedule meetings directly from your calendar. When you update the date or time of the event in Google Calendar, Calendly also updates the meeting and notifies your invitee. To use this feature, make sure automatic sync is turned on in your calendar settings” (checked 19 August 2026). One named calendar, one setting. Where either does not hold, dragging the block moves your copy and leaves the invitee’s confirmation saying Thursday.
The things booked separately. The room. The parking space. The interpreter. The person covering reception. None of them are on the invitation, so none of them hear about the move.
Any sentence that restated the time. If the description says “as agreed, Thursday at 10:30”, the fields now say one thing and the prose says another, and a reader in a hurry believes the prose. This is the specific failure that writing a calendar invitation that arrives complete tells you not to plant, and a move is when the planting gets paid for.
Choosing the new time from what you already know
Here is the reason a move should not cost a fresh round of proposing times, and it is worth saying explicitly because almost nobody uses it.
The original negotiation produced facts, and you still have them. Not before ten. Hard stop at eleven. Wednesdays are out. Half an hour is enough. They are in Dublin. Those constraints were expensive, they are written down in a thread you can still read, and none of them expired when the time did. A move is a search inside a constraint set you already own. Asking “when are you free?” throws the set away and buys it again, which is how one moved meeting turns back into the full eight message chain that scheduling without the email chain counts out message by message.
So the sequence is: find the replacement, then write.
Try the same shape first. Same weekday, same time, next week. Whatever made Thursday at 10:30 possible for them is usually a weekly pattern rather than a one off, so the same slot seven days later is the likeliest single hour in their calendar to be free. Same week, adjacent day, same time is the next best.
Keep the length. Trimming an hour to forty minutes so it fits a gap is a second change, and one they did not agree to. If it genuinely has to be shorter, that is a thing to say rather than a thing to do quietly.
Make the proposal yourself. You are the one causing the trouble, so finding the time is your job, not theirs. A message that moves the meeting and also hands them the work of rearranging it asks them to pay twice. The exception is when they are the ones who wanted it moved, which is a different conversation with different manners, and it is when they ask to move.
Name one slot, with a second in reserve. An opening offer and a move are different messages doing different jobs, and the arithmetic of how many times to put in front of somebody cold belongs to the opening one. On a move you already know their constraints, so a single well chosen slot is usually enough, and a long list of options reads as though you have not thought about the trouble you are causing. Keep one alternative in the same message so that a no still ends in one reply.
Do not move it twice. The second move is a different animal from the first, and if you do not yet know whether the replacement will hold, say so instead of booking a slot you will move again next week. “I need to move Thursday and I will not know my Friday until this afternoon” is an honest sentence. A confident booking you withdraw two days later is not.
Sometimes it genuinely is a new negotiation, and the honest signals are few enough to list. Three or more diaries, where the intersection has to be found again from scratch. A move of more than about a fortnight, by which point the constraints you are carrying have gone stale. And any move where their side has changed too, not just yours. In those cases you are not editing a meeting, you are arranging one, and the opening move is the same one that works for any meeting: propose real times rather than asking for theirs.
Who needs telling, and who the calendar will not tell
There is a comfortable assumption underneath most reschedules, which is that updating the event tells everybody. It does not, in two separate ways.
The first is that the update reaches exactly the people on the invitation and nobody else. RFC 5546 is unambiguous about who receives a request: “The recipients of the ‘REQUEST’ method are the CUs invited to the event, the ‘Attendees’.” A list is a list.
The second is that the notification is optional at both ends. Google’s own help page on inviting people to an event describes updating as something you choose to announce, saying “To make guests aware of the event and updates, we recommend you send these emails”, and notes that a guest will not receive one if “They opt out of email notifications for changes to their calendar” (checked 19 August 2026). So a calendar update is a change to a record. Whether it becomes news depends on a checkbox you tick and a preference they set, and neither of those is visible to the other party.
That gives you two lists to think about, and the second is the one that gets missed.
On the invitation, and told by the update. For a routine internal shift with a fortnight’s notice, the update is genuinely enough, and sending eleven people a personal note about a fifteen minute change is its own small imposition. Let the record do the work.
On the invitation, and owed a sentence anyway. Anyone whose day this actually rearranges. Clients, without exception. Anyone travelling to it. Anyone who is presenting. The distinction is not seniority, it is whether the change costs them anything beyond a line in a diary.
Not on the invitation, and affected regardless. This is the list worth writing out once for your own practice, because it barely changes between meetings.
- Whoever keeps the other side’s diary. An assistant who is not a guest still has a version of Thursday that is now wrong.
- The colleague who blocked the hour afterwards for the debrief, or the two hours beforehand to prepare the pack.
- Whoever booked the room, the parking, the cover, the childcare.
- The third party you told you would come back to after Thursday’s call.
- Anybody who already declined. A new time may suit them, and an update lands as bookkeeping rather than as an invitation to reconsider unless you say so in a sentence.
- Your own future self, in the form of a task or a follow up dated off the old meeting.
Order matters, and it is simple: tell the person with the most to rearrange first, and tell them before the invitation update lands if you can. An event that changes in somebody’s diary before anyone has explained why is the version that reads as carelessness, even when the reason was perfectly good.
What the message has to settle
A move needs about sixty words, and they have six jobs.
Whether this is decided or proposed. The commonest failure in the whole subject is a message that does both: the calendar update arrives, so the meeting has visibly moved, while the covering note asks whether the new time works. The reader cannot tell which one to believe and often answers neither. Pick one. If you are proposing, hold the update until they agree. If you have decided, say so and let them push back.
The new time, written so it cannot be misread. Day, date and hour, and the zone if anyone is in a different one.
What has not changed. “Same half hour, same link, same two of us.” One clause, and it stops four questions that would otherwise arrive separately.
What has changed besides the time, if anything. A different room, one fewer person, a shorter slot. Buried changes are how a move becomes a second move.
Why, in about six words. A short reason reads as honest. A long one reads as a defence, and invites the reader to weigh whether it was a good enough excuse, which is not a question you wanted asked.
What to do if it does not work. One line, and then make it easy when they take it up.
That fits in a message somebody can read standing up:
“Thursday at 10:30 has to move, a filing deadline landed on that morning. Same time next Thursday, the 27th, works at my end and I have updated the invitation. Everything else is unchanged, same half hour, same link, same two of us. If the 27th is awkward, Tuesday the 25th at 10:30 is also free.”
The apology sits inside that, proportioned rather than performed. At three weeks’ notice, “sorry for the shuffle” is the right size, and a paragraph of contrition for a change nobody has noticed makes a reader wonder what else is going wrong at your end.
The same move at three weeks and at nine minutes
Notice is not a detail of the move, it is most of what the move is.
Weeks out. Bookkeeping. Change the event, send the update, add a line. Nobody has arranged anything around it yet.
Days out. They may already be preparing, and that is worth asking rather than assuming, because the answer changes what you owe them. Somebody who has spent an evening on a document for Thursday has lost something real when Thursday becomes the following Tuesday.
The morning of. Their day is already built around the hole where your meeting was. Moving it now is not a change of time, it is a change to today, and the message has to acknowledge that rather than pretend it is a small edit.
Inside the hour. Telephone. An email arriving four minutes before a call will not be read, because the person is either walking to a room or already sitting in an empty one. This is the single case where the calendar is the wrong instrument entirely, and the reason a mobile number belongs in every invitation you send.
After it should have started. Not a reschedule. An apology, and then a reschedule, in that order and probably in that many messages.
It is worth keeping the ordinary frequency of this in view, because the guilt attached to moving a meeting is usually out of proportion to how unusual it is. Reclaim, which makes scheduling software, surveyed over 1,300 professionals for its Smart Meetings Trends Report, published 23 April 2024, and found that people “average 17.1 meetings/week, yet 3.5 meetings are skipped and 4.2 are rescheduled every week”. That is a vendor asking its own market to estimate its own behaviour, so take the proportion and leave the decimal place. The proportion is that about a quarter of what is on a calendar moves, every week, for everybody. One moved meeting is unremarkable. The same meeting moving twice is what people notice, and it is the thing worth spending effort to avoid.
When moving it is the wrong answer
When the meeting no longer has a purpose. Moving it is the polite way of not saying so, and it costs both of you another hour in a fortnight to reach the same conclusion. Cancel it, say briefly why, and offer to pick it back up if the reason returns. That is a better message than a third reschedule.
When you are moving it because you are not ready. Frequently the correct call, and worth naming as what it is. “Can we push to Friday, I would rather come with the numbers finished than half done” gives them a decision to make, which a bare move does not, and sometimes the answer is that they would rather meet on Thursday anyway.
When somebody else keeps the diary. If the meeting was arranged by a client’s assistant, send them the constraint and let the change come from where the diary lives. Two versions of one move is worse than a slow one.
When it is a dated obligation rather than an hour of anyone’s time. Deadlines do not reschedule, they slip, and pretending otherwise by dragging a block around is how a real commitment gets quietly lost.
When they asked, rather than you. The mechanics below are the same, and almost none of the judgment is, which is when they ask to move.
Moving it in the week you are already looking at
Point sits on the Gmail or Microsoft 365 mailbox you already have and gives you the whole of it, mail and diary, in one surface. The calendar in front of you is your real one rather than a picture of it, which for this particular job means a move is a gesture rather than a form.
Grab the block and drag it. A dashed preview shows the exact slot it will land in while you are still moving it, so you see where the meeting is going before you let go, and the drag does not commit on release: one keystroke confirms it, so a slip of the mouse never moves a real meeting. Look at the same week in Google Calendar afterwards and the change is already there. The whole move is a drag and a keystroke, and your real calendar stays in step with what you are looking at.
Because the correspondence has not been left in another window, the constraint that decides the new time is in view at the moment the move is made rather than three messages back. Point runs the scheduling correspondence itself, so a move that needs agreeing rather than announcing does not become another thread for you to hold. Coming the other way, an ask like “any chance we could do Thursday instead” is spotted three paragraphs down a reply about something else, matched against the meeting it means, and the change readied for your approval. That half of the subject belongs to when they ask to move.
How much of that runs on its own is a dial you set, per kind of action, and scheduling carries its own. It ships on review, which here means a prepared move waits for you before anything reaches a client’s diary, and the moment to raise it is once you have watched a few land where you would have put them. Turned all the way up, Point makes the move and tells you afterwards. Every action sits in a record you can read back and reverse from, stopping where reality stops it: a new time already delivered to somebody else’s calendar gets changed again, not erased. For what the same treatment does to the other nine tenths of a mailbox, see benefits.
Common questions
How do I reschedule a meeting without going back to square one?
Pick the new time before you write, and pick it from the constraints the first negotiation already gave you. The thread will tell you they cannot do mornings, that half an hour was enough and that Wednesdays are out, and none of that stopped being true when the date did. Change the time on the existing event, send one short message naming the new slot and a fallback, and the whole thing costs one reply instead of the eight it took to arrange in the first place.
Should I cancel the meeting and send a new invitation instead?
No, edit the one you have. The calendar standard treats a same identifier update with a higher revision number as a rescheduling and a new identifier as an entirely different meeting, and the difference is not academic: cancelling loses the description, the attachments and the guest list you assembled, and it sends two emails, a cancellation that reads as the meeting being off and an invitation that reads as a new ask. People answer the first and leave the second.
Do people have to accept a meeting again after I change the time?
Effectively yes, and this is the one thing a move genuinely destroys. RFC 5546 requires the organiser to increment the event’s revision number whenever DTSTART, DTEND or DURATION changes, because such a change “will jeopardize the validity of the participation status of the ‘Attendees’”. The protocol’s own view of a time change is that every previous yes is now in doubt, so whatever your tracking said before the move, read it as unanswered afterwards and chase the ones that matter.
Who do I need to tell when I move a meeting?
Everyone on the invitation gets the update, and the people who are not on it get nothing. That second list is the one that bites: the assistant who keeps the other side’s diary, the colleague who blocked the hour afterwards, whoever booked the room or the cover, the person you promised to come back to after the call, and anyone who already declined and might now be able to make it. The update is also not guaranteed to arrive even for guests, since Google’s help notes that a guest who has opted out of change notifications will not get the email (checked 19 August 2026).
How much notice should I give when moving a meeting?
Enough that the other person has not yet built their day around it, which in practice means weeks out is bookkeeping, days out needs a sentence and a check on whether they have started preparing, and the morning of needs an acknowledgment that you are changing today rather than changing a date. Inside the hour, stop emailing and telephone, because a message arriving four minutes before a call reaches somebody who is already walking to a room.
What happens if I move one meeting in a recurring series?
You are asked to choose between this occurrence, this one and everything after it, and the whole series, and the wrong choice is silent until the following week. A single occurrence is right for a one off clash and wrong for a permanent change. Note also that a series can only be redirected forwards: the calendar standard defines a range covering an instance “and all subsequent instances” and explicitly deprecates the value that would have reached backwards, so history stays as it was recorded.
The short version
A booked meeting that has to move is an edit, not a fresh request. Both of you still want it, it is still the same length with the same people about the same subject, and one field has stopped being true. Change that field on the event that already exists rather than cancelling and starting again, because the identifier is what carries the description, the attachments, the guest list and every reference already pointing at it.
What the move genuinely costs you is the accepted column, which the standard treats as invalidated by any change of time, and the loose ends that were anchored to the old slot: the preparation, the travel, the debrief, the follow up you promised for that afternoon. What it does not cost you is the negotiation. The constraints that produced the original time are still in the thread, so find the replacement first, try the same slot a week later before anything else, and send one message that says whether this is decided or proposed, what has not changed, and what to do if it does not work.
Then tell the people the calendar will not. A coaching practice moving a fortnightly session mostly has one person to tell and a policy to honour, so the whole job is the notice and the sentence. A consultancy moving a four person review at a client site is telling the room, the assistant who keeps the diary and the colleague who cleared a morning to travel, none of whom are on the invitation. The rest of the trades this is built for sit between the two, and the list barely changes from one move to the next once you have written it down.