Training & competency
Versioned documents, a competency catalogue, server-scored assessments and observed practical sign-off — producing qualification records that hold up.
Training & competency →Training · Competency · Work allocation
Only qualified people get the work.
Unity Logic Task Manager connects employee training and competency sign-off directly to operational task allocation. If the qualification evidence isn't there, the work is held — and everyone can see exactly why.
For operations teams where doing the wrong job untrained is a real risk — not a paperwork inconvenience.
My work — now
In progressUpdate outstanding PODs
Transport operations · System task
Active time00:24:31
Next: Customer callback logReady
Goods-in discrepancy checkGate held
Forklift refresher trainingDue
Illustrative view of the employee work queue.
The problem
Training records and daily work usually live in different worlds
Competency sits in a spreadsheet, tasks sit in another, and attendance sits somewhere else again. Nothing stops an unqualified person picking up the wrong job, and nobody can prove afterwards who was signed off for what.
Qualification is assumed
Work gets handed out by availability and habit. The competency check happens later, if at all.
Records go stale silently
A procedure is revised and nobody is returned to retraining, so the training record describes a document that no longer exists.
Time is reconstructed
Hours are estimated at the end of the day, which makes workload arguments unwinnable in either direction.
How it works
Train → Qualify → Allocate → Execute → Review
One loop, each stage producing the evidence the next stage relies on.
- 01
Train
Version-pinned training assignments
- 02
Qualify
Assessment and practical sign-off
- 03
Allocate
Eligibility, capacity and fairness
- 04
Execute
Queue, sessions and measured time
- 05
Review
Held work, reasons and audit trail
Core capabilities
Real capabilities, described plainly
Each of these is implemented and running in the platform today.
Qualification gates
A hard, fail-closed gate between evidence and work. Missing documentation never grants access; it holds the work and names the gap.
Governance model →Task master
Defined operational tasks with owning departments, competency requirements, readiness states and visible reconciliation of imported source data.
Task management →Work allocation
Department-first eligibility, attendance freshness, the qualification gate, then capacity and workload distribution — evaluated, not assumed.
Work allocation →Employee work queue
Now, next and the rest of the queue, plus Task Companion for people who are not sat in front of a desktop all day.
Employee experience →Measured active time
Start, pause, resume and complete recorded as server-side session events, so active time is measured rather than remembered.
Operational visibility →Integrations
What is connected, and what is not
Nothing on this site is shown as connected unless it is.
Available
Platform-native authentication, private document storage, and the full training, competency, task and allocation modules.
Architecture ready
Unity attendance and presence sync, and AI-assisted assessment drafting. The contracts exist; the providers are not connected.
Configuration required
Customer communication channels. The work trigger is defined, but no communication provider is wired up.
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.