Active Days counts the number of days during the period on which the team or member transitioned at least one item — moving it from one workflow state to another. It's a presence-and-engagement signal, not a productivity score.
What it measures
Distinct calendar days within the period where the member or team caused at least one item-state transition.
How Leanmote calculates it
active_days = count(distinct_days(transitions where actor = member in period))
Workweek-only counting respects your organization's configured workweek.
Days off, PTO, and holidays are not subtracted from the period denominator unless configured.
How to interpret it
Use Active Days to normalize other metrics. A member with 8 active days and 16 throughput delivers more per active day than someone with 18 active days and 12 throughput.
Sharply low Active Days for an extended period usually signals PTO, on-call, parental leave, or a process-mapping issue. Confirm before acting.
Best paired with Working Time — high Active Days with low Working Time can indicate context-switching across many small touches.
What to do about it
Don't optimize for higher Active Days. Focused work blocks are valuable; we don't want everyone touching everything every day.
Use it to cross-check capacity numbers during planning.
Related metrics
Working Time
Throughput
Done Active Time