Wrivio
Get Wrivio
7 min readBy Wrivio Team

How to Reply When Someone Asks "Any Updates?"

The message is two words long: “Any updates?” It arrives from your manager, a client, or a colleague who is waiting on you, and it lands harder than its length suggests. If the work is going well, you wonder why they are asking. If it is not, you feel caught.

So people reply badly in one of two directions. Some write a defensive paragraph listing everything they have touched since Monday. Others send “Working on it!” and hope that buys a few more days. The first buries the answer, and the second invites a sharper follow-up.

A good reply to “any updates?” is short, specific, and gives the asker something to plan around. Here is how to write it whether the news is good, bad, or nothing at all.

Read The Question As A Planning Request

Most “any updates?” messages are not accusations. The person asking has their own deadline, meeting, or customer, and they need to know whether your piece will be ready. Microsoft’s Work Trend Index report on the infinite workday found that the average worker receives 117 emails and 153 Teams messages a day (June 2025 figures). Your colleague is skimming the same flood. They are not asking for your story; they are asking what to do next.

That reframe changes the job. Your reply needs to answer three things, in this order:

  1. Where it stands, in one sentence.
  2. When they will have it or hear from you next, as a real date.
  3. What you need from them, if anything.

Everything else is optional.

Lead With The State, Not The Effort

The instinct is to prove you have been busy. Resist it. A list of activities makes the reader do the work of figuring out whether you are on track.

Before:

Hi, yes, so I’ve been going through the vendor contracts and had a call with legal on Tuesday, and then I started pulling the numbers together but some of the regional data was in a different format so I’ve been cleaning that up, still a bit to do there.

After:

About 70% done. The regional data needed cleanup, which cost a day. You’ll have the full summary by Thursday at noon.

The second version answers the actual question in its first three words. It still mentions the delay, but as a reason attached to a date, not as an excuse looking for sympathy. If you want a deeper treatment of writing for people who skim, see how to write a status update executives read.

When The Honest Answer Is “Nothing Yet”

Sometimes nothing has moved. You were pulled onto something urgent, or you are waiting on someone else. “Working on it” is technically true and practically useless, because it gives no date and no reason.

Before:

Still working on it, will let you know!

After:

Not started yet. I was pulled onto the outage review this week. I can start Monday and have a draft to you by Wednesday. If you need it sooner, tell me and I’ll ask Priya which one should wait.

This is the reactive version of the no-news status update: you state the state plainly, give the reason in one clause, and offer a real choice. That last sentence matters most. It hands the priority decision to the person who can actually make it, instead of you silently guessing.

When You Are Blocked By Someone Else

If the delay belongs to another person, say so, without making it sound like blame. Name the dependency, what you have done to unblock it, and when you will escalate.

Before:

I’m still waiting on finance, they haven’t gotten back to me.

After:

Blocked on the Q3 cost figures from finance. I asked Daniel on Monday and followed up this morning. If I don’t have them by Friday, I’ll send the draft with Q2 figures marked as placeholders so you’re not held up.

The after version shows you are managing the blocker rather than waiting on it, and it offers a fallback so the asker is not stuck either. If the blocker is serious enough to threaten a date others depend on, it has outgrown a quick reply and deserves a proper project risk update.

When You Genuinely Do Not Know Yet

Some questions cannot be answered on the spot: you need to check a number, ask a colleague, or look at something you do not have open. Do not guess, and do not go silent. Send a holding reply with a time attached.

Let me check where the review landed and come back to you by 3pm today.

Then actually reply by 3pm. A holding message only works if the follow-through arrives, which is the whole argument of how to acknowledge a message you cannot action yet.

Get Ahead Of The Next One

If you are getting “any updates?” regularly from the same person, that is information. It usually means they do not know when to expect news from you, so they ask. The fix is to give them the cadence before they need it: end each reply with when you will next update them, and then send that update unprompted.

“I’ll send a quick note Thursday either way” turns you from someone being chased into someone who reports. After two or three cycles, the check-ins tend to stop.

Use A Context For Check-In Replies

A Wrivio Context for replying to update requests could say:

Rewrite this as a short reply to a request for a status update. Start with the current state in one sentence. Then give the next date or time the reader will hear from me or receive the work. Then state any decision or input I need from them. Cut lists of activities and apologies longer than one clause. Keep every name, date, figure, and commitment exactly as written. Do not add a deadline or promise that is not in the draft.

Press Ctrl+Shift+Space over Slack, Teams, or Outlook, paste your rambling first attempt, and check the diff. Watch that the rewrite has not quietly firmed up a soft date (“maybe Thursday”) into a hard one; that is the one change you must approve yourself. If the update mentions client names or internal figures you would rather not send anywhere, switch to the Local engine so the text stays on your machine.

Common Questions

How do you reply to “any updates?” when there is no update?

Say so plainly, give the reason in one clause, and give a date when you will have something or when you will next report. “Not started yet, I was pulled onto X, I’ll have a draft by Wednesday” is better than “still working on it” because the reader can plan around it.

Is “any updates?” rude?

Usually not. It is shorthand from someone who needs to plan their own work around yours. Treat it as a request for a date rather than a judgment about your effort, and reply to that.

How long should a reply to a status check be?

Two to four sentences in chat, and rarely more than a short paragraph in email. If the honest answer needs more than that, it is probably a risk or delay that deserves its own message rather than a reply in the thread.

How do I stop people asking me for updates all the time?

Tell them when the next update is coming before they ask, and then send it on time. Repeated check-ins usually mean the asker has no idea when to expect news, and a predictable cadence removes the need to chase.

Should I apologize for the delay in my reply?

Only briefly, and only if you actually caused one. A one-clause acknowledgment is enough; a long apology pushes the useful part of the reply further down and makes the situation sound worse than it is.

Download Wrivio for Windows to turn a flustered reply to “any updates?” into a clear status, a real date, and a clean ask in a few seconds.