Calendar Control

A calendar is a record of what other people have asked for unless its owner sets rules for it. Calendar Control audits the current calendar, sets default rules, and gives the user words for saying no. It is personal: it covers one person's time, not a team's meeting policy.

Input required

• The last two to four weeks of the calendar, as a list or a description (no need to share private details; categories are enough).
• Role and goals: what outcomes the user is judged on or wants.
• Who can book them: manager, clients, colleagues, family; whether they have a booking link or an assistant.
• Calendar tool in use, so settings are described in its terms.
• Constraints: fixed commitments, time zones, caring duties.

Questions to ask first

Ask in one batch of at most five questions, skipping any already answered:

1. What work or life outcome gets squeezed out by your calendar today?
2. Which recurring meetings could you shorten, skip, or drop?
3. When do you do your best focused work, and how long can you hold it?
4. Who can add events to your calendar without asking?
5. Whom is it hardest for you to decline, and why?

Method

1. Audit. Sort a few weeks of events into categories: focus work, meetings you run, meetings you attend, admin, travel, personal. Total the hours by category and mark each meeting keep, shrink, or drop. Flag back-to-back runs and days with no unbooked block.
2. Set default lengths. Change the calendar's default event length to a shorter one, for example 25 or 50 minutes instead of 30 or 60. Treat these as starting defaults; adjust to the user's work.
3. Add focus blocks. Place recurring blocks at the user's best hours, named for the outcome ("Draft report"), set to busy, and guarded from invitations where the tool allows it.
4. Add buffers. Leave gaps before and after meetings for travel, notes, and a break. Protect a lunch slot and a shutdown slot.
5. Set booking rules. Decide who may book, in which windows, and how much notice is required. Consider a booking link limited to certain days.
6. Prepare declines. Use the scripts below; offer an alternative instead of a bare no where that is honest.
7. Review weekly. Spend five minutes each week removing, renaming, and moving events. Re-audit monthly or after a role change.

Decline scripts

| Case | Wording | |---|---| | No agenda | "Could you send the agenda or decision needed? I'll decide then." | | Not needed | "I don't think I add value there. Please send me the notes." | | Too long | "I can do 25 minutes. Will that work?" | | Clash with focus time | "I'm booked then. Thursday morning is free." | | Good idea, no capacity | "I can't take that on now. I can revisit next month." |

Output format

• Audit table: category, weekly hours, keep/shrink/drop decisions.
• Calendar rules: defaults, focus blocks, buffers, booking windows.
• Concrete edits for this week, listed in order.
• Two or three decline drafts tailored to the user's real cases.
• Weekly review checklist of five items.

Ground rules

• Never decline, delete, or accept events on the user's behalf without explicit approval for each one.
• Do not paste meeting contents or private details into outputs beyond what the user supplied.
• Do not propose defying a manager's explicit request; offer a conversation instead.
• Name tools only as examples; settings differ by product.
• Respect time zones and caring or health commitments.

Self-check before answering

• Did I base the plan on actual calendar data, not a generic ideal?
• Are focus blocks at the user's best hours, and named for an outcome?
• Are there buffers, and a lunch and shutdown slot?
• Do the decline scripts match how the user actually speaks?

Common pitfalls

• Focus blocks nobody respects: unnamed or left as "free", then filled by invitations.
• Buffers eaten in a week: add a rule about what may enter them.
• Over-declining: dropping meetings that build relationships or carry decisions.
• Audit without action: a report but no changed defaults.
• Moving the problem: shortening meetings while adding more.
• Ignoring other calendars: family and personal events belong on the same view.

Example prompt

Audit my calendar for the last three weeks. I'm in back-to-back meetings and never get focused work done. Set default meeting lengths, focus blocks, and buffers, and draft how I can decline status meetings politely.

Learn more

• Ideal Week System to design the template week the calendar then protects.
• Weekly Planning Meeting for the team version of weekly planning.
• Focus Blocker for guarding focus blocks against digital distraction.
• Tomorrow Setup for checking and preparing tomorrow each evening.