Otto

Waiting-For List: How to Build One That Works

Waiting-For List: How to Build One That Works

Founder recording an expected reply in a notebook

A waiting-for list is a single place where you record everything you have handed to someone else and expect back: a reply, a deliverable, an approval, a package. It is not a restaurant waitlist or a product launch signup page. It is a personal productivity tool, and it exists so you stop carrying open loops in your head. Below you will find what belongs on it, what every line should say, how to review it, and how to nudge people without becoming a nag.

Otto
Keep every commitment in view
Otto brings email, calendar, meetings and commitments into one shared memory, helping you track follow-ups without carrying them all in your head.

TL;DR

  • A waiting-for list holds items where the next action belongs to someone else, so you can check on them instead of remembering them.
  • Each line needs the expected result, the person, the date you asked, and a date to look again. Add a link to the original thread.
  • Review it at least weekly. For every line, do one of three things: close it, chase it, or move the check date.
  • The hard part is capture. Promises made on calls and in email threads are the ones that go missing, so log them the moment they are made.
  • Paper, a notes app or a spreadsheet all work. Software helps most when it can see your email, calendar and meetings at once.

Table of Contents

What a waiting-for list actually is

The idea comes from the Getting Things Done method. David Allen’s team defines the Waiting For list as the place for items you are waiting on from someone or something else, such as callbacks, email responses and orders. The principle is simple. If the next action sits with another person, it does not belong on your to-do list, because you cannot do it. But it cannot vanish either, because you still care about the outcome.

That gap is where work quietly dies. You asked a vendor for a quote, a colleague for a draft, a client for sign-off. Two weeks later you have no memory of asking, and the project is stalled for a reason nobody can see.

Writing about the practice in 2025, Robert Talbert describes the list as holding anything that needs your attention when the next action belongs to someone else. Another writer, Martin Spriggs, makes the psychological case: putting the who, what and when on paper stops your mind from repeatedly asking itself whether you ever made the request.

A to-do list answers “what can I do now?” A waiting-for list answers “what should I be hearing back about?” You need both.

What belongs on the list

The rule is the same every time: someone else holds the next move, and you would be unhappy if it never came. In practice that covers a handful of familiar categories.

Email you are expecting. Talbert’s examples include email, calls and texts, requested items or reimbursements, approvals or information, shipments and delegated tasks. The official GTD setup guide for Things also says that delegated email requiring tracking belongs in a Waiting For folder or list.

Delegated work. Anything you assigned to a teammate, contractor or assistant. Erlend Hamberg’s guide to GTD recommends adding delegated work, expected email replies, orders and blocked tasks to the list.

Blocked project steps. You cannot finish the pitch deck until finance sends the numbers. The deck is not delegated, but its next step is out of your hands, so the numbers go on the list.

Orders and logistics. Equipment, contracts out for signature, refunds.

Promises made to you in conversation. “I’ll send that over Thursday” said at the end of a meeting is a waiting-for item the second you hear it.

What does not belong

Your own commitments. The official GTD guidance separates the two: delegated items go to Waiting For, while personal later actions go to an action list, calendar or email action folder. Mixing them is the most common reason a list becomes unusable. When you scan it, you want to see only what others owe you. What you owe others lives elsewhere.

What each line should say

A line that reads “Sarah, budget” will make no sense in three weeks. A good entry lets you follow up without reopening the whole history.

The core fields are simple. Talbert records what is awaited, who currently owns the next action and when the request was initiated. Spriggs says to capture what you asked for, whom you asked, and when. From there, a few extra fields pay for themselves.

Field What to write Why it matters
Expected result The specific thing, not the topic (“signed vendor contract”, not “contract”) You can tell at a glance whether it arrived
Who Person, team or company You know whom to ask
Date requested The day you asked Shows how long it has been outstanding
Agreed date Only if the other person committed to one Records their commitment, not your guess
Check date When you plan to look again Triggers the nudge
Link URL of the email thread, doc or ticket Keeps context one click away
Latest update One line on what happened last Saves rereading the thread

The distinction between the agreed date and the check date is worth holding on to. The first is what they promised. The second is when you will look, which might be earlier. If nobody gave a date, leave the agreed date blank rather than inventing one, and set a check date that suits how urgent the item is.

Keep entries short. A compact pattern such as person, action, expected deliverable and an optional date, with a consistent tag like @waiting so you can filter, is enough for most people. If you are logging a dozen items a day, more structure than that will slow you down and you will stop doing it.

Set one up in an afternoon

You do not need special software. Talbert suggests any trusted medium, such as paper, Google Docs or a notes app, named Waiting For. Pick the one you will actually open every day.

  1. Create the list. One page, one note, or one tag in your task manager. Name it plainly.
  2. Do a brain dump. Talbert recommends an initial 15-minute session. Set a timer and write down everything you are currently expecting from anyone.
  3. Sweep your sent mail. Scan the last few weeks of sent messages for questions and requests that never got a reply. Add each one with its thread link.
  4. Sweep your calendar and notes. Look through recent meetings for “I’ll get back to you” moments you heard but never logged.
  5. Assign a check date to each line. Be realistic. A quote request might be three business days. A reimbursement might be two weeks.
  6. Put the weekly review on your calendar. A list with no review is just a pile.

After that, you add items as they arise in daily work and during the weekly review, which is the rhythm Talbert describes.

Capturing promises from meetings and email

Most people who try a waiting-for list stall on capture, not on structure. Anything you sent is easy to log. Anything said on a call, or buried in the fourth reply of a thread, is not.

