You send a request, delegate a task or ask for approval. The next step now belongs to someone else, so you remove it from your task list. Three days later, you suddenly remember it while doing unrelated work. You search email, check chat and wonder whether you should follow up yet.
This is not a memory problem. It is a tracking problem. Ordinary task lists are good at showing what you need to do, but they are often poor at showing what you are waiting for from other people. A waiting-for list gives those open loops a reliable home.
The system is simple: whenever progress depends on another person, record the commitment, owner, expected date and next follow-up point in one place. Then review that list on a predictable rhythm instead of carrying every promise in your head.
What belongs on a waiting-for list
A waiting-for item is work that matters to you but cannot move until someone else responds, delivers, approves or decides. Common examples include:
- A manager’s approval on a proposal.
- Figures promised by Finance for a report.
- A customer’s answer to a contract question.
- A colleague’s draft for a shared presentation.
- A vendor’s revised quotation.
- A decision from a meeting that was deferred pending more information.
- A task you delegated and still need to verify.
Do not add every message you send. Add only the items where silence would create a real problem: a missed deadline, blocked work, an unprepared meeting or a commitment that could quietly disappear.
Use six fields, not a complicated project board
You can maintain the list in a spreadsheet, notes app, task manager or project tool. The software matters less than the fields. Each entry should answer six questions:
- What am I waiting for? State the deliverable or decision, not just the topic.
- Who owns the next move? Name one person whenever possible.
- When was it requested? Record the date so you can judge how long it has been open.
- When is it expected? Use an agreed deadline or a reasonable review date.
- What is blocked? Note the consequence so you know which items deserve attention first.
- When will I follow up? Decide this in advance rather than reacting to anxiety.
A clean entry might read:
Revised customer pricing table
Owner: Marcus
Requested: August 3
Expected: August 5 at noon
Blocks: Proposal review on August 5
Follow up: August 5 at 10:00 if not received
The expected date and follow-up date do not need to be identical. Set the reminder around the real consequence, not merely the promised delivery time.
Capture the item at the moment responsibility moves
The most important habit is not reviewing the list. It is adding an item whenever ownership shifts away from you.
Useful capture moments include:
- Immediately after sending a request that blocks your work.
- When a meeting ends with another person owning an action.
- When you delegate a task.
- When somebody says, “I’ll get back to you.”
- When an approval moves into another department.
A clear meeting recap that records actions, owners and deadlines makes this much easier. Copy the actions that depend on other people into your waiting-for list before closing the notes.
Capture should take less than a minute. If the system requires opening several screens or filling fifteen fields, you will skip it during busy days. Keep the entry short and link back to the source email, document or meeting note when more context is needed.
Separate “waiting” from “next action”
A common mistake is moving the entire responsibility to the other person. You may be waiting for their input, but you still own the follow-up and the final outcome.
For example, “Waiting for Legal” is not a complete plan. Your next action may be:
- Follow up Thursday morning if no response arrives.
- Prepare the unaffected sections while the clause is reviewed.
- Tell the project lead by Friday if approval is still outstanding.
Your task list should contain your next action. Your waiting-for list should contain the dependency. The two lists work together.
This distinction is particularly useful when you are coordinating across teams without formal authority. The approach in managing a project when you are not anyone’s boss relies on visible ownership and shared facts rather than repeated personal pressure.
Review the list at two speeds
Not every waiting item needs daily attention. Use two review rhythms.
A quick daily scan
Spend one or two minutes checking items that are due today, overdue or blocking a current priority. This can sit beside your five-minute daily planning routine.
During the scan, ask:
- Is anything due before my next review?
- Has a response arrived that I have not processed?
- Does a blocked item now threaten today’s work?
- Do I need to communicate a risk before it becomes urgent?
A fuller weekly review
Once a week, examine every open item. Close completed entries, update dates, identify stale commitments and decide whether each dependency still matters. A weekly review that stays under 30 minutes is a natural place to do this.
The weekly review catches quiet problems: a request with no deadline, an owner who never confirmed, or a deliverable that is no longer needed. It also prevents the list from becoming a graveyard of old promises.
Follow up from the agreement, not from frustration
A useful follow-up refers to the commitment and explains the next consequence. It does not accuse the other person or hide behind “just checking in.”
Use a structure like this:
Hi Priya — following up on the revised figures we agreed for Tuesday. I need them to complete the client deck before tomorrow’s review. Are you still able to send them by 3:00 today, or should I adjust the deck and flag the missing section?
This message does four things: names the deliverable, refers to the agreed timing, explains why it matters and offers a practical next step.
When there was no agreed deadline, avoid pretending that one existed. Write:
Hi Daniel — I’m planning the next stage of the onboarding update and need your confirmation on the access rules. What would be a realistic time for your review? Thursday afternoon would keep the current timeline intact.
A waiting-for list improves the tone of these messages because you are responding to recorded facts, not a vague sense that someone has taken too long.
Escalate only after making the dependency visible
Some items will remain blocked despite a clear request and reasonable follow-up. Before escalating, confirm that the owner understands the request, timing and consequence. Then escalate the work, not the person.
A constructive escalation might say:
The launch checklist is still waiting on security approval, originally expected August 5. Without that approval, testing cannot start on August 6. We need either a confirmed review time today or a decision to move the testing date.
This gives a manager something they can act on. It is more useful than “Security is not responding.”
Also consider whether the request itself is vague. A specific question produces a faster answer than a general request for an update. The same principle behind asking smart questions in meetings applies here: give context, ask for a defined answer and explain the decision it supports.
Common waiting-for list mistakes
Recording topics instead of deliverables. “Budget” tells you very little. “Approved Q4 budget ceiling from Lena” is actionable.
Leaving out the expected date. Without a date, every item feels equally uncertain and you cannot tell when to follow up.
Tracking too much. Routine messages that do not affect your work do not need an entry.
Using the list as a substitute for communication. Recording a dependency does not make the owner aware of it. Confirm the request directly.
Reviewing only when anxious. A predictable daily and weekly rhythm is what allows you to stop mentally checking the list.
Keeping completed items open. Close or archive them promptly. A short, trustworthy list is easier to use than a comprehensive but stale one.
A simple template you can start today
Create one table with these columns:
Item | Owner | Requested | Expected | Blocks | Follow-up date | Source link | Status
Add the three to ten dependencies that would cause a problem if forgotten. Do not reconstruct every old request. Start with what is active now.
Then put two recurring reviews on your calendar: a two-minute scan near the start of each workday and a ten-minute cleanup during your weekly review. After a week, adjust the fields only if you repeatedly need information that is missing.
Stop using memory as a follow-up system
Reliable follow-up is not about remembering more or sending more reminders. It is about creating one trusted place for work that has temporarily moved into someone else’s hands.
Capture the commitment when ownership shifts. Record the expected date and consequence. Decide the follow-up point in advance. Review urgent items daily and the full list weekly. When you need to follow up, refer to the agreement and the next decision.
Once the system is trusted, you can stop rehearsing every open request in your head. The work is still visible, but it no longer has to stay mentally active all day.