Here is the thing that bothered me for a while before I could name it: I had a task management system I trusted, and it still felt like I was carrying weight that the system should have been carrying. Items would sit in the backlog for days, and when I finally got to them I’d realise the only reason they were there was that someone had sent me a message about them and I hadn’t replied.
That’s not a task. That’s a deferred receipt.
Most productivity frameworks divide the world in two. You have time-critical things — the dentist appointment, the medication reminder, the call at 3pm — and you have everything else, which lives in a list you work through when you have capacity. The first category gets a Due date; the second gets a someday. The system feels complete because it covers the full range of urgency. But it quietly ignores a third dimension: whether an external signal already exists for the thing.
Think about what happens when your bank texts you about a suspicious transaction. Or a government department sends a letter saying your form has been processed. Or a recruiter follows up on an interview. The common thread is that the world has already arranged for you to remember this. There is a notification, a letter, a thread in your inbox. The external trigger is already there, doing exactly what a reminder would do. So what happens when you add it to your backlog anyway?
You’ve now set up two tracking mechanisms for one thing. The SMS is sitting in your messages, the item is sitting in your list, and you’re burning a small amount of mental energy maintaining the relationship between them. Every time you see the backlog entry you have to remember that it came from that message, and every time you see the message you’re vaguely aware it’s also somewhere in your system. This isn’t safety — it’s overhead dressed as safety.
The right move, the moment one of these lands, is to act immediately or to park it in a short-term holding pen — something like Due, set for later today or tomorrow — with the explicit intention of acting and archiving, not of managing long-term. The backlog is for things that have no external trigger. It’s for ideas you want to revisit, projects you’re shepherding, commitments you made to yourself. It is not for things that already have a string attached.
The test is simple: does the item live anywhere else? Is it a thread you haven’t replied to? A letter sitting on your desk? A portal notification in your email? If the answer is yes, then your list isn’t tracking the task — it’s tracking your anxiety about the task. There’s a difference, and systems that conflate the two end up doing more cognitive work than they save.
There’s a related failure mode that’s easy to slide into. You get a notification, you don’t act, you add it to the list. Then the original notification expires or gets buried, and now the list is the only place it lives. The external trigger is gone, so the item has graduated from a deferred receipt into a genuine backlog item — except you’ve lost all the context that came with the original message. You’re now managing a dehydrated version of the thing, without the thread, without the sender’s tone, without the urgency signal that was baked into the original medium. This is how backlogs become archaeological digs.
The cleaner habit is to treat act-on-receipt items as a separate primitive entirely. When something arrives with an external trigger, you have three moves: act now, set a short-term placeholder in Due and act later today, or consciously decide this isn’t worth your time and archive it. There is no fourth move. Adding it to the backlog is just a delayed version of not deciding.
I’ve started auditing my list with this lens — looking for items that only exist because I didn’t act on the notification that created them — and the results are uncomfortable in the useful way. A lot of what I thought was careful task management turns out to be careful procrastination with better aesthetics. The system was absorbing the things I didn’t want to deal with and calling it organisation.
Which raises the obvious question: if you can get this clean, if the backlog really does contain only things with no external trigger and act-on-receipt items either happen or get a hard placeholder — what else in your system is secretly a fourth category you haven’t named yet?