Grab the block, drop it half an hour later, let go. That’s a reschedule when it goes well, and it goes well far more often than the dread attached to it suggests. A booked meeting is the cheapest thing in your week to change. Everything expensive about it was settled once and has stayed settled: who’s on it, what it’s for, how long it runs, where it happens.
The gesture is small, and it does one thing. It writes a new time into the record.
The work the last four parts were about stays in your hands. The question the first part built is yours to ask. The calendars the third part reconciled are yours to read. The day at the far end that the fourth part had you write down is yours to picture. The drag holds no hour in reserve, and the far end hears about the change when a message arrives. That’s what a drag is: a decision written straight to the record, and the record is your own calendar.
Three things live in moving a meeting without restarting the negotiation: what a move disturbs, how to find the new time inside the constraints the thread already gave you, and the sixty words the covering message has to carry. That’s the whole of the manners and most of the mechanics. It’s said once, there.
This part is narrower. It’s about the second before you let go.
The gesture that decides instead of asking
Everything in this series so far has run the same way. You check the week. You choose the hours, name them, and hold them. The other person answers with a choice rather than a question. The decision goes into the message.
A drag turns that around. The decision goes into the calendar, and the message follows it.
Most of the time that’s exactly right, and it’s worth saying why. The change is yours, the notice is long, and the other person’s honest answer would be “fine either way”. Asking then is theater. You’ve made them read a message, form an opinion they don’t have, and write back. The answer they reach is where the calendar already was. An announcement is the shorter and the more respectful instrument.
Asking earns its place when their answer is genuinely in doubt. Then the gesture arrives ahead of the question, and whatever you write underneath it reads a decision back to somebody who was left out.
You settle that before you write a word, and the instrument settles it for you. Once a calendar update has landed, a covering note can only report it, however carefully the note is phrased. That’s why the choice between deciding and proposing lives in your hand rather than in your prose. The collection piece is blunt about what happens when a message tries to have it both ways. By the time you’re writing, the choice is behind you.
The two large mailboxes differ on how tightly the edit and the announcement are bound together, and that changes what your hand is committing to. Microsoft’s page on changing an appointment, meeting, or event states one half of it plainly: “When changing a meeting you’ve created, you must send an update in order to save the changes” (checked September 6, 2026). There, the edit and the notice are one act, and the first arrives with the second. Elsewhere they come apart, and whether the guests hear about the change at all is a separate choice made a moment later, which the collection piece covers properly.
So the first check is the shortest one in this piece. Before your hand is on the block, know whether you’re announcing or asking. If you’re asking, hold off on the drag. The reason is practical rather than about etiquette, and it’s set out further down.
The lookup a drag does not run
A drag lands where the grid is white, and the first part of this series spent a section on what white space actually tells you: that nothing is written there yet.
Moving a meeting is where that bites hardest, because a drag is a spatial judgment. The gap looks big enough. That’s the entire query, and your eye runs it in about a fifth of a second while your hand is already moving.
Three things sit outside that query, and they’re the same three every time.
Your standing rules. Nothing before ten, no client calls on Friday, Wednesday afternoon belongs to the work. Written down, those are a filter that runs every time. Held in your head, they’re a judgment you re-apply by hand, and a drag is the moment that judgment gets skipped.
Your other calendars. The white space you’re aiming at belongs to whichever grid you happen to be looking at. A grid that draws all of them shows you Thursday as it really is. Reconciling that is the third part’s whole subject, and a hurried move is the specific moment people skip the second look.
The shape of the day around the drop. The first part makes the case that an hour placed hard against an existing meeting costs about what the invitation says. The same hour dropped into the middle of a clear morning takes the morning with it. A move is the one time you get to place a meeting well for free, since you’re placing it anyway. It’s also the time people place one worst, because the target they pick is whatever sits nearest the block in their hand.
Then the part that surprises people. The search a move needs is harder than the search that produced the original hour.
The original had room. You were looking at a whole open window, several days out, with every slot still in play. The replacement search has a shorter horizon, because the meeting is coming up rather than being arranged. It carries a constraint the first one lacked, which is that one specific slot is now spoken for. And it usually carries a second, which is the reason you’re moving at all. Move the meeting to clear Thursday morning, and Thursday morning is off the table, along with the hour on either side of whatever fills it.
Three parts of the query got tighter, and the attention you’re giving it went down. That’s the wrong way round. It’s the whole argument for asking the week a question rather than reading it, even when the change is small enough to do by hand, and especially then.
Half an hour at the far end
Half an hour is the smallest change in scheduling, and nobody thinks twice about it. On your own grid that instinct is right. Thirty minutes is one row. It’s the unit the interface is built out of.
At the far end, half an hour is a position inside a band. The band is the thing the fourth part had you write down.
Take an overlap of two hours: eight to ten in your morning, four to six at the end of their afternoon, with a meeting sitting at the front of it. Nudge it half an hour later and it still fits, right up to the edge. Nudge it half an hour earlier and it has left the band entirely, and it leaves quietly, because your grid draws your own clock only. The same gesture, in the same direction, is free at one end of a band and expensive at the other. On a wide enough gap it changes the day.
Two things follow, and the first is nearly free.
A second column makes this visible while your hand is still on the block. A display zone beside your own week is the cheapest thing in the whole of this subject, and a move is when it earns out. A move is the moment you convert from memory with the least attention you’ll give it all day. Reading their clock off the screen is a different skill from remembering the difference, and only one of the two survives being in a hurry.
The second follows from what software knows about somebody else’s day. One mechanism draws another person’s working day for you, and it’s narrower than people assume. Google’s help page for working hours and location describes the feature as a way to let people know you are unavailable when they try to schedule a meeting with you. It states its own boundary in a sentence: “You can use working hours and availability if your account is through your work or school organization” (checked September 6, 2026). Inside one organization that’s a real guard rail. Between two, which is what almost all client work is, the band you wrote down by hand is the only version you have.
The far end has its own week, and it sits outside every system you own. The thirty minutes you took off the front of their afternoon may be the thirty minutes that were holding a school pickup apart from a call. A drag stays silent about the cost it puts on somebody else. A sentence is the instrument that finds out. Which moves are worth one, and which are genuine bookkeeping, is the collection piece’s list.
One last thing belongs here rather than anywhere else. A move of a few weeks can carry a meeting across a clock change, so it now happens at a different local hour from the one the other person wrote down. That’s the same failure the fourth part describes for standing meetings, arriving in a one-off, and what to send before a changeover weekend is where the habit lives.
The meeting that is not yours to move
On a grid that draws every calendar you keep, the meetings you created and the meetings you were invited to look identical. They behave differently, and the third part explains why. An event belongs to the account that wrote it, and that ownership decides where a change can legitimately start.
Rescheduling is where the difference becomes expensive. Microsoft’s own page on changing an appointment or meeting says both halves of it in two sentences. The first: “You cannot change the details of a meeting you were invited to by others”. The second, on what happens when you try: “Outlook will warn you that the organizer will not be notified of the change and the meeting on your calendar will be at the wrong time” (checked September 6, 2026).
Sit with the second sentence, because it describes a success rather than a refusal. The gesture works. Your copy moves. Nothing else does. You’re holding a private, confident and wrong version of a meeting that everybody else still has at ten. Nothing later reconciles the two, because from every other system’s point of view nothing happened. An error message would have been a better outcome.
So the check is one question, asked before the gesture rather than after it. Whose meeting is this. If the answer is somebody else, the move is a message rather than a drag. It goes to whoever owns the event: the organizer, or the assistant who keeps the calendar, or the client’s system it was created in. Sending a constraint to the person who can act on it costs one more message and gets it right, and the collection piece is right that two versions of one move is worse than a slow one.
Two related cases end the same way, and both are worth knowing on sight. Each one needs something other than a drag.
A meeting created from the wrong account stays with that account. The transfer both platforms offer works inside an organization, and your accounts are separate organizations, so the remedy is a cancellation and a fresh invitation. That’s the third part’s finding, and a move is when people discover it.
A meeting that a booking tool created is recorded in two places, and whether the gesture reaches the second of them depends on plumbing somebody else built. Where it falls short, your calendar says Friday and the invitee’s confirmation still says Thursday. The conditions under which the two stay in step are documented, and they’re in the collection piece rather than here.
When the move has to be offered
When their answer is genuinely in doubt, you’re making an offer about a meeting rather than moving one, and the machinery from the second part applies at a smaller scale.
The first move people make here is the one that costs the most, and it’s the one people get backwards.
Keep the old hour while you offer a new one. The original slot is your fallback, and it’s yours for exactly as long as you leave it alone. Drag first and ask second and it’s white space again: your own next lookup will offer it, a page you published will sell it, a colleague with visibility will book across it. Then the answer comes back saying Friday is hard and could you keep Thursday, and both hours are gone.
So a proposed move has you holding two hours, and one of them looks after itself. The old one holds by being left alone. The candidate takes a tentative block, like every other offer you make. Set its expiry as you place it rather than when somebody answers, for the reasons the second part sets out at length. When the answer arrives, one gesture settles all of it: the meeting moves, the tentative block comes off, and the hour you left goes back into stock on purpose.
The side effect is useful. The two states are legible on the calendar itself. An announced move is an event at a new time. An offered move is an event still at the old time, with a tentative block sitting next to it. Anybody reading your week can tell those apart, including you on Friday afternoon, and the messages the two of them produced are harder to tell apart than that.
Two smaller things belong to pieces that already own them. How many alternatives to put in front of somebody on a move, and why that number is smaller than it is for an opening offer, is the collection piece’s. And a reply that agrees to your new time while changing the length or the shape of it is a counter-offer wearing an acceptance. The second part flags that for opening negotiations, and it’s more common here, because by now the other person has a stake.
What speed does not settle
Four limits, and a fast gesture makes the first one easier to duck rather than easier to face.
Whether the meeting should happen at all. Moving something is the polite alternative to saying it has lost its purpose, and a two second move makes that alternative two seconds easier. The honest version is a short cancellation with the reason in it and an offer to pick the subject back up, and when moving it is the wrong answer sets out the rest of that family.
Whether this is the first move or the second. The grid keeps no memory of the last one. The instrument charges the same for both, and the other person keeps a tally: one moved meeting is unremarkable, and the same meeting moving twice is the thing people notice. That memory lives with you, or in the thread.
The copy somebody else is keeping. Their calendar gets the update. The copies that live outside a calendar wait for a person: an agenda already circulated, a room booking made by somebody who is not a guest, an assistant’s own note of your Thursday. Your gesture reached one system, and the others find out when somebody tells them.
Everything that was anchored to the old hour. A calendar moves one block. The preparation, the travel, the debrief and the follow-up you dated off the meeting stay exactly where they were. That list, and the second list of people who are affected and off the invitation, are the collection piece’s. They’re the reason a moved meeting sometimes produces four things to fix.
Dropping a block into a checked week
Point is a full email client running on the Gmail or Microsoft 365 mailbox you already have, and the calendar inside it is your real one rather than a picture of it. For this particular job that means the move is a gesture, and the checks around it are in the same place your hand is.
The gesture itself is short. Take hold of the block and move it. A dashed outline marks the slot it’s about to take while you’re still deciding, so the placement is something you look at rather than something you find out about afterward. Letting go places the block, and one keystroke commits it, which is what keeps a two second reschedule from being an accidental one. Open the same week in Google Calendar afterward and the change is already sitting there.
What the series adds is the week you’re dropping into. It’s the reconciled one, so the white space under the block has already survived every calendar you keep rather than answering for whichever account you happen to be composing from. An event’s time zone is a label you can tap, and the picker takes a city, an abbreviation or a plain offset. The far end can be read off the screen in the second before the confirm rather than converted from memory afterward. Dismissing that view puts the event back in your own clock and changes no settings.
Where the move needs agreeing rather than announcing, the correspondence stays one job. Say what has to change, in plain words, on the thread it belongs to. Point proposes from your real availability and reads whatever sentence comes back. Once a time is agreed and you approve it, the event moves on the calendar you actually use, with everyone on it.
Scheduling keeps an autonomy setting of its own, apart from the rest of your mail, and it opens on review. The thing worth watching before you raise it is where prepared moves land, since a move is the one scheduling action that changes something a client has already written down. Further up, Point carries the exchange to the limit you set, and each position on the dial is written out. What Point did is kept in order, and undo runs back along that record. It stops where your own systems stop: a new time already delivered to somebody else’s calendar can be changed again, not erased. Everything else Point does is the longer list. And the trades this is built for decide which half of this piece matters. A coaching practice moving a standing session is mostly working on the far end and the notice, while a consultancy moving a meeting somebody else created is working on who owns the event.
Everything above starts in the same place. You know the meeting has to move, and the only question is what you do next. That half of rescheduling behaves. The gesture is two seconds, the checks around it are about twenty, and the whole thing is finished before you’ve left the thread.
Plenty of moves start somewhere else. They start four lines down somebody else’s reply, after the part about the invoice, in a sentence wondering whether Thursday is still sensible given how the week has gone. It carries no request, no time, and nothing that catches an eye at 11:40 on a Tuesday.
A two second move is only ever as fast as the moment you find out it’s needed, and the sentence that calls for it is written to be easy to send rather than easy to see.