A digital task list can collect years of good intentions. An annual review should make the system easier to trust, not simply delete everything that looks old. Preserve history first, distinguish active commitments from reference material, and make changes in small batches.
1. Inventory lists and owners
Record each list, its purpose, owner, collaborators, and whether it is active, reference-only, shared, or ready for later archival. Include smart lists and tasks created by integrations. Microsoft documents that To Do can show Planner assignments and Outlook tasks, so the visible list may combine records from more than one source. Identify that source before editing an item.
2. Review overdue and undated tasks
Sort or filter for overdue tasks, tasks without dates, and tasks with no clear next action. Sample the oldest items and decide whether each is an active commitment, delegated work, reference note, or abandoned idea. Do not infer completion from age. Record items that need an owner decision rather than bulk-deleting them.
3. Inspect recurring tasks
Check the next due date, recurrence rule, time zone, owner, and notification for recurring items. Confirm that the task still represents a real obligation. Google notes that tasks can recur and that tasks with subtasks cannot repeat, so a complex routine may need a different structure than a single repeating parent task. Test one harmless recurrence rather than changing every series at once.
4. Verify reminders and daily views
Review tasks with due dates, reminders, priorities, and calendar visibility. Google documents that dated tasks can appear in Calendar and that notifications depend on date and time settings. Microsoft explains that My Day is a focus view while tasks remain stored in their underlying lists. A clean daily view therefore does not prove that the backlog is clean.
5. Review sharing and connected accounts
Confirm collaborators, shared-list links, work or school ownership, and connected apps. Note any account that no longer belongs to the team. Do not remove access during the review without approval; a shared task may be the only remaining record of a handoff. Record the proposed change and the person responsible for confirming it.
6. Export a representative sample
Use the provider's documented export route and inspect the archive. Google says a Tasks export can include titles, descriptions, due dates, completed and creation timestamps, recurrence, IDs, source information, and list metadata, but deleted user data cannot be exported. That makes pre-cleanup export especially important. Verify that a sample task and completed task appear as expected.
7. Make bounded cleanup decisions
Create a short queue for archive, clarify, reassign, reschedule, or delete. Handle one list at a time and preserve evidence before bulk actions. Microsoft provides a confirmation setting for task deletion and documents a recovery path for some To Do tasks through Outlook, but that should not be treated as a substitute for a controlled cleanup.
8. Record the annual result
Save the review date, account, lists checked, source integrations, export location, recurring-task issues, notification test, collaborators, cleanup decisions, unresolved items, and next review date. The goal is a task system whose active commitments are understandable and whose historical record is not accidentally destroyed.
Sources
- Export your data from Google Tasks — Google Calendar Help
- Add or edit a task — Google Tasks Help
- See Planner tasks in Microsoft To Do — Microsoft Support
- Create, edit, delete, and restore tasks — Microsoft Support