A follow-up system for delegated work: the waiting-for list
The field-house project manager remembers asking for a supplier confirmation but cannot find whether the coordinator received the task or when the answer was expected. Her procurement review is approaching. A note saying chase supplier does not distinguish an assigned action from a requested or conditional contribution.
Keep a personal view of contributions you are waiting for, linked to the records that control them. Include the received task or request, accurate timing and the work that depends on the return. A waiting list supports follow-up; it does not guarantee delivery or replace the shared issue, procurement or design process. A promised date also does not mean you must ignore a changed consequence until that date passes.
Give every expected return an accurate status
- Capture the received arrangement. Identify the contribution, person, source reference, intended receiver and agreed return or confirmation point. Distinguish a task accepted by your coordinator from an external request still awaiting acknowledgement. Record conditional promises as conditional. The phrase asked on Monday tells you when you sent something, not whether the other person received responsibility or confirmed the proposed timing.
- Connect the return to its real need. Identify when you and any following recipient need the information, including preparation or review. Check whether the agreed timing fits that need. Set a suitable follow-up point from the actual consequence and prerequisites. Do not invent one chase date for every task or discover that a timely return still arrives too late for the next person's contribution.
- Review open returns at useful intervals. Check received results, approaching needs and conditions that changed since assignment. Ask a specific status question through the appropriate route and provide missing help where agreed. Act earlier when a material consequence requires it. A routine list review should not delay an urgent response, and repeated messages without a clear question or receiver do not establish progress.
- Close or change the entry with evidence. Link the actual return and assess whether it answers the assigned contribution; a partial response may leave another action. Record any received timing change and notify affected people. Retain required project records rather than deleting their history from your notebook. Close your waiting entry when your receiving task is resolved, not merely because someone sent a document.
Common mistakes
- Recording a sent request as an accepted assignment.
- Tracking the promise without the following receiving need.
- Waiting for a chase date despite a changed consequence.
- Closing an entry when a partial document arrives.
Checklist
An expected-return entry includes
- The specific contribution and linked source.
- Received responsibility or explicit pending acknowledgement.
- Promised timing, conditions and actual needed date.
- A suitable review point and earlier exception route.
- Actual return, remaining action or received timing change.
Check your understanding
The coordinator's promised return is Wednesday, but a Monday update shows the supplier cannot answer before Friday. Should you wait until Wednesday to follow up?
