How do concurrent timers work?

Overview

Keepr lets you run more than one timer at the same time — useful when you juggle organizations or bill a retainer alongside project work. Each running timer tracks its own task, project and workspace independently.

The front timer is the one shown large in the bar; the others stack underneath it. Click a stacked timer to bring it to the front.

Limits

You can run at most three timers at once. The limit applies across all organizations and workspaces you belong to — the composer hides the “Start another timer” row when you reach it.

Limiting timers per workspace

A workspace can restrict concurrent timers in one of two ways. “One timer per workspace” lets each person run a single timer in that workspace, while leaving them free to run timers in other workspaces. “Exclusive — one timer at a time” is stricter: while you track time there, you cannot run any other timer anywhere — in any workspace or organization.

When starting a timer would break either rule, Keepr asks before stopping anything. It stops only the timers that actually conflict, logs them at the moment of the switch, and never shows what a timer in another organization was.

Examples

One timer per workspace. Your company tracks client work in a “Delivery” workspace set to one timer per workspace, and a few people also have access to “Labs”, which allows concurrent timers. You can run one Delivery timer and up to two Labs timers at the same time. Start a second Delivery timer and Keepr offers to stop the first one; your Labs timers keep running.

Exclusive. If Delivery were exclusive instead, starting a Delivery timer would ask to stop every other running timer — the Labs ones and any in other organizations too. And while the Delivery timer runs, you could not start a Labs timer at all.

Allow concurrent. In a workspace with no restriction you can run up to three timers. That limit of three always applies, across all your workspaces and organizations, whatever the policies say.

Overlap policies

Each workspace also decides what happens when saved entries overlap in time: Reject blocks the save, and Allow & highlight permits it but marks the overlapping rows in amber on the tracker so they are easy to review.

Entries that share a minute or less do not count as overlapping, under either policy — switching tasks often stops one timer and starts the next within the same minute.