Skip to content

CleanCore · Compliance & safety

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.

Book a demo See pricing

The problem this solves

Safe Work Method Statements are usually implemented as paperwork: a document exists, a signature is collected somewhere, and an auditor is shown a folder. None of that prevents an unsigned worker starting a task.

CleanCore puts the gate in the path of the work. The refusal happens at the moment a task is started, it carries the document that is missing so the phone can deep-link straight to it, and completing is refused the same way — a gate on "start" alone is one a worker walks around by pressing the other button.

Behind it, documents are controlled rather than merely stored: versioned, issued, acknowledged, and a revision moves the pointer so yesterday’s sign-on stops satisfying today’s requirement. Every write is sequenced and hash-chained per organisation under a uniqueness constraint, so tampering is detectable rather than merely discouraged.

Worked example

A cleaner opens the round runner and taps start on a bus interior clean.

  1. 1

    The start is refused

    Not with a warning banner — the task does not start, and the refusal names the mandatory SWMS that is unsigned.

  2. 2

    The refusal carries the document

    The phone deep-links to the sign-on screen for that exact document, so the fix is one tap rather than a search.

  3. 3

    They sign on, and start

    The sign-on is logged against the document version in force at that moment.

  4. 4

    Completing is gated too

    The same check runs on completion, so the gate cannot be avoided by starting elsewhere and finishing here.

The control is the software, and the audit trail behind it is the evidence that the control ran.

Capabilities

What compliance & safety gives you

All 3 of these are in the product today. Each one names what it is built on.

SWMS sign-on that actually blocks work

Live

A cleaner cannot start or complete work at a site with an unsigned mandatory SWMS. WHS Reg 2017 (NSW) cl 299 as a control, not a document.

First included in the Pro tier

Controlled documents and acknowledgement

Live

Policies, procedures and SWMS versioned, issued and acknowledged, with a revision moving the pointer so old sign-ons stop satisfying.

First included in the Pro tier

Hash-chained audit trail

Live

Every write sequenced and chained per organisation under a uniqueness constraint, so tampering is detectable rather than merely discouraged.

First included in the Starter tier
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.

SWMS sign-on that actually blocks work
ADR 0053 · bus-cleaning-tasks/PATCH.ts swmsGate
Controlled documents and acknowledgement
ADR 0053 · imss_controlled_documents
Hash-chained audit trail
src/server/imss-audit.ts · uq_imss_audit_events_org_sequence

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

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.

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.

Book a demo See pricing