On this page
The short version
- Audit one real week before changing anything. Look back at a week that already happened before you fix anything.
- Give every recurring meeting an expiry date. A standing meeting with no review date runs forever by default, whether or not it's still earning its slot.
- Protect one block a day before meetings take it. Put focus time on the calendar first, and let meetings fill in around it.
- Turn optional attendance into an actual no. Decline, or send someone in your place. That's a real answer. An unanswered invite isn't.
- Batch your own meetings back to back. Three scattered 30-minute gaps are worse than the same 90 minutes blocked together.
A calendar that fills up gradually, one recurring meeting at a time, rarely empties out the same way. Nobody schedules a session to remove a meeting. People only schedule sessions to add them. One field study of 24 office workers found that 57% of task periods were interrupted before they finished. A calendar cut into thirty-minute fragments by back-to-back meetings is a common cause of that kind of interruption.
Taking a calendar back is mostly subtraction, done on purpose, because nothing else does it for you.
Audit one real week before changing anything
Before you cancel or decline a single meeting, look at one actual week that already happened: every meeting, how long it ran, and whether it needed you specifically. You can’t fix a calendar you only remember through a vague sense that “there are too many meetings.” A concrete week of data turns that feeling into a specific list.
This usually surfaces something you didn’t expect: a status meeting you attend but never speak in, or three separate 15-minute check-ins that could have been one email.
Give every recurring meeting an expiry date
Give any meeting set to repeat weekly or monthly a review date, even a rough one, three months out. A standing meeting created to solve a problem that’s since been solved keeps running anyway, because nobody’s job is to notice it’s no longer needed and cancel it.
When you create a new recurring meeting, put “review on [date]” in the description. When you inherit one that already exists, pick a review date for it this week, rather than assume someone else already has.
Protect one block a day before meetings take it
Pick one time of day, ideally when your energy is highest. Put a recurring block on your calendar for focused work before other meetings get scheduled around it. Scheduling tools fill whatever’s empty. A block that exists first is a block that stays protected.
Ninety minutes is enough for most people. The block must exist, and it must exist before the rest of the week gets booked. Its exact length is a detail.
Turn optional attendance into an actual no
If a meeting invite marks your attendance optional and you don’t need to be there, decline it. Or send someone in your place who’s better positioned to represent you. An unanswered optional invite stays on your calendar. It keeps taking up the mental space of “should I go to this,” even when you never do.
A clear decline, with a one-line reason if it helps the organiser, is a real answer. Silence just leaves the invite pending.
Batch your own meetings back to back
When you have any say over scheduling, put your own meetings next to each other instead of spreading them across the day with gaps. Three thirty-minute meetings with fifteen-minute gaps between them leave you with no usable block of focus time at all. The same three meetings, back to back, leave the rest of the day open.
Where this breaks
This method assumes you have some control over your own calendar, which isn’t true in every role. If most of your meetings get scheduled by someone else, start with the audit step regardless. Even without the authority to decline, knowing exactly what fills your week is what makes the conversation with whoever does control it possible.
It also doesn’t fix a calendar problem that is a staffing problem underneath. Meetings can proliferate because there aren’t enough people to cover the work any other way. No amount of batching or expiry dates changes that. It just makes the underlying shortage more visible.
Where Beemy fits
Beemy watches your work and personal calendars together and flags a real clash the moment it appears, so you don't have to spot it yourself. It drafts RSVPs and reschedules for your approval, but it never accepts or declines a meeting on your behalf. Live today on Google Calendar, alongside Gmail.
One item, shown
Illustrative example, built with mock data.
In Google Calendar · work
What arrived
Weekly sync — attendance optional
A recurring invite marked optional lands again, the fourth week running you haven't said anything either way.
Beemy's draft
Re: Weekly sync — attendance optional
A decline is drafted with one line: you're not needed this week, and someone else on the team already has it covered.
You approve the decline. The invite stops sitting there unanswered.
Questions
What if I don't control my own calendar?
Start with the block you do control: the one focus hour in step three. Even one protected block a day changes how fragmented the rest of the week feels.
Isn't declining a meeting risky?
Declining with a reason, or sending a delegate, reads very differently from silently skipping a meeting. The silence is usually the risky part, more than the no.