Capacity

/team/capacity (Team → Capacity tab) shows allocated hours per person per week for the next 6–12 weeks. It's the present-tense companion to Utilization (past) and Scenario (future).

How a cell is computed

For each (person, week):

allocated = sum(project_assignment.allocated_hours pro-rated for that week)
tracked   = sum(work_event.minutes / 60 for that person, that week)

Weekly capacity = 40 hours = 100% (holidays not yet subtracted — coming).

Reading the grid

• Red cell — allocated > 40h for that week. Over-booked.
• Green cell — 0 < allocated < 20h. Under-utilised.
• Default (white) — 20 ≤ allocated ≤ 40h. Healthy zone.
• Tooltip on hover — shows the project list contributing to that cell's allocation.

Horizon picker

The chip strip at the top toggles between 4 / 6 / 8 / 12 week views. Default 6.

Where the allocations come from

• Project allocations — manager assigns a person to a project at /projects/<id> and sets allocated_hours. That's the per-project total — capacity pro-rates it across the project's start_date → end_date.
• No tasks yet? — capacity will show the project-level total but no task breakdown.

Scope

Same as the rest of /team/*: managers see themselves + direct reports, admins see the whole company.

What's coming (Tier 1 holidays)

Company-wide holidays (entered manually by admin or pulled from a shared M365 calendar) will reduce that 40h baseline per cell. So Christmas week shows available = 32h instead of 40h, and over-allocation flags trigger sooner. Personal PTO (Tier 2) is a later upgrade.

When this view can't help

• For a single project's capacity, use the project detail page's Team panel.
• For "what if I re-allocated", use the Scenario planner.
• For past performance vs target, use Utilization.