Most requests to move a meeting arrive as a clause inside a reply about something else. They come wrapped in an apology and stripped of every word you scan for. Missing one is ordinary. The habit that catches them takes a few seconds, and it saves you the version that lands two days later, on somebody else’s calendar.
- Politeness works by removing the signals you scan for. A request softened enough to be comfortable to send keeps very few request-shaped words.
- The biggest variable in how fast the ask gets answered is which day of the week it occurred to them. Weekends are when people look at the week ahead and see that Tuesday is a problem.
- What perishes first is the alternatives, the hour you’d have given back, and their ability to plan around either.
- The expensive reply answers everything in their message except the sentence about Tuesday.
The sentence that is not a question
Here’s the ask as it usually arrives, in a reply from a client about something else:
“Thanks for sending those through, I’ll look properly this evening. One thing, I’m in Leeds all day Tuesday now. Anyway, on your second point, I think the answer is…”
That’s a statement about Leeds. It carries no question mark, no “could we”, no “would you mind”. It sits between two sentences about a different subject, in the middle of a paragraph. And it’s doing the work of “please move our Tuesday meeting”. The writer knows they’ve asked. You read past it.
That’s care at their end, 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. They 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 removes the parts that make a request recognizable as one. The strategies they measure are exactly the ones that gather around a reschedule. Apologizing, 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 read it as a description of how the language works rather than as a measurement of your inbox.
Now think about where a reschedule sits on that scale. You’re withdrawing from something you already agreed to. What you’re taking back is an hour of a finite week that somebody set aside on your word. Few asks in professional correspondence come more awkward than that, so it gets the full apparatus. The rule that falls out is worth keeping: the more the person minds asking, the less it looks 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’m in Leeds on Tuesday.” “We have the auditors in that week.” A statement, offered in the hope that you’ll 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’s 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’s easy.” “If that doesn’t 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 left out.
From somebody outside the invitation. A client’s assistant, a colleague copied in, a partner replying on their behalf. The words may be perfectly direct. They arrive from an unfamiliar address, in a thread where they’re a surprise.
On a thread about something else entirely. They’re already writing to you about the year end, so they mention Tuesday there. A fresh email would make it a bigger thing than it is. The correspondence about the meeting sits somewhere else, and that’s where you’ll go looking for it later.
With no words at all. A “maybe” on the invitation, or a bare decline. That’s 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. That’s the next section, and it helps less often than it sounds.
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 organizer’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 August 19, 2026).
So the tidy version of this subject exists, has for years, and sits on the screen of everybody you correspond with. Four reasons your problem survives it.
The gaps are exactly where the reschedules are. Google’s page puts the option out of reach for “Events with more than 200 guests” or “All day events”. Microsoft’s limit matters more for a small practice: “You can’t propose a new time for recurring meetings.” An every-other-week client session is the single most rescheduled object in most calendars, and it sits outside the mechanism. 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’re 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’s easier” or “no rush at all”. Between colleagues that’s a virtue. For a client withdrawing from a time they agreed to, it’s blunter than they want to be. They reach for prose because prose carries 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. That’s the category of mail everybody has trained themselves to skim. An ask buried in a paragraph and an ask buried in a notification are the same problem in different clothes.
Treat the feature as an occasional favor. The habit you can install is on your side of the correspondence.
What a day of silence costs
Start with when the ask was written. 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. Their paper is 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 check mail less regularly on 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. The ratio says that the single largest variable in how fast a reschedule request gets answered is which day of the week the thought occurred to the person writing it. That beats how clearly it was written and how much it mattered. And the thought lands on the weekend more than its share of the time. The weekend is when people look at the shape of the week ahead and see that Tuesday is a problem.
The same paper’s other findings stack on top of that. They’re the subject of unanswered emails, and the threads that come back, which reads them properly. The short version here is that mail carrying a request, mail crossing out of the company, and mail longer than a few lines each draw a slower answer. A client’s reply with a reschedule buried in it has all three, and it was written on Sunday evening.
So the ordinary case runs like this. They write on Sunday night, you find it on Monday, and the meeting is Tuesday. Your attention was fine. Here’s what the intervening hours spend.
The alternatives thin out. Thursday at eleven was free in their week on Sunday. By Wednesday afternoon somebody else has taken it. Now you’re looking for a slot that suits two calendars that have both moved, and a move that was an edit turns back into a negotiation. The way to keep it an edit is moving a meeting, and every hour of delay puts it further out of reach.
The hour you’re giving back loses its value. A Tuesday afternoon released on Sunday is a slot somebody can book. Released on Monday evening it’s 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. That’s booking links.
They resolve it without you. Between asking and hearing, the careful ones hold both slots and commit to neither. That costs them a day of their own week. The rest act on the reasonable assumption that they told you. They book over your Tuesday, they decline the invitation, or they simply stay away. A bare decline arriving on Monday carries no counter-proposal, 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 sits outside the scheduling. If you answered the invoice question in their email and said nothing about Tuesday, you’ve proved you read the message. Your silence on the ask is now an answer. It reads as a refusal you didn’t trouble to write down, or as a signal that their week was worth less than a sentence. You meant neither. Explaining on Wednesday that you missed it lands badly too, 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 isn’t the slot. It’s the hours in which they don’t know whether they’ve been heard.
Reading a reply for asks and not for questions
The habit is one adjustment. Read a reply through to the end before you answer any of it. That’s it, and it beats “read more carefully”, which is advice nobody has ever successfully taken.
Almost every missed reschedule is the same accident. The first paragraph holds a question you can answer. You answer it and send. The second half of their message is now in a thread you count as dealt with. Reading to the end first costs about eight seconds and closes the whole failure mode.
While you’re doing it, here’s what to stop on.
Any date or day name that belongs to another subject. If a message about an invoice mentions Tuesday, Tuesday is doing something.
Words of absence. Away, out, off, traveling, 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’re 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’s easier, no rush, only if, might we, could we possibly. The hedge marks the request, and the request is still a request.
An apology with no visible cause. “Sorry to be a nuisance” in an otherwise unremarkable email is a strong signal that the imposition sits somewhere further down. An apology attaches itself to an imposition. If the imposition is still out of sight, keep reading.
The last paragraph and the postscript. That’s where an imposition goes, for nearly everyone, nearly always.
A change of tense about a commitment. “I was going to bring the figures on Tuesday” says something different from “I’ll bring the figures on Tuesday”, and the difference is a decision somebody has already made.
An unfamiliar name on a thread you know. An assistant appearing in a client’s thread is usually appearing about a calendar.
It’s a short list of shapes that repeat, and it stays a list rather than a system. After two weeks of noticing them you’ll stop having to think about it. What the habit really buys you is the difference between answering on Sunday and answering on Monday. On the arithmetic above, that’s 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. It can go out before you have a new time.
That’s the part most people hold backwards. You see the ask, you want to offer a time, and the whole message waits until you have one. So the acknowledgment, which is free and perishable, sits 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. It costs you 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 on its own. Until they have that answer, the rest of what you write goes past them.
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 carried a constraint, and usually a proposal. They’re 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’d finished. That’s 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 save you the third and fourth messages.
Who is doing the calendar. Somebody has to change the event. When both of you stay quiet about it, both of you assume the other did. The person moving it is normally you, because you sent the invitation and the organizer is the one who can edit it. Say so in three words and the ambiguity is gone.
Two things to leave out.
A list of options. They’ve already told you which times are out. Offering five slots after that reads as though you skipped the constraint, 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’s fine. “Well, it does make things tight” attaches a small charge to a request they were already uncomfortable making, and the charge outlasts the meeting.
What you owe them is a prompt decision. Agreement is a separate question. “Tuesday is the last slot I have before the return goes in, so I’d rather keep it if you can make the morning work” is a perfectly good reply. It beats a grudging yes followed by a rushed piece of work. Say no in the same message, and with the same clarity you’d have said yes.
Once the new time is agreed, the mechanics are the same whoever asked for it, and the list is short. Edit the event rather than canceling and rebooking. Keep the length. Remember that some of the people affected sit outside the invitation. That’s 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. Read one of those as calendar admin and it costs you more than a badly scheduled hour.
The third one. A meeting that has moved twice and is moving again is a question about the work rather than the calendar. Treat it as scheduling and you get a client drifting away politely over four months. The question worth asking, once, in a friendly sentence, is whether the meeting is still the right thing. Sometimes 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 still deciding whether to work with you is frequently a soft no. It arrives in the same indirect register as everything else in this piece. Treat it as information. In August it’s worth more to you than a slot in October.
Not ready, said as not available. People move meetings because the work is behind, far more often than they say so. If you suspect it, offer the shorter version of the meeting rather 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’s often a second, quieter request: could this be half an hour, could we do it on the phone, does everyone need to be there. Answer those separately. A reply about the date alone brings them to 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’ve sent you the figures” is a question about the figures. 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’s email task management, without writing it down.
When you can’t tell which of these you’re holding, widen the door rather than narrowing it. Somebody who hedged their way to asking for a different Thursday keeps the real reason back when the question is “does Thursday at eleven work?”. They might offer it in answer to “Thursday at eleven is fine, or if it would help we can leave it two weeks and do it properly then.” You’ve made the larger request askable, and that’s how you get to hear it.
What careful reading does not reach
Somebody who says nothing at all. A person who means to ask and stays quiet, or who declines silently and hopes you notice, sits outside what any reading habit reaches. 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’d put down. Write those down at the moment they happen. That’s the only thing that works.
Whether you are actually free at the new time. Agreeing to Thursday at eleven from memory is a guess, and a rougher one than usual, because you’re answering quickly and out of a client’s reply. If your commitments sit 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 carries 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. Catching a reschedule quickly depends on the message surfacing at all, and that’s 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, while you’re still on your way to something else.
So the reply comes in. It’s mostly about an invoice query. 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, ahead of the general pile. One click opens it with the ask already identified.
Then the step that settles the message rather than flagging it. Point matches the ask to the meeting it means. That’s the work you’d otherwise do by opening the calendar and working out which of your Tuesday appointments they’re talking about. Point prepares the move: the same event, at the time they proposed. The change waits at the top of the feed, made up and ready. One tap approves it. 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 separate from the drafting one. Review is where it starts. The prepared move is put in front of you, and it waits there until you approve it. Raise the dial when you’ve watched a few arrive where you’d 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 wants a counter-proposal rather than a yes stays off the pile you carry across the week. Each action is written down as it happens, and that written record is what an undo works from. The undo stops 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, so you answer it and send. The rest of the message is now in a thread you count as dealt with. While you read, stop on any date or day name belonging to another subject. Stop on words of absence like away, out or traveling. Stop on hedges attached to a time, and on the last paragraph, because that’s 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 sits 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 looks like asking.
Somebody asked to move a meeting and I did not reply for three days. What do I do?
Answer the ask first, then apologize briefly for the delay, and keep the explanation short. Take the constraint they gave you and propose one slot rather than asking when they’re free. 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. What you’re repairing is the three days in which they wondered whether they’d been heard.
Do I have to agree when a client asks to move a meeting?
No, and a clear no beats a grudging yes. “Tuesday is the last slot before the filing, so I’d 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. The middle option is the costly one: agreeing while making it clear you’re being put out 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’ll do with each answer. “Just to check, would you rather move Tuesday, or shall I keep the two o’clock?” That’s faster than deducing it, and it’s free. Guessing costs more either way. Guess that they wanted a move, change the event without agreement, and you’ve created a second problem. Guess the other way and they’re left with the silence.
Can I ask people to use the calendar’s propose a new time feature instead?
You can, and some will, though the habit stays theirs to keep. The mechanism is real and both major calendars have it. The gaps sit exactly where reschedules cluster. Google’s help says it skips events with more than 200 guests and all day events. Microsoft’s says “You can’t propose a new time for recurring meetings”, which is the most rescheduled object in most calendars (both checked August 19, 2026). It’s also a direct request by construction, with nowhere to put an apology or a reason. That’s precisely why somebody uncomfortable about asking writes 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. It’s hedged, apologized for, and stripped of the words a request is normally made of. That’s 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’s external, it’s longer than average, it carries a request, and the reschedule that occurs to somebody over the weekend gets written on a Sunday evening. So you find it on Monday. By then the alternatives have thinned, and the hour you were giving back has become a hole rather than a slot. 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. When you find the ask, answer it straight away, even while you’re still looking for a time to offer. Say whether the move is fine, take the proposal they already gave you rather than asking when they’re 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 every-other-week sessions gets these constantly, mostly about a single recurring hour, and what matters there is the speed of the answer and a policy applied evenly. A consultancy gets fewer and heavier ones, where a moved review pulls three calendars and a site visit with it, and what matters there is spotting it while there’s still room to move. Across the trades this is built for the reading habit is the same, and it’s the cheapest thing in the whole subject.