How to Follow Up When an Action Owner Isn't Responding

Do not send “Just chasing this.” Do not send “Any update?” Those lines are easy to ignore because they ask for nothing in particular.

Name the action. Name what was agreed. Name what now depends on it. Ask for a concrete reply.

[Action] was due [day]. [Downstream work] is now waiting on it. Can you confirm one of these by [time]: it will land [new time], you need a different owner or you cannot do it?

That is a follow-up. The other person can answer without writing an essay. They can also tell you they cannot deliver it, which is more useful than another silence.

This is not about who has the authority to choose a trade-off. If the real problem is a decision nobody will make, use how to ask for a decision without sounding pushy. If the risk is now material, use when to escalate a delivery issue.

Manager wording

First follow-up

Assume the first miss is clutter, not character.

Checking [action], which we had as [day]. I need to know whether it will land by [time] or a new time I can plan around.

[Name], the [pack / reply / extract] was due yesterday. [Team] is blocked from starting [next step] until it lands. When can you send it, or who should I speak to if this has moved?

On Teams:

[Action] still outstanding from [day]. Need a time I can tell [downstream owner]. Today / tomorrow / needs a new owner?

Give them an easy way to tell the truth:

If you cannot do this, say so. I would rather reassign it today than discover on [date] that it never moved.

Second follow-up

The second note should not be a slightly sharper version of the first. It should name the dependency.

Second note on [action], originally due [day]. [Named piece of work] now cannot start. I need one of three replies by [time]: a delivery time, a new owner or “I cannot do this”.

I am not looking for a status story. I need a time, a name or a no.

If they are senior:

I know this is in a busy week. I still need a usable answer on [action] by [time], because [dependency] sits behind it. If it is no longer yours, tell me who it moved to.

When the dependency is now at risk

Do not pretend you are still in a gentle nudge.

[Action] has not come back. [Date / rehearsal / supplier window] is now at risk. I need a reply by [time] so I can either wait with a real date or move the work.

If I do not hear by [time], I will [reassign / raise / change the plan] so [downstream work] does not sit still. Tell me before then if the action is still with you.

Peer version

I am stuck without [action]. Can you send it, give me a time or tell me it has moved? I will stop pinging once I have one of those three.

No drama. I just cannot brief [Name] until this lands.

What not to say

• “Just chasing.” Chasing is about you. Name the work.
• “Friendly reminder.” Reminds them you are waiting. Does not tell them what to do.
• “When you get a minute.” There is never a minute.
• “Looping you back in.” Extra names without a new ask.
• “As per my last email.” That is score-settling. Restate the action and the reply you need.

Why this wording works

Silence leaves the work without an owner. A closed choice (time / new owner / cannot do it) gives you something you can plan around.

Making it safe to say “I cannot do this” is not softness. It is how you stop fake ownership.

If that still does not work

If you have a named owner, a named action and two clear follow-ups, and the work is still stuck, you are leaving follow-up and entering risk.

Use when to escalate a delivery issue to check hold, flag or raise. Use the Escalation Pack to get the evidence and the first conversation straight.

If the original date was never a real commitment, fix that next time with how to ask someone to commit to a date.

Free tool

If silence is now a delivery risk, prepare the raise

Use the Escalation Pack when follow-up has failed and you need a steer on hold, flag or raise. It runs in your browser and does not send your answers anywhere.

Build your Escalation Pack