Role
Staff for skill and margin — not availability theater.
Capacity, allocations, skills, and demand-supply — the same guardrails whether people are staffed on a project or the support queue.
Capacity · this week
Utilized
87%
Over allocated
3
Available
11
Where it actually helps
The bench is invisible until it’s too late.
A capacity heatmap shows who’s free, overloaded, or about to roll off — across projects and the support queue.
Over-allocation is discovered in standup.
Over-allocation thresholds and soft/hard allocations flag a conflict before it gets scheduled, not after.
Skills live in a spreadsheet nobody updates.
A skills matrix and demand-supply view match the right person to the right engagement — including support rotations.
Questions
Before you ask.
Does resourcing cover ticket staffing, or just projects?
Both. The same capacity view covers project allocations and skill/load-aware ticket routing, so staffing isn’t split across two systems.
How do placeholders work before I’ve hired?
Allocate a placeholder role, then swap in a named person once they’re hired or assigned — the allocation history carries over.
Do allocation changes need sign-off?
Yes, when you want them to — allocations can route through the same approval flow as time and expenses.