Skip to content
PIAGOGO! Site Approved

Reporting

Records you can hand to an auditor.

Knowing everyone on your site is compliant is one thing. Being able to show it — at any point in time, for any worker, with dates and names against it — is the thing a spreadsheet cannot do.

A line of haul trucks parked at an Australian mine site

Working with PIAGO

  • Glencore
  • Komatsu
  • Abbot Point Operations
  • Hawkins Group
  • Frontline Equipment Maintenance
Customer stories

How it works

Run it once, or let it run itself.

Step 01

The question is already answered

Compliance across a site or a crew, everything one worker holds, who was rostered but did not show, who came through the gate. Nobody assembles these — they read the same records everything else does.

Want to see the report your auditor actually asks for?

The full list

Everything you can report on.

Compliance reports

Who is compliant, who is not, and what is missing — across a site, a crew or a company.

The skills matrix

The workforce against the requirements of their roles, in one grid.

The individual training profile

One worker, everything they hold and everything required of them, with dates and sign-offs.

Scheduled reports

Set the report, the cadence and the recipients once. It surfaces expiring tickets rather than waiting to be asked.

Exports and formats

Take reports out in the format the audit actually wants, rather than screenshotting a dashboard.

Message templates

Control the wording that goes out with notifications, so what your contracting companies receive sounds like your operation.

The difference

Having the data is not the same as being able to hand it over.

How it usually goes

  • The report is rebuilt by hand every time somebody asks for one.
  • By the time it is finished it describes last week.
  • Two people run the same question and come back with two answers.
  • An auditor asks for the evidence, and you go looking for it.
  • Nobody sees a problem until the month-end pack lands.

With GO! Site Approved

  • Reports read the live records, so running one is not a rebuild.
  • It is current at the moment you ran it, because the records are.
  • One set of records underneath, so the answer is the same either way.
  • Exportable evidence, dated and attributed, ready to hand over.
  • Put it on a schedule and it arrives before anybody has to ask.

Questions about reporting

We can pull a report when we need one. Why schedule them?
Because the reports that matter are the ones nobody thought to run. A report on demand answers a question you already knew to ask; a scheduled one surfaces the ticket expiring in three weeks that nobody was looking for. That is the difference between reporting on compliance and actually managing it.
Can reports run without somebody remembering to run them?
Yes, and that is the point of scheduling. Set the report, the cadence and the recipients once, and expiring tickets surface on that cadence rather than waiting for somebody to ask the question.
What formats can we get data out in?
Reports export for handing to an audit, a client or a regulator. If you have a specific format an auditor insists on, raise it on the demo and we will show you exactly what comes out.
Can workers see their own compliance?
Yes. Worker self-service gives them a view of their own training and compliance — what they hold, and what is coming up for renewal — which takes a surprising amount of chasing off the admin.
Can we change the wording of the notifications that go out?
Yes, through message templates, so what a contracting company receives reads like it came from your operation rather than from a system.

See the reports on your own data shape.

Tell us what your auditor asks for and we will show you the report that answers it.

Not the person who signs it off?

Send it to your GM