DEV Community

Duaer Team
Duaer Team

Posted on

How to track follow-up tasks so nothing quietly stalls

Follow-up work is the stuff that happens after the "real" task: chasing a reply, checking that a fix actually shipped, confirming that a request someone promised to handle got handled. It's rarely hard. It just slips. One person in an automation forum listed the usual casualties: "a client wrote and nobody replied, a deal sat untouched for weeks, a payment was started and never finished."

None of those are failures of skill. They are failures of tracking. This article walks through a simple, tool-agnostic way to track follow-up tasks for yourself or a small team: what columns to keep, what each status means, how to run a weekly overdue review, and a formula you can drop into a spreadsheet to flag what's late. It isn't about meeting action items specifically; it covers any loose end that needs someone to come back to it.

Why follow-ups get lost

Follow-ups have three properties that make them easy to drop:

  1. They're triggered by something else. You send an email and the follow-up is "check for a reply on Thursday". The original task feels finished, so the follow-up never gets written down.
  2. They depend on other people. You can't complete them alone, so they sit in a vague "waiting" state with no date.
  3. They're small. Nobody wants a project plan for "ping the supplier again", so they live in memory, chat history or a sticky note.

A tracker fixes all three if it does one thing well: every follow-up gets a line, an owner and a date the moment it's created.

Step 1: Pick one place

The specific tool matters much less than having exactly one. A spreadsheet, a task app, a plain text file—any of these works if it's the only place follow-ups live. The common failure is a split: some in email flags, some in a notebook, some in a chat "saved messages" list. Then the weekly review has to search four places and nobody does it.

If you're tracking for a team, use a shared spreadsheet or shared list everyone can see. Visibility is half the value: people follow up faster when the item has their name on it in public.

Step 2: Use a small set of columns

Here is a layout that works for most people. Keep it this small at first; add columns only when you notice you keep needing the information.

Column What to write Why it matters
ID A short number (F-001, F-002…) Lets you refer to an item in chat without retyping it
What The follow-up as an action: "Get signed quote back from Supplier X" A verb forces clarity about what "done" is
Owner One name Two owners means no owner
Waiting on Who or what you're waiting for, if anyone Separates "my move" from "their move"
Created Date the item was added Shows how long things really take
Next check The date you'll look at it again The single most important column
Status One of the defined statuses below Lets you filter
Done when One sentence describing completion Stops items closing too early
Notes Latest update, with date History without a separate log

Illustrative rows:

ID What Owner Waiting on Created Next check Status Done when
F-014 Get signed quote back Person A Supplier X 2026-10-02 2026-10-08 Waiting Signed PDF saved in contracts folder
F-015 Confirm login fix works for user Person B — 2026-10-09 2026-10-12 Open User confirms they can log in
F-016 Reply to client question about invoice Person A — 2026-10-10 2026-10-20 Open Reply sent and client acknowledged

Note the column called Next check rather than "Due". Many follow-ups don't have a real deadline, but every one of them needs a date when somebody looks again. If you leave this blank, the item is already lost.

Step 3: Define your statuses and stick to them

Statuses only help if everyone means the same thing. Four is usually enough:

  • Open — the owner needs to act next.
  • Waiting — someone else needs to act; the owner checks again on the next-check date.
  • Blocked — it can't move until something specific changes; the note says what.
  • Done — the "Done when" sentence is true. Not "mostly", not "I sent it".

Two rules make statuses trustworthy:

  1. Every status change gets a dated note. "2026-10-08 chased by email, they said Friday" is enough.
  2. Waiting always has a next-check date. "Waiting" without a date is how deals sit untouched for weeks.

Avoid adding statuses like "In progress" or "Almost done". They feel informative but don't tell anyone what to do next.

Step 4: Capture follow-ups at the moment they're created

The tracker is only as good as what goes into it. Build the habit of adding a line at the exact moment a follow-up is born:

  • You send an email that needs a reply → add a line with next check in two or three working days.
  • Someone promises to do something for you → add a line with them in "Waiting on".
  • You hand something to a colleague → add a line, owner is them, and tell them.
  • A ticket or request is "fixed" → add a line to confirm with the requester.

