Calendar Audit SKILL.md

This is the exact file agents read, including the credit header and licence notice. Save it as calendar-audit/SKILL.md.

---
name: calendar-audit
description: "Audit a calendar and design a better week: time by category over four weeks, meeting load and fragmentation, a keep, shorten, reduce, async, delegate or leave decision for every recurring meeting, meeting and focus windows, acceptance rules, polite messages to organisers and a four-week review. Use whenever someone has too many meetings, no time for important work, a calendar that fills itself, starts a new role, wants fewer recurring meetings or wants to redesign their working week."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/productivity/meetings-calendar/calendar-audit/
  category: productivity
  subcategory: meetings-calendar
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-13"
---

# Calendar Audit

Calendars fill themselves. Recurring meetings outlive their purpose, invitations are accepted by default, gaps between meetings shrink to nothing and the work that matters happens in the evening. Microsoft's Work Trend Index has reported that people spend more of their working time communicating (meetings, email and chat) than creating, and that unproductive meetings are a common complaint. [Reported, Microsoft Work Trend Index 2023] Shopify drew attention in 2023 when it removed recurring meetings with more than two people from calendars to reset how time was used. [Reported, Shopify 2023]

This skill audits a calendar: where time goes by category, meeting load and fragmentation, recurring meetings worth keeping, shortening or ending, meetings to decline or delegate, missing focus time and personal time, and a new calendar design with protected blocks, meeting windows and rules for accepting invitations.

## Operating principles
1. **Measure the last month.** Real data beats impressions of how busy the week feels.
2. **Every recurring meeting earns its place.** Keep, shorten, reduce frequency, make async or end.
3. **Protect the work, not just the meetings.** Focus time and breaks go in the calendar first.
4. **Decline politely and specifically.** Offer alternatives such as written input.
5. **Design the week.** Meeting windows and focus windows, not random placement.

## Categories
| Category | Examples |
|---|---|
| Recurring internal | Team meetings, stand-ups, one-to-ones |
| Ad hoc internal | Project discussions, reviews |
| External | Clients, partners, candidates |
| Focus blocks | Deep work, writing, analysis |
| Admin | Email, expenses, planning |
| Personal | Breaks, exercise, family, appointments |

## When to use, and when not to
Use it when the week is full of meetings, there is no time for important work, someone starts a new role or gets promoted, a team wants fewer meetings, or at the start of a quarter.

Don't use it to schedule one meeting across time zones (`scheduling-time-zones`) or to write agendas (`meeting-agenda`).

## Inputs
- Calendar access or an export for the last four weeks and the next two.
- Role, priorities and goals for the quarter.
- Meetings the user must attend (non-negotiable).
- Energy pattern and working hours, including time zones of colleagues.

## Workflow

### Step 1. Measure
Hours per category per week, number of meetings, average length, longest stretch without a break and number of focus blocks over 90 minutes.

### Step 2. List recurring meetings
For each: purpose, frequency, length, attendees, the user's role, and whether it led to decisions or useful information in the last month.

### Step 3. Decide on each
Keep, shorten, reduce frequency, switch to a written update, delegate, or leave.

### Step 4. Review ad hoc patterns
Who books the user most, which meetings had no agenda, which could have been an email.

### Step 5. Design the week
Meeting windows (for example, afternoons), focus blocks in high-energy hours, admin blocks, buffers between meetings, and protected personal time.

### Step 6. Set acceptance rules
Accept when there is a clear agenda, a role for the user and a decision or contribution needed; otherwise ask for the purpose, propose written input or decline.

### Step 7. Draft the messages
Polite notes to organisers about leaving, shortening or changing meetings.

### Step 8. Review in four weeks
Compare hours in meetings and focus time with the baseline.

## Audit summary template
```
Last 4 weeks (average per week)
Meetings: 24 hours (31 meetings, average 46 min)
Focus blocks 90+ min: 1
Longest stretch without a break: 4.5 hours
Recurring meetings: 12 (keep 5, shorten 3, async 2, leave 2)
Hours freed: about 7 per week
```

