Alerts & notifications
The chasing does itself.
Expiry alerts set against the credential so the chasing runs itself, email and SMS to a tagged group when something will not wait, and every message kept on the file, sent by the system or sent by you.

Working with PIAGO
How it works
From a date on a record, to somebody actually booking it.

Step 01
The system notices before you do
Expiry alerts are configured against the credential rather than the calendar, with the lead time set by you, so the first to know a ticket is running down is the software rather than the client's gatehouse.
Want to see what would be alerting across your people in the next ninety days?
The full list
Everything in alerts and notifications.
In the app itself this sits under Communications, alongside the mailbox and the SMS log.
Expiry alerts
Set against the credential, as far ahead of the date as you want. Ninety days on the medicals above. The administrative burden of reminding people to renew stops being a person's job and becomes a setting.
Mailbox
Email one person or a whole tagged group, with attachments, from inside the system rather than a personal account, so the send is on the record either way.
SMS
Broadcast what will not wait to people who are not at a desk: a site change, a shutdown call, a credential that lapses this week.
Correspondence history
A complete record of what was sent, to whom and when, held against the person or the job it concerned. Auditable rather than recoverable.
Recipients from the register
The list is drawn from the records themselves, so who gets a message follows from who holds the credential or the job rather than from a contact list somebody maintains.
Roster schedules by email
Send people their own schedule from the job scheduler, so the roster reaches them in a form they can keep rather than a screenshot in a chat.
Bulk without the mail merge
Tag people by project, team or ticket, then message that group and nobody else. Somebody has left a tool on site and every fitter needs to know: one message, no spreadsheet, and no texting the whole company.
Evidence you told them
Where a lapse becomes a question later, the record shows the worker was notified and when, which is a different conversation from taking somebody's word for it.
The difference
What changes when the reminding is not a person's job.
How it usually goes
- Chasing renewals is somebody's recurring calendar reminder.
- The reminder goes to a group chat and everyone assumes someone else acted.
- Proving you told a worker means going through a personal inbox.
- The list of who to contact is rebuilt in a phone each time.
- The one person who does the chasing takes leave.
With GO! Site Ready
- The alert is set against the credential and fires on its own.
- It is addressed to the person who has to book it, by name.
- The message sits on the record with the date it was sent.
- The list comes from the register, so it is right without being rebuilt.
- It keeps running while they are away, because nobody is running it.
Questions about alerts and notifications
We already remind people. Why does this need to be in the software?
Does the worker get told, or just us?
Can we prove a worker was notified?
Is SMS actually useful, or is email enough?
How far ahead should we set the alerts?
The rest of the pipeline
It is one problem, not five.
- Workforce complianceEvery ticket, medical and induction against the worker who holds it.Explore
- Job schedulingWho is going where, and whether they are actually site-ready.Explore
- Equipment managementPlant records and servicing in the same register as your people.Explore
- ReportingSeven reports covering your people, your plant and your tools.Explore
- Alerts & notificationsExpiry chase-ups that run themselves, by email or SMS.Explore
The obligation behind this
Plain-English explainers, free, whether you ever buy anything or not.
Related reading
Worth reading next.
The credentials that expire on a five-year clock, and why they catch everyoneStandard 11, the coal mine workers' health assessment and high risk work licences all run on five-year cycles, long enough to be invisible to any annual compliance review. What that blind spot costs, and how to close it.Read it
Keeping tickets current across a team that works for four clientsLicences, statements of attainment, medicals and site inductions all renew through different bodies on different clocks. Why one list of "tickets" guarantees the wrong lead time on half of them.Read it
Ten questions worth asking a contracting company before they mobiliseThe questions that actually predict whether a contracting company's compliance will hold up, not at onboarding, but in month eight when the person who maintains their spreadsheet is on leave.Read it

See it against your own renewal windows.
Bring the credentials your people actually hold and we will set the alert windows to how long each one really takes to arrange.
14 days, no credit card needed. Or book a demo with Carl
Not the person who signs it off?
Send it to your GM







