Skip to content
PingCadence
Get started

Status updates · Templates

How to ask your team for a status update (and get an answer you can use)

By PingCadence · · 7 min read

Short answer

Ask about one task at a time, show the dates you’re holding them to, and offer three answers: on track, not on track or hard to say. If it’s not on track, ask for a new date rather than an explanation. Send it on a fixed day, give a deadline, and remind once.

Why “any updates?” doesn’t work

An open question pushes all the work onto the person answering. They have to work out which task you mean, what “update” covers, how much detail you want, and whether “it’s going fine” is enough. Most people do the reasonable thing: reply later, reply vaguely, or don’t reply. You then chase, which costs you more time than the answer was worth.

A good status request flips that. You do the setup (which task, which dates) so the other person can answer in seconds, and the answer comes back in a shape you can act on.

Anatomy of a status check-in people answerA check-in for one task shows: 1, the specific task; 2, the planned start and end dates; 3, three answers: On track, Not on track, Hard to say; 4, a new end date asked only when not on track; 5, an optional comment.Website launch · task 1 of 2Supplier quotePlanned startOct 14Planned endNov 13Duration31 daysIs this on track?On trackWill finish by Nov 13Not on trackYou’ll give a new dateHard to sayToo early, or it depends on somethingNew end date (if late)Comment (optional)Send update123451One specific taskNot “the project” or “your stuff”2The dates you’re asking aboutSo “on track” means the same thing3Three answers, one honest middle“Hard to say” beats a hopeful “yes”4A date only when it’s lateA number you can put in the plan5Room for contextOptional, never required
Each part of the request removes a reason not to answer, or a reason to give a vague one.

The five parts of a request people answer

  1. One task, named the way they know it. Use the task name from the plan, not a summary line. If someone owns three tasks, list three short questions in one message rather than one long one.
  2. The dates you’re holding them to. “Planned to finish Nov 13” anchors the answer. Without it, “on track” can mean on track for a date they remember differently.
  3. Three answers, not two. A yes/no question forces people who aren’t sure into “yes”. Hard to say is the honest middle, and it’s the answer you most need to hear early: it’s the conversation to have this week.
  4. A date, not a reason, when it’s late. “Running a bit behind” can’t go into a plan. “Now Nov 20” can. Ask for the new end date (or how many days it needs) and let the comment carry the why.
  5. Comments optional. Some people will tell you a lot. Don’t make everyone write a paragraph to say “fine”.

Templates you can copy

Replace the bracketed parts. They work as email or as a message.

Template 1: one task

Subject: Quick status check: [Task name]

Hi [First name],

Checking in on [Task name] for [Project].
It's planned for [start date] to [end date].

Is it on track?
  - On track: will finish by [end date]
  - Not on track: what's the new end date?
  - Hard to say: what does it depend on?

A one-line reply is plenty. Please answer by [day].

Thanks,
[Your name]

Template 2: several tasks, one message

Subject: Quick status check: 3 tasks ([Project])

Hi [First name],

Three quick ones for [Project]. For each: on track, not on track (with the new date), or hard to say.

1. [Task A] (planned to finish [date])
2. [Task B] (planned to finish [date])
3. [Task C] (planned to finish [date])

If everything is on track, "all on track" is a perfect answer.
Please reply by [day]. Thanks!

Template 3: the one reminder

Hi [First name], just a nudge on [Task name] (planned to finish [date]).
On track, not on track, or hard to say? One word is fine.

Template 4: Teams or Slack

Quick one on [Task name] (due [date]): on track / not on track (new date?) / hard to say?

Cadence: pick a day and keep it

Weekly works for most projects; every two weeks for long, slow phases. What matters more than the interval is predictability: when people know the question arrives on Monday morning, they start keeping the answer in their head. Give a deadline a couple of working days out, send one reminder to anyone who hasn’t answered, and then pick up the phone instead of sending a third email.

What to do with the answers

  • On track: nothing. That’s the point of asking a precise question.
  • Not on track: you now have a proposed date. Decide: accept it into the plan, negotiate it, or escalate. Don’t silently overwrite the baseline; keep the original date so the slip stays visible.
  • Hard to say: your shortlist for conversations this week.
  • No answer: one reminder, then talk to them. Silence on a task that’s due soon is itself an answer.

Doing this without the copy-paste

PingCadence runs exactly this loop from your existing plan: it drafts one check-in per person with their tasks and planned dates, waits for you to approve it, sends it from your own Outlook or Gmail, and collects on track / not on track / hard to say answers with new dates. You decide what changes in the plan. See how it works.