There is no follow-up line that is safe everywhere. The same sentence reads as considerate to one person and impatient to another, and what changes isn't the wording — it's who's waiting, what they owe you, and what you've already told them.

Which is why you're stuck. What you've written is perfectly reasonable. Your cursor is on send. And you can't tell whether it sounds fine or annoyed, because a sentence on its own doesn't have a tone yet.

Why can't you tell how your follow-up reads?

Because tone isn't a property of the sentence. It's what the sentence does when it reaches one particular person.

Most writing problems can be checked. Is the grammar right, is the meaning clear, is the word the one you wanted. A follow-up gives you nothing to check against, because its tone is produced by the whole message — the line, the subject, what you said last time, how long ago that was — arriving in front of that one reader. Change the reader and the same words do something else.

And you rarely find out which happened. Nobody replies to say your email felt impatient. They just take a little longer next time.

Start with one question: do they owe you a reply?

Before anything else, this is the split that decides most of what follows.

Sometimes they owe you one. An agreed deadline has passed. An approval is blocking work. An invoice is overdue. A deliverable was promised. Here you have standing. Following up is part of the job, and a short, plain message is usually the right one — you don't need to earn the right to ask.

Sometimes they don't. You've sent a proposal, a quote, an introduction, a request for someone's time. Nothing obliges them to answer. Here a follow-up is a request in its own right, and it has to give the reader a reason to spend attention on you again.

Almost every piece of advice about follow-ups quietly assumes one case or the other, which is why so much of it contradicts itself. "Add new information" is good advice in the second case and unnecessary in the first. "Give them an easy way out" works in the second case and undermines you in the first. Sorting your own situation first makes the rest of these decisions much easier.

The same sentence, three times

Take one ordinary line:

Just following up on this.

Look at what it doesn't contain. There's no subject — no I, no we — and no reason, no deadline, nothing about why it matters. That emptiness is the whole problem. A short line gives the reader almost nothing to interpret, so their relationship with you fills in the rest. Many non-native writers keep follow-ups short because short feels efficient and safe. Short is efficient with someone who already knows your tone. With everyone else, short is a blank space the reader fills in themselves.

Watch what happens across three situations.

You asked a colleague for a file, and the deadline you both agreed on has passed. Here it works. They owe you the file, the request is factual, and brevity is a kindness — you're not asking them to apologize, you're moving the work along. It stops working when a lot of time has passed with no word from them, or when what "this" refers to is no longer obvious from the thread, or when other people are copied in. At that point the same line stops feeling like a light reminder and starts feeling like a written record.

You sent a client a quote three days ago and heard nothing. Here it reads thin — when this is early in the relationship, when the sum or the decision is large enough to need internal discussion, or when a weekend sat in the middle. Three days isn't a long silence for someone still deciding, and a bare line offers them nothing new to respond to. The same message is fine when you already have a rhythm of short exchanges with this client, when the quote is routine, or when they told you they'd come back within a few days.

You asked your manager to approve something a week ago. Here the risk isn't that they outrank you. It's pressing without having given them a reason to prioritize it. Read as pushy when you've never said what's blocked or by when, and the message asks them to reconstruct the request from "this" alone. Read as ordinary diligence when the approval is genuinely holding up work and you say so, when a date you'd previously agreed has passed, or when it's a routine sign-off they've simply lost track of.

Same sentence. In one situation it's right, in another it's too thin, in another it presses without support — and note that those last two go in opposite directions. That's why "just be more polite" doesn't solve this. Softening the third one makes it worse, because what was missing was never warmth.

What else moves the answer

How far away the person is. Someone you message daily reads your brevity as efficiency, because they have months of context for your tone. Someone you've met twice has only this email, and brevity is all they can see.

How many times you've asked. A first follow-up is information. A third one says something about the relationship whether you mean it to or not — which is the point at which changing the wording stops helping.

Whether something real is waiting. If a genuine deadline is at stake, saying so plainly lands better than hinting at it. If nothing is actually blocked, urgency you construct will be heard as pressure, and usually recognized as constructed.

Whether you've shown you know their situation. When you're aware someone is buried in work and your message doesn't acknowledge it, not mentioning it sends a message of its own.

What do you say the first time?

Keep it short, make it easy to answer, and — when they don't owe you a reply — take some of the pressure out of it.

The last one is useful because it offers a reason that isn't their fault. Most silences really are inbox accidents, and naming that possibility lets someone reply without opening with an apology.

