Open any task manager and look at what a task can be. It can be done or not done. It can have a date, a tag, a project, maybe a priority. What it almost never has is a state that means: I have done my part, and this is now sitting with someone else, and I am still accountable for it.
That state is most of coordination work. The referral you sent. The quote you requested. The approval you're waiting on. The candidate who said they'd confirm by Wednesday. None of these are things you can do. All of them are things you will be asked about.
What people do instead
In the absence of a waiting state, people improvise, and the improvisations are all bad in the same way — they push the tracking back into memory.
- Leave it in the list as an open task. Now your to-do list contains items you cannot action, which teaches you to skim past items in your to-do list.
- Flag the email. Now the tracking lives in a channel, so an obligation that arrived by phone has nowhere to go.
- Set a reminder to check. This works, and it costs a separate deliberate act per item, so it gets used for the important three and not the other twenty.
- Remember. The default, and the reason "sorry, chasing this again" is the most-typed sentence in operations.
Three fields is all it takes
A waiting item needs remarkably little structure to become manageable: who it's with, what you asked for, and when you'd want to chase if nothing happens. That third field is the one that does the work, because it converts an open-ended anxiety into a dated event.
Once those exist, several things become possible that weren't before. You can see everything outstanding with one person before a call with them. You can see what's been sitting longest. And you can be told, on the right morning, that a thing has gone quiet — rather than discovering it when the deadline it was blocking arrives.
A follow-up system's job is not to remind you to chase. It's to make the decision "is it time to chase?" happen without you having to think about it.
The second half: what you owe
Waiting has a mirror image that's even less often modelled: the commitments you made. "I'll get you those numbers by Friday" is a real obligation created in a real conversation, and unless you wrote it down at the moment, the only record of it is in the other person's head.
This is the asymmetry that damages working relationships. You remember the things you're chasing, because they block you. You forget the things you promised, because they don't. From the outside that looks like a pattern of being unreliable, and no amount of being busy reads as an explanation.
Which is why a brief that only shows what's due today is doing half the job. You promised deserves its own section, and it deserves to be uncomfortable to read.
Drafting the chase without sending it
The last piece is the follow-up message itself, and it's a smaller problem than it looks. By the time you need to chase, the system already knows who it's with, what was asked, when, and what it's blocking. Composing a polite two-line nudge from those facts is a narrow, well-specified writing task.
The important part is what happens after it's written: nothing, until you look at it. A drafted follow-up is a saved minute. An auto-sent follow-up is a message going to a client on a schedule you didn't check, possibly about something that was resolved by phone yesterday and never marked done. The first is useful. The second is how you teach people to ignore your emails.