A weekly planning incident is any failure that makes the plan unreliable: events disappear, tasks are deleted, recurring commitments duplicate, two devices disagree, or an account change hides important work. Respond by preserving the current state, identifying the authoritative copy, restoring only what can be verified, and recording every correction.
Open a record outside the affected tool
Write the discovery time, devices, accounts, calendars or task lists involved, the last known good review, and the exact symptom. List commitments that may be affected, but separate confirmed omissions from suspicions. Capture sync messages and sharing settings without copying unrelated private details. Ask anyone who edits the same plan to pause changes until the scope is understood.
Preserve before repairing
Export whatever still exists before bulk edits. Google's Calendar export guidance says a user can export all calendars or one calendar from a computer as `.ics` files. It also notes that the user needs the relevant sharing permission and that an organization administrator can restrict export. Save the export with a timestamp and account label. A file created after the incident is evidence of the current state, not proof of what existed earlier.
For task lists, use the product's supported archive or print route when available. Do not clear trash, merge duplicate series, or re-import a full calendar until a copy has been made and a small restoration has been tested.
Check recovery locations
Google's deleted-event guidance says deleted events normally remain in that calendar's trash for 30 days and can be restored from a computer. The same page warns that some recurring-event deletion choices are not moved to trash and cannot be restored there. Check the trash for each calendar separately and confirm that the reviewer has edit access. Record the original calendar, event owner, recurrence rule, and deletion time before restoring.
If the routine uses Microsoft To Do, Microsoft's task recovery instructions explain that deleted tasks can be recovered through Outlook's Deleted Items because To Do tasks are stored in Exchange Online. Use this as a product-specific recovery route, not as a guarantee for another task service.
Find the authoritative version
Compare the web version, each authorized device, the export, and any human notes from the last weekly review. Check event IDs, owners, time zones, recurrence settings, due dates, and completion states. A recently modified copy is not automatically correct. Name one source as authoritative for each disputed item and record why, such as the organizer's event or a timestamped client confirmation.
Restore in small batches
Recover one representative event or task, verify its owner, time zone, recurrence, guests, and notifications, then confirm that it appears correctly on another device. Restore the remaining verified items only after that test. Avoid importing a full archive into the main calendar without checking whether it will create duplicates or omit details. When a commitment cannot be confirmed, put it on a review list instead of silently recreating it.
Rebuild the week and close the incident
Compare the corrected plan with email confirmations, meeting invitations, project deadlines, and the previous review notes. Contact affected people when a missed or duplicate commitment could change their plans. Close the record with the cause if known, items restored, unresolved gaps, people notified, and the date of the next verification.
Reduce recurrence by naming a primary calendar and task list, documenting which accounts may edit them, exporting on a sensible schedule, and testing one small recovery periodically. The useful result is not merely a repaired screen; it is a plan whose commitments can be traced to an owner and verified source.
Sources
- Export events from your Google Calendar — Google Calendar Help
- Delete an event — Google Calendar Help
- Create, edit, delete, and restore tasks — Microsoft Support