Capacity

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

How a cell is computed

For each (person, week):

capacity  = 40h − full-day company holidays − approved PTO in that week
allocated = sum of each project's allocated_hours, spread evenly across the
            workdays of the project's start_date → end_date that fall in the week
tracked   = hours actually logged by that person in that week (local calendar week)
free      = capacity − allocated (never below zero)

• Workdays only. Allocation is spread over Mon–Fri, skipping full-day company holidays, so a two-week project loads exactly the two weeks it runs in — not a thin smear across the whole horizon.
• Holidays inside PTO count once. If someone is on PTO over a company holiday, the holiday isn't subtracted a second time.
• Week in progress (*). The current week's utilisation is measured against the workdays already elapsed, not the whole week — otherwise everyone looks idle on Monday morning. A * after the tracked figure marks that week.
• Who's on the grid. Staff logins only; non-staff accounts (contractors' portal logins, service accounts) and personal/non-project time are excluded.

Reading the grid

• Red cell — allocated exceeds that week's capacity. Over-booked.
• Green cell — under-utilised.
• Default (white) — healthy zone.
• Tooltip on hover — the full arithmetic for that cell: capacity (40 − holidays by name − PTO), free hours, paused-project hours, and each contributing project with its hours.
• ⏸ paused — a small line under the cell when the person has hours on an on_hold project that week (see below).

Free column (right-most)

Free in Nw totals the hours still going spare across the whole horizon and names the first week with at least 8h free ("free from 6 Oct"). "Booked solid" means no week in the horizon clears that bar. This is the column to read when the question is "who can take on more work in October?"

Horizon picker

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

Paused (on_hold) projects

Hours allocated on paused projects are listed but not counted by default — they show as ⏸ Nh paused in the cell and don't push anyone into the red. Click Count paused projects (top right of the chip strip) to include them, e.g. when deciding whether restarting a project would overload someone.

Projects that can't be placed on the grid

If a project has allocated hours but no usable start/end dates, there's no way to know which weeks it loads. Those projects appear in a yellow "N projects can't be placed on the grid" card above the grid, with the hours, the people affected and the reason. Add the dates on the project's edit page and they'll drop into the grid.

Where the allocations come from

• Project allocations — a manager assigns a person to a project at /projects/<id> and sets allocated_hours. That's the per-project total; capacity spreads it across the project's workdays.
• Holidays — Holidays (admin-entered or pulled from the shared M365 calendar).
• PTO — approved requests in PTO.

Scope

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

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.