Home/Product/People & capacity

People & capacity

Work in the plan with nobody to do it.

Every over-run project has hours that were sold, planned and never staffed. They are visible from week one if anything is looking for them. This is the tab that looks.

Workforce & RACI

Named people, real capacity.

Seven resource rows ship seeded — five waiting for names, two filled in as examples. Each person carries a job role, an hourly rate, a weekly capacity and an allocation to this project.

FieldWhat it meansDefault
RoleMust match the role on WBS tasks exactly — that match is how demand finds a person
Hourly RateTheir cost, used by the budget
Weekly CapacityHours available in a normal week. Seeded rows carry realistic part-time figures rather than a blanket 40varies
AllocationShare of them on this project, as a decimal. 0.5 is half their time0.25
Planned HrsPulled automatically from WBS tasks whose role matches theirs, split by allocation where a role is sharedauto
UtilisationPlanned hours ÷ (weekly capacity × allocation × the real length of your plan)auto
The role match is exact, and that is a feature. A task assigned to "Functional Consultant" and a person whose role reads "Functional consultant" do not match, so those hours land in unstaffed rather than being quietly absorbed. It looks like pedantry until the first time it catches sixty hours of integration work nobody owned.

Four numbers at the top

The workforce view opens with demand, capacity, utilisation and unstaffed hours. Those four together answer the only staffing question that matters at kickoff: can the people we have actually do the thing we sold?

RACI

Exactly one accountable person per workstream.

Responsible, accountable, consulted, informed — per person, per workstream. The tab validates the two rules that make a RACI worth having rather than a grid of letters.

Exactly one A

One accountable person per workstream. Not two, which means nobody, and not zero, which also means nobody. The tab flags a workstream that breaks this rather than letting it ship into a steering pack.

At least one R

Somebody has to be doing the work. A workstream with an accountable owner and no responsible party is an area that will be discussed weekly and progressed never.

Both rules are checked, not just documented. Most RACI matrices are built once in week two and then never validated again. This one is a live tracker, so when a person leaves the engagement the gap shows up as a rule violation instead of as a surprise in month four.

Utilisation

Measured against your plan, not a fixed window.

Utilisation is planned hours divided by capacity across the real length of your project, summed from your own phase durations. A twelve-week engagement is measured over twelve weeks, so it does not report half its true load the way a hardcoded window would.

Someone at 118% across the plan is not busy. They are the reason the date is going to move, and you can see it in week one.

1,842Demand — planned hours from the WBS
1,560Capacity — people × capacity × allocation
118%Utilisation across the length of the plan
212Unstaffed hours — planned work with no matching role

Find the unstaffed hours in week one.

Load your plan and your people and let the role match tell you what nobody owns.