The digital pre-start: putting safety before the timer

Every trade business has a version of the same morning: the crew arrives, the work is obvious, the paperwork is not, and the pre-start form gets filled in at smoko, from memory, after the risky part already happened. Nobody involved is careless. The process is simply shaped wrong: the paperwork trails the work instead of gating it. This post is about what changes when the order is enforced by the tools, and it is a plain-English discussion, not legal advice.

The paper problem

Paper safety forms fail structurally. They live in the ute, not on the person. They get filled in retrospectively, which converts a control into a record of good intentions. They pile up in a folder nobody audits until someone has to, usually after an incident, which is exactly when gaps are most expensive. And they are invisible to the office: nobody in town knows whether this morning's pre-start happened until the folder comes back on Friday.

The gate: no signed form, no timer

The structural fix is simple to say and transformative to work under: the clock-in is gated by the signed form. In ONYX1, a business builds its own form templates, pre-start, permit to work, end of day, gear checks, and marks the ones that gate. If the required form is not signed, the timer will not start. Safety stops being a parallel paperwork stream and becomes the doorway to getting paid for the day, which is the one incentive that never needs reinforcing.

The cultural shift is the point. Nobody has to police the paperwork, because the system will not move without it. The conversation on site changes from 'did anyone do the pre-start' to the pre-start itself: the hazard that is actually present today, the control that is actually agreed. The form gets filled in at the moment it is useful, standing in front of the work, on the phone already in the person's pocket.

Records that keep themselves

• Site reports flow to the office as they are filed, with a nightly roundup email, so town knows the morning happened before lunch.
• The incident register cannot be deleted, by any role. There is no code path that removes an incident, which is what makes it a register rather than a diary.
• Certifications, licences and PPE inspections live in one register with an expiry engine that warns before the date, so a lapsed ticket is a calendar event, not a surprise.
• Reports a business clears for sharing appear in the customer's client portal automatically, which quietly answers the building owner's where-is-the-paperwork question.

What the law asks, in plain English

New Zealand's Health and Safety at Work Act 2015 puts duties on a business to manage risk and to be able to show how it was managed. The practical shape of that for a small crew is evidence: the hazard was identified, the control was agreed, the person on site signed that they understood it, and anything that went wrong was recorded honestly at the time. Software does not make a business compliant, and any vendor implying it does is selling something else. What good software does is make the evidence a side effect of doing the work, so the record exists because the day happened, not because someone remembered the folder.

Rolling it out without a fight

Bring the crew in on the templates: the people who face the hazards write the best checklists, and a form the crew authored is a form the crew signs without grumbling. Start with one gating form on one kind of job, let the habit set for a week, then extend. Keep forms short; a pre-start that takes ninety seconds gets answered honestly, one that takes ten minutes gets answered automatically. And resist the urge to gate everything: the gate earns its authority by guarding the genuinely risky work. The mechanics, form templates, the gate, the registers and the site reports, are at onyx1.co.nz/product/safety.