We Analyzed 71,000 Calendar Blocks. Meetings Were Only 5% of Them

Every product team says it cares about focus time. We say it too. But we got tired of saying it without proof, so a few weeks ago we pulled the anonymized, aggregated data behind our own time blocking feature and looked at what people actually put on their calendars when nobody was telling them to.

The dataset: about 71,300 blocks created over roughly 90 days, late June through late September 2026, from somewhere between 540 and 840 people active in any given week. Nothing about who these people are. Just what they blocked, and what kind of thing it was.

We expected meetings to dominate. That is the story everyone tells about calendars: they are where your day goes to die, eaten by other people's agendas. We hear it from users constantly. "My calendar isn't mine, it's just where meetings live."

The data said otherwise. Of those 71,300 blocks, 65,402 were tagged as personal tasks. Only 3,943 were meetings or events involving other people. Another 1,884 were breaks. Meetings made up about 5.5 percent of everything people deliberately put on their own calendar.

The calendar isn't the problem. The habit is.

This surprised us enough that we checked it three different ways before believing it. The ratio held across the full window, not just one good week. Whatever people are complaining about when they say their calendar is out of their control, it isn't the sheer volume of meetings sitting on it, at least not among people who have already picked up the habit of blocking time.

Here is the less flattering read, and probably the more honest one. The people who bother to block time are already doing the thing that fixes the meeting problem. They are not waiting for their calendar to defend itself. They are claiming space for their own work before anyone else gets the chance to fill it. The 92 percent isn't proof that meetings are rare in general. It is proof that blocking works, for the people who actually do it.

That is a smaller finding than "meetings are dying," and we think it is the true one. Time blocking does not make meetings go away. It just stops them from deciding everything else about your day by default. The five percent left over is exactly the part of your calendar you already knew you didn't control. Everything else, apparently, people take back on their own.

People keep changing their minds about being done

The second thing we looked at was what happens after someone marks a task complete. Over the same 90 days, people completed tasks 67,230 times. They also undid a completion 5,662 times: roughly one reversal for every twelve tasks finished.

We did not expect that number to be interesting, but it kept nagging at us. A reversal is not a misclick. Nobody undoes a completed task by accident twice in a row. People are marking something done, then coming back later and deciding it was not actually done, or that the definition of "done" changed once they looked at it again with fresh eyes.

Talk to enough users and you hear the same story in different words. A task gets checked off because it felt resolved in the moment. Then a client replies, or a draft comes back covered in comments, and now it isn't finished after all. Completion, in other words, is a claim you make about the present, not a fact you get to record permanently about the past. About 8 percent of the time, that claim quietly stops holding up within a day or two.

We do not have a fix for this, and we are not convinced it needs one. If anything, it is an argument against products that treat "done" as a fixed, celebratory state, complete with confetti and streaks. Work is often provisional. Letting someone walk a completion back without asking them to explain themselves matches how people actually work far better than treating every checked box as final.

Two things worth doing with this

If you have never tried time blocking, this data gives you a reason to start that has nothing to do with your meeting load. You do not need fewer meetings to benefit from it. Most of what a blocking habit protects is work that never had a natural claim on your day to begin with: the report nobody scheduled a slot for, the deep work that keeps getting pushed to "later" until later stops arriving.

If you already block your time, the number worth sitting with is the reversal rate. If something like one in twelve of your own completed tasks comes back around, it is probably not because you are careless. It is because the work itself keeps changing shape after you first touch it. Building in a little slack for that, instead of treating every checked box as final, will save you the small, specific frustration of feeling like you failed at something you actually just revisited.

This is part of why we build Arch Calendar the way we do. Tasks and time blocks live in the same view, and marking something done or undone takes one click either way, with no streak to break and no explanation required. We did not design for a world where completion is permanent. We designed for the one where you are allowed to change your mind about your own day, quietly, as often as the day requires.

A note on the data, and an invitation

We are not publishing this as a rigorous study. It is one product's anonymized, aggregated usage over a single 90 day window, and we have no way to know how far it generalizes past people who have already adopted a time blocking habit. What we can say is that it is real, it is ours, and it surprised us enough to sit down and write it out instead of filing it away in a dashboard nobody opens again.

If you keep similar data for your own product and want to compare notes, or if you run this same breakdown yourself and get a different split, we would genuinely like to see it. We will probably write about it if you do.

If you want to try blocking your own time and see where your own ratio lands, Arch Calendar's time blocking view is free to start with, and it takes about five minutes to set up your first week.