Demand planning reports

Cards on the entities

They appear in the Reports tab of the respective detail page. Details: Reports tab.

Where	Cards
Demand	Coverage per period · Assignments · Profile gap
OKR, project, value stream, cost centre	Demand from this object · Demand/Planned/Actual · open demands
Value stream (in addition)	Demand, plan and actuals per step — see below
Role	Demand for this role · who performs it and what is free
Person, AI agent	Planned for · utilisation
Competence	Open demands against members holding it

The profile gap is the most interesting: it shows that a numerically covered demand can still have a gap in substance — the hours add up, the skill is missing.

Per value stream step

The value stream carries one card that exists nowhere else: demand, plan and actuals per step. It does not answer “the value stream is 40 hours short” but where they are short — for example “the review step is understaffed while intake is overplanned”. Only that leads to a decision.

Three things worth knowing when reading it:

Direct sub-steps are shown. Without that limit a whole value chain would be pulled into one table.
A step with neither demand nor bookings is omitted. Zero rows hide the two rows that matter.
A step that is booked on without a recorded demand is marked. That is the interesting row: work is happening there that nobody planned — either the demand is missing, or the work belongs elsewhere.

The card is also where it becomes visible that a run demand needs adjusting: if plan and actual effort drift apart over months, the recorded target no longer holds. Nobody adjusts it automatically — booked time measures what was, not what is needed. The decision stays with you.

Dashboard tiles

For everyone — own data, no extra permission

Tile	Question
Planned for	Demand, period, hours
My utilisation	Run and change separately, available capacity
Where I would be needed	Open demands — planning as an offer, not an allocation

These three show exclusively your own data. Same reasoning as for booking: your own planning must never fail on a role assignment.

For leadership — `demand:report`

Tile	Question
Overall coverage	How much is open across all demands
Run vs. change	How much capacity goes into operations, how much into initiatives
At risk	What tipped without anyone changing the plan
Load distribution	How many members below 70%, between 70 and 100%, above 100%

Run vs. change is the figure asked for in every strategy conversation — and it existed nowhere before. A falling change share is the earliest visible warning that an organisation is getting stuck in day-to-day business.

The load distribution deliberately names only bands, not people. It answers “where does it pinch?”, not “whose fault is it”.

For planners — `demand:plan`

Tile	Question
Unstaffed	Demands that are not fully planned yet

The three states that are not zero

This is the most important reading aid for every report here:

Display	Meaning
“not quantifiable”	The demand lacks its start date or quantity. It does not count into totals — and the tile says how many are missing.
“no limit on record”	No capacity is recorded for this member. Not “unlimited” but unknown.
“not reported”	No consumption was reported for an AI agent. roleALPHA does not run agents and cannot measure it.

And for the actuals row: if effort booking is unavailable for the tenant or you lack read access, the row is omitted with a reason. A zero would mean “nothing was booked” — a claim nobody can support.

Demand & Resource Planning — The overview
Resource planning — Backlog, utilisation, at risk
Capacity — baseline, deductions, available — Where the capacity figures come from
AI agents have limits — The two limits of an agent
Reports tab — How the Reports tab works