The paperwork is in before anyone picks up a tool.
Say once what a job, a site or a new starter has to have on file. It raises itself, it goes to whoever can actually complete it, and the work waits until the evidence is in.
Science block rewire
Blocked- Client
- Geelong Grammar School
- Site
- 50 Biddlecombe Ave, Corio
You write the rule once. After that it turns up on its own.
A requirement is set up in the office — what evidence, who it’s for, when it’s due and what it holds up — and from then on it raises itself: when a job is created, when someone is crewed onto a stage, when a new starter accepts their invite. Nobody has to remember to attach anything to anything.
An induction a particular builder insists on can sit as a default on that client or that site, and every new job for them carries it from the moment it’s captured.
Onboarding can be aimed at a role — a White Card for everyone in the field, a supervisor sign-off only for supervisors — and promoting someone raises what their new role owes.
Bring in a new requirement mid-year and one action applies it to the people or jobs it fits, all of them or a chosen few, and never twice to the same person.
A new starter gets one welcome listing everything they owe, rather than a separate notice per certificate.
Whoever is best placed to do it is the one asked.
Some evidence is the office’s: insurance, a permit, a supplier’s paperwork. Some is the crew’s: the site induction, the SWMS, the photo of the isolation. The office decides which is which, one requirement at a time, and each obligation is then put in front of the people who can genuinely complete it — and only them.
A requirement handed to the field is completed on the job where it sits, and the job says up front what’s holding it and who it’s waiting on.
Anything sensitive — a police check, a medical — stays manager-eyes-only. Even the person who submitted it can’t read it back.
A new starter can finish everything they owe from a laptop before they’re ever on site, or from the phone once they are.
The office has its own list of what it owes across every job, including an obligation delegated to a role nobody on that job holds.
Science block rewire
Ready to startNothing moves until it’s in.
A requirement can be set to hold the work: the job can’t start, can’t be marked done, or can’t be invoiced until the evidence has landed and been cleared. The hold applies to everyone, office included — and the controls don’t dangle a move that would then be refused. The button isn’t there, and the reason is in its place.
A softer hold lets an owner or admin proceed with a recorded reason. That isn’t waiving it — the requirement stays owed, it just stops holding the work up.
Someone whose own onboarding is outstanding won’t be booked onto work that needs it, and the office is told who was left off and why, by name.
Design your own SWMS, induction or permit as a template — your fixed wording plus the fields a person fills in — and the finished document renders as a branded PDF onto the job, with the client, the site and the date already filled in from the system.
A form still attached to a live requirement can be archived but never deleted, so a document you produced last year still says what it said.
Who it’s for.
The same feature reads differently depending on which end of the business you’re standing at.
The owner
Evidence collected as a matter of course rather than the week before an audit, with a record of who provided it and who accepted it.
The office
One place that says what’s outstanding across every job and every teammate, what it’s holding up, and what’s about to expire.
The crew
The requirements on the job they’re standing on, with the ones that are theirs marked as theirs, and one tap to deal with them.
Next door.
The parts of the system this one hands off to.
Put one requirement on a real job.
Fourteen days. Attach a SWMS to a live job and watch exactly what it holds up.