One caution on the first example: only use "no rush" when there genuinely isn't one. If a deadline is waiting, saying no rush contradicts the thing you actually need, and the reader is left unsure which half to believe. When they do owe you a reply, drop the cushioning and be plainer. Saying what you need and by when is not rude; it's the part that lets them act.

What about the second time?

Adding something the reader didn't have works better than sending a softer version of the same message.

Repeating yourself with the volume turned down is the most common second follow-up, and it's the one that starts to feel like nagging — not because it's impolite, but because it gives the reader nothing new to act on. Politeness still matters. It just isn't what's missing.

What counts as "something new" is smaller than people assume. It doesn't have to be news. A deadline you can now name, a next step, a question narrow enough to answer in one line, an offer to make the reply easier for them — any of these give the message a reason to exist.

That second one deserves a caveat, because it only works in one of the two cases above. When the other person is free to decline — a proposal, a pitch, a request for their time — offering an exit lowers the cost of replying, and people who felt trapped into silence often answer once they're released from it. When they owe you something, the same sentence hands back the thing you were asking for. Used on a late deliverable or an overdue approval, it reads as withdrawal, and it teaches the reader that the deadline was negotiable.

One phrasing to avoid

Whatever else you write, keep the other person out of the subject position.

You didn't reply to my email.

You haven't got back to me on this.

Both are accurate. Both also make the reader feel accused, and that lands harder in English than the writer usually intends — it converts a request into a complaint. The safer move is to make the message the subject, not the person: in case my earlier email was missed, I wanted to make sure you received this, following up on my email below. Same facts, no accusation, and the reader can respond without first defending themselves.

Is it rude to follow up?

No. Following up is a normal, expected part of working over email, and most people who get one are relieved rather than annoyed — you've resurfaced something they'd lost track of.

What reads badly is narrower than most people fear. Chasing faster than the request warrants. Manufacturing urgency that isn't there. Repeating yourself with nothing added. Implying the other person has done something wrong. Those are the common ones, though the list isn't closed — how often you've written, how much power sits between you, and whether the original request was clear all shape it too. What they have in common is that none of them are about choosing the wrong word. They're about the fit between the message and the situation. If you're worried enough to be reading this, you're unlikely to be the person sending rude follow-ups.

Why this is harder in a second language

Reading someone else's follow-up and writing your own are different tasks. Reading, you need the gist, and the tone is their problem. Writing, you're setting a temperature — and if you didn't grow up in the language, you have no reliable way to feel where the setting landed. The sentence can be correct in every checkable way and still be two degrees colder than you meant.

Habits from another language travel with you, too. If you learned to write where more hedging signals more respect, softening will be your instinct, and past a certain point English business email reads added softness as uncertainty rather than courtesy. There's no rule of the language behind that. It's where the register happens to sit, and register is exactly what a dictionary can't tell you.

Why I write about this

I spent a few years living and working in a language I couldn't speak, doing business in a third. Grammar was never what stopped me. What stopped me was the send button — rereading two lines for ten minutes, unable to tell whether they sounded respectful or cold, with nobody to ask. I built LangPont because that particular kind of silence deserved a better answer than guessing.

The part no list can do for you

Everything above names what moves the answer. It can't give you the answer, and any page that claims to is guessing about your situation.

The variables that actually decide it are ones only you hold. How this client reacted the last time you pushed. Whether your manager reads a reminder as diligence or as noise. Whether the deadline is real or something you'd like to be real. Nobody writing a general guide knows any of that, which is why even good advice about follow-ups can only get you close.

What you need at that moment isn't more phrases. It's a way to see how your message will land — this message, for this reader — before you send it. That's the problem LangPont was built for.

FAQ

Is it rude to follow up on an email?

No. It's normal and usually welcome. What reads badly is chasing faster than the request warrants, inventing urgency, or repeating yourself with nothing added.

How long should you wait before following up?

It depends on what you asked for and whether they owe you an answer. An overdue deliverable can be raised the day after it was due. A proposal someone has to think about generally deserves several days, and a rough norm is three to five business days — though any date you agreed beforehand overrides the norm.

How many times can you follow up?

Usually twice before changing the approach rather than the wording. A third message that repeats the first two rarely helps; one that narrows the ask to a single question, or gives the person an easy way to finish it, usually does better.

Should you apologize for following up?

Generally no. "Sorry to chase you" frames a normal act as an imposition and can make you sound unsure of your own request. Being brief, or thanking them for their patience, reads better.

LangPont.
Push Translation.
Send with confidence.

Try LangPont