Contractor compliance

Induction is day one. Compliance is every day after that.

The approval you granted six months ago is only as good as the records behind it. A lapse should be surfaced, not discovered at the gate — so requirements are worked out per role, evidence is held as dated records, and a schedule you set does the chasing.

Book a Demo

Coal handling infrastructure silhouetted at dusk on an Australian mine

Working with PIAGO

Customer stories

How it works

How a ticket goes from required, to current, to chased.

Step 01

Requirements follow the person

A training needs analysis works out what a worker must hold from the role, crew and employment type they are actually in. Move them and the requirements move with them — nobody maintains a master list of who needs what.

Want to see what would be expiring across your workforce this month?

Book a Demo (07) 3251 2468

The full list

Everything in ongoing compliance.

Live compliance per worker

Open any worker's profile and see their status right now — which qualifications are required, which are current, which are approaching expiry, which have lapsed. No report run needed.

Expiry alerts you configure

Set the review windows that suit your operation — 90, 60 and 30 days is a common pattern — and choose who hears about them. Workers can be notified directly.

Renewal workflows

Re-upload new evidence, redo an online course, or carry unchanged evidence forward when only the dates move. The record updates in place and every change writes history.

Change-driven re-qualification

Change a worker's role, crew or employment type and the requirements recalculate. A new mandatory requirement resets the profile for re-approval.

Bulk validity changes

When a skill's validity period changes, change it once at the skill rather than worker by worker, and every holder updates.

Termination and re-hire

Archive a worker and their site-specific qualifications expire immediately, with the access system updated at once. History is preserved if they come back.

Where you see it

Three views of the same records.

The individual training profile: One worker, everything they hold, and what is required of them.
The skills matrix: The whole workforce against the requirements of their roles, in one grid.
Compliance reports: Run on demand or on a schedule, and exportable for an audit.

All three read the same records.

There is no separate compliance database kept in step with the training one — the matrix, the profile and the reports are three ways of looking at the same evidence.

The difference

What changes when the records age themselves.

How it usually goes

The spreadsheet is only as current as the last person who updated it.
A lapse is discovered at the gate, or by an auditor.
Someone moves crew, and nobody re-checks what they now need to hold.
A ticket’s validity period changes, so every holder is edited by hand.
Somebody leaves, and their card still works on Monday.

With GO! Site Approved

Every record carries its own expiry date, so the status is always current.
Scheduled reports surface what is close to lapsing, on a cadence you set.
Change a role or crew and the requirements recalculate on their own.
Change the validity once at the skill, and every holder updates.
Archive a worker and their site qualifications expire immediately.

Questions about ongoing compliance

We track this in a spreadsheet and it works. What are we missing?

Usually two things. A spreadsheet is a snapshot of the moment somebody last updated it, so it cannot tell you a ticket is about to lapse — you have to remember to look. And it holds what someone typed rather than the evidence itself, so in an audit it proves that a cell said something, not that a qualification was current. Where spreadsheets fail is rarely the maths; it is the day the person who maintained it is on leave.

Does it warn us before something expires, or do we have to look?

Both, and the distinction matters. A worker's profile always shows current status without running anything. For chasing, you configure expiry alerts and scheduled reports — set the windows and the recipients once, and the schedule surfaces what is approaching expiry on a cadence rather than waiting to be asked.

What happens when someone changes role or crew?

The requirements recalculate for the role they are now in. If the new role carries a mandatory requirement they do not hold, the profile resets for re-approval rather than quietly carrying the old approval forward.

A ticket's validity period changed. Do we re-do every worker?

No. Validity is a property of the skill, so you change it once and every worker holding that skill updates.

What happens to access when we terminate someone?

Archiving a worker expires their site-specific qualifications immediately and updates the access system at once, rather than leaving a live card attached to somebody who has left. Their history is kept in case they are re-hired.

The rest of the pipeline