Skip to main content
Plans lists the blocking plans in your organisation. Blocking is optional and separate from tracking, and most organisations never create one. For what a plan can actually do, see Plans for groups.
If you only use ReclaimTime for tracking, you can ignore this page entirely. An empty Plans list is a normal, healthy state.

The list

Plan Details expands a row to show the full rule set without opening the editor.

Starting and stopping

The action on each row starts or stops the plan.
A plan that exists is not a plan that is running. Creating a plan and assigning it to a group does nothing until its status is Active. This is the usual explanation for “we set up blocking and nothing happened”.
Stopping a plan leaves it in place so it can be started again later. Deleting removes it.

Getting a plan onto machines

Three things all have to be true. Miss any one and nothing is blocked:
  1. The plan’s status is Active.
  2. The plan is assigned to a group, on the Plans tab of that group’s panel in Groups.
  3. The people in that group have Enable Plans ticked on their account. It is off by default for a tracked employee. See Accounts.
The client asks for the plans that apply to its user’s groups and refreshes roughly every two minutes, so a change reaches machines in minutes rather than instantly. Enforcement is local, so it keeps working when a machine is offline.

Before you switch blocking on

Blocking is visible to employees in a way that tracking is not. A tracked employee normally sees nothing at all. A blocked one gets a closed tab or a message. Whatever consultation your organisation required for monitoring, blocking is a separate conversation, and it is much better had before the first plan goes Active than after somebody’s browser closes on them.
A safer rollout: create the plan, set it to notify rather than block, and watch for a fortnight. Finding out that a rule catches a work tool is far cheaper before it starts stopping people working.
Checked against ReclaimTime client 8.0.0.9 and dashboard V3 on 5 September 2026.