How I Reclaimed 10 Hours a Week by Auditing My Calendar

Three months ago, I sat down on a Sunday evening and did something I'd been avoiding for years: I counted the actual hours I was spending in meetings each week. Not a rough guess. Not a vague sense that "things are busy." I pulled up my calendar, exported it to a spreadsheet, and added it all up.

The number was 23.5 hours. Per week. In recurring meetings alone — not counting the spontaneous ones, the "quick syncs" that ran long, or the prep time before each one. I nearly closed the laptop and went to bed.

Instead, I spent the next three weeks methodically dismantling that calendar. And by the end, I'd gotten down to 13 hours — with better outcomes than before. That gap of 10+ hours didn't magically appear; I had to excavate it. Here's exactly how I did it.

Why a Gut Feeling Isn't Enough

Everyone knows they have "too many meetings." But knowing it and seeing it are completely different experiences. When I actually looked at the data, I realized my instincts had been wrong about which meetings were the real culprits. I'd been mentally blaming a Friday afternoon check-in with a client — but when I looked at the spreadsheet, that was 30 minutes a week. The actual time thief was a supposedly essential Monday morning team standup that had slowly inflated from 15 minutes to an hour over the course of a year, and nobody had said anything.

The audit forces honesty. It replaces "I feel overwhelmed" with "here are the 11 recurring events eating my week, and here's what each one is actually costing."

The Spreadsheet Method (Exactly What I Used)

I built this in Google Sheets, but Excel or even Notion works fine. The key is to capture everything in one flat table before you start making decisions. Here are the columns I used:

Meeting Name — the actual calendar title
Frequency — weekly, biweekly, monthly
Duration (mins)
Attendees — just the count
My Role — owner, contributor, observer, or "unclear"
Last Time It Was Useful — a date, or "can't remember"
What Would Break If This Stopped — force yourself to answer this
Monthly Hours Cost — calculated field: (duration/60) × frequency per month
Value Score — 1 to 5, gut rating
Action — Keep / Shorten / Cut / Async / Delegate

That last column is the one that does the real work. But you can't fill it in honestly until you've filled in all the others first.

For the data entry, I went week-by-week through three months of my calendar — not just the current week, because the current week might be atypically light or heavy. Three months gives you a realistic picture. This took about 90 minutes, which felt annoying until I realized I was about to save 10 hours every single week going forward.

The Four Categories That Changed Everything

Once the spreadsheet was populated, I sorted by Monthly Hours Cost, high to low, and then started scoring Value. The meetings naturally fell into four buckets:

Keep: High cost, high value. These stay. For me, this was our weekly product strategy call and a 1:1 with my manager. Non-negotiable, and I could see why every time.

Shorten: High cost, medium value. These were the ones that had drifted. Our Monday standup was here. The meeting itself was valuable — but 60 minutes wasn't. I went back, rewrote the agenda to cover only blockers and decisions needed that day, and moved it to 25 minutes. Nobody complained. If anything, people seemed relieved.

Cut: Medium-to-low cost, low value. Easier to kill than I expected. I'd been on a biweekly "cross-functional alignment" call for eight months. When I asked myself "what would break if I stopped attending?" the honest answer was: nothing. I checked this with the organizer. She said she'd just been inviting me out of habit. I was off it within a week.

Async: This was the biggest category I hadn't expected. Several meetings existed purely to share information — project status updates, weekly reports, "keeping everyone in the loop." These don't need to be meetings. They need to be a Loom video or a shared doc with comment threads. I converted four of these to async updates. That alone reclaimed about 90 minutes a week.

The Conversation Nobody Wants to Have

Some of these changes required actually talking to people, which is where most calendar audits stall out. I've been there — it feels rude to leave someone's meeting, or to tell a colleague their standup is too long.

What helped me was framing it as a system problem, not a personal one. "I've been auditing how I'm spending my time and trying to make sure I'm in the right rooms" lands very differently than "your meeting isn't worth my time." One sounds like self-management; the other sounds like a complaint.

I also gave myself permission to do a trial period. Instead of saying "I'm leaving this meeting," I'd say "Can we try running this as an async update for the next four weeks and see if it works?" Four weeks feels low-stakes. And in every case — every single one — after four weeks, nobody wanted to go back to the meeting format.

The Recurring Task Problem (Not Just Meetings)

About two weeks in, I realized meetings were only half the problem. I had a matching issue with recurring tasks — things I'd added to my weekly routine that had quietly outlived their usefulness.

I ran the same audit, same spreadsheet columns, on my task list. I had a weekly "competitive monitoring" task I'd set up 18 months earlier when we were launching a new product. That product had launched. We weren't in launch mode anymore. But the task was still there, eating 45 minutes every Friday because I'd never officially decided to stop.

The exercise I found most useful here: for each recurring task, I asked whether I had started it as a response to a specific situation that no longer existed. A surprising number of them had. I cut or reduced about six of these, saving another couple of hours a week.

What I Actually Protect That Time With

Here's the part people don't always talk about: reclaiming time is worthless if you don't intentionally fill it with something better. I'd done calendar audits before and watched the recovered time immediately get colonized by new requests, new meetings, new noise.

This time, I blocked the recovered time before canceling anything. I added two 90-minute "deep work" blocks each day — mornings, protected, no invites accepted. Only after those were locked in did I start canceling the low-value meetings. That sequencing mattered. If you clear space without immediately claiming it, the calendar fills itself.

I also added a 15-minute "calendar review" to my Friday close-out routine. Every week I look at what's coming up and ask: does anything on here need to be questioned? This prevents the drift from happening again. It's a small habit, but it's the maintenance that makes everything else stick.

Three Months Later

My calendar now sits at about 11-13 hours of meetings per week, depending on the month. The work is genuinely better — not just because I have more time, but because the meetings I do attend are sharper. When you can't hide low-value discussion inside a two-hour catch-all call, people get better at focusing on what actually needs a room.

The spreadsheet still lives in my Google Drive. I run it again every quarter — takes maybe an hour now that I have the template — and it always surfaces at least one or two things that have quietly crept back in.

If you're reading this and thinking your situation is different because you don't control your own calendar — I hear that, and I'd push back gently. I thought the same thing. But I had more influence than I'd assumed. Not over every meeting, but over enough of them to make a real difference. Start with the ones where your presence is optional. That's usually more than you think.

The spreadsheet template isn't magic. But honest accounting is. Most of us are just too busy with our calendars to actually look at them.