Document a weekly planning routine in one short operating record. It should identify the routine's owner, its decision rules, the calendars and task lists it uses, the access settings that matter, and the evidence another person needs to take over.
State the purpose and owner
Begin with the outcome the routine is supposed to create: a committed weekly plan, a team workload review, a household schedule, or something else. Name one accountable owner and one backup. Record when the review happens, which time zone governs it, which week boundary is used, and what event triggers a reschedule.
Describe what is in scope. List the calendars, task boards, inboxes, and reference lists that must be checked. Also list what is deliberately excluded. This prevents a future operator from adding every visible task and turning a focused weekly review into an unbounded cleanup session.
Capture access and sharing settings
For each calendar, record who owns it, who can view details, who can edit, and who can manage sharing. Google's calendar-sharing guidance distinguishes permissions ranging from free/busy visibility to full control over events and sharing. It also notes that work or school administrators may restrict sharing. A handoff record should therefore capture the actual permission level, not merely say that a calendar is “shared.”
For each task plan, record whether it is personal or shared, its group or workspace, and the people assigned to recurring responsibilities. Microsoft's Planner guidance shows that tasks can carry due dates, assignees, progress, descriptions, checklists, attachments, comments, and labels. Decide which of those fields your routine actually uses and define them consistently.
Do not store passwords, recovery codes, or private event details in the operating record. Point to the approved credential manager and identify the role authorized to recover access.
Write the weekly decision rules
Document how work becomes a commitment. For example: collect candidate tasks, confirm fixed appointments, estimate capacity, choose priorities, assign owners, resolve conflicts, and publish the plan. Define what “done” means for the review itself.
Record the rules for overdue work, unassigned tasks, conflicting calendars, and tasks with no clear next action. If a decision requires another person, specify the escalation route and the latest useful response time. Avoid rules such as “use judgment” unless the record also explains the factors that judgment should consider.
Keep a compact decision log
At each review, note the date, participants, material changes, deferred commitments, unresolved conflicts, and owner of each follow-up. Link to the task or calendar item instead of copying changing details into several places. If the routine changes, record the old rule, the new rule, who approved it, and when it should be reviewed.
A useful log explains why a week looks different without becoming a diary. Routine selections do not need narration; exceptions and tradeoffs do.
Test the handoff
Ask the backup owner to perform a dry run using only the operating record and approved access. Check whether that person can find every source, interpret priorities, update the plan, and identify items requiring escalation. Correct the record where the test depended on oral history.
Review the document after ownership, calendar, permission, workspace, or time-zone changes. The result should be a routine that survives an absence because its decisions, settings, and responsibilities are visible and testable.
Sources
- Share Your Calendar — Google
- Build your plan in Microsoft Planner — Microsoft