SmarteBuild
Running the job New

“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

app.smartebuild.com.au/checklists
The checklists page showing templates on one side and recent completed runs on the other.
Templates on the left, what has actually been done on the right.
The distinction that runs through the module

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.

Worth being clear which one you are doing

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.

Tied to the stage you bill and the task you tick

Link a checklist to a contract stage or a schedule task when you start it. A frame inspection that has not passed is then flagged on the progress claim for that stage, and shows on the schedule against its task, pink when it failed, amber while it is in progress, green when it passed. Ticking the task done asks first.

The safety register

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".

When the regulator has to be told

Tick Notifiable and the incident starts a process. The job’s sign-off people and your administrators get a bell and an email, wherever it was ticked, with the regulator’s phone number for the job’s state. They are reminded an hour later, then daily, until the call is recorded.

  • The incident records the call, who was spoken to, when the area was released and the workers’ compensation report
  • A red strip stays on the Dashboard until the regulator is recorded
  • It cannot be deleted, closed before the call is recorded, or unticked once the regulator has been told

SmarteBuild does not make the call for you. It makes sure somebody does, and keeps the record.

An incident, or a finished checklist, also makes a PDF: open it to send, or save it to the job’s Documents.

One incident open, showing what happened, who it was assigned to and how it was closed out.
Desk and site

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.

A checklist template being built, with items and photo requirements.
Build it once
A completed checklist run with photos, a signature and a timestamp.
A run is a record, not an assertion
The incident register listing near misses and injuries with their status.
The register behind 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.

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.