What it does
Every task can carry a time estimate, and you can track actual time spent against it with a start/stop timer right on the task. A workspace-wide Timesheet page rolls every logged entry up by day.
Who needs it
Teams that bill by the hour, or just want to know where the week actually went versus where it was planned to go. Managers checking their direct reports' logged time without needing owner or admin access to everyone else's.
Why use it
The timer lives on the task itself, so starting and stopping it doesn't require switching tools — and an estimate sitting next to the actual time gives you a running check on whether your estimates are any good.
How it works
Open a task and use the timer toggle in the task detail panel to start or stop tracking time against it. While it's running, the task keeps a live entry; stopping it records the duration and adds it to the task's total logged time, shown alongside the list of past entries with who logged each one and when.
Estimates: a task can carry an estimate in minutes — brought in through CSV import or set via the REST API or MCP tools — shown as the "Est." column when it's turned on in table view, and factored into the Workload view's per-person capacity math.
Logging time after the fact: beyond the live timer, you can add a manual time entry with its own start time, end time, and description through the REST API or an MCP tool call — useful for time that happened before you thought to start the timer.
Timesheet lists every stopped time entry in the workspace, grouped by day with a running total. What you see depends on your role: Owners and Admins see every entry in the workspace; everyone else sees only their own entries plus their direct reports' — anyone whose manager is set to them.