Most requests to move a meeting are not written as requests. They arrive as a clause inside a reply about something else, wrapped in an apology and stripped of every word a reader scans for. The habit that catches them is small and takes a few seconds. The cost of not having it lands two days later, in somebody else’s diary.
- Politeness works by removing the signals you are scanning for. A request softened enough to be comfortable to send has very few request-shaped words left in it.
- The largest variable in how fast the ask gets answered is which day of the week it occurred to them, and the weekend is when people notice that Tuesday will not work.
- What perishes first is not the meeting. It is the alternatives, the hour you would have given back, and their ability to plan around either.
- The expensive reply is the one that answers everything in their message except the sentence about Tuesday.
The sentence that is not a question
Here is the ask, as it usually arrives, in a reply from a client about something else:
“Thanks for sending those through, I will look properly this evening. One thing, I am in Leeds all day Tuesday now. Anyway, on your second point, I think the answer is…”
There is no question in that. No question mark, no “could we”, no “would you mind”, nothing a person skimming for something to answer would stop on. It sits between two sentences about a different subject, in the middle of a paragraph, and it is doing the work of “please move our Tuesday meeting”. The writer knows they have asked. You have not noticed that you were asked.
That is not carelessness at their end. It is the opposite, and the mechanism has been measured. Cristian Danescu-Niculescu-Mizil, Moritz Sudhof, Dan Jurafsky, Jure Leskovec and Christopher Potts built a corpus of requests annotated for politeness and set out which linguistic strategies actually drive the perception, in A computational approach to politeness with application to social factors, presented at ACL in 2013. Of being indirect they write: “Being indirect … is another way to minimize social threat. This strategy allows the speaker to avoid words and phrases conventionally associated with requests.”
That last clause is the whole problem in a line. Politeness is not a coat of paint applied to a request. It is the removal of the parts that make a request recognisable as one. The strategies they measure are exactly the ones that gather around a reschedule. Apologising, which “deflects the social threat of the request by attuning to the imposition itself”. The counterfactual modal, “could” and “would” in place of “can” and “will”. The first person plural, which spreads the burden across both of you. And hedges, which the authors note combine with indirectness to convey “that the addressee is unlikely to accept the burden”, giving them “a face-saving way to deny the request”. Their scores run the other way too: an opening of the blunt “so can you do this or not” kind lands in the politest quarter of requests only 9% of the time. Their corpora were Wikipedia and Stack Exchange rather than business email, so take it as a description of how the language works rather than as a measurement of your inbox.
Now consider where a reschedule sits on that scale. You are withdrawing from something you already agreed to, and what you are taking back is an hour of a finite week that somebody set aside on your word. Not many asks in professional correspondence are more awkward, so it gets the full apparatus, and the rule that falls out is worth keeping: the more the person minds asking, the less it will look like asking.
The forms are a short list, and they repeat.
As a fact about their week rather than a request about your meeting. “I am in Leeds on Tuesday.” “We have the auditors in that week.” A statement, delivered in the hope that you will draw the conclusion, because drawing it yourself would be the imposition.
After the real subject, and often after the word “anyway”. The ask goes last because that is where an imposition goes. The politeness paper measures this one directly, as the strategy it labels indirect, with “by the way” as its example: requests carrying it fall in the politest quarter 58% of the time. A postscript is the same move.
Wrapped in permission for you to refuse. “No rush.” “Only if it is easy.” “If that does not suit, ignore me.” Every one of those is a real request with an escape hatch fitted to it, and the hatch is what your eye lands on.
As a question about whether the meeting is still happening. “Are we still all right for Tuesday?” reads as confirmation-seeking and is very often the opening of a negotiation. Somebody wanting confirmation has a reason to want it, and the reason is the half of the message they did not send.
From somebody who is not on the invitation. A client’s assistant, a colleague copied in, a partner replying on their behalf. The words may be perfectly direct, but they arrive from an address you have no history with, in a thread you did not expect them in.
On a thread that has nothing to do with the meeting. They are already writing to you about the year end, so they mention Tuesday there, because a fresh email would make it a bigger thing than it is. The correspondence about the meeting is somewhere else entirely, which is where you will go looking for it later.
With no words at all. A response of “maybe” on the invitation, or a decline that carries no note. That is a person who has told you something and left you to work out what.
As a formal counter-proposal. Occasionally the ask arrives as a proper calendar message, which is the next section, and which is not the rescue it sounds like.
The button both calendars have, and why the ask still comes as prose
Calendars have had a dedicated mechanism for this since 2009. RFC 5546, the iCalendar Transport-Independent Interoperability Protocol, defines a method called COUNTER, “used by an Attendee to negotiate a change in an iCalendar object. Examples include the request to change a proposed event time or change the due date for a task.” It defines the answer as well, DECLINECOUNTER, and describes the exchange plainly: “The Organizer rejects the counter proposal by sending the Attendee a DECLINECOUNTER method. The Organizer accepts the counter proposal by rescheduling the event.”
Both major calendars implement it. Google’s help page on responding to event invitations says of the feature: “If you can’t attend an event or need to inform the event organizer about schedule conflicts, you can propose a new time.” Microsoft’s equivalent page for proposing a new meeting time in Outlook describes the organiser’s side: “If you’re the meeting organizer and a recipient proposes a new meeting time, you can decide whether to accept or decline the proposal” (both checked 19 August 2026).
So the tidy version of this subject exists, has for years, and is on the screen of everybody you correspond with. Four reasons it does not solve your problem.
The gaps are exactly where the reschedules are. Google’s page states that the option cannot be used for “Events with more than 200 guests” or “All day events”. Microsoft’s is more consequential for a small practice: “You can’t propose a new time for recurring meetings.” A fortnightly client session is the single most rescheduled object in most diaries, and it is the one the mechanism does not cover. Microsoft also notes that “Meeting organizers can send meeting requests that restrict the ability to propose alternate meeting times”, so whether the option appears at all is partly a decision somebody else made about your invitation.
It only works on an event you are looking at. The reschedule occurs to somebody while they are reading their mail, or on a train, or halfway through writing to you about something else. Using the formal mechanism means leaving that, finding the event, and treating the thought as a piece of calendar administration. Almost nobody does. They finish the sentence they were writing instead.
It is a direct speech act, which is what they were avoiding. A counter-proposal is unhedged by construction. It states a new time and asks you to accept or decline, with no room for “if it is easier” or “no rush at all”. For an internal meeting between colleagues that is a virtue. For a client withdrawing from a time they agreed to, it is blunter than they want to be, and they will reach for prose precisely because prose can carry an apology and a reason.
And when it does arrive, it looks like bookkeeping. A counter-proposal lands as a calendar notification, in among the accepts and declines, which is the category of mail everybody has trained themselves to skim. An ask you have to notice inside a paragraph and an ask you have to notice inside a notification are the same problem wearing different clothes.
Treat the feature as a thing that occasionally does you a favour, not as a habit you can install in other people. What you can install is on your side of the correspondence.
What a day of silence costs
Start with when the ask was written, because that turns out to matter more than anything in it.
Liu Yang, Susan T. Dumais, Paul N. Bennett and Ahmed Hassan Awadallah measured what predicts an answer across the Avocado research collection, a year of ordinary operation inside one technology company, in Characterizing and Predicting Enterprise Email Reply Behavior for the ACM SIGIR conference in 2017. Weekday mail in their data drew a first reply in under an hour at the median. Then: “emails sent on the weekend have 13 (for Sunday) or 30 (for Saturday) times longer reply latency.” Their explanation is the obvious one, that people do not check mail as regularly at the weekend, and they note that most of it simply waits until Monday.
Read the ratio rather than the minutes, because the archive dates from the turn of the century. What the ratio says is that the single largest variable in how fast a reschedule request gets answered is not how clearly it was written or how much it mattered. It is which day of the week the thought occurred to the person writing it. And the thought occurs at the weekend more than its share of the time, because the weekend is when people look at the shape of the week ahead and notice that Tuesday will not work.
The same paper’s other findings stack on top of that, and they are the subject of unanswered emails, and the threads that come back, which reads them properly. The short version for this purpose is that mail carrying a request, mail crossing out of the company, and mail longer than a few lines are each answered more slowly than mail without those properties. A client’s reply with a reschedule buried in it has all three, and it was written on Sunday evening.
So the ordinary case is not a failure of attention. It is Sunday night, and you find it on Monday, and the meeting is Tuesday. Here is what the intervening hours actually spend.
The alternatives thin out. Thursday at eleven was free in their week on Sunday. By Wednesday afternoon somebody else has taken it, and now you are looking for a slot that suits two diaries that have both moved, which is the point at which a move stops being an edit and becomes a negotiation again. The way to keep it an edit is moving a meeting, and every hour of delay makes it less available to you.
The hour you are giving back stops being worth anything. A Tuesday afternoon released on Sunday is a slot somebody can book. Released on Monday evening it is a hole in your Tuesday. If you publish availability, the difference is close to automatic, because a page answers the question at the instant somebody looks at it, which is booking links.
They resolve it without you. Between asking and hearing, the careful ones hold both slots and commit to neither, which costs them a day of their own week. The rest act on the reasonable assumption that they told you: they book over your Tuesday, or they decline the invitation, or they simply do not come. A bare decline arriving on Monday has no counter-proposal in it, no reason, and none of the goodwill that was in the original message.
And silence starts to mean something. This is the real cost, and it is not the scheduling. If you answered the invoice question in their email and said nothing about Tuesday, you have proved you read the message. Your silence on the ask is now an answer. It reads either as a refusal you did not have the manners to write down, or as a signal that their week is not something you thought worth a sentence. Neither is what you meant, and neither is repairable by explaining on Wednesday that you missed it, because the explanation is that you read their email and skipped the part about them.
That last one is why the reply matters more than the rescheduling. The perishable thing is not the slot. It is the hours in which they do not know whether they have been heard.
Reading a reply for asks and not for questions
The habit is one adjustment, and it is not “read more carefully”, which is advice nobody has ever successfully taken. It is to read a reply once through to the end before answering any of it.
Almost every missed reschedule is the same accident: the first paragraph contains a question you can answer, you answer it, you send, and the second half of their message is now in a thread you consider dealt with. Reading to the end first costs about eight seconds and removes the entire failure mode.
While you are doing it, these are what to stop on.
Any date or day name that is not about the subject of the email. If a message about an invoice mentions Tuesday, Tuesday is doing something.
Words of absence. Away, out, off, travelling, on site, at a client’s, in Leeds, with the auditors, back on the ninth. These are the ask in its commonest disguise, and they are the reason a scan for question marks fails.
Hedges attached to anything with a time in it. Any chance, would it be possible, if it is easier, no rush, only if, might we, could we possibly. The hedge is a marker of the request, not a substitute for one.
An apology with no visible cause. “Sorry to be a nuisance” in an otherwise unremarkable email is a strong signal that the imposition is somewhere further down. An apology attaches itself to an imposition, and if you cannot see the imposition it has attached to, keep reading.
The last paragraph and the postscript. Because that is where an imposition is placed, by nearly everyone, nearly always.
A change of tense about a commitment. “I was going to bring the figures on Tuesday” is not the same sentence as “I will bring the figures on Tuesday”, and the difference is a decision somebody has already made.
Anything from a name you do not recognise on a thread you do. An assistant appearing in a client’s thread is usually appearing about a diary.
None of this is a system, and it does not need to be. It is a short list of shapes that repeat, and after a fortnight of noticing them you will stop having to think about it. What the habit is really doing is buying you the difference between answering on Sunday and answering on Monday, which, on the arithmetic above, is most of what this subject costs.
The reply that ends it
The answer to a buried reschedule request is one sentence, sent inside the reply you were writing anyway, and it does not have to contain a new time.
That is the part people get wrong. They see the ask, cannot immediately work out what to offer, and defer the whole message until they can. So the acknowledgment, which was free and perishable, waits behind the proposal, which is neither. “Yes of course we can move Tuesday, let me look at Thursday and come back to you this afternoon” ends the expensive part of the problem, and it costs you nothing but a line.
Four things belong in the answer.
Whether the move is fine, said before anything else. They asked a question they found awkward. Answer that question first and separately, because until it is answered nothing else you write is being read properly.
A time, if you have one, taken from what they gave you. This is the half of the subject that gets thrown away. Their message contained a constraint, and usually a proposal: they are out Tuesday afternoon, and they suggested Thursday at eleven. Replying “when are you free?” hands back the work they already did and restarts a negotiation you had finished, which is how one moved meeting becomes the full eight message chain a second time. Take their proposal or counter it with one, and say which.
A named limit if you have one. “I can do Thursday, but it has to be before the eleventh because of the filing.” Constraints in a reply are cheap, and they stop the third and fourth messages.
Who is doing the calendar. Somebody has to change the event, and if neither of you says so, both of you assume the other did. The person moving it is normally you, because you sent the invitation and the organiser is the one who can edit it. Say so in three words and the ambiguity is gone.
Two things do not belong in it.
A list of options. They have already told you when they cannot do. Offering five slots after that reads as though the constraint was not read, and it turns their reply into work. One slot with an alternative behind it is the right size.
Reluctance, performed. If the move is fine, say it is fine. “Well, it does make things tight” attaches a small charge to a request they were already uncomfortable making, and the charge is remembered longer than the meeting.
What you owe them is a decision, promptly. What you do not owe them is agreement. “Tuesday is the last slot I have before the return goes in, so I would rather keep it if you can make the morning work” is a perfectly good reply, and it is a better one than a grudging yes followed by a rushed piece of work. Say no in the same message and with the same clarity you would have said yes.
Once the new time is agreed, the mechanics of making the change are the same whoever asked for it, and they are not many: edit the event rather than cancelling and rebooking, keep the length, and remember that some of the people affected are not on the invitation. That is all in moving a meeting.
When the ask is not about the time
Some requests to move are requests to move. Others are something else arriving in the most comfortable available form, and reading them as diary admin costs you more than a badly scheduled hour.
The third one. A meeting that has moved twice and is being moved again is not a scheduling problem, and treating it as one is how a client drifts away politely over four months. The question worth asking, once, in a friendly sentence, is whether the meeting is still the right thing. Sometimes the answer is that they need a different meeting, or a shorter one, or a document instead.
The push from a prospect. “Can we pick this up after the summer” from somebody who has not yet decided to work with you is frequently a soft no, delivered in the same indirect register as everything else in this piece. That is not bad news requiring a rescue, it is information, and it is worth more to you in August than a slot in October is.
Not ready, said as not available. People move meetings because the work is not finished far more often than they say so. If you suspect it, offering the shorter version of the meeting can be more useful than the later one: “we could keep Tuesday and just do the first half, or move the whole thing to the tenth” gives them a real choice.
The ask that is actually about length or format. Buried in the same paragraph as the date, there is often a second, quieter request: could this be half an hour, could we do it on the phone, does everyone need to be there. Those are worth answering separately, because if you only answer the date they will arrive at the new time with the same unspoken problem.
The ask that is a commitment with a deadline attached. “Can we push the review until after I have sent you the figures” is not really a meeting question. The dated thing in it is the figures, and a commitment with a date on it wants a list rather than an hour of the week. That is email task management, without writing it down.
The general move, when you cannot tell which of these you are holding, is to widen the door rather than narrow it. Somebody who hedged their way to asking for a different Thursday will not volunteer the real reason in answer to “does Thursday at eleven work?”. They might in answer to “Thursday at eleven is fine, or if it would help we can leave it a fortnight and do it properly then.” You have made the larger request askable, which is the only way you are going to hear it.
What careful reading does not reach
Somebody who says nothing at all. There is no reading habit that catches a person who intends to ask and does not, or who declines silently and hopes you notice. Threads that go quiet on you have their own repair, in unanswered emails, and the threads that come back.
An ask made somewhere other than email. On the telephone, in the last two minutes of the previous meeting, in a message on a phone you were not holding. Those need writing down at the moment they happen, and nothing else will do.
Whether you are actually free at the new time. Agreeing to Thursday at eleven from memory is a guess, and it is a worse guess than usual because you are answering quickly and out of a client’s reply. If your commitments are spread across a work account and a personal one, this is the moment that gap gets paid for, and reconciling two calendars closes it properly.
Whether eleven means the same thing to both of you. An ask that comes with a time in it comes with an assumption about whose clock, and the assumption is usually invisible. Scheduling across time zones covers the habits that make the error announce itself.
Which mail you see first. A reschedule caught quickly is largely a function of whether the message surfaced at all, and that is a question about the whole inbox rather than about this one thread. How the ranking gets made is how email triage works.
Catching it before you have read the thread
Point sits on the Gmail or Microsoft 365 mailbox you already have, and reads mail as it lands rather than when you get to it. Which matters here for one reason: the sentence about Tuesday gets found by something that has read the whole reply, instead of by you skimming the first paragraph on your way to something else.
So the reply comes in. It is mostly about an invoice query, and three paragraphs down the client mentions being out on Tuesday afternoon and asks about Thursday at eleven instead. Point reads that for what it is and lifts the thread to the top of the feed, under Now, rather than leaving it in the general pile. One click opens it with the ask already identified.
Then the step that saves the message rather than just flagging it. Point matches the ask to the meeting it means, which is the work you would otherwise do by opening the calendar and deciding which of your Tuesday appointments they are talking about, and prepares the move: the same event, at the time they proposed. It waits at the top of the feed with the change made up. One tap approves it, and the week view shows the meeting sitting on Thursday at eleven with Tuesday afternoon clear again.
How much of this runs unattended is a setting of its own, held per kind of action, and the scheduling one is not the drafting one. Review is where it starts, which means the prepared move is put in front of you and travels no further until you approve it. Raise it when you have watched a few arrive where you would have put them yourself. At the top of the dial Point answers the ask and tells you what it did. Either way the correspondence is Point’s to run, so a reply that needs a counter-proposal rather than a yes does not become one more thread you are carrying across the week. Each action is written down as it happens, and that written record is what an undo works from, stopping where reality stops it: an update already sitting in somebody else’s calendar gets changed a second time rather than erased. For what the same reading habit does to the other nine tenths of an inbox, see benefits.
Common questions
How do I stop missing requests to reschedule in email?
Read each reply once to the end before you answer any of it. Nearly every missed reschedule is the same accident: the first paragraph holds a question you can answer, you answer it, you send, and the rest of the message is now in a thread you think you have dealt with. While you read, stop on any date or day name that is not the subject of the email, on words of absence like away, out or travelling, on hedges attached to a time, and on the last paragraph, because that is where people put an imposition.
Why do people not just say “can we move the meeting”?
Because asking is uncomfortable, and the ways English makes a request comfortable all work by removing the words that mark it as a request. The Stanford politeness work puts it exactly: being indirect “allows the speaker to avoid words and phrases conventionally associated with requests”. Withdrawing from a time somebody set aside for you is near the top of the awkwardness range in ordinary business email, so it gets the full treatment, and the more the person minds asking, the less it will look like asking.
Somebody asked to move a meeting and I did not reply for three days. What do I do?
Answer the ask first and apologise briefly for the delay, in that order, and do not explain at length. Then take the constraint they gave you and propose one slot rather than asking when they are free, because their week has moved since they wrote and a list of options now reads as more work. If the original meeting is imminent, telephone rather than email. The thing being repaired is not the diary, it is the three days in which they did not know whether they had been heard.
Do I have to agree when a client asks to move a meeting?
No, and a clear no is better than a grudging yes. “Tuesday is the last slot before the filing, so I would rather keep it if you can make the morning work” is a perfectly reasonable answer, and it gives them a decision to make. What you owe is a prompt decision rather than agreement. What is worth avoiding is the middle option, agreeing while making it clear you are being put out, which attaches a charge to a request they already found awkward to make.
What if I cannot tell whether they were asking to reschedule?
Ask, in one sentence, and say what you will do with each answer: “Just to check, would you rather move Tuesday, or shall I keep the two o’clock?” That is faster than deducing it, and it costs nothing. The alternative failure is worse in both directions, because guessing that they wanted a move and changing the event without agreement creates a second problem, while guessing that they did not leaves them with the silence.
Can I ask people to use the calendar’s propose a new time feature instead?
You can, and some will, but it is not a habit you can install in other people. The mechanism is real and both major calendars have it, though the gaps sit exactly where reschedules cluster: Google’s help says it does not cover events with more than 200 guests or all day events, and Microsoft’s says “You can’t propose a new time for recurring meetings”, which is the most rescheduled object in most diaries (both checked 19 August 2026). It is also a direct request by construction, with nowhere to put an apology or a reason, which is precisely why somebody uncomfortable about asking will write a sentence instead.
The short version
The ask to move a meeting rarely arrives looking like an ask. It comes as a clause in a reply about something else, placed near the end, hedged, apologised for and stripped of the words a request is normally made of, because that is how English makes an imposition bearable to send. The politer the person, the harder it is to see.
Every property that predicts a slow answer is stacked on that one message. It is external, it is longer than average, it contains a request, and the reschedule that occurs to somebody over the weekend gets written on a Sunday evening. So you find it on Monday, and by then the alternatives have thinned, the hour you were giving back has become a hole rather than a slot, and your silence has started to mean something, because you answered the rest of their email and skipped the part about their week.
The fix is one adjustment and one sentence. Read each reply through to the end before answering any of it, and when you find the ask, answer it immediately even if you have no time to offer yet. Say whether the move is fine, take the proposal they already gave you rather than asking when they are free, and say who is changing the event. Everything after that is the ordinary mechanics of moving a meeting.
The shape of it varies with the work. A coaching practice running fortnightly sessions gets these constantly, mostly about a single recurring hour, and what matters is the speed of the answer and a policy applied evenly. A consultancy gets fewer and heavier ones, where a moved review pulls three diaries and a site visit with it, and what matters is spotting it while there is still room to move. Across the trades this is built for the reading habit is the same, and it is the cheapest thing in the whole subject.