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.

The short answer

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.

Three things the block was doing

Worth separating, because only one of the three is about time, and the other two are what you lose when the block stops holding.

Each row fails on its own. Most calendars lose all three at once.

Why the automatic version was fragile

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.

What replaces it

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.

• Name the kinds of work you do, in your own words. Deep work, review, admin. Two or three is plenty; the names matter less than the number.
• Give each kind a recurring window, and write the intent into the title instead of the word focus. "Writing, unless a client needs the hour" survives an override. "Focus Time" does not.
• When something has to take a window, decide what leaves it. Something always leaves. Write down where it went, or that it went nowhere.
• On Friday, read the list of what left. That list, not the calendar, tells you whether the windows were honest.

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.

The part nobody automates

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.

When somebody books over it anyway

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.

Common questions

Is focus time the same as time blocking?

No. Time blocking gives every part of the working day to a kind of work. Focus time is one protected window inside an otherwise reactive calendar, which is why it is easier to adopt and easier to lose.

Should a protected window move when a meeting is booked over it?

Only if you decide where it moves to. Automatic rescheduling sends it to whatever hour is empty, and the empty hours are usually empty for a reason.

How long should a protected window be?

Long enough to finish one thing rather than start three. If you cannot name what would be done by the end of it, it is too short.

Does this work for a team, or only for one person?

One person first, because the record of what did not fit is personal. A team version needs one more thing: each person able to see what the others have already committed to, so an interruption is a choice rather than a guess.

What if my whole week is meetings I cannot move?

Then the windows go around them and the honest output of the week is a long list of work that did not fit. That list is the argument for changing the meetings, and it is more persuasive than the complaint.

The whole procedure, in four sentences

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.

The problem isn't that time blocking is wrong. It's that everyone's blocks are invisible to each other. Maya is doing deep work from 9–11. Jordan is in back-to-back meetings. Sam blocked the afternoon for a design review. None of them know what the others are doing, so the interruptions keep coming.

Shared blocks change the math

When a team agrees on block types and schedules them together, something shifts. Instead of protecting your own time against your teammates, you're all working within the same rhythm. Deep work is respected because everyone is doing it at the same time.

This is the insight behind Centers. Not just individual scheduling, but shared visibility into when each person is available for what kind of work.

Getting your team started

• Start with three block types: Focus, Sync, and Free. Most teams don't need more than this to start.
• Set blocks as a team, not individually. The goal is a shared rhythm, not perfectly optimized personal calendars.
• Protect the Focus blocks ruthlessly for the first two weeks. Habits take time.
• Review and adjust after one month. The first version of your schedule will be wrong. That's expected.

The goal isn't to account for every minute. It's to make your team's time legible to each other.

Time blocking for teams isn't about control — it's about reducing the invisible coordination tax that drains energy from everyone's day. When your team knows when to reach out and when to go heads-down, everyone does their best work.

The rules that stick are the ones that describe intent, not mechanics.

Intent-based rules

Instead of "no meetings before 10am," try "mornings are for focused work unless a client or deadline requires otherwise." The outcome is the same on most days. But the rule survives contact with reality.

• Describe what you're protecting, not just what you're blocking.
• Name the exceptions explicitly — it makes them feel legitimate rather than like failures.
• Keep the rule list short. Five rules followed consistently beat twenty rules ignored.
• Revisit rules quarterly. Your team's work changes; your schedule should too.

Where AI fits in

Centers lets you define custom scheduling rules in plain language. The AI translates your intent into actual schedule logic — so you can write rules the way you think about them, not the way a calendar app understands them.

Good rules are written by people who understand the work. They're applied by systems that don't get tired of applying them.

"Is now a good time?" "Can you look at this?" "Quick call?" Every one of these is a scheduling decision. You're just making them ad hoc instead of in advance.

What the overhead actually costs

Research on context switching consistently finds that it takes 20–30 minutes to return to deep focus after an interruption. On a team of five, even two interruptions per person per day adds up to hours of lost productive time — every day.

The cost isn't just the interruption. It's the ambient uncertainty. When you don't know when you'll be interrupted, you can't fully commit to the task in front of you. That's where the real productivity loss lives.

Structure as a form of respect

A shared schedule isn't bureaucracy. It's an agreement between teammates about how to respect each other's time. When everyone knows that 9–11 is focus time, no one has to defend their attention during those hours.

The absence of a schedule isn't freedom. It's a continuous tax on everyone's attention.

Centers makes it easy to establish that shared agreement — and to keep it updated as your team's work evolves.