Record more than a person's name
“Waiting for Ms Weber” explains little. State what information is expected and why it is needed. Perhaps a confirmed quantity is missing before an internal order can be prepared. Add the last contact and a reference to the relevant message where the system allows.
Separate promised responses from requests without an agreement. For a promised answer, refer to the agreed date. Without a commitment, first establish whether and when the other person can provide the contribution.
Choose the next review point
A daily check is not useful for every case. Match timing to urgency and dependency. If other work can continue meanwhile, a later review may be sufficient. If a deadline depends directly on the answer, it needs earlier attention.
A reminder should lead to a decision: has the response arrived, is follow-up needed or must the plan change? Avoid reminders that are merely postponed repeatedly. The task then stays visible while its bottleneck remains untouched.
Return incoming information to the workflow
Check whether the response actually resolves the required question. A new message is not automatically a complete result. If something remains missing, update the waiting entry with the precise gap. Otherwise, move your next action into normal task planning.
Close completed waiting items so the list remains manageable. Keep the substantive context where the case is documented. The waiting list need not become a second complete file. Its purpose is to make the transition between another person's contribution and your own continued work reliably visible, including when someone else covers the list during an absence.
Describe the missing response so action remains possible
Instead of “waiting for purchasing”, record: “Available quantity requested; final room allocation depends on the answer; follow up on Thursday.” This identifies the missing contribution, its consequence and the next action you control. The task remains with its owner even when the immediate input sits elsewhere.
Where several answers are missing, distinguish essential prerequisites from additional information. A draft may be possible while final confirmation must wait. A blanket waiting label could conceal work that can already proceed.
When repeated reminders fail, check whether the original request was understandable and reached the right person. More reminders do not resolve an unclear question. State the information needed and why the timing matters; if the delay continues, agree a decision about scope or schedule. Record that decision alongside the dependency so the next reviewer sees the current arrangement instead of an obsolete expectation.
Keep the agreed follow-up date with the case so it does not also need to be maintained in a private reminder list.