## Decline and change messages
**Leaving a recurring meeting**
```
Hi <name>, I'm reviewing my calendar to protect time for <priority>.
I'll step out of <meeting> from next week and read the notes instead.
If a topic needs me, please add it and I'll join for that item.
```
**Asking for an agenda**
```
Hi <name>, happy to help. Could you share the goal for this meeting?
If it's an update, I can send my input in writing.
```
**Shortening**
```
Could we try 25 minutes instead of 60 for the next month, with a
pre-read? If it doesn't work, we'll switch back.
```

## Output format
```
1. Time by category (last 4 weeks)
2. Recurring meeting table with decisions
3. Ad hoc patterns and booking sources
4. New weekly calendar design
5. Acceptance rules
6. Draft messages to organisers
7. Four-week review measures
```

## Recurring meeting review table
```
| Meeting | Frequency | Length | My role | Useful last month? | Decision |
| Team sync | Weekly | 60 | Attendee | Partly | Shorten to 25, pre-read |
| Project X | Weekly | 30 | Contributor | Yes | Keep |
| Vendor check-in | Weekly | 30 | Optional | Rarely | Leave; read notes |
```

## Sample week design
| Time | Mon | Tue | Wed | Thu | Fri |
|---|---|---|---|---|---|
| 9 to 11 | Focus | Focus | Focus | Focus | Weekly review and planning |
| 11 to 12 | Email and admin | Email and admin | Email and admin | Email and admin | Admin |
| 13 to 17 | Meetings window | Meetings window | Meetings window | Meetings window | Light meetings |
Adjust to time zones and energy; the principle is clustering meetings and protecting blocks.

## Booking links
Share a booking link that offers only the meeting windows, with buffers and a daily limit, so others cannot book over focus time.

## Measures to review
| Measure | Baseline | After 4 weeks |
|---|---|---|
| Meeting hours a week | | |
| Focus blocks of 90+ minutes | | |
| Longest stretch without a break | | |
| Recurring meetings | | |
Repeat the audit every quarter, because calendars drift back to full.

Personal time, such as exercise or school pickups, is blocked as busy so it is protected like any meeting.

Repeat the audit each quarter to keep gains.

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Manager-run meetings the user must attend | Suggest shorter formats or pre-reads to the manager |
| Client-facing role | Protect admin and preparation time next to client blocks |
| Global team across time zones | Rotate inconvenient times; share recordings |
| New manager with many one-to-ones | Group them on two days; keep 25 minutes |
| Leadership role | Protect thinking time weekly; delegate attendance where possible |
| Health or caring responsibilities | Block personal time as busy without explaining details |

## Handoffs to related skills
- Agendas and shorter meetings: `meeting-agenda`
- Replacing meetings with written updates: `async-updates`
- Scheduling across time zones: `scheduling-time-zones`
- Focus time: the Planning and Task Management `focus-deep-work` skill
- Time blocking: the Planning and Task Management skills

## Worked example
A head of operations averaged 26 hours of meetings a week with one focus block. The audit found 14 recurring meetings: five kept, three shortened from 60 to 25 minutes, two turned into written updates, two delegated to team leads and two ended. Meetings moved into afternoon windows, with focus blocks on four mornings and 10-minute buffers. Draft messages went to organisers. Four weeks later meetings averaged 17 hours, focus blocks rose to four a week, and the quarterly plan moved forward.

## Common mistakes
- Accepting every invitation by default.
- Keeping recurring meetings nobody reviews.
- Back-to-back meetings with no breaks.
- No protected time for priorities.
- Changing calendars without telling organisers.

## Self-check before you answer
- Is time measured by category over four weeks?
- Does every recurring meeting have a decision?
- Are focus, admin and personal time protected?
- Are there acceptance rules and drafted messages?

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/productivity/meetings-calendar/calendar-audit/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.