Reclaim AI protects time around meetings with flexible scheduling

Reclaim AI helps people organise time across Google and Outlook calendars. Its scheduling tools protect flexible work and routines around meetings, while calendar sync makes commitments visible across accounts. The company is also introducing a more conversational Reclaim 2.0 experience. Buyers should distinguish the version available to their account from beta features and evaluate whether the resulting schedule is workable, not simply full.

01 / ProductCalendar automation needs to reflect how time can actually move

Reclaim works alongside a calendar provider, adding scheduling and planning tools around the events already there. The product includes flexible routines, focus time, buffers, booking links and calendar sync. The central idea is that some commitments have fixed times while other work can move within reasonable boundaries.

That distinction creates the value. A customer appointment may be fixed, while a planning session or lunch break has an acceptable window. Automation can rearrange the flexible parts when a new commitment appears, provided the user has described the constraints accurately. A system cannot create extra working hours when every commitment is treated as immovable.

There is an important current product transition. The Reclaim 2.0 overview², checked on 15 September 2026, explicitly describes the new experience as a private beta. It introduces a conversational assistant and a different planning interface. The guide directs users to check their account version, so the new interface should not be assumed to be generally available to every subscriber.

02 / AudienceFor schedules that change often but still have clear priorities

Reclaim is a useful candidate for consultants, managers, engineers and other knowledge workers whose calendars repeatedly consume the time intended for individual work. It is particularly relevant when multiple calendars make someone appear available even though another account contains a commitment. The intended outcome is a realistic week with fewer avoidable conflicts.

The product requires more judgment than simply importing a task list. Users need to identify acceptable working hours, the minimum useful length of a focus session and the routines worth defending. If a project needs sustained concentration, several scattered ten-minute gaps may not be an adequate substitute for one uninterrupted block.

Teams should also agree what kinds of time can move. A flexible personal work block differs from a meeting involving several colleagues. Frequent rescheduling may be mathematically possible while still creating confusion for participants. Set expectations about important meetings and short-notice changes before treating schedule optimisation as a team-wide policy.

03 / WorkflowStart with calendar visibility, then add one flexible commitment

A proposed pilot should start with one person’s ordinary working week. Identify fixed appointments, genuine free time and work that can move. Connect the necessary calendars and check what another person sees when looking for availability. This is an evaluation design drawn from public documentation, not evidence of private calendar testing.

The Calendar Sync page⁴ explains that Reclaim creates and maintains event copies across connected Google and Outlook calendars. Visibility options can show details or a more generic busy commitment. Test a personal appointment, an all-day event and a changed meeting before assuming the chosen settings produce the intended result across accounts.

Next add a single recurring routine or focus goal with realistic hours and duration. Observe what happens when a new meeting conflicts with it. In the documented Reclaim 1.0 scheduling model⁵, priorities and scheduling constraints determine how Habits, Tasks and Smart Meetings fit. Higher-priority work can displace lower-priority flexible work, and locked events constrain rescheduling.

Users with Reclaim 2.0 access should evaluate its review flow separately. The 2.0 FAQ³ describes Preview Mode, where assistant-driven changes are staged before being applied to the live calendar. The preview includes the effects of enabled scheduling agents. Review the whole proposed schedule, including moved routines and participant notifications, rather than only the first change requested.

Finally, record whether the protected time was actually usable. A focus block that survives on the calendar but is routinely interrupted may need a different team agreement. Compare planned time with completed work and the amount of manual rearranging required. Those observations are more useful than counting the number of automated calendar changes.

04 / PricingBuy for the scheduling range, agents and calendars needed

The pricing page¹, checked on 15 September 2026, presents the current agent-based plan structure below in US dollars. Annual prices are monthly equivalents under yearly billing. Confirm that the purchased plan and account version include the exact workflow being evaluated.

For ten Starter seats, the displayed annual rate implies US$1,200 per year before taxes or additional items. Ten Business seats imply US$1,800 on the same basis. Evaluate the difference against the scheduling horizon, calendar connections and team capabilities that will be used regularly.

The page also discusses charges for certain meeting attendees without paid seats. Its launch-promotion copy still names a July 31 end date, which precedes this review. Do not assume that historical free-attendee promotion applies to a new purchase. Ask for the current attendee allowance and charges when pricing larger recurring meetings, and include them in the total rather than comparing seat prices alone.

05 / DistinctionsPreviewing a schedule exposes the consequences of a change

Reclaim 2.0’s preview model is a meaningful product distinction because calendar changes can cascade. Moving one meeting can shift a focus block, compress a routine or change the time available for preparation. Seeing the proposed week before applying an assistant’s changes gives a user a chance to judge those consequences together.

The FAQ also distinguishes assistant changes from background automation. Configured agents can continuously manage flexible time, while assistant and MCP changes are staged for review. A user should understand both modes. Preview approval for a conversational request does not mean every background adjustment always waits for another confirmation.

The 2.0 overview changes the task model as well: tasks are suggested during focus time rather than automatically scheduled as individual tasks. A user migrating from 1.0 should test that difference with their real work. The same task integration can have a different practical role when it becomes a recommendation source instead of a series of calendar blocks.

Our Notion blueprint is relevant when the main need is organising the project information behind those tasks. Our Otter blueprint explores capturing decisions and actions from meetings. Reclaim addresses when work can happen; those systems address the work or conversation itself. A simple calendar with manually protected focus time remains a useful baseline for comparison.

06 / QuestionsVersion differences and overfull calendars can change the result

The private-beta label should influence a rollout decision. The 2.0 overview marks some meeting auto-scheduling as still in development. Do not infer that every feature described on a broad product page is ready in the account being purchased. Ask to see the particular conflict-resolution and recurring-meeting workflow required by the team.

Calendar visibility also needs an end-to-end check. A generic busy copy can protect availability while keeping event details private, but the result depends on the chosen sync rules and permissions of the destination calendar. Review the copied event from the perspective of a colleague or booking-link visitor, rather than judging privacy only from the owner’s screen.

The older 1.0 scheduling guide explains that non-Reclaim events receive high priority by default and are not freely moved by the scheduler. This helps explain why a heavily booked week may leave too little space for flexible tasks or habits. The sensible response may be to remove a meeting or reduce commitments, rather than repeatedly lowering the priority of important personal work.

Time analytics also need interpretation. A calendar block labelled focus does not prove focused work occurred, and a meeting-heavy day can still be necessary. Use the schedule to identify patterns and ask better questions. Avoid turning a planning tool into a simplistic score of individual productivity without understanding the work that happened during those hours.

07 / DecisionChoose Reclaim when protected time becomes more usable

Reclaim is worth testing when calendar conflicts and repeated rearranging interfere with important work. Start with correct availability across accounts, one realistic focus goal and a small number of flexible routines. Evaluate the resulting week before adding more automation.

Choose a plan around the actual calendar and scheduling requirements, with the account version confirmed. Compare a simpler manual approach when the schedule is stable. Prepare priorities and meeting conventions when those remain unresolved: a scheduling assistant becomes more useful when the organisation can say which commitments should win.