How to track follow-ups without keeping them in your head
By OS for You · September 11, 2026
Track a follow-up as a commitment you are waiting on, not just a reminder to check your email. Write who has the next move, what you expect, and when you will look again. That gives every handoff a place to return to.
Write down the expected outcome
‘Alex’ is not a complete follow-up. ‘Alex to approve the revised proposal’ tells you what would close the loop. Link it to the project it supports so you can see why it matters.
Choose a follow-up date, not an invented deadline
If Alex promised Tuesday, record that commitment. If no date was agreed, choose a reasonable day to check in. Keep your reminder to follow up distinct from a deadline the other person actually accepted.
Separate your action from their action
If you still need to send the proposal, that belongs on your next-action list. Once you send it, create the waiting-for item. This separation keeps you from waiting for a reply to a message you have not sent.
Close the handoff when the answer arrives
Record the result, close the waiting-for item, and decide what comes next. If the reply only resolves part of the request, update the expected outcome. Keep the unfinished part explicit instead of marking everything complete.
Review the list as a whole
Look at due follow-ups during your daily check and review all open handoffs weekly. Several overdue commitments from one person may call for a conversation about priorities rather than another sequence of reminders.
Your working checklist
- Person: Alex
- Expected result: approved proposal
- Requested: Monday
- Follow up: Thursday
- Related project: new client launch
- Close when: approval is received and recorded
Put it into practice
OS for You keeps waiting-for items alongside your projects and next actions. The value comes from making the commitment visible and reviewing it regularly. It does not guarantee someone else will respond.
Create your workspace