Somewhere on your calendar there is a recurring event called Focus Time. Last Tuesday a meeting landed on top of it, and nobody asked you first.
Protected focus hours were this category's one good idea for teams. The best-known tool that scheduled them automatically, Clockwise, closed on 27 March 2026; its own shutdown notice gave customers about a week, deleted their data shortly afterwards, and pointed them at a competitor. The idea outlived the product as a recurring event most people now ignore, which is a shame, because the useful part was never the block.
Focus time protected a decision, not an hour. The block held a choice you had already made about what Tuesday morning was for. When it worked, it worked because the choice was made before the week started and somebody else could see it. When it failed, it failed because a block is a claim on a shared document that anybody can write to.
Worth separating, because only one of the three is about time, and the other two are what you lose when the block stops holding.
| What it protected | What broke it |
|---|---|
| A default. Mornings were for one kind of work unless something overrode it. | Nothing defined what counted as an override, so everything did. |
| A reason to decline. You could point at a block instead of at yourself. | A block with no stated purpose is easy to move, so the purpose had to be written on it. |
| A signal. Other people could see the shape of your week before interrupting it. | When everybody protects the same hours, the meeting still has to go somewhere. |
The automated products moved your focus block when a meeting arrived. That sounds like the right behaviour and it removes the thing that made the block work. A block that moves is not a commitment; it is a preference the calendar consults. By Thursday it has drifted to five in the afternoon, which is not when anybody does hard work, so the hard work does not get done.
The block was never the mechanism. The decision was, and an automatic reschedule is a decision made by something that does not know what the work is.
Not a smarter block. A written rule, and a record of what did not fit. You can run this this week with the calendar you already have.
The fourth step is the one people skip, and it is the one that carries the method. A calendar shows what you intended. The list shows what happened.
Every scheduler in this category answers one question: where does this piece of work go. Almost none of them answers the harder one. What happens to the work that fits nowhere?
A block that moves hides the overflow, because every hour still looks accounted for. A block that holds makes the overflow visible, and visible is what you want. An hour of work with nowhere to go is a decision you have not made yet.
A protected hour is only worth protecting if you can see what was displaced to protect it.
They will. The rule that survives is the one that says who decides. Name in advance the few people who may take a window without asking — a client, whoever is on call, the person you report to. Everybody else is making a request, and a request can be answered tomorrow.
That is a norm, not a setting. It works whether or not any software agrees to it, which is the test of a rule worth writing down.
Name your kinds of work. Give each one a window with its intent in the title. Record what displaces it. Read that record on Friday. None of it needs a product, and it is worth doing before you shop for one.
Centers is one way to keep that record without keeping it by hand. It generates about four weeks of schedule from your tasks and your own time blocks. Your calendar is read as busy time and never written to. Anything that will not fit lands on an unscheduled list rather than disappearing.