How to Ask for an Update in an Email: Phrases That Are Polite and Actually Work

“I wanted to follow up on [X] — could you share a quick update?” Fill the bracket with a noun phrase — the quote, the invoice, the draft contract — and you have a sentence you can send to a client in Dublin, a boss in Dallas, or a vendor in Dhaka. It is the sentence I would defend in front of any style guide, so before you calibrate anything, look at the three parts that make it work.

The opener, I wanted, is past tense, and the wanting is not actually past — you want the update right now, which is why you are writing. The past form is a cushion: it describes your approach rather than the reader’s obligation, and English reads that cushion as politeness. Then could you frames the ask as a modal question, which leaves the answerer somewhere to stand; can you would ask about their ability, not their willingness, and read flatter. Finally, a quick update keeps the ask small, specific, and answerable in two lines — and asks that are cheap to answer are the ones that get answered.

Every other sentence in this article is a calibration of that one: warmer for a peer, more indirect for a new client, sharper when a date matters. When you are unsure, send the default. The only failure modes are drifting too far toward the imperative or too far toward the apology, and sections 3 and 5 keep you on the ladder between them.

Most advice about asking stops at “add please.” But please is the weakest politeness tool English has: it decorates an order without softening it. “Please send me an update” is boss-shaped whatever the please is doing there. The machinery that actually works is grammatical, and it comes in six parts.

One: past-tense hedging. “I wanted to follow up.” “I was wondering if you had a chance.” “Just checking in.” None of these refers to past time — the wanting is happening now. The past form lowers pressure by describing your approach instead of the reader’s obligation. It is among the most dependable politeness devices in the language, and learners systematically underuse it because their own language encodes the present feeling directly.

Two: modals. Could and would soften more than can. “Can you give me an update?” is not rude between peers, but it asks about ability and reads flat with a client. “Could you let me know where this stands?” asks about willingness and convenience, which is the whole point.

Three: imperatives. Orders are direct, and they have a place — with peers, in genuine urgency, to people who owe you the task: “Update me by noon.” But they are the ceiling of ordinary email, not a step on the ladder beneath it, and please will not rescue one with a senior reader. If an imperative is the right tool, use it cleanly rather than apologizing around it.

Four: indirect questions. English embeds a question inside a statement to soften it: “Could you let me know where the quote stands?” The direct versions — “I’d like an update on the quote” or “Where is the quote?” — are not wrong, just closer to demands. Indirect structure is the politeness engine of the language, and the word-order machinery is the same as in reported speech: the embedded clause goes back to statement order, no auxiliary flip. Our guide to direct and indirect speech teaches that whole system.

Five: just. “Just following up.” The minimizer shrinks the request so it does not read as an intrusion. One per email is grace; a string of them across follow-ups turns you into someone apologizing for existing, and an update you apologize for requesting tends to get postponed.

Six: fragments. “Any update on the invoice?” drops the subject and auxiliary (“Is there any update...”). It is idiomatic and efficient in an ongoing colleague thread — and grammatically incomplete, so save it for people you already talk to every day. With a new client, a fragment reads as truncated effort, not ease.

Two things set the rung you should stand on: social distance and stakes. English registers distance mainly through how embedded the question is — the greater the distance, the more layers between your verb and their action. Four rungs cover almost every business relationship.

Watch the pattern rather than memorizing the sentences. As distance or stakes rise, the question gets more embedded and the pressure migrates out of the verb and into the deadline. “Any word on it?” and “Whenever you have a moment, could you...?” are the two rungs worth knowing so well you can feel the intermediate ones: most real emails land a half-step from one of them, and the fix for an email that sounded too blunt or too timid is almost always one rung up or down, not a rewrite.

A request with no date is a wish. The polite instinct — leave the timing entirely to them — is what produces the two-week silence you were trying to avoid. The fix is a deadline delivered so it does not land as a shove: a named day, plus your reason. “Could you send the figures by Thursday? We close the books Friday.” The second sentence changes everything. The date stops being your impatience and becomes a fact about the world that you are both dealing with, and a stated reason turns a demand into a shared task. No amount of please does that work.

Give the date a shape, too. “By Thursday afternoon” survives a day of travel; “by EOD” assumes the other person’s day ends when yours does. And state the consequence once — “so the design review can happen Friday” — then stop repeating it. A deadline explained once is a plan; the same deadline repeated in every follow-up is a countdown, and countdowns make people defensive rather than fast.

No reply. The second email is where most writers lose their grammar: embarrassment tips them into over-apologizing, or they swing the other way and reach for the classic passive-aggressive opener, “Per my last email.” That phrase is grammatically unimpeachable, and it is also pure blade — it points at the other person’s failure to read and answer, which is precisely why readers flinch at it. Use it knowing it will be received as irritation wearing a tie; I would not use it at all.

The neutral alternative references the previous email without the accusation: “Following up on my note from Monday.” Same information, no sting, because it anchors on your action rather than their inaction. The second tool is the offer of help: “I know this week has been heavy — do you need anything from me to unblock this?” That is a face-repair move, and it doubles as genuine diagnosis, because some silences mean the task is stuck rather than that the person is rude. If the reply is “waiting on legal,” your follow-up just saved a week.

One grammar note on the chaser itself: keep the ask identical to the first email. Silence is often ambiguity, and a second message that quietly changes the request (“actually, just send a rough estimate”) confirms the reader’s suspicion that the task can wait. Same ask, softer opener, new date — that is the whole anatomy of a second email that gets answered.

Three worked examples, annotated. Steal the shapes, not the sentences.

Each template contains the same three parts — soft opener, one clear ask, a date or an offer. Swap in your own noun and your own reason and the politeness holds, because it is structural rather than decorative. Tone problems in email are rarely isolated: they cluster, which is why a quick pass over the common grammar mistakes in business emails is worth an afternoon, and the free grammar checker catches what your eye has stopped seeing in your own drafts.