When a weekly planning routine stops working, separate the failure into layers: the event or task, its owning account, synchronization, visibility, notification settings, and the device that should display it. A change log lets you test those layers in order. Begin by recording the date, device, app version, account, calendar or list name, time zone, exact symptom, and last known-good event. Use a harmless test event rather than editing a real appointment.
Define the symptom precisely
“Calendar is broken” is not actionable. Record whether an event is missing, appears on one device only, has the wrong time, lacks a notification, is stored in the wrong calendar, or repeats incorrectly. Check the web version first when available and write down whether the item exists there. If it does, the account's server copy may be intact and the investigation can focus on visibility, sync, or notification layers.
Google's Calendar sync guidance starts with connectivity and app updates, then checks whether the calendar is visible, whether the event was created in the intended Google account, and whether account sync is enabled: https://support.google.com/calendar/answer/6261951?hl=en-7. It also notes that a device without available storage can stop syncing. Record the result of each check before changing the next setting.
Track each change and its result
Use one row per action: timestamp, device, account, setting before, setting after, reason, expected result, actual result, and rollback. Refresh or sync, then wait a defined interval before judging the result. Avoid changing the default calendar, notification permissions, sync window, and app storage at the same time. Multiple simultaneous changes hide the cause and can create a second problem.
Treat clear-storage or reset steps as late-stage actions. Google warns that clearing Calendar app data can remove unsynced event information that is not visible in Google Calendar on a computer. Confirm the web copy and export critical calendar data before considering that step.
Separate sync from notifications
An event can synchronize correctly and still fail to alert. Google recommends checking the event's own notification, the calendar's notification settings, browser permissions, and operating-system notification settings: https://support.google.com/calendar/answer/12200012?hl=en. Put those checks in a notification-specific section of the log. Record focus or quiet modes and whether the browser or app was allowed to notify.
For iCloud Calendar, Apple recommends checking service status, confirming that every device uses the same Apple Account, verifying that Calendars is enabled, checking date and time, and confirming that the intended calendars are visible: https://support.apple.com/en-lb/102543. These checks illustrate why account, device, visibility, and time-zone details belong in the record.
Close and preserve the case
After the test event appears and its notification fires, repeat the check on every device used in the weekly review. Record the root cause if confirmed, the retained setting, any temporary workaround, and who owns follow-up. Remove only the disposable test item. Keep the change log outside the calendar system so it remains available if the planning account fails again. The goal is not just to restore one event, but to leave a reproducible path that prevents the same hidden setting from disrupting another week.
Sources
- Fix sync problems with the Google Calendar app — Google Calendar Help
- Troubleshoot missing Google Calendar notifications — Google Calendar Help
- If your iCloud Contacts, Calendars, or Reminders won't sync — Apple Support