CleanCore · Workforce
Induction and competency, checked by the roster
One register for every worker’s induction, policy acknowledgements and competencies — and a roster that refuses anyone whose mandatory items are outstanding.
The problem this solves
The compliance question is never "do we have an induction process". It is "was the person who cleaned that ward on Tuesday inducted, and can you show it". A register nobody checks at the point of rostering answers the first question and not the second.
CleanCore keeps induction, policy acknowledgement and competency together per worker, and puts the check where it bites: the roster will not place someone whose mandatory items are outstanding.
It also closes the loop the other way. A non-conformance resolves to the cleaner, their induction and their competency record — so a cause that repeats becomes a training decision with evidence behind it rather than a conversation.
Worked example
The same defect type comes back three times at one site.
- 1
The findings resolve to people
Each non-conformance traces to the clean it is about and the worker who performed it.
- 2
Their record is already there
Induction, the policies they have acknowledged and the competencies they hold — in one register rather than three systems.
- 3
The gap is visible, not inferred
A missing competency or an unacknowledged procedure is a row, not an impression.
- 4
The roster enforces the outcome
Until the mandatory items are complete, the roster does not place them.
Quality data turns into a training decision you can evidence, which is what a tender is asking for when it asks about continuous improvement.
Capabilities
What workforce gives you
All 2 of these are in the product today. Each one names what it is built on.
Induction and onboarding register
LiveEvery worker’s induction, policy acknowledgement and competency in one register, with the roster refusing anyone whose mandatory items are outstanding.
Complaint traced back to training
LiveA non-conformance resolves to the cleaner, their induction and their competency record, so a repeat cause becomes a training decision rather than a conversation.
What backs these claims
Each capability names the decision record, module, route or table it is built on. Ask us for any of them in an evaluation and we will walk you through the code.
- Induction and onboarding register
- ADR 0053 · imss_onboarding_programmes · evaluateOnboardingGate
- Complaint traced back to training
- ADR 0053 · src/scripts/imss-maintenance/seed-workforce-qms.ts
Where this sits
Back to
CleanCore — every capability in one place
The whole module: what is live, what is committed, what is only on the roadmap.
Read next
A SWMS sign-on that actually blocks the work
A cleaner cannot start or complete work at a site with an unsigned mandatory SWMS. WHS Regulation 2017 (NSW) cl 299 as a control, not a document in a folder.
Twenty minutes on a real contract.
Real data, four logins, nothing typed on the day — including the parts we have not built, which we will point out ourselves.