Would be great to get your thoughts by Thursday if possible.
That sentence has no deadline in it. It has a date, which is a different thing. Asking for feedback by a deadline works when something happens on Friday morning, and asking for it by a date works when the reader was going to reply anyway.
The difference is one clause, and this post is mostly about that clause.
The ask sentence
Four parts, in this order. Drop any one and the sentence stops working.
A named person. Not a channel, not “the team”, not “anyone who has views”. A request addressed to a group is addressed to nobody, and everybody in the group knows it. If three people genuinely need to respond, write three sentences.
A specific action, small enough to picture. Review the doc is not an action; it is a category, and its size is unknown, which means the reader defers it. Confirm the 8 May date works for your team is an action, and the reader can tell it takes ninety seconds.
A date, with a time if the day matters. Thursday means end of Thursday to the writer and sometime Thursday-ish to the reader. If Friday morning is when you act, say by Thursday 17:00.
What happens if the date passes. This is the part people leave out, and it is the part that makes the other three real.
Assembled:
Marta — can you confirm by Thursday 17:00 that the 8 May
cutover date works for finance? If I have not heard, I will
book the cutover for 8 May and tell the team it is confirmed.
Thirty-eight words, one person, one action, one time, one consequence.
Why a deadline without a consequence is not a deadline
A request with a date and no consequence is a request to be polite about. The reader’s actual choice is between replying and not replying, and if both branches lead to the same place, the branch that costs nothing wins — not out of rudeness, but because a person with sixty open threads is triaging by consequence, correctly.
Stating the consequence changes what silence means. Before: silence is a neutral non-event that costs the reader nothing. After: silence is an active choice to let you proceed, and it is on the record as one.
That produces replies from people who would have ignored the request. It also produces the specific reply you want, because a person who is happy with the default does not need to reply at all, and a person who is not will now say so quickly and precisely.
The consequence has to be something you will actually do. This is the whole load-bearing part. A default you do not act on teaches everyone that your deadlines are decoration, and it takes exactly one instance. If you write I will book 8 May and Thursday passes and you send another chaser instead, you have spent the mechanism and you will not get it back on this project.
So the test before you write the sentence is not whether the deadline is reasonable. It is whether you are willing to do the thing on Friday morning.
The four shapes it takes
The reversible default. The strongest and the one to reach for first. You proceed with the option that is cheapest to undo, and you say which:
If I have not heard by Thursday I will ship the current report
format. Changing it later costs about two days in May, so this
is reversible — it is not the last chance to weigh in.
Naming the reversibility is not softening the ask. It is accurate, and it removes the reader’s fear that a non-reply is catastrophic, which is a real cause of paralysis in people who are busy and cautious.
The escalation, stated plainly. When the decision genuinely is not yours and nobody has replied:
If I do not have a decision by Thursday I will take it to
Dan on Friday with both options and a recommendation, because
the vendor needs an answer on the 24th.
Written this way it is a fact about a constraint, not a threat, and it gives the reader a reason that is not you. It is also honest about what will happen, which means when you do it on Friday nobody is surprised.
The removal. For a request that has a scope you can shrink:
If nobody has commented by Thursday I will assume section 4
is uncontroversial and cut it from the meeting agenda. It will
still be in the doc.
The stop. For work whose continuation depends on the answer, and the one to use sparingly:
I am not going to start the migration script until this is
decided. If there is no decision by Thursday the 8 May date
goes, and I will re-plan on Friday for early June.
The stop is the only one that spends real political capital, because it makes your inaction visible and someone will read it as coercion. Use it when it is true — when you genuinely cannot proceed — and never as a way of applying pressure to a decision you could work around.
What silence is allowed to mean
Be precise about this in your own head, because the reader is inferring it either way.
Silence can mean consent to a stated default. That is the whole design above, and it is legitimate on one condition: the default was stated, in the same message, before the silence. Retroactively deciding that no reply meant approval is not the same mechanism and it does not survive contact with the person who later disagrees.
Silence cannot mean agreement with your reasoning. Even a fired default only tells you nobody objected in time. It does not tell you the approach is right, and a document that later says the team agreed on the strength of a passed deadline is claiming something that did not happen.
Silence from one person is different from silence from everyone. One quiet reader is busy. Everyone quiet is a signal about the document, and it is a good moment to run the diagnosis for a document nobody engaged with rather than to fire the default and move on.
Record what the silence decided, where the decision lives. One line, in the document, on Friday: No objection received by Thu 17:00; proceeding with the current format. — 24 April. That sentence costs six seconds and it is the difference between a decision with a date on it and a thing that somehow happened.
The version that failed
Hi all — I've shared the reconciliation format doc in the
channel. Would really appreciate any thoughts or feedback
before the end of the week if people get a chance. No rush,
but it would be good to have some input before we move
forward. Thanks!
Nobody replied. Four reasons.
“Hi all” is nobody. Nine people read a request addressed to nine people and each of them privately assigns it to one of the other eight, mostly to whoever is most senior or most obviously the domain owner. Naming one person removes that entire mechanism.
“Any thoughts or feedback” has no size. It could be a two-line reaction or an hour of review, and the reader cannot tell, so they defer until they have time for the large version, which is never.
“No rush” cancels “before the end of the week”. The two clauses are in the same sentence and they contradict each other, and readers resolve the contradiction in the direction that costs them less. If there is no rush, do not put a date on it; if there is a date, do not apologise for it.
Nothing happens on Monday. The message ends with before we move forward, which implies the work is blocked, but does not say what moving forward would look like or when. So the reader has no way to know that their silence costs anything, because as written it does not.
The repaired version was the thirty-eight-word one at the top of this post, sent to one person, and it was answered in forty minutes.
What this costs
You have to do the thing on Friday. This is the real price and it is not small. Firing a default means acting without the confirmation you asked for, and if it goes wrong, the fact that you gave someone until Thursday will not be the first thing anyone remembers.
A stated default makes you the decider. Marta’s silence becomes your choice, and you own it. That is usually better than a decision nobody made — it is at least attributable — but it is a transfer of responsibility toward you, not away.
Deadlines have a rate limit. Two or three live at once across a project is normal. Six is a person who has turned every request into an ultimatum, and the effect decays fast: readers start treating your dates as a formatting convention. Reserve the mechanism for the requests where the date is genuinely load-bearing, and ask for the rest without one.
Some readers experience it as pressure regardless of wording. A person junior to you, new, or in a timezone where Thursday 17:00 is the middle of their night reads if I have not heard differently from a peer. Adjust the date rather than removing the mechanism, and say why: Thursday 17:00 my time is Friday morning yours — Friday noon your time is fine.
When not to set one
When you do not need the answer. A deadline attached to a request you would proceed without is a deadline you will not honour, and it trains the reader accordingly.
When the reply requires real work. A deadline is for a decision or a confirmation. Asking someone to review forty pages by Thursday is not a deadline; it is a task assignment, and it should be negotiated as one.
When the person cannot say no. A request with a default, sent down the org chart, is an instruction wearing a question mark. Send the instruction.
When you have already fired one on this person this week. Ask, wait, and follow up without the mechanism. Its power comes entirely from being used rarely.