Management
Operational visibility built from what the system already knows
Managers do not get invented metrics. They get the operational state the platform genuinely holds: what is ready, what is held, what cannot activate, and where qualification or attendance is the constraint.
- What is held, and why?
- Held work carries its blocking reason: an unmet competency, an employee without current attendance, or a task definition that cannot activate. The reason is part of the record, not a support conversation.
- Who can actually do this work today?
- Eligibility is evaluated per employee against department, presence, qualification and capacity, so the shortlist reflects reality rather than an org chart.
- Where are our training gaps costing us?
- When a competency gap holds operational work, it appears as an operational problem — which makes training prioritisation an evidence-led decision.
- What did we change, and who changed it?
- Manager interventions and work session events are retained as append-only history. Nothing overwrites the previous version of the truth.
What is not claimed
There is no business-intelligence suite, no forecasting engine and no productivity league table. Reporting is limited to the operational state and history the platform records. Live attendance is sourced from the external Unity system, and that connection is configuration-dependent rather than active by default — see security and governance.
See the platform running against real operational tasks
We can walk you through the full loop: a training document, the competency it proves, the qualification gate it opens, and the work that gets allocated because of it.