Linear Metric
Issue Tracking
Capacity Utilisation = (Allocated Estimate Points / Available Capacity) × 100
Team Capacity Utilisation measures the proportion of available team capacity that is actively allocated to Linear issues. It compares the total estimated work assigned to the team against their available capacity, accounting for team size and any known availability constraints.
Team Capacity Utilisation
Team Capacity Utilisation measures the proportion of available team capacity that is actively allocated to Linear issues. It compares the total estimated work assigned to the team against their available capacity, accounting for team size and any known availability constraints.
How to calculate team capacity utilisation
Why team capacity utilisation matters for Linear users
Optimal utilisation ensures that teams are productive without being overburdened. Over-utilised teams experience burnout, increased errors, and higher turnover. Under-utilised teams represent wasted investment and missed delivery opportunities.
For Linear teams, capacity utilisation data enables evidence-based decisions about work allocation. It helps leaders identify teams with spare capacity for new initiatives and teams that need relief before quality or morale suffers.
Understand and act on team capacity utilisation with KPI Tree
KPI Tree calculates utilisation from Linear assignment and estimation data in your warehouse. Place this in your resource management tree alongside workload balance and velocity metrics.
Assign RACI ownership to engineering managers for capacity balance. Set alerts for utilisation rates outside the sustainable range to catch problems early.
Get started with your Linear data
Pull metrics from Linear directly through the Model Context Protocol.
Connect your existing warehouse where Linear data already lands.
Our professional services team can build you turn-key AI foundations in a matter of weeks. Data warehouse on Snowflake/BigQuery, ELT with Fivetran, all modelled in dbt with a semantic layer.
Related Linear metrics
Developer Workload Balance
Issue TrackingMetric Definition
Developer Workload Balance analyses the distribution of assigned issues, estimated effort, and active work across team members in Linear. It identifies imbalances where some developers carry disproportionate loads while others have available capacity.
Team Velocity Analysis
Issue TrackingMetric Definition
Velocity = Total Estimate Points Completed per Cycle
Team Velocity Analysis measures and analyses the amount of work completed per cycle by Linear teams. It tracks velocity trends, variability, and the factors that influence throughput to provide a reliable basis for capacity planning and delivery forecasting.
Seasonal Development Patterns
Issue TrackingMetric Definition
Seasonal Development Patterns identifies recurring cyclical trends in Linear development activity, such as productivity dips during holiday periods, velocity surges before major releases, or reduced throughput during hiring seasons. It helps teams anticipate and plan for predictable capacity fluctuations.
Cross-Team Dependency Impact
Issue TrackingMetric Definition
Cross-Team Dependency Impact measures how dependencies between Linear teams affect delivery timelines. It quantifies the additional cycle time, blocked time, and coordination overhead caused by cross-team handoffs and blockers.
Explore team capacity utilisation across integrations
All Linear metrics
Empower your team to understand and act on Linear data
Map what drives your metrics, measure progress at any grain, prove what works statistically, and deliver personalised action plans to every team member.