If adding a line takes more than thirty seconds, the tracker is too complicated. Trim columns until it doesn't.

Step 5: Flag overdue items automatically

A spreadsheet can do the nagging for you. Add a Flag column with a formula that looks at the status and the next-check date. Assuming Next check is in column F and Status in column G, put this in row 2 and fill down:

=IF(G2="Done","",IF(F2<TODAY(),"Overdue",IF(F2-TODAY()<=2,"Due soon","")))
Enter fullscreen mode Exit fullscreen mode

What it does:

  • Done items show nothing.
  • If the next-check date has passed, it shows Overdue.
  • If it's within two days, it shows Due soon.
  • Otherwise it stays blank.

I tested the logic in LibreOffice Calc with a fixed reference date of 2026-10-11 in place of TODAY(): a Waiting item dated 2026-10-08 showed Overdue, an Open item dated 2026-10-12 showed Due soon, an Open item dated 2026-10-20 stayed blank, and a Done item dated 2026-10-01 stayed blank. Depending on your locale, LibreOffice may expect semicolons instead of commas between arguments.

Add conditional formatting so "Overdue" turns red and "Due soon" turns amber, then sort or filter by the Flag column. That view is your daily list.

Step 6: Run a weekly overdue review

Daily glances catch the urgent items. A weekly review keeps the tracker honest. Set a fixed fifteen-minute slot, same day each week, and go through it in this order:

  1. Overdue first. For each one: act now, set a new next-check date with a note explaining why, or close it.
  2. Waiting items. Has the other person gone quiet twice? Change the approach: call instead of emailing, or ask whoever can unblock it.
  3. Blocked items. Is the blocker still real? If it's been blocked for more than two weeks, raise it with someone who can decide.
  4. Items with no next-check date. There shouldn't be any. Add one.
  5. Done items. Move them to a "Closed" sheet so the active list stays short. Don't delete them; the history is useful.

For a team, do this review together for the overdue items only, and keep it brisk. The goal is decisions, not status reports.

Step 7: Decide when to escalate

Some follow-ups will never close by politeness alone. A simple rule removes the awkwardness of deciding each time:

  • Second missed next-check on a Waiting item → change channel (phone, a direct message, or in person).
  • Third missed next-check → tell the person who asked for the work, or someone who can make the call.
  • Blocked for two weekly reviews → escalate with a one-line summary: what's needed, from whom, since when.

Write the rule at the top of the tracker so it's not personal when you apply it.

A checklist for a healthy tracker

  • [ ] Every item has exactly one owner.
  • [ ] Every non-Done item has a next-check date.
  • [ ] Every Waiting item says who it's waiting on.
  • [ ] Every item has a "Done when" sentence.
  • [ ] The Flag column shows no overdue items older than a week.
  • [ ] Done items have been moved out this week.

Common mistakes

  • Tracking tasks instead of follow-ups. The tracker becomes a full to-do list and the follow-ups drown. Fix: only add items that depend on coming back later or on someone else.
  • Shared ownership. "Person A / Person B" means each assumes the other did it. Fix: one name; mention the second person in Notes.
  • Closing on effort, not outcome. "Emailed them" isn't done. Fix: the "Done when" column.
  • Skipping the weekly review when busy. That's exactly when things slip. Fix: keep it to fifteen minutes and review overdue items only if time is short.
  • Endless date pushing. Moving next check forward without a note hides a stuck item. Fix: every date change needs a dated note, and the escalation rule applies after two misses.

Wrapping up

Tracking follow-up tasks comes down to a handful of habits: one place, one owner, a next-check date on everything, clear statuses, a formula that flags what's late, and a short weekly review. None of it needs a special tool. Start with the columns above, add your current loose ends today, and run your first review at the end of the week.

This article was drafted with AI assistance.

Top comments (0)