Active Days counts the days in the period on which a member or team did enough work for the day to register. It's a presence-and-engagement signal, not a productivity score.
What it measures
Distinct calendar days within the period on which the member reached the activity threshold — two actions by default, not one. A day with a single action does not count.
An action is any of the events Leanmote already ingested for that person, across all four kinds of source:
Git — commits, merge requests, reviews, approvals.
Work items — status changes, worklogs, tasks created.
Chat — messages.
Calendar — meetings.
That last one surprises people: a day spent in two meetings counts as an active day, because meetings are actions like any other.
How Leanmote calculates it
active_days = count(days where actions(member, day) >= threshold)
The threshold defaults to 2 and is configurable. If your numbers look lower than you expect, this is usually why.
Every source counts into the same daily total. Two commits, or one commit and one meeting, both reach the threshold.
Days off, PTO and holidays are not subtracted from the period.
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