“We always check the reinforcement” is an assertion. Six photographs at 7:42am is a record.
Two related things live here: checklists, for the checks you repeat on every job, and a safety register for incidents. Both are filled in on a phone by the person standing in front of the work, because that is the only place the evidence exists.
Available on the Builder plan
A template is the checklist. A run is one performance of it.
Template
"Pre-pour check"
The items, what each one asks for, and which of them require a photograph. Built once on the desktop, and used on every job after it.
Run
"Pre-pour check, 18 Beach Road, 28 October, 7:42am, signed by Dave Marsh"
One performance on one job on one day, with its answers, its photographs, a signature and a time.
Checklists do two different jobs
Quality
A pre-pour check, a pre-plaster check, a handover inspection. The value is catching the thing before it is covered up — while fixing it still costs an hour instead of a fortnight.
Compliance
A safety walk, a plant inspection, an SWMS sign-off. The value is being able to show it was done, to whoever asks, months later. This is why every run captures a signature and a timestamp.
Near misses, injuries and damage, recorded and closed out
It sits in the same module because the same people fill it in from the same phone — and because an incident very often has a checklist behind it.
Every entry is recorded, assigned and closed out, so the register answers the question an insurer or a regulator actually asks: not "do you have a policy" but "show me what happened and what you did about it".
Running a check from the site office defeats most of the point
The photographs are the evidence, and they have to be taken where the work is. The desktop builds the templates and reviews what came back; the phone does the part that matters.
Where each part happens
- Building templates
- Desktop
- Assigning a template to a contract stage
- Desktop
- Running a checklist
- Phone, on site
- Capturing photos and the signature
- Phone
- Reporting an incident
- Phone
- Reviewing runs and the register
- Desktop
A closer look at checklists and safety
The template, the run it produces, and the register beside it.
What it connects to
Nothing in SmarteBuild is an island — that is the point of it. Checklists & Safety reads from and feeds into these.
Site Diary
What happened on site today, with the weather recorded for you
Mobile & On Site
The job in your pocket, including where reception is poor
Defects & Handover
Log it, assign it, close it out, hand over clean
Schedule & Gantt
Plan the build, move a date, and see what shifts with it
Want the detail?
The help centre documents Checklists & Safety step by step, with worked examples — written for people using it, not for a brochure.
Start with one job and see
Try the whole thing free for 30 days. No credit card to start, and no lock-in contract.