Half the reschedules in your week start with you. You know the meeting has to move, and the last part is the whole of what to do about it: one gesture, four checks, and a covering line.
The other half start somewhere in the middle of somebody else’s reply. The sentence reads like small talk, and it leaves the thing it’s asking you to change unnamed.
Reading that sentence is its own subject, and it’s worth saying so at the top so you can go and get it. Why the ask arrives stripped of every word you scan for, what its usual disguises are, and the one line that ends the expensive part of the problem are all in catching a reschedule request buried in a reply. That piece is about the message in front of you. It’s the better half of this subject.
It assumes three things. That the reply reached a mailbox you actually read. That you could tell which meeting it meant. And that you could say, in the same pass, whether the time they named was any good.
Those three are machinery, and the previous five parts have already installed all of it. This part turns it the other way round. For five parts the query ran outward. You asked your week a question and turned the answer into a message. Now a message arrives carrying somebody else’s constraint, and the same machinery has to answer inward, at the busiest moment it gets asked anything all week.
Where the ask was always going to arrive
The third part had you decide which of your calendars a meeting gets created on. One of the four questions in that decision was where the replies land. That question looked like it was about acceptances. It was about this.
The account that created the event is the return address on everything the meeting ever produces. The accepts, the declines, the joining problems on the morning. And the sentence on Sunday night saying Wednesday has become difficult. You chose that account for good reasons, most of them about which address a client sees and who gets to edit the event. In the same act you chose something else. You chose the inbox where the most valuable message this meeting ever sends you will sit. It barely felt like a decision at the time.
It turns up in three places, and some are much better than others.
The thread the invitation went out on. The best case, and the one everything downstream assumes. The correspondence about the meeting and the request to change the meeting sit in the same place.
A different thread in the same mailbox. They have the year end message open in front of them, so the line about Wednesday goes in there. That’s reasonable of them. A whole separate email about a calendar change would make more of it than it deserves. The consequence is mechanical rather than social. The meeting’s correspondence now lives in two threads, and anything that files by conversation keeps them apart. When you go looking for what was agreed, you’ll open the wrong one.
A mailbox that’s barely yours. This is the expensive one. A booking tool sent the confirmation from its own address, so the client’s reply goes to a system rather than to you. The event was created on a client tenant, so the notice arrives in a seat you open on Thursdays. The invitation went out from a personal account two years ago, because that was the account open on the laptop. That account now holds a live negotiation about a client meeting.
One related case catches people who have done everything else right, and it’s worth knowing on sight. The ask often comes from somebody who’s off the invitation. A client’s assistant, a partner answering for them, a colleague copied in halfway down. Your calendar only knows the guest list. So when you make the change, the update goes to the guests, and the person who actually asked hears silence. They wait. Then they ask again, and the second ask reads as a chase. A line in your reply is the only thing that covers it, because the gap is in the addressing rather than in your manners.
The audit is short, and it uses a list you may already have. The third part asks you to write down everything allowed to create an event in your name. Put a second column next to it. Where does a reply to that thing arrive, and do you open that place daily? Any row where the second answer is no is a row where a client asks you to move a meeting and gets silence for a week. Both of you did everything right.
An ask with no meeting in it
Here’s the ordinary shape of one, in a reply about something else:
“Wednesday is going to be tight for me now, the auditors moved to that week.”
Set the noticing aside, which the collection piece covers. Assume you saw it. You’re holding a request that names a day and leaves the meeting out, and something has to put one back.
That join is structural work, and it feels more automatic than it is. Your calendar is indexed by time. Your mail is indexed by conversation. The meeting keeps its own identity somewhere else again. The calendar standard gives every event a unique identifier, defined in RFC 5545 as being there “to specify a persistent, globally unique identifier for the calendar component”. That string is what every system involved uses to know that two copies are the same meeting. Hardly anyone has ever seen one. It travels in the invitation, and it stays out of every reply a human writes.
So a person makes the join, out of memory, from a sentence that names a day. That’s a lookup, the same one the first part asks you to stop doing by eye. It goes wrong in the same way. You run it at 11:40 while you’re inside something else, and you get an answer that’s usually right.
Usually right is the problem. Two failures come out of it, and both stay quiet.
The second meeting. You have one thing with this client on Wednesday, so you move it. They had two. The one they meant is the internal review your name is on, organized by somebody else. You’ve just moved a conversation they left out of the ask.
The one somebody else owns. The Wednesday thing they mean was created by their office. You’re looking at a copy, and the last part is blunt about what happens when you drag a copy. The gesture succeeds, your calendar goes quietly wrong, and it stays that way.
Running the lookup as a query catches both, and the query is a surprising one. Search the person, and let the day go. Their address, across the window they named, in the reconciled week rather than in whichever calendar you happen to have open. What comes back is every meeting the two of you have in that window, with the organizer written on each one. That answers both questions above in a single pass, and it takes about as long as remembering would have.
One small thing belongs in the answer as a result. Name the meeting as well as the day. “Wednesday’s scope review” costs four words more than “Wednesday”, and it settles the ambiguity while settling it is still cheap. If you picked the wrong one, they’ll tell you before anything moves.
The ask that is already a field on your calendar
Some requests to move arrive as data rather than prose. Those slip past you more reliably than the buried ones.
A guest’s answer to an invitation is a stored property of the event, one per person, and the vocabulary runs wider than yes and no. RFC 5545 defines a participation status whose purpose is “to specify the participation status for the calendar user specified by the property”. Its values for a meeting are needs-action, accepted, declined, tentative and delegated. The specification gives it a default too, and the default is needs-action. That’s the state an invitation sits in while everyone leaves it alone.
That default is what makes this the quiet one. A guest who is stalling and a guest who has yet to open the invitation leave the same mark on your calendar.
The rest of it arrives in the form least likely to be read. Google’s page on responding to event invitations says that “when you respond to an invitation, the organizer gets a notification”, and that a guest may attach a note, which is “visible to all invitees” (both checked September 6, 2026). The note is optional, so the common case is a bare status change. It lands in the run of calendar notices most people clear on sight.
What each state is worth checking for is short.
A bare decline, three weeks out. That’s a request to move with the request taken out of it. Somebody who wants to cancel outright usually says so. Somebody who wants a different time, and would rather skip the negotiation, declines and waits to be asked.
A maybe on one occurrence of a standing session. Usually it’s about that occurrence alone, and usually it’s a conflict they expect to clear. It’s worth one sentence from you. Leave the calendar as it is for now.
Silence on a client meeting inside two weeks. Read it as a signal rather than as agreement. It’s the most common precursor to a reschedule request arriving late, because the person has known for a while and is still looking for a comfortable way to say it.
The useful part is that this form of the ask is a field rather than a sentence, so you can put a question to it. Once a week, look across everything in the next two weeks. See who answered maybe, and who has still to answer. That’s the same move the first part makes about your own availability. Query the grid instead of scanning it. It takes under a minute, and it’s the one place in this subject where you find out before they tell you.
This Wednesday, or every Wednesday
A standing session is the most-moved object in most practices, and the ask about one is ambiguous in the same way almost every time.
“Could we do Thursdays instead?” might mean this week, because of the auditors. It might mean from now on, because their Wednesdays have changed for good. People rarely say which. Partly they’re still deciding. Partly the permanent version is the bigger imposition, and the whole reason the ask is softened is to make impositions smaller.
Your calendar makes you settle the ambiguity on the spot. Microsoft’s page on creating, modifying or deleting a meeting request in Outlook.com sets out the three choices you get when you edit a repeating event. “This event” changes “the event you’ve selected in the calendar”. “This and all following events” changes the selected event “and all subsequent events in the series”. “All events in the series” opens “the complete series of events” (all checked September 6, 2026). Google Calendar asks the same question in the same shape, telling you to “choose which events in the series the updates apply to” when you save (checked September 6, 2026).
Three options, and the dialog arrives at the moment your attention is lowest. Most people read it as a two-way choice between this one and all of them. The middle option is the one that matches what somebody usually means by a permanent change, and it’s the one that gets skipped.
The two ways of getting it wrong cost very different amounts.
Choose this event when they meant all of them, and the same conversation comes round again in two weeks. That’s mildly irritating, and it corrects itself. Choose all events when they meant this one, and you’ve quietly rewritten six months of somebody’s Wednesdays, including occurrences they had already planned other things around. Your side of it stays silent. It surfaces later, as a person missing a session they never agreed to move.
So name a permanent change as one before you touch anything, and handle it as a different kind of decision, because it is one. Moving next Wednesday is an edit. Moving every Wednesday is a new standing commitment. Reread the fourth part if the client is in another zone. A recurring session placed inside a narrow band of overlap isn’t one meeting a week, it’s your entire capacity for that direction of the world.
One free thing is available while you’re in there. Editing the whole series is the moment the meeting’s anchor is open. If the session is anchored to your city while the client sits somewhere that holds its clocks steady all year, this is the cheapest chance you’ll get to move the anchor to theirs. That trade, and why it’s the right way round, belongs to the fourth part.
What their sentence was worth keeping
The first part ends its list of limits with a concession. You can be excellent at all of this and still get a no, because the binding constraint lives on the other side of the correspondence, out of your view.
A reschedule request is that constraint, arriving unprompted, in writing, for free. It’s the best view of somebody else’s week you’ll ever be given. The ordinary fate of it is to be answered and then dropped, because the message got dealt with.
There are two halves in one of these, and they keep for very different lengths of time.
The perishable half. The auditors are in that week. They’re in Denver on Tuesday. Useful for one exchange and spent afterward. This is the half everybody keeps, because it’s the half the reply is about.
The durable half. Fridays are gone from now on. They’ve moved, and the city in your head is the old one. The school run changed, so mornings before ten are finished. Their quarter end is the last week of every second month, and that week is always booked. Each of those is exactly what the fourth part asks you to write down about a relationship, and here it arrives without your having to ask. Each of them gets re-derived badly in six weeks if you let it go.
Their proposal belongs in the durable half too, and it’s the piece most often thrown away. If they offer Thursday at eleven, you’ve just learned something your own systems can never produce. Thursday at eleven is open in their week. That’s worth more than the constraint, because a constraint only points you away from things.
So the discipline is one step long. When you answer the ask, put the durable part where your standing rules live, in the same pass, before the thread closes. It costs about ten seconds. It’s the difference between a client who has told you their Fridays are gone and a client who has told you three times.
From there the mechanics are already written. If you can agree to what they proposed, the change itself is the last part’s two seconds and four checks. If their answer to your alternative is genuinely in doubt, you’re making an offer rather than a move. The second part’s machinery applies at a smaller scale, with the one rule the last part sets out most firmly. Hold the old hour while you offer a new one.
What catching it in ten minutes does not buy
Four things, and the first one sits outside all of this.
A person who keeps it to themselves. Somebody decides to ask, leaves it, and turns up to a meeting they had already privately given up on. Mailboxes and queries stay out of reach of that. A thread that simply stops is a different problem with a different remedy, and the remedy is bringing an unanswered thread back rather than anything on this page.
An ask made away from mail. On the phone. In the last two minutes of the previous session. In a text message on a device you’d put down. Those exist and they’re common, and one thing catches them: writing it down at the moment it happens. Anything that reads email stays blind to them.
Being able to act on it. You can find the sentence in ten minutes and still be holding a meeting somebody else created. Then the move is a message to whoever owns the event, rather than a change you make. That costs one extra hop. The awkward part is that the person who asked sees none of it, so they’re waiting on you while you’re waiting on somebody else. Say so, and keep them posted while you sort it out.
A meeting that only ever existed out loud. The first part lists things agreed out loud among the categories your calendar misses, and this is where that comes due. An ask about a call you agreed to on a call has nothing to match against. All the query returns is a clear Wednesday, which looks like good news and is the opposite.
Answering it out of a week already checked
Point is a mail client in its own right, working on the Gmail or Microsoft 365 account you already use. What that buys here is narrow, and this is the whole of it. The reply carrying the ask and the calendar that has to answer it sit in one place. Mail is read as it arrives rather than when you get to it, so a sentence three paragraphs into a message about an invoice is found by something that read the message to the end. The thread rises in the feed with the ask already lifted out of it.
The part that matters for this series is what happens next, because a flag on a thread still leaves you the join and the lookup.
Point works out which meeting the ask refers to. Point prepares the change against the reconciled week, the same week the first part built and every part since has been adding to. So the time in the prepared move is one that cleared all of your calendars, rather than one that suited whichever account the message happened to arrive in. Where the far end is in another zone, an event carries its zone on a label you can tap. What the picker behind it accepts is a city, an abbreviation or a plain offset, so their eleven is read off the screen before you approve. Approve it, and the meeting shifts on your live calendar, guests and all. Where the ask needs a counter-proposal instead of a yes, Point proposes from your real availability, then reads whatever sentence comes back. A move that needs negotiating gets settled there, instead of becoming one more thread you carry across the week.
Scheduling has an autonomy setting to itself, held separately from the rest of your mail, and out of the box it sits on review. What’s worth watching here, as against the other parts of this series, is the join. Whether the meeting Point matched is the meeting you would have matched. And whether a prepared change to a standing session is scoped to the one occurrence or to the series. Those are the two judgments in this piece that are made from a sentence rather than from a calendar, and watching a few of them go past is how you find out what raising the dial would be agreeing to. Wound higher, Point runs the exchange as far as you’ve allowed, and the dial sets out what each position means. Everything done on your behalf is written down in sequence, and an undo works off that sequence rather than off a reconstruction. Its limit is the ordinary one. A new time that has already reached a client’s calendar can be updated again, and the first one was still seen. The full list of what Point does runs much wider than one subject, and the trades it was built around decide which section here earns its keep. A coaching practice is mostly dealing with standing sessions and the scope of the edit, while a consultancy is mostly dealing with asks that arrive from people who are off the invitation.
Back where the series started
Six parts ago, a message arrived at 11:40 on a Tuesday asking for half an hour next week. It sat until Thursday, and the writing was the easy part. What held it up was a lookup you could run only from somewhere else.
This part is the same message with the sequence reversed. The meeting already exists, and the constraint belongs to them rather than to you. The lookup you’re missing is which of your Wednesdays they meant, and whether Thursday is any good. Everything between the two, the holds, the writing account, the band, the anchor, the gesture, has been one long answer to a single question. Can your week be asked something at the moment somebody asks it, rather than at the moment you next have the calendar open.
When the answer is yes, this stops being a subject. A request to move lands, gets found, gets matched, and gets answered in a sentence with a real time in it. The two seconds of dragging at the end is the least interesting thing that happened.
Which leaves the one decision that stays yours, and it’s worth being honest about it. Six parts have plenty to say about moving a meeting and nothing to say about whether it should exist. A week that answers instantly will book, move and rebook a standing call that stopped being useful in March, faster every time, and it will stay quiet about it. A person asks that question or it goes unasked. The good news is that you now have somewhere to ask it from. A week you can see all of, on a Tuesday, from inside the message.