Skip to content
PIAGOGO! Site Ready

Job scheduling

A roster is only as good as who can actually work.

A scheduler built for office shifts cannot tell you whether the person you just assigned is cleared for that site. The roster and the compliance status sit in one view, so what you build is a team that can actually mobilise.

The GO! Site Ready job scheduler, with people and equipment booked across a week of sites

Working with PIAGO

  • Frontline Equipment Maintenance
  • BRW Transport
  • Hydrapower
  • Kerembla
  • Premier Plant Repairs & Fabrication
  • Whiteman Welding
Customer stories

How it works

From an empty week to a team that can mobilise.

The job scheduler, timeline month

Step 01

One timeline, not four calendars

Your whole team on a single board by day, week or month, coloured by worksite. Who is where, who is free, and what is already committed — without opening a second system to find out.

Want to see your own sites and shift patterns on the board?

The full list

Everything in job scheduling.

Visual job scheduler

Your whole team's schedule on one live board, by day, week or month, colour-coded by worksite so you can see who is where at a glance.

Compliance checked as you schedule

The requirements of the client's site are read as you assign somebody, so the roster you build is one that can actually mobilise.

Equipment on the same board

Assign plant to a job alongside the people operating it, held to the same site requirements as the workers are.

Per-occurrence editing

Change a single shift without disturbing the rest of the series, and add notes that belong to that shift rather than the whole job.

Worker logins

People can log in and see their own shifts, job details and what they hold — which takes a surprising amount of chasing off the office.

Schedule notifications

New and updated schedules go out by email or SMS, so a change reaches the person it affects rather than the group chat.

Timesheets

Timesheet status tracked per shift, in the same place as the schedule that created it.

Jobs, worksites and companies

Work is scheduled against the client, the worksite and the job it belongs to, which is also what makes the requirements site-specific.

Across several clients at once

Multiple clients and sites on one board, rather than one board per client and a person holding the overlap in their head.

The difference

What changes when the board knows who is cleared.

How it usually goes

  • The roster lives in a spreadsheet and gets sent round as a screenshot.
  • You find out the person you rostered is not cleared on the morning.
  • The machine is booked in somebody's head, or on a whiteboard.
  • A shift changes, and whoever missed the message drives to the wrong site.
  • Timesheets are chased separately, after the fact.

With GO! Site Ready

  • One live board, by day, week or month, coloured by worksite.
  • Compliance for that site is checked as you assign them.
  • Plant is assigned to the job beside the people operating it.
  • The change goes out by email or SMS, and it is in their own login.
  • Timesheet status sits against the shift it belongs to.

Questions about scheduling

We already have a scheduling tool. Why change?
Most schedulers are very good at deciding whether somebody is free. What they cannot tell you is whether the person you just placed is cleared for that particular client's site — so they will happily let you build a roster that cannot mobilise, and the first time anybody finds out is at the gate. That check is the difference here, not the calendar.
Can we schedule equipment as well as people?
Yes, on the same board and against the same job. That matters because sending a cleared operator with a machine that is overdue for service is still a turnaround — the pairing is what a site actually assesses.
Somebody's ticket lapses mid-roster. What happens?
The lapse surfaces against the shifts it affects rather than waiting to be discovered, and the alerts run ahead of the expiry date so in most cases you are moving a renewal rather than moving a person.
How do our people find out about their shifts?
Schedules go out by email or SMS, and workers can log in to see their own shifts and job details. Both, in practice — the message gets attention and the login is what they check on the drive.
Can we change one shift without rebuilding the series?
Yes. A single occurrence can be edited on its own, with its own notes, and the rest of the series is left alone.
We work across several clients. Does it handle that?
That is the normal case. Jobs are scheduled against the client, the worksite and the role, so several clients sit on one board and the requirements stay specific to whichever site the shift is at.

See the board with your own sites on it.

Bring a fortnight you have actually had to roster and we will build it on the call.

Not the person who signs it off?

Send it to your GM