How to Ask for an Update Politely

Asking for an update is not rude. It becomes rude when the message is vague, shifts blame, or ignores the recipient's context. A polite follow-up is specific about what you need, clear about why it matters now, and easy to respond to, even if the answer is "not yet."

Most follow-up anxiety comes from a gap between what the sender means and what the recipient hears. Research on email urgency bias has found that recipients consistently overestimate how quickly senders expect a reply, particularly outside work hours. Your casual nudge can register as pressure if it lands without context or a clear reason. The fix is not to stop following up. It is to write messages that close that perception gap.

This guide covers what separates polite from pushy, ten alternatives to "just checking in," example lines for different workplace relationships, timing and channel guidance, a reusable template, and the mistakes that make follow-ups backfire.

Key takeaways

• A follow-up is polite when it includes context, a specific ask, and a realistic timeline.
• "Just checking in" signals you have nothing concrete to say. Replace it with a reason.
• Tone shifts with the relationship: a peer gets different wording than a client or a recruiter.
• Follow up after the promised date if one exists. Otherwise, match timing to urgency and stakes.
• When email gets no reply, switching to chat or a call is usually more effective than sending a third message.

What makes a follow-up sound polite instead of pushy

A polite follow-up does three things: it reminds the recipient what you are waiting for, explains why it matters now, and makes responding easy.

A pushy follow-up does the opposite. It leaves context vague ("just circling back"), implies the other person dropped the ball ("I still haven't heard from you"), or asks for something without offering a timeline.

Politeness research treats requests as face-threatening acts whose weight depends on the power gap, social distance, and size of the imposition. A quick check with a close teammate carries little face-threat. The same request sent to a senior executive you rarely email needs more framing and a lighter touch.

The safest pattern is: context + specific ask + easy out.

The first version gives the recipient no reason to prioritize. The second ties the ask to a specific event and deadline.

10 polite ways to ask for an update

These alternatives run from casual to formal. Pick the register that fits your relationship and the stakes.

#	Phrase	Register	Best for
1	"Any update on [X]?"	Casual	Close teammates, Slack
2	"Where are we on [X]?"	Casual	Peers, standups
3	"Quick check: is [X] still on track for [date]?"	Neutral	Cross-team projects
4	"Could you share an update on [X] when you have a chance?"	Neutral	Manager, cross-functional partner
5	"I wanted to follow up on [X]. Is there anything you need from my side?"	Neutral	Collaborative, removes blame
6	"Do you have an estimated timeline for [X]?"	Professional	Client, vendor, external partner
7	"I'd appreciate an update on [X] by [date], if possible."	Professional	Deadline-sensitive requests
8	"Following up on my [date] message regarding [X]."	Professional	Second follow-up, external
9	"Could you kindly provide an update on the status of [X]?"	Formal	Senior leadership, regulatory
10	"I'm writing to inquire about the current status of [X]."	Formal	First contact, institutional

Skip these: "Just checking in" (no substance), "Per my last email" (reads as irritation), "Friendly reminder" (the word "friendly" often reads as passive-aggressive in writing). If you find yourself defaulting to fillers like "sounds good" or "just checking in," the problem is usually that you have not identified what you actually need from the other person.

If a phrase keeps sounding off, try selecting it in Inki's editor and comparing context-aware alternatives before replacing it.

Example lines by situation

Tone shifts depending on who you are writing to.

Colleague (Slack): "Hey, any movement on the [deliverable]? I need [specific piece] for my section by [date]."

Manager (email): "Hi [name], I wanted to follow up on the [request] from last week. Is there a timeline I should plan around?"

Client or vendor (email): "I'm following up on the proposal sent on [date]. Please let me know if you need additional information, or if you have an estimated timeline for a decision."

Recruiter (email, post-interview): "Thank you again for the conversation on [date]. I'd welcome any update on next steps whenever you have one."

The pattern across all four: name what you are waiting for, explain why now, and keep it short. One sentence works on Slack. Two to three over email.

When to follow up, and when to switch channels

No single timing rule works everywhere. The right interval depends on whether a deadline was already set.

If you have a promised date, follow up the day after it passes. If no date exists, three to five business days is a reasonable default for external contacts. One to two days for internal teammates.

For a second follow-up, wait at least as long as the first interval and add new context or restate the stakes. A third email on the same thread rarely gets a reply. Switch channels instead.

Workplace communication guidelines from sources like Boston University HR classify email as best for medium-urgency, documentation-oriented requests. For anything truly urgent, a direct message or a call gets faster results. Research on compliance and persuasion consistently finds that synchronous, voice-based requests outperform written ones.

When to stop emailing:

• Two follow-ups have gone unanswered.
• The deadline is approaching and you need a decision now.
• The topic is complex enough that a five-minute call replaces a long email thread.

A simple update-request email you can adapt

Subject line options:

• "Status update: [project name] deliverables"
• "Following up: [item] from [date]"
• "[Project name]: next steps?"

Example email:

Hi [name],

I'm following up on [item] from our [date] conversation. The [reason: milestone, client deadline, team dependency] is coming up on [date], so I'd like to confirm the current status.

Could you share an update by [realistic date]? If the timeline has shifted, let me know so I can adjust on my end.

Thanks, [Your name]

That runs about 60 words. The recipient can scan it under a minute, which matters when the average professional inbox holds well over 100 messages a day.

What to avoid

Three patterns make a follow-up sound passive-aggressive instead of professional.

Empty openers. "Just checking in" and "just wanted to touch base" signal that you have no real reason to write. Name the reason instead.

The first version could apply to any email about anything. The second names the item and when it was discussed.

Missing context. "As discussed" without specifying what was discussed forces the recipient to dig through their memory. Name the item and date.

No clear ask. Messages that end with "let me know" and nothing else are easy to skip. Ask a direct question with a suggested deadline. For more on fixing vague and error-prone email drafts, see the guide on common mistakes in business emails.

Before you send: a quick tone checklist

• The message names the specific item you are waiting on.
• You have included why the update matters now (a deadline, dependency, or next step).
• The timeline you are asking for is realistic for the recipient.
• You are using the right channel: email for documentation, chat for quick pings, call for urgency.
• The closing makes it easy to say "not yet" without guilt.

If all five pass, send it. A clear, specific follow-up is a professional courtesy, not an imposition.