Runs and sign-off

Available onBuilder

A run is one performance of a checklist, on one job, on one day. It is the thing that has evidential value.

Starting one

Pick the template and the job. The run belongs to that job, and appears in its list of outstanding checks.

Most runs are started and completed on the phone, on site. See Checklists and incidents.

Working through it

Answer each item. Items that require a photo will not accept an answer without one, and the run cannot be closed out until they are all answered.

That is deliberate. A half-finished run is not evidence of a check; it is evidence that somebody started one.

Failing an item

A Fail is more useful than a pass, and it should not be avoided.

The point of a check is to catch things. A run with everything passed on a job where something was clearly wrong is worse than useless — it is a document that says the problem was inspected and approved.

When something fails, say what and where in the text or the photo. Then deal with it:

Raise a defect if it needs fixing by a trade
Raise an incident if it is a safety matter
Re-run the check once it has been rectified

Re-running is the right move rather than editing the original. Two runs — one failed, one passed, with dates — is the honest record and shows the process worked.

Closing out

Close out collects a signature on the device and finalises the run.

Stored together: the answers, the photos, the signature, and when each was captured. That combination is what makes it a record rather than a form.

What a closed run is worth

Concretely: it is the document you produce when somebody asks whether a check was done.

A client disputing workmanship that was signed off
An insurer after an incident
A regulator asking about safety process
A subcontractor claiming the work was accepted

In each case the useful thing is not that a check exists in your system. It is that this specific check, on this date, with these photographs, was signed by a named person at a recorded time.

Reviewing runs

The runs list shows what has been done and what is outstanding, filterable by category and status.

Two things to look for:

Outstanding runs on stages already passed. A pre-pour check still open on a slab that was poured last week is a gap in the record that cannot now be filled.

Runs where everything always passes. Consistently perfect results usually mean the checklist is being ticked rather than performed, and that is worth knowing before somebody else discovers it.

Copying a run’s outcome forward

Where a check is repeated — a weekly safety walk — each week is its own run. Do not reuse one and edit the date. The timestamps are the point, and a run whose photos predate its signature by a fortnight is worth less than nothing.