You keep one list. One line per ask, written at the moment you send, rather than reconstructed six weeks later. Each line carries six things. Who has it, what you asked for, and the day you asked. Then the day you’ll act if nothing comes back, what it’s holding up, and what you’ll do when that day arrives. Sort it by person. Sweep it once a week. Take lines off it as carefully as you put them on.
That’s the whole apparatus, and it’s small on purpose. Every other judgment about following up is a judgment about a set. Is this the third chase this week, or the first? Does the deadline two weeks out belong to this item, or to a different one with the same client? Is the person you’re about to nudge already sitting on two other things of yours? Each of those needs the set in front of you, and one thread is where email keeps you.
- Write the list as you send. Reconstructing it later is the step that fails, because you’re hunting for a message with no reply beneath it, and a mailbox can’t search for an absence.
- A line that names only the item keeps working on you. A line that names what you’ll do about it, and when, settles.
- Sorted by thread, the list tells you what you already knew. Sorted by person, it tells you the one thing you needed before writing.
- Entries leave as reliably as they arrive. A list that only grows is a list you stop opening, and you end up back where you started with a worse conscience.
Five questions next door are settled elsewhere, and this page takes them as read. Choosing the interval belongs to how long to wait before following up. Whether a run of messages is starting to read as nagging is following up without nagging. What to do once the ordinary route has plainly failed is chasing a client who will not reply. Why the mail you most need answered is the slowest of all, and what an unanswered email actually is, is unanswered emails and the threads that come back. Money is tracked differently again, because its dates come from your terms rather than from anybody’s attention. That’s following up on an unpaid invoice.
Six things a line has to carry
The temptation is a list of subject lines. A subject line tells you that a conversation happened. In a busy month you need what’s owed and what to do next, and the subject line is silent on both.
Who has it, by name. The field is the person. Two people at the same firm are two lines, and one person at two firms is still one person when you sit down to write. This is the field that makes the whole list worth keeping, and the section on sorting below says why.
What you asked for, specifically enough to ask again. The March statement for the operating account, the one showing the transfer in on the 14th. In six weeks that detail is gone from your memory. A vague chase invites a vague answer or the wrong document, and that costs you another cycle.
The day you asked. The one field your sent folder already gives you. It’s the input to every interval decision you make later. It’s also what you’ll want if this ever turns into a disagreement about who was waiting on whom.
The day you’ll act. Choose it when you send, on a quiet afternoon, while you can still think straight about it. The right date depends on what you asked for and how fast that person normally answers, and the intervals for each are worked out in the wait before a first chase.
What it’s holding up. The field everybody skips, and the one that does the most work. On a Tuesday with forty minutes, it tells you which three of your nineteen open items are worth spending them on. It’s also the honest test of whether the line belongs on the list at all.
What you’ll do if nothing comes. Extension filed, slot released, file closed where it stands, work planned around the gap, or nothing at all. Writing it down as you send is far easier than inventing it in week six. It turns the eventual chase from a request into a notice. The message that carries a default, and the three tests it has to pass before you send one, are in chasing a client who will not reply.
Some lines carry a date somebody else chose, and on those the fourth field is arithmetic rather than judgment. A client electing S corporation status has to file Form 2553. The IRS sets the window at “no more than 2 months and 15 days after the beginning of the tax year the election is to take effect, or at any time during the tax year preceding the tax year it is to take effect”. The form needs other people too, since “each shareholder consents by signing and dating either in column K or on a separate consent statement” (checked September 6, 2026). So the line is blocked on named people with a fixed outside date. A scope question that simply goes quiet behaves differently. Mark the dated ones, because they’re where waiting quietly gets expensive.
The two fields that let you put it down
An entry carrying a date and a default behaves differently from an entry carrying neither, and the difference shows up in how much room it takes in your head.
The finding behind that is Consider It Done. E. J. Masicampo and Roy Baumeister showed that unfinished tasks intrude on unrelated work. They also showed that letting people set out how, when and where they’d deal with a task stopped the intruding, while the work itself stayed undone. The study is laid out where the date on a task comes from, in email task management without writing it down. What matters here is a wrinkle that shows up on this side of the ledger.
You can’t make a plan to do the thing. Dana has the engagement letter. Whatever you write down, the doing belongs to them. That’s what makes a debt owed to you feel different from every other item on a list, and why it goes on circling after you’ve written it down.
So the plan on one of these lines is a plan about the absence rather than about the task. Get that the wrong way round and the entry quietly stops working, so it’s worth a moment. Not sign the engagement letter, which was never yours to do. Instead: on the 19th, if it hasn’t come, call rather than write, and file the extension on the 30th whatever happens. That has a how, a when and a where, all of it inside your control, and it’s the only kind of plan this sort of entry can carry. Which is why the fourth and sixth fields carry weight. They turn something outside your hands into an appointment you can keep.
One condition travels with that research, and it belongs on any list built from it. What predicted the quiet was whether the plan was one the person meant: “reduction of the effects was mediated by the earnestness of participants’ plans: Those who ultimately executed their plans were those who also exhibited no more intrusions”. A date you name and let pass is a wish. Name enough of them and the list stops working, because you’ve taught yourself that its dates are decorative. That’s the argument for the sweep further down, and it’s a stronger one than neatness.
Where the list actually lives
This list always ends up somewhere concrete. Where it lives decides whether it survives March.
The best account of what people do instead is Quality Versus Quantity, the PARC study of email task management published in Human-Computer Interaction in 2005. It’s used elsewhere on this site for what makes the inbox a poor task list. One sentence of it belongs on this page. Bellotti and colleagues concluded that the weight of email comes from work you need somebody else to finish: “tasks cannot be completed until a response is obtained and so they are interleaved. Interleaving means that the e-mail user must somehow simultaneously keep track of multiple incomplete tasks, often with the only reminder for each one being an e-mail message somewhere in the inbox or a folder”.
Their count of where such things end up is worth having before you choose a home for yours. Across 16 people in varied jobs they counted 882 to-dos, and “the largest proportion of ‘to-dos,’ 35% were represented in e-mail, which was as many as in ‘to-do’ lists and the calendar combined”. So roughly a third of what people owe already lives in mail, wherever they meant to keep it. An average near 55 open items each is a useful answer to the private suspicion that you personally are disorganized.
That’s one American research lab and two other firms, twenty years ago, and there are more tools now than there were. The five places are the same five.
Your head. Free, instant, and correct until the week it fails you, which is reliably the week you needed it. You also can’t sort it, so the per-person view below stays out of reach.
Flags and stars in the mailbox. The cheapest step up from memory, and it fails for a reason worth naming exactly. A flag holds none of the six fields, so a flagged message can’t be sorted by person, ranked by what it blocks, or closed with any confidence. A chief executive in the PARC study described the end state, still working the flags down “to where my flags really mean something” and reporting that “I’m constantly trying to eliminate them, but I can’t.” Treating a private return date as a follow-up is the related error, and snoozed email takes that apart.
A folder or label for things awaiting a reply. Better, because it’s a set you can look at in one go. Copy yourself on the outgoing message and the folder holds your ask rather than their last note. Its weakness is that it stays quiet until you go and look, and two weeks of ordinary mail is enough to bury the fact that it exists. Attach the weekly sweep below to it and it survives.
A spreadsheet or a note. The one option here that holds all six fields, sorts by any of them, and opens for a second person in your practice. The cost is a transcription per message and the discipline to close rows, and it’s a real cost. For a practice with a busy season and a handful of clients whose silence is expensive, it’s usually worth paying.
Wherever your other work already is. A task manager, or the workflow tracker inside practice management software if you run one. This is the recommendation, for one reason. The debts owed to you compete for the same hours as the work you owe other people, and ranking two things against each other takes one list. If your task list already carries the deliverables, put the waiting-ons in it too, marked so you can filter them apart.
All five leave you the transcription. Every one of them is a copy of something you already wrote, made by hand, at the moment you were trying to move on. That’s the step that fails first, and the step worth handing over. The last section is about that.
Sort by person before you sort by date
A list of outstanding asks has three useful orders. Most people only ever see the one their tool defaults to.
By person, before you write anything. This is the order that changes what you do. Three separate threads with Dana, each chased proportionately this week, is three defensible messages and one impression: a week of you. Seeing everything Dana owes you before you write turns three interruptions into one message. It often shows you why they’ve gone quiet on all of them, because the items relate to each other in a way you can only see once they sit together.
The batching itself, including when to skip it, belongs to following up without nagging.
By the day you’ll act, for running a morning. This is the order that makes the list a working document rather than an archive. Today’s lines are today’s chases. Everything else can wait.
By what it’s holding up, when time is short. The field most people leave blank is the only one that ranks. An unsigned form standing between you and a filing outranks a scope question that’ll still be there in November, and neither of those is obvious from the date.
A fourth order matters once you’re more than one person, which is by who in your practice is waiting. A debt owed to your colleague sits outside your view, and yours sits outside theirs. That’s how two people chase the same client in the same week, or how the chase falls between them. The coordination problem has its own shape, and the question that stops getting asked works it through.
The sweep that keeps it honest
A list of outstanding items stays alive on a scheduled look at the whole thing, and the scheduled look is the part people drop first.
The practice has a name and a long history. Getting Things Done treats a waiting for item as one of the three things that can keep a project alive, alongside a next action and a calendar entry, and it puts the check on a fixed cadence. “The Projects list and project plans are typically reviewed in your GTD Weekly Review, ensuring each project has at least one current next action, waiting for, or calendar item” (checked September 6, 2026). Take two parts of that and leave the rest. The outstanding column is a list in its own right rather than a note in the margin, and somebody looks at all of it on a schedule rather than when it occurs to them.
Twenty minutes, the same slot every week, Friday afternoon or Monday morning. Five questions per line, and most lines take four seconds.
Has this actually been answered? More often than you’d expect, and by all sorts of routes. The client mentioned it on a call, the document came in through a portal, somebody in your office dealt with it.
Is the act-on date still right? A holding reply, a vacation, or a date they named all move it. Feeling impatient on a Tuesday leaves it where it is.
Is it still holding anything up? Some of what you’re owed stops mattering. The quarter closed, the decision got made another way, the project you needed it for is finished.
Is this the fourth thing this person owes me? The sweep is where you find that out. Consolidate on the spot, while the four lines are in front of you.
Has the ask stopped working? Three chases with no reply tells you something about the size of the ask, the person, or the channel. A fourth chase answers none of that, and the repair is in chasing a client who will not reply.
The sweep also gives you a report you can get nowhere else. After two months you can see which clients answer, which ones want a phone call rather than a note, and which kinds of ask never come back in writing at all. That’s the material for changing what goes in your engagement letters, and that’s a cheaper fix than any amount of chasing.
How a line comes off
A list that only accumulates stops getting opened, and a list you’ve stopped opening is worse than no list, because it turns a manageable worry into a documented one. So closing lines is what keeps the thing usable.
There are four honest exits, and one of them is the obvious one.
It arrived. Close the line the day it lands, rather than at the weekly sweep. Telling the other person it landed is a separate habit and a valuable one, covered in following up without nagging.
It was settled somewhere else. The most common reason a line is wrong. Somebody answered on the phone, or in a meeting, or by quietly doing the thing. These lines produce the worst message you can send, which is a chase for something the client dealt with on Thursday. A sweep that asks the question is what protects you from it.
You absorbed it. You found the number another way, reconstructed it from last year, or decided to go ahead as things stand. Close the line, and say so to the client if they might still be looking for it. An ask you quietly withdrew is still an open loop on their side, and it counts against you exactly like the ones you sent.
You stopped. You’ve decided the answer isn’t coming, and the work goes ahead on your stated default, or stops where it is. That’s a real closure, and it deserves recording as one, with the date and what you did.
Watch for the line that sits half open. Three months old, nothing depends on it any more, and you skip past it every week because deciding takes more effort than scrolling. Two or three of those and the sweep starts to feel like a chore, which is where dropping it begins. Clear them on sight. A line you’d leave alone today is a memory, and a memory can live somewhere with no dates on it.
What should never go on it
The list stays credible by staying short, and one question does the filtering. Name what changes if this never comes back.
If the answer is nothing, you sent a message, and a message is a fine thing to have sent. Courtesy notes, status updates, copies for information, the thing you asked in passing: those are messages too, and putting them on the list dilutes the entries that are real debts. Track everything and you end up where the chief executive did, with a wall of flags that mean nothing.
Two other kinds look like entries.
Waiting on an event rather than a person. A bank issuing a statement on the 5th, a filing acknowledgment coming back, a portal notification. The event arrives on its own schedule, nobody is deciding anything, and there’s nothing there to chase. What you want is to be told when it happens rather than a reminder to go and check. That’s a watch, and setting your first watch in plain words covers which of your open loops it suits.
Waiting on yourself. If the next move is yours, that’s work. It belongs on the ordinary list with the ordinary deadlines, and mixing the two is how a waiting-on list turns into a second inbox.
The debts pointing the other way
Bellotti and colleagues split their first challenge into two halves that most people run together: keeping track of “a. My own actions” and “b. Outstanding actions (things other people are doing for me)”. A director in their study described the whole cycle in one breath: “I have to remember that something is actually needed by someone. Then I have to find it and remember to send it. Then I’ve got to remember that I sent it and I’m waiting for a response”.
Both halves matter, and they’re two different jobs. What you owe has a completion you control and a deadline somebody gave you. What you’re owed has neither. Keep them in one place, in one list with two marks on it, for a reason that shows up at the person level. Open Dana’s name. You see an engagement letter and a March statement they owe you, and an answer about the scope of the audit that you owe them. You write a different message than either half alone would have produced, and one list is what puts all three in front of you.
The half where the ask arrived in somebody else’s message has a good automatic answer now. The obligation is written down in a paragraph somebody sent you, and it can be lifted straight out of it. That’s email task management without writing it down. The half in this piece is harder, because the evidence for it is a message you sent and a reply that never came.
What Point keeps without you writing it
The six fields are easy enough to think of. Filling them in is a second job, performed at the moment you’re trying to finish the first one. In a busy week it’s the transcription that gets dropped, and your judgment was fine all along.
Point is a full email client, so the message you sent and the answer you’re waiting for are one object rather than two records in two places. As you send, you say in ordinary words that the next move is theirs. The sentence becomes a dated task, carrying your plan and one link back to the conversation it came from. You supply the fields at the only moment you actually hold them, while you still remember what you asked for, who has it and what it’s blocking.
For this problem the list earns its keep more than the reminder does. Everything you’ve handed off is tracked and gathers in one place, alongside the work you owe other people, and that’s what makes the per-person view possible. You see that this is the fourth thing outstanding with the same client before you write, rather than hearing it from them.
On the date you named, a thread that’s still silent comes back in front of you with a prompt attached. A thread that was answered in the meantime stays where it is, because the silence is what brings it back and the calendar alone leaves it be.
Where the item turns out to have been dealt with elsewhere, over the phone or in a room, Point marks the task as looking finished and shows you the evidence behind that. The line stays there until you say so. That’s the sweep’s second question, answered before you ask it.
When what you’re waiting on is an event rather than a person, a standing request does the watching. The watch reports to you a single time and then ends.
You set how far Point goes on its own, one level for each kind of action, from suggest-only, through preparing something and holding it for review, to handling it outright. Every kind starts at review. Point keeps a record of every action in sequence and in ordinary language, and undo works back from that, with the exception you’d expect for a message already sitting on somebody else’s server. Years of flagged mail holding the old version of this list stay exactly where they are. Everything else Point does with a mailbox is set out on the benefits page.
The comparison worth having before you choose anything is with the explicit version, where you mark a message on the way out and it comes back if nobody replied. That works, on the messages you remembered to mark, and Point compared with Boomerang takes the difference apart properly.
Writing the chase stays with you either way, and that division is the right one. A list tells you that Dana has owed you an engagement letter for eleven days. The sentence that gets it signed is yours to write.
Common questions
How do I keep track of emails I am still waiting on a reply to?
Keep one line per outstanding ask, written at the moment you send. It carries who has it, what exactly you asked for, and when you asked. Then the day you’ll act, what it’s holding up, and what you’ll do if nothing comes. Reconstruct that list later from your sent folder and you’re hunting for a message with no reply beneath it, which is the one thing a mailbox can’t search for. Sweep the list once a week, and close lines the day they resolve.
What should go on the list, and what should not?
The test is whether you can name what changes if the answer never arrives. If nothing changes, it was a message rather than a debt, and putting it on the list makes the real entries harder to see. Two other things look like entries. Waiting on an event nobody is deciding, such as a bank issuing a statement, wants a watch rather than a chase. Waiting on yourself is ordinary work, and it belongs on your ordinary list.
How often should I look at it?
Daily for the lines whose act-on date has arrived, which takes a minute, and once a week for the whole thing. The weekly pass catches what the daily view misses. Items already answered by phone, dates that have moved, things that have stopped mattering, and clients who have quietly accumulated four open items. Twenty minutes in a fixed slot is enough, and a fixed slot survives a busy month far better than an intention to check when you think of it.
Should I keep it separate from my normal to-do list?
One list with two marks on it, rather than two lists. Debts owed to you compete for the same hours as the work you owe other people, and ranking the two against each other takes a single list. The stronger reason is the per-person view. Seeing that a client owes you two documents while you owe them an answer changes the message you write, and that view appears once both halves sit in one place.
How many open items is normal?
More than feels reasonable. One count across sixteen professionals in varied jobs found 882 to-dos between them, an average near fifty-five each, with about a third of those living in email rather than in any list. That’s one study of one kind of workplace, so read the number as scale rather than as a target. If you’re carrying twenty outstanding asks and feeling disorganized about it, your memory is doing what anybody’s does. Twenty is simply more than a person holds.
Can software keep this list for me?
The part worth handing over is the transcription and the return, because those are what fail in a busy week. The judgment about which debts are worth chasing, and what to write when you chase them, is yours, and automation usually makes it worse. What a tool should do is capture the ask as you send it, hold the date you chose, bring the thread back only if it is still unanswered, and stand down quietly when the reply arrives.
The whole thing in one page
What you’re owed has no natural home, so you build it one, and the build is small. One line per ask, six fields, written at the moment you send.
Two of those fields do most of the work. What it’s holding up is the only field that ranks your open items against each other. What you’ll do if nothing comes is the one that lets you put the item down until the day arrives. A task with a plan attached behaves differently from a task without one, measurably so, and a plan you mean is the only kind that counts.
Then two habits keep it alive. Sort by person before you write anything, because that’s the view that turns three chases into one message and shows you why the client has gone quiet. And sweep the whole list weekly, closing lines with the same care you opened them, because the entries that resolved somewhere else are the ones that send you chasing a client for something they handled on Thursday.
What sits on the list differs by trade. An accounting practice is mostly owed signatures and documents with hard outside dates behind them. A consultancy is mostly owed decisions with no date at all, which is why one list goes urgent and the other goes cold. Both of those, and six more, are set out by who is doing the waiting.