Team availability for the next two weeks ​

Cadence: Weekly, or ad hoc · Who: Managers and Owners

Situation ​

A prospect asks if you can start a new project next month. A PM needs to pull someone onto an urgent piece. You need to know who has real capacity — not who looks free on a calendar, but who has unallocated hours after accounting for their current commitments and any time off.

In the console ​

Open Capacity (/console/capacity). The heatmap is one row per person, one column per week — each cell is committed vs available hours for that week, colour-banded so over-commitment is obvious at a glance. Prev/Next slide the window; click a person for their per-project burn. Above the heatmap, a By discipline card rolls up this week's free hours per discipline and flags when that slack is fragmented — spread across people with no single full day open, so it can't absorb a real task.

What you see ​

A table, one row per person:

| Name | Discipline | Committed hours | Available hours | Remaining | OOO in window |

  • Committed hours is the prorated share of their current allocations that falls in the two-week window, not the lifetime total. This is the important bit — envelopes are project-lifetime, but this play tells you what lands in this window.
  • Available hours is the window capacity net of time off already approved
  • Remaining = Available − Committed. A negative number means over-committed.

Sorted: most remaining capacity first.

Any person whose commitments include envelopes without a project deadline is flagged — their window share is an estimate based on a 12-week rolling horizon.

Who can run it ​

Managers and Owners. Availability is hours only — no cost or billing figures — so both Managers and Owners see the whole team's capacity.