Utilization & Capacity

Klority's Utilization module gives you an at-a-glance view of how your team's bandwidth is being consumed across a project. Spot burnout risk and underutilization without wading through spreadsheets.

The Utilization Heatmap

Navigate to Project → Utilization to see the capacity heatmap. Each row is a team member; each column is a day. The cell color represents how much of that person's daily capacity was logged on that day.

Heatmap Color Key

Idle (0%)

No hours logged that day. The resource may be on leave or unallocated.

Low (1–49%)

Underutilized — the resource has significant available bandwidth for additional work.

Optimal (50–99%)

The sweet spot. The resource is productively engaged without risk of overload.

Overloaded (100%+)

Logged hours exceed daily capacity. Sustained overloading is a burnout risk.

How Capacity Is Calculated

Each team member's daily capacity is derived from their Capacity (h/wk) setting in Project Settings → Team. Klority divides this by 5 (working days) to get a daily target.

Utilization Formula


Daily Utilization % = (Hours Logged That Day / Daily Capacity Target) × 100

Example: If a developer's capacity is 40h/wk (8h/day) and logs 10h in a day, their utilization is 125% — shown in orange as overloaded.

ℹ️

Capacity Must Be Set

The utilization calculation requires a non-zero Capacity (h/wk) to be configured for each member in Project Settings. Without it, the denominator is zero and utilization cannot be computed.

Reading the Heatmap

Use the heatmap to answer common resource management questions:

Who is overloaded?

Look for a row with several consecutive orange cells. This person may be a single point of failure or at risk of burnout. Consider redistributing tasks or adjusting their sprint commitment.

Who is on "The Bench"?

Rows that are mostly empty (dark/idle) indicate underutilized team members with available capacity. Ideal candidates to absorb new work or assist overloaded colleagues.

Was the sprint realistic?

If the entire team shows orange for the last week of the sprint, it may indicate sprint over-commitment — a signal to recalibrate velocity for future sprint planning.

Filtering and Date Range

The heatmap defaults to the last 30 days. Use the date range picker to zoom into a specific sprint period, billing month, or any custom time window. All logged time (including time logged against tasks completed in prior sprints) is reflected accurately.

Utilization vs. Financials

The Utilization tab shows hours logged relative to capacity. It complements the Financials tab which shows the cost and revenue impact of those same hours.

📊 Utilization Tab

Answers: "Is my team working at the right pace? Who is overloaded or idle?"

💰 Financials Tab

Answers: "Is this project profitable? How much have I spent, and how much am I billing?"

Tips for Effective Capacity Management

Set accurate capacities: Ensure each team member's h/wk reflects their actual availability on this project (e.g., 20h/wk for a half-time resource).
Review weekly: Make the utilization heatmap part of your weekly project sync. Catching overload early prevents burnout and missed deadlines.
Compare with Financials: A highly utilized team that's generating low revenue may indicate your billing rates are too low — a signal to renegotiate the contract.
Use with Monthly Per Resource billing: Utilization data helps you justify resource quantity in client conversations ("Your dedicated team logged X hours last month").