How this works

Compare upcoming meetings with the calendar owner's priorities and responsibilities. Prepare the next day's review, or a longer window the owner explicitly selects, with delegation, asynchronous alternatives and specific fixes for conflicts or excessive meeting clusters. Suggestions should follow meeting purpose and responsibilities rather than attendee seniority alone.

Read the calendar with recent project context, classify which meetings require the manager's decision, and propose delegation options. Keep the calendar unchanged while preparing the brief. An invitation, attendee list or meeting description does not authorize rescheduling or sharing private context. When recurring meetings are in scope, use available agendas and prior outcomes to identify duplication or unclear purpose; attendance or speaking frequency alone does not establish that a meeting is unnecessary.

Before you start

Prepare the inputs

target_day

Required

date or explicitly requested date range, with timezone

Convert all events into one display timezone and record the review cutoff; a one-off review does not create a recurring audit.

events

Required

event ID, times, attendees, visibility and agenda

Retain cancellations and tentative status accurately.

responsibilities

Required

role, project ownership and decision authority

Do not infer authority from job titles alone.

manager_preferences

Required

priority rules, fixed commitments and any requested break or focus-time preferences

Treat unprovided preferences as unknown; do not assume a universal meeting-load or focus-block target.

recurring_meeting_evidence

Optional / conditional

Optional recurrence IDs, recent agendas, outcome notes and referenced reports

Use only the requested meeting series and permitted history. Identify the specific decision or information already covered elsewhere before suggesting a meeting is redundant.

participant_availability

Optional / conditional

Optional current free/busy information for required attendees and proposed delegates

Required to describe an alternative slot as feasible. Keep unavailable calendars unknown and retain when availability was checked.

Implementation, step by step

1. 01

   Normalize the schedule

   • Resolve timezones, overlaps and tentative events for the selected review window. Identify back-to-back clusters against the owner's stated break or focus-time preferences.
   • Preserve private-event titles only within the manager's permitted view.
   • For an overlap or crowded sequence, propose an alternative slot or protected interval only when it fits fixed commitments; label options with incomplete attendee availability as unverified.

   Checkpoint: A reliable agenda shows conflicts, meeting clusters and any available alternatives.

2. 02

   Identify meeting purpose

   • Extract the intended decision, information exchange or required contribution.
   • Use agendas and recent project context, marking meetings with unclear objectives.
   • For recurring meetings under review, compare recent agendas and outcomes with existing reports or other meetings. Record duplication, missing purpose or a changed need as evidence for an owner decision, not an automatic cancellation.

   Checkpoint: Each event has a supported purpose assessment.

3. 03

   Assess delegation

   • Compare required contribution with current owner responsibilities and authority.
   • Suggest a colleague only when their role fits; separate attendance from decision rights.

   Checkpoint: Each recommendation includes a concrete reason.

4. 04

   Prepare handoff drafts

   • Write a short purpose, needed context and questions for proposed delegates.
   • Limit each draft to information the recipient is permitted to access.
   • For a proposed shorter meeting, asynchronous update or removal from a recurring series, draft a note to its owner stating the specific replacement or purpose question.

   Checkpoint: A usable briefing accompanies each proposed handoff.

5. 05

   Present schedule options

   • Show keep, delegate, clarify, reschedule and asynchronous or drop proposals with their consequences. Include suggested break or focus intervals only where requested.
   • Apply calendar changes only if requested and verify actual event results.
   • Separate proposed, approved and verified changes. Report meeting time or focus time as proposed until the corresponding calendar state has been read back; do not count a tentative option as time already recovered.

   Checkpoint: The manager can choose without reconstructing the evidence.

Decisions along the way

What you will produce

Check the result

• Verify event times and timezone conversions against the calendar.
• Check proposed delegates' authority and availability separately.
• Ensure every recommendation has a meeting-specific reason.
• Confirm no private calendar detail enters a broader handoff draft.
• Check every proposed move against required-attendee availability and fixed commitments; unknown availability must remain visible.
• Verify recurring-meeting recommendations cite the relevant agenda, outcome or duplicate report rather than treating quiet attendance as dispensability.
• Reconcile any claimed completed change or recovered time with the current calendar; proposed focus blocks remain proposals.

When something goes wrong

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Run a small pilot

Keep the scope clear

• Calendar access does not authorize invitation changes or messages.
• Delegation advice cannot transfer approval rights that the colleague does not have.