Use one task row with the expected result, owner, due time, current state and closure check. Reassign absent owners explicitly, preserve original commitments when blocked, and reopen tasks when acceptance fails.
Turn “please check” into a clear task
A useful follow-up names the result, not merely the activity. “Send the bill copy” is different from “confirm the customer received bill B-22.” “Call for payment” is different from “record the customer’s answer and next commitment.”
| Expected result | Owner and due time | State | Next check or blocker | Closure check |
|---|---|---|---|---|
| Customer receives bill B-22 | Meera · 11:00 | Done pending acceptance | Customer reply expected | Delivery or customer acknowledgement |
| Payment date recorded for B-22 | Ravi · 15:00 | Blocked | Customer’s accounts person unavailable; check 16:30 | Named date or recorded refusal/no commitment |
| Dispatch approval for order O-18 | Asha · 13:00 | Closed | None | Approver and time recorded |
Sending a document can be complete while payment collection remains open. Keep them as separate tasks when they have different owners, evidence or due times.
Make the handover survive an absence
- Assign a new owner by name.
- Keep the original owner and reassignment time in history.
- Require the new owner to acknowledge the task and context.
- Carry forward the source documents, last reply, due time and next action.
- Escalate if no eligible owner accepts before the task’s decision deadline.
A task is not reassigned because it appears in a group chat. Someone must accept responsibility.
Keep blocked work honest
When an external reply blocks progress, retain the original due time. Add the blocker, next check and any revised commitment approved by the relevant owner. Repeatedly replacing the due date hides how long the task has been blocked.
| Field | Fictional entry |
|---|---|
| Original due time | 22 Sep, 15:00 |
| Blocker | Customer accounts contact unavailable |
| Next check | 22 Sep, 16:30 |
| Approved revised commitment | 23 Sep, 11:00, agreed by Ravi |
Close with evidence and acceptance
Match the closure check to the task. A sent-message timestamp may prove sending, but it does not prove receipt, approval or payment. Record who accepted completion and when. If acceptance fails, reopen the task with the reason; do not erase the earlier attempt.
This board is an original proposed workflow, not a research-proven productivity system or an automatic Dhandha GPT delegation feature. Adapt approvals and evidence to the consequence of each task.
Tell us one report or follow-up question you need from your existing software. Do not include customer records in the enquiry.
Questions you might ask
What should a daily follow-up tracker contain?
Record the expected result, owner, due time, current state, blocker or next check, and the evidence required for closure.
How should a task be handed over when someone is absent?
Name the new owner, preserve history and context, and require acknowledgement. Escalate if nobody accepts before the decision deadline.
When is a follow-up task complete?
When the task-specific evidence is present and the appropriate person accepts it. Reopen it with a reason if that acceptance fails.