A weekly planning routine is verified when it still captures the right work, assigns realistic dates, preserves recurring commitments, surfaces unfinished items, and gives you a usable plan for the next week. After changing an app, template, account, calendar, or planning method, do one controlled rehearsal instead of assuming that a clean-looking screen means the process works.
Record the change and protect the old plan
Write down what changed, when it changed, and which lists, calendars, automations, shared spaces, and notification settings may be affected. Save an export or screenshots of the current week if the tool permits it. Do not delete the former setup until the replacement has passed a complete weekly cycle.
Choose a small test set: one normal task, one overdue item, one task with a due date, one recurring commitment, one calendar event, one item delegated to someone else, and one private note. Use recognizable test labels and remove them after the check. Avoid experimenting on an irreplaceable appointment or deadline.
Verify capture and prioritization
Enter one item through every capture route you actually use, such as desktop, phone, email, browser extension, or shared list. Confirm that each item lands in the intended account and list only once. Check its title, notes, due date, reminder, priority, assignee, attachments, and time zone.
If your routine uses Microsoft To Do, Microsoft explains that the My Day list resets nightly, while unfinished entries remain in Tasks and can appear in later suggestions. That behavior makes a useful rollover test: an incomplete item should not disappear merely because the daily focus view resets. Microsoft also says tasks with due dates or reminders appear in the Planned smart list, and repeat options include daily, weekdays, weekly, monthly, yearly, or custom schedules in its due-date and reminder guidance.
Rank the test items, then close and reopen the app. Confirm that order, labels, and filters remain understandable. A view is not verified if it hides overdue or unassigned work without making that filtering obvious.
Test recurrence and calendar behavior
Inspect the next several occurrences of each repeating commitment. Verify the weekday, local time, end condition, reminder, and whether editing one occurrence changed the whole series. Google documents that repeating tasks can be edited as a series and that only a limited number of future instances may appear on the calendar grid at once; additional instances appear over time in its repeating-task guidance. Do not treat a limited preview as proof that later occurrences were deleted.
Compare the task list with the calendar. Reserve time for the highest-priority work, include fixed appointments, and look for double booking or work scheduled outside available hours. Verify reminders on the actual device that must deliver them, because a correct due date does not prove that device notifications are enabled.
Run the weekly review end to end
Perform the routine in the order you intend to use it: empty capture points, review overdue items, examine the previous week, update projects, choose priorities, check calendar capacity, assign next actions, and schedule the next review. Time the rehearsal and note every manual workaround.
The routine passes only if a second person or your future self can tell what matters, what is waiting, what is scheduled, and what has no next action. Record the test date and any limitation. Keep the old setup available until a real week has completed without missing work, duplicates, or silent reminder failures.
Sources
- My Day and suggestions — Microsoft Support
- Add due dates and reminders in Microsoft To Do — Microsoft Support
- Manage repeating tasks in Google Tasks and Google Calendar — Google