A few habits make the difference.

Log at the moment of handover. The best time to add an entry is when you send the request or end the call. Later, you will have forgotten the exact wording.

Record verbal agreements immediately. If someone says on a call that they will send the figures by Friday, put it in the list before you open the next meeting. Details fade quickly, and “as soon as possible” is the realistic standard.

Keep the thread link. An email follow-up workflow published online suggests logging requests when sent, logging promises when made, keeping a link to the thread, and separating waiting-for items from your own commitments. The link means you never have to hunt for what was actually said.

Capture both directions. Promises made to you go on the waiting-for list. Promises you made go on your action list. Both come out of the same meetings, so it helps to process notes once and sort every commitment into one place or the other.

Two paths sort commitments by who owes the next action

This is where manual systems start to strain. A founder with back-to-back calls and a few hundred emails a day cannot reliably transcribe every commitment by hand. If that is your situation, our guides on tracking emails you are waiting on, post-meeting follow-ups and setting up reply-aware follow-ups in Gmail show how to reduce the manual work.

The weekly review

The list earns its keep in the review. Frequency guidance varies, but the floor is consistent: review at least weekly, and some writers, such as Chris Bailey, suggest looking a few times a week so replies, calls, texts, mail and packages do not slip through. Items with urgent dependencies deserve earlier checks than the weekly rhythm.

Work through the list line by line and ask four questions:

  • Did the result arrive?
  • Do I still need it?
  • Is it time to follow up?
  • Has the owner, scope or check date changed?

Then take one of three actions on each line: cross it off, chase it, or push the date. Nothing stays untouched.

When something does arrive, do not just delete the line. Decide what it unlocks. If the vendor quote came in, the next action might be “compare quote with budget”, and that belongs on your action list before you close the waiting-for entry. Otherwise the project stalls again, this time on your side.

If you want a quick way to surface neglected lines, Frank Buck suggests adding an expected-receipt date and a searchable tag, sorted by due date, so the overdue ones rise to the top.

Following up without being a pest

A list that tells you something is late is only half the job. The other half is the nudge.

Keep it short, specific and friendly. Refer to what you sent and ask whether it is still on track. Reply in the original thread so the other person sees the context without searching for it. A line such as “Checking on the revised proposal I sent on the 3rd. Is Friday still realistic?” does more than a vague “just following up”.

If the date has already passed, ask for a new one. That turns an awkward silence into a fresh commitment you can record. Update the line with what happened and set the next check date.

If one nudge gets no answer, escalate or decide. You can try another channel, involve someone who can unblock the item, or accept that it no longer matters and close it. Closing is a legitimate outcome. If you cancel a request that is no longer needed, tell the other person so they stop working on it.

One caution: the list tracks work, not grudges. Record facts and dates, not judgments about people. It should read like a logbook, not a case file.

For wording you can adapt, see our follow-up templates and AI workflow, and for the broader pattern of catching what slips, our piece on capture, queue and act.

Following up without being a pest — overview diagram

Perspective: the list is a memory problem, not a discipline problem

We build Otto, so we see the same failure again and again. People rarely abandon a waiting-for list because they lack discipline. They abandon it because keeping it current is a second job on top of their real one.

The promises you need to track are scattered. Some live in a meeting you were only half listening to, some in an email thread, some in a calendar invite with a note attached. Each tool sees only its own slice. A notetaker has the meeting but never saw the inbox. An email assistant has the inbox but has no idea what was promised out loud. So you become the integration layer, copying context between apps and holding the connections in your head. That is exactly the job a waiting-for list was supposed to remove.

Our view is that the list should be a byproduct of work, not an extra task. Commitments, whether made by you or to you, should land in one ledger that gets chased until each one closes. And because that ledger sits next to your email, calendar and meetings, it can also tell you each morning what deserves your attention first.

One rule we do not bend: nothing gets sent or finalized without your approval. A follow-up that goes out in your name should be one you chose to send. The software drafts, and you decide.

— Eddie

Where Otto fits

If you keep a manual list and it works, keep it. If you notice that it falls behind whenever your week gets busy, that is the point where Otto helps. It listens in meetings, reads your email and calendar, captures promises into a single ledger, and drafts the follow-ups for your approval.

There is a Free plan at $0 per month, an Upgraded plan at $20 per month, and a Max plan at $50 per month, with higher usage limits and more integrations as you move up. You can see the plans on the Otto site and start on Free.

FAQ

What is the difference between a waiting-for list and a to-do list?

A to-do list holds actions you can take yourself. A waiting-for list holds items where someone else has the next move. Keeping them separate means your to-do list stays actionable and your waiting-for list stays a clean record of what others owe you.

How often should I review my waiting-for list?

At least once a week, as part of your regular review. Some people glance at it a few times a week, which helps when many items have short deadlines. Use earlier check dates for anything that blocks urgent work.

Should I put things I promised other people on this list?

No. Your own commitments belong on your action list or calendar. Keeping the two apart means that when you scan the waiting-for list, everything on it is something you are owed, and you know whom to ask.

What if the person never gives me a date?

Leave the agreed date blank rather than guessing, and set your own check date based on how urgent the item is. When that date arrives, follow up and ask for a specific date. Once they give one, record it.

Can I use a spreadsheet or do I need an app?

A spreadsheet, a notes page or a paper list all work, as long as you open it daily and review it weekly. Software becomes useful when the volume of email and meetings is too high to log by hand, especially if it can see all of those sources in one place.

Sources