Work allocation
Competency-based work allocation with fair workload distribution
Allocation answers one question honestly: who is genuinely allowed and able to do this work right now? The answer is assembled from department, presence, qualification and capacity — in that order — and it is recomputed rather than remembered.
Department first
Work belongs to an owning department. Employees are considered through their department memberships and staffing seats, not through an open pool of everyone.
Attendance, fail-closed
If presence information is missing or out of date, the employee is not offered new work. Stale data is treated as unknown, never as available.
Qualification gate, hard
If the task requires a competency the employee cannot evidence, allocation stops. There is no override that lets missing documentation pass the gate.
Capacity and workload
Allocation respects concurrent work limits and distributes workload across eligible people, with deterministic ordering so the same inputs always produce the same result.
Attention protection
Work that keeps being passed over is protected from starvation and escalated rather than sitting unnoticed at the bottom of a queue.
Explainable holds
When work is not allocated, the reason is recorded and shown to managers — an unmet competency, an inactive employee, or a task that cannot activate.
Why 'fail-closed' matters operationally
What the employee sees
Allocation is invisible to the person doing the work. They open their work queue and see current work, next work and what remains — including training work, which is treated as real work with real measured time.
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.