Skip to main content

Total Active Time

Team-level total time spent actively working on tasks during the period.

Updated yesterday

Total Active Time aggregates the time the whole team spent actively working on tasks during the selected period. It's the team-level counterpart to per-member Done Active Time and Working Time.

What it measures

Sum of active-state durations across every task touched by the team in the period — completed and in-flight.

How Leanmote calculates it

total_active_time = sum(time_in_active_states(i, period)) for items where team in (this team)

  • Active states are defined in your workflow mapping (typically in_progress, in_review, qa).

  • Waiting states are excluded — those are reported in Total Waiting Time.

How to interpret it

  • Use as a denominator for productivity ratios — Throughput per active hour, items per active week.

  • Total Active Time growing without Throughput growing means each item is consuming more active time. Slice work or remove blockers.

  • Total Active Time much smaller than total elapsed time means the team is spending most of its workflow time waiting. Pair with Flow Efficiency.

What to do about it

  • Don't aim to maximize this. More active hours doesn't equal more value.

  • Use it for capacity planning: "we deliver X items per Y total active hours."

Related metrics

  • Total Waiting Time

  • Flow Efficiency

  • Working Time

  • Done Active Time

Did this answer your question?