The objection to automated scheduling is loss of control. It is worth examining that objection, because the honest baseline is not a calendar you control — it is a calendar controlled by whichever colleague opened the booking tool first.
Reclaim.ai scores 7.3 on our 361 score. This is what it does well, what it needs from you, and where it fails.
What it actually does
Reclaim finds time for things that are not meetings — tasks, habits, focus blocks, breaks — and defends that time by placing real events on your calendar. When a meeting lands on top, it moves the flexible block instead of silently losing it.
That last behaviour is the product. A focus block you protect manually gets sacrificed the first time someone books over it. A focus block that reschedules itself survives the week.
Setup decision one — be honest about your real hours
The most common setup mistake is declaring aspirational working hours. If you tell it you start at 8 and you actually start at 9:30, it will schedule deep work into a slot where you are commuting, and you will start ignoring it within a week.
A tool you override constantly is worse than no tool, because you now have a calendar that is confidently wrong. Enter the hours you actually keep, not the ones you would like to keep.
Setup decision two — priority has to mean something
Automatic scheduling depends on knowing what yields when there is a conflict. If everything is high priority, the algorithm has no information and its choices will look arbitrary.
Be ruthless here. A small number of things that genuinely outrank meetings, and everything else flexible. The quality of the output is almost entirely a function of the quality of this input.
Setup decision three — decide what is immovable
Some blocks must not move: the standing 1:1 you would look rude rescheduling, the school run, the recurring commitment with people outside your organisation.
Mark those as fixed explicitly rather than trusting the tool to infer social weight from a calendar entry. It cannot know that moving one particular meeting is politically expensive.
Where it goes wrong
It works considerably better when both parties use it. In a team where one person automates and everyone else books manually, the automated calendar absorbs all the flexibility — you become the person who is always available to move, which is not the outcome you wanted.
It also cannot fix a fundamentally overcommitted schedule. If your obligations exceed your hours, an optimiser will simply find the least-bad arrangement of an impossible week and present it neatly. The tidy calendar can disguise the real problem for months.
And it adds calendar noise. Habits and buffers rendered as events make a week look full at a glance, which some people find motivating and others find suffocating. This one is temperament, and worth a two-week trial before committing.
A reasonable starting configuration
Start narrow. One recurring focus block, real working hours, two or three genuinely high-priority tasks. Run it for two weeks and check one thing: did the protected time survive?
If it survived, widen. If it got eaten, the problem is not the tool — it is that your calendar has no slack, and no amount of optimisation creates hours that do not exist.