A customer email can appear twice in a review if the unread thread and the task both look actionable. Keep one open task with a link to the thread. Put the next action in the task where you can also record its owner.
Set aside a 25-minute review with the task list, the inbox and next week's calendar open. Start with the promises other people are waiting on. Open the calendar last to see where the remaining work fits.
Review overdue, waiting and underspecified work
For overdue work, open each item and decide whether its original deadline still applies. “Reply Friday” can become “send the signed estimate Monday by noon,” with a link to the thread. When a deadline has already passed, tell the person who depends on it and record the new promise in the same place.
For waiting work, add the person or system you are waiting on, the outcome, and a follow-up date. “Waiting for Sam to confirm room access on Thursday” is easy to act on if the reply never arrives. The reminder belongs to whoever will follow up. A handoff app may have a waiting status. A personal list can use one label. Todoist filters can combine labels, dates and other fields for a saved view.
For work without a next action, rewrite the title as a specific step. “Quarterly report” could be a folder containing many tasks. “Export last month's canceled orders” is a task you can estimate and act on. Keep the folder or project reference with the task.
Use the calendar as the capacity check
Look at the following seven days. Transfer time-sensitive commitments onto a calendar or add a dated reminder in the task list. Google Calendar's task controls distinguish a date due from the period reserved to work. For larger jobs, place the first step next to a real available block. If all available blocks are full, change a commitment or ask for help before the review ends.
Close the review by comparing five messages you acted on with the tasks you kept. Each should have an owner, a next action, or a recorded reason it can be closed. A week later, check which of the three passes caught work you would otherwise have missed. That gives you a basis for changing the review length or the filters.
Run the review with a short list
Set the scope before opening your oldest messages. For a small team, a useful review might cover outstanding promises to clients, tasks due before the next review, and items assigned to a person who is away. Put the rest in a project list you can search when needed. A review that starts at the bottom of a year of archived email can use all its time before you discover a job due this afternoon.
For a 25-minute review, spend the first five minutes on deadlines another person is counting on. Give the next eight to work that needs a reply or approval, another seven to unclear tasks, and the last five to the calendar. Change those amounts once you see where your own missed work comes from. If an urgent problem needs investigation, record who will handle it and when. Use the remaining review time to catch other commitments before you investigate the problem.
| What appears in the review | Record to keep | Check later |
|---|---|---|
| A client request with an unread reply and an open task | The task with a link to the original conversation | Does the latest reply change the deliverable or time? |
| A quote outstanding with an outside vendor | A task to follow up, assigned to someone on your team | Can that person see the quote request? |
| A calendar block labelled “Report” | A task with a specific next action and a calendar block when needed | Is there enough time for export, drafting, and review? |
| A finished job missing a confirmation | The obligation to confirm, with its owner and recipient | Is the delivery visible to the recipient? |
Decide where you will update each kind of work
If an email is the only place an external deadline is written, keep the link to it when you capture a task. Preserve the original wording for deadlines that may be disputed. The task can carry your next action. It might say “Ask Maya to confirm the corrected shipping total.” If Maya accepts Tuesday at noon, update the task and record her reply in the source conversation. Moving a personal reminder alone tells her nothing. For projects where teammates need to see the new commitment, update the shared record that they actually consult.
Make the return path work too. Calendar blocks often become detached from the task after someone changes the start time. Open the block and try to locate the actual action within a few seconds. A link or a short unique project identifier is enough when a detailed task already exists. An external guest may have no access to that task, so put information they need in the invite and keep team notes in the shared system. If you repeatedly have to search both places, fix the link when you spot it.
Check saved views with a known example
Create a test task with your waiting label and a follow-up date in the past. Use the view you intend to open on Friday and verify that it finds the task. Change only its date to next week. It should move out of an overdue view but still appear in a view for waiting work. Ask a teammate to try the filters in their own account if the view depends on assignment or a shared project. Record the filter purpose in a short note, so the owner can test the right behavior when changing it.
A saved search sees what you put into the fields it reads. If a promise is buried only in an email or a comment, make its follow-up explicit before expecting it in a dated view. Run the same check after a holiday or a new project handoff. When several small personal reminders make the calendar hard to scan, start with the rollover rules for recurring tasks and keep just the next work period in your calendar.



