Wrivio
Get Wrivio
7 min readBy Wrivio Team

How to Write to a Colleague Who Has Gone Quiet on Something You Need

You asked for a review, a number, a file, or a decision. It has been nine days. Your own deadline has not moved, and the person you are waiting on is clearly alive, because they posted in another channel this morning.

Most people handle this badly in one of two ways. They send a third “just checking in”, which adds nothing, or they skip straight to copying the person’s manager, which spends trust you may need later. There is a message that sits between those two, and it is worth knowing how to write it.

Name The Dependency, Not The Silence

The weakest version of this message is about the other person’s behavior: “I haven’t heard back from you.” The stronger version is about the work: what you need, what it unblocks, and by when.

Silence has many ordinary causes. The request got buried, the person assumed someone else owned it, or it turned out to be bigger than it looked. A message that describes the dependency gives them something to act on without first having to defend themselves. It also happens to be the same information a manager would need if this did escalate later, so you are building the record while being kind.

Before:

Hey, I still haven’t heard back about the pricing numbers. This is really holding things up. Can you please get back to me?

After:

I need the Q4 pricing numbers to finish the proposal, which goes to the client on Friday. I first asked on the 14th. If the numbers are not ready, a rough range would let me keep going. Which is easier for you this week?

The second version states the dependency, the date, the consequence, and a smaller version of the ask. Nothing in it assigns fault.

Make The Smaller Ask Easy To Say Yes To

People go quiet on requests that feel large or vague. Shrinking the ask is often more effective than repeating it.

Offer one or two lower-effort options: a rough estimate instead of final figures, a ten-minute call instead of a written review, a pointer to who else could answer. Give a real choice, because “which is easier” is a question that takes five seconds to answer, while “please get back to me” is a task.

This is the same instinct behind a good handoff, where you make the next person’s job obvious. If you want the longer version of that idea, see how to write a clear task handoff.

Change The Channel Once

If three messages in the same thread have not worked, a fourth in that thread will not either. Move one step sideways: a direct message instead of a group channel, a short call, or a calendar hold titled with the actual topic.

Say that you are doing it, in one sentence, so it does not read as an ambush: “I will grab five minutes on Thursday to sort this out, since the thread is getting long.” Keep the tone matter-of-fact. Escalating the medium is not the same as escalating the conflict.

Say What You Will Do If You Do Not Hear

This is the sentence most people leave out, and it does the most work. It tells the other person what happens next, and it turns an open-ended wait into a date.

If I have not heard by Wednesday, I will use last quarter’s figures and mark them as provisional in the proposal, and I will flag the gap to Dana so she is not surprised.

That sentence is not a threat. It is a plan, stated early enough that the person can change it by replying. It also makes a later escalation unsurprising, because they were told it was coming. When you do reach that point, how to write an escalation email without blame covers the next message, and how to follow up when your manager has not replied covers the case where the quiet person is above you.

Project teams have long treated unresolved dependencies as a thing to surface early rather than absorb. Atlassian’s dependency mapping play frames the exercise around finding what could impede a project before it does, which is the right mindset for the message above: you are reporting a risk to the work, not a complaint about a person.

Keep Working While You Wait

Do not stop. Move to a piece of work that is not blocked, and say so in your next status update in neutral terms: “Pricing section is waiting on Finance; everything else is on track.” A status line that names the dependency reads as information, not grievance, and it lets anyone who can help notice without you having to ask.

A Wrivio Context for a blocked-dependency message could say:

Rewrite this as a short, neutral message to a colleague whose input I am waiting on. State what I need, what it unblocks, and the date, and offer one lower-effort alternative. Say what I will do if I do not hear back by a stated day. Keep every name, date, figure, and commitment exactly as written. Do not add blame, sarcasm, guilt, or phrases like “as I mentioned”.

Press Ctrl+Shift+Space, paste the draft, and check the diff. Watch for two failures: a rewrite that softens the date into “when you get a chance”, or one that drops the sentence about what you will do next. Both remove the parts of the message that make it work.

Common Questions

How long should I wait before writing to someone who is not responding?

Wait as long as the work can bear, then act before the deadline puts you in a corner. A good rule is to send the dependency message while there is still enough time for the person to do the task comfortably, not on the day you are already late.

Should I copy their manager on this message?

Not yet. Copying a manager is a step up in seriousness, and it works best after a clear, friendly message has already been ignored. Telling the person you will flag the gap to a named colleague is fair, but keep the manager off the first attempt.

What if they reply but still do not deliver?

Treat it as a new, smaller dependency. Confirm a specific date in writing, restate what you will do if it slips, and keep the record short and dated. If it repeats, you will have a factual timeline to share.

Is it rude to say what I will do if I do not hear back?

No, as long as the plan is reasonable and stated as a plan rather than a warning. It gives the person a clear chance to change the outcome and removes the surprise later.

What if the person is more senior than me?

Keep the same structure but lead with how the work reflects on them or their team, shrink the ask as far as possible, and offer to take on the effort yourself, for example by drafting the answer for them to approve.

Download Wrivio for Windows to turn a frustrated “still waiting on you” draft into a neutral message that states the dependency, the date, and your next step.