Reports tab
An entity’s detail page (role, project, OKR, value stream …) gains an extra Reports tab as soon as other domains have something worth charting about that entity. The cards present key figures as meaningful diagrams rather than raw tables.
When does the tab appear?
Section titled “When does the tab appear?”The Reports tab (in expert mode: a dedicated Reports section below the other sections) is only shown when reports actually exist — i.e. when at least one card returns data. If there is nothing to show, the tab stays hidden; an empty “Reports” tab never appears.
Whether a card shows up depends on:
- the contributing service being enabled for your tenant (e.g. effort booking),
- that service being subscribed — enabled and subscribed are two different things: a service that is enabled but whose item was removed in the Platform Admin no longer contributes a card,
- available data for the open entity,
- your permission to view that report.
A service that is not subscribed is never even queried — so no data reaches your browser either.
Which cards exist today?
Section titled “Which cards exist today?”- Logged effort — hours booked against this entity over time, plus the total. Source: Effort booking.
- Plan vs. actual — planned versus actually booked effort for the current period.
- OKR progress — progress of the OKRs linked to this entity (see OKRs and Relationships).
Each domain decides for itself whether it offers a card for the open entity — more cards will arrive over time without changing how you use the tab.
- If a single card fails to load, only that card is flagged as an error; the remaining cards stay visible.
- Reports are tenant-specific and respect visibility: you only see data for entities you already have access to.
Cards from demand planning
Section titled “Cards from demand planning”| Card | Where it appears | What it says |
|---|---|---|
| Coverage | Demand | Per period: demand, planned, open |
| Assignments | Demand | Who takes on how much |
| Profile gap | Demand | Which required competence no assigned member covers |
| Demand from this object | OKR, project, value stream, cost centre | Sum of all demands from this source per period |
| Demand / Planned / Actual | the same | Plan against actually booked effort |
| Open demands | the same | What is still unstaffed on this source |
| Demand, plan and actuals per step | Value stream | One row per sub-step — and marked where work is booked without a recorded demand |
| Demand for this role | Role | How much this role is required |
| Who performs it | Role | Members and their free capacity |
| Planned for | Person, AI agent | Demand, period, hours |
| Utilisation | Person, AI agent | Baseline, available, planned per period |
| Demand for this competence | Competence | Open demands against members holding it |
If a figure is missing, a hint appears — not a zero. If effort booking is unavailable for the tenant or you lack read access, the Actual row is omitted with a reason. A zero would mean “nothing was booked”, and that would be a claim.
Details: Demand & Resource Planning.