From daily work to proof that holds.
We built HAVTO because the people who run real work on real sites carry the risk twice: once when the work is done, and again when someone asks them to prove it. Everything here is built for that second moment.
Mobile — the field
Incidents, checklists, JSA sign-on, PPE and vehicle checks, timesheets and visitor flows — built for a phone on site, offline when the signal drops, and synced when it returns with nothing lost and nothing doubled.
Tablet — the supervisor
On site, but not on a phone. Supervisors assign checklists, work the approval queue, and run inspections and visitor sign-in with the list and record side by side. In kiosk mode the tablet locks to one job and resets after each use.
Web — the authority
Configuration, org administration, investigation closure, officer verification, and the regulatory steps that must stay authoritative. Operational command happens here.
Together — one loop
One system, one set of rules. What the field submits is what the office sees — a notification opens the exact record, and lists refresh the moment a phone syncs.
| No. | State | What moves it on |
|---|---|---|
| 01 | Incident raised | Captured on mobile, on site — offline-safe |
| 02 | Corrective action assigned | To a named person, with a due date |
| 03 | Fix verified with evidence | A supervisor confirms — not just marked "done" |
| 04 | Learning published | Distributed to the relevant teams by name |
| 05 | Workers acknowledge | Per-version acknowledgement recorded |
| 06 | Loop closed | The chain proves itself, end to end |
Nothing is recorded as done unless the audit trail and the evidence behind it were written too.
Practical completion shouldn't be a week of PDF hunting.
The client wants one pack; the team has twelve folders. HAVTO indexes and links documents where they already live and rolls them up through sites into the project — so the pack assembles itself out of work your crews and office already did, and is ready before anyone asks for it.
What the standard said
The guidance HAVTO held at the time, recorded as exactly that: what our library referenced, not a claim about which standards were in force. The pack says which it is.
What actually governed the work
The values really in force on that record — our default, or your override — kept as a permanent entry that cannot be edited away. This is the part that carries weight in an audit.
| No. | Group | When it matters | What sits here |
|---|---|---|---|
| 01 | Proof that holds up | When contested | A trail nobody can quietly edit | officer due-diligence attestations against your region's duty — HSWA s44(4) in NZ, WHS Act s27(5) in AU | Pattern Intelligence across modules | statutory payment claims for the NZ Construction Contracts Act and all eight Australian security-of-payment regimes | high-risk permits countersigned by more than one supervisor | a pack the recipient can verify themselves |
| 02 | Oversight and audit | Under audit | Records that know their own basis, and notice when guidance moves away from your settings | three layers of audit history | regional rules with analytics and a violations queue | an AI summary of the pack with anomaly detection | scheduled delivery | a coverage statement that admits what is missing |
| 03 | Everyday safety work | Day to day | Incidents, corrective actions and risk | training and induction | policies with per-version acknowledgement | emergency procedures | seven specialist safety guides | checklists and the Verify & Learn loop | visitors | vehicles, equipment and PPE | projects | permits and JSA | time and attendance | contractors | competency | fatigue |
| 04 | The platform itself | Every login | Safety & Evidence Overview | My Work | incident assignments | the readiness hub | standards status | risk configuration | calendar integrations | AI Help, complimentary on every tier | desktop app |
Everyday safety work is where most of the day goes. The first two groups are why the record still holds when someone questions it a year later.
Essentials
We record- Incidents & investigations
- Risk & hazard register
- Training & induction
- Policies & procedures
- Corrective actions
- Sites & locations
- Evidence reports
Operational Pack
We run daily safety- Safety checklists & audits
- PPE management
- Visitor management
- Vehicle inspections
- Equipment inspections
- Custom business rules
Project Pack
We assemble handover-ready records- Projects command centre
- Work permits & JSA
- Host contractors
- Time & attendance
- Fatigue management
- Project Evidence Pack
Guidance built into every module.
Inspection intervals, thresholds, and checklist defaults are preset per standard — AS/NZS 3760, 1891, 4024, 1715 and 2210 among them. Override any value for your organisation and the change is recorded. HAVTO provides the defaults and the evidence trail; the decision stays yours.
It fills in your report from what you say.
Not just transcription. Speak what happened and HAVTO drafts the structured report — the right fields for the right module. If voice is not working, every form can still be filled by hand, and the draft is yours to check before it is saved. AI assists; a person owns the record.
“HAVTO is a compliance spine — not your ERP or document library. You keep your job systems where they belong; HAVTO registers, links, and exports the compliance story.”
Ready to see it in action?
Start a 14-day Project Pack trial — full access, all modules, no credit card. Or talk to people who understand AU and NZ H&S guidance and configuration.