Reading the team utilization view

The CapacityIQ Dashboard shows your team's utilization across 5 time horizons. Here's how to read it.

The four cards at the top

When you open CapacityIQ, you see four summary cards:

• Total Capacity — sum of weekly capacity across all members
• Allocated — sum of hours assigned to initiatives
• Available — total capacity minus allocated
• Utilization % — allocated divided by total capacity

If utilization is >100%, the team is over-committed. Time to push back, slip a date, or add capacity.

The team utilization chart

Each row is one team member. For each row:

• Avatar + name
• Capacity bar — colored segment showing allocated vs available
• Hours — allocated / capacity (e.g., 32h / 40h)
• Utilization % — bar fills to this percentage
• Health dot — green / amber / red

Click a row to see what they're allocated to (which initiatives, how many hours each).

Color codes

Color	Range	What it means
Green	60-80%	Healthy, sustainable
Amber	80-95%	Tight; surprises will hurt
Red	>95% or >100%	Over-committed; surprises are now critical
Gray	<60%	Under-utilized; capacity available

The 5 time horizons

Toggle the Daily / Weekly / Monthly / Quarterly / Yearly tabs at the top right.

• Daily — Today + next 6 days. Use for firefighting and urgent escalations.
• Weekly — Default view. Most planning happens here. The "this sprint" view.
• Monthly — Roll-up over 4 weeks. Catches over-commitment that hides in the weekly noise.
• Quarterly — Strategic horizon. "Can the team handle this Q4 commitment?"
• Yearly — Hiring and OKR planning. "Do we need to hire?"

Different horizons surface different problems. Weekly looks fine, but Quarterly might show a 110% load — meaning the team will burn out by week 8.

Filtering

Top-right filter button:

• By team (Mobile / Core / Growth)
• By role (Engineering / Design / PM)
• By initiative (show only allocations to a specific roadmap initiative)

Useful for:

• "Show me just Mobile team capacity for Q3"
• "Show me everyone allocated to the API migration"

Requirements coverage panel

Below the team utilization, the Requirements Coverage panel shows:

• Total estimated effort for committed initiatives (PRD-estimated hours)
• Available capacity for the same date range
• A coverage demand-vs-availability progress bar

If demand exceeds availability, the panel shows a red banner: "Over capacity. PRD-estimated effort exceeds available capacity for this window. Consider extending the timeline or splitting scope."

This is the most actionable metric in CapacityIQ — it tells you if your roadmap commitments are realistic before you ship them.

Per-person workload drill-down

Click a team member's row to see:

• All initiatives they're allocated to
• Hours per initiative per week
• Concurrent initiatives this period (parallelism is a workload signal)
• Time off / vacation periods

Use this when one member's red bar isn't obvious — drill in to see which initiatives are competing for their time.

What to do when you see red

1. Slip a date — push one initiative right by 1-2 weeks
2. Reduce scope — cut a sub-feature; deliver MVP first
3. Re-assign — move work from over-loaded member to under-utilized one (capacity isn't team-fungible, but sometimes it is)
4. Add capacity — bring in a contractor or hire (if quarterly/yearly view shows persistent red)

Next steps

• Capacity check before commitment — the rule that prevents over-commitment
• The 80% utilization rule