JHA, schedule, evidence, accounting export — one immutable chain of custody per job

For NZ trade and service businesses
JHAs, SDS, assets, and the schedule on one record — so the job you planned is the job you can prove you did. Aviaur is a small-business operating system for NZ trade and service businesses, built around an immutable chain of custody from request to accounting export.
20-minute demo. We're onboarding a small cohort of NZ operators as design partners this quarter — starting with lawn care crews. See the lawn-mowing view →
Not ready for a demo? Tell us what breaks with the tools you use today — we read every response and the roadmap is built against them. Share your struggles →
JHA, schedule, evidence, accounting export — one immutable chain of custody per job
every safety and closeout event hashed and timestamped, append-only after sign-off
transparent pricing — 20% margin on cost, published math, no extractive tiers
The system
Most trades run their business on a calendar, a spreadsheet, Xero, WhatsApp, and memory. Aviaur replaces that stack with four tightly integrated pillars that share a single ledger.
Digital JHAs with template packs for each trade, hazard rules, SDS, and incident reporting — attached to the job, not scattered across drives and inboxes.
Respects real availability, travel feasibility, predecessor/successor work, and who actually holds the competency to do the job. Recurring work auto-populates.
Track equipment, parts, materials used on a job, and what's on the truck.
Every JHA, approval, and closeout is hashed, timestamped, and append-only. If someone asks “was this job done safely, by a competent person, and can you prove it” — you can.
The loop
Every step is attached to the same job record. The JHA is not a PDF on someone's phone; the schedule is not a whiteboard; the week's costing is not reconstructed from memory on a Sunday before you can invoice from Xero.
Request comes in — customer, property manager, or recurring schedule.
JHA + competency gate — right people, right tickets, right controls before work starts.
Schedule — real availability, route density, travel feasibility respected.
Mobile job run — crew sees the job, captures evidence, materials, and time.
Closeout — accounting exports with evidence attached. One record, one source of truth.
Integrity of record
Every JHA, approval, and closeout event is hashed at creation. Append-only after sign-off. Corrections are new entries that reference the original — the original is never mutated.
Get started
Design-partner cohort gets 90 days free in exchange for weekly feedback and real jobs on the system. Founding customers lock in cost × 1.1 for 24 months.

For NZ trade and service businesses
JHAs, SDS, assets, and the schedule on one record — so the job you planned is the job you can prove you did. Aviaur is a small-business operating system for NZ trade and service businesses, built around an immutable chain of custody from request to accounting export.
20-minute demo. We're onboarding a small cohort of NZ operators as design partners this quarter — starting with lawn care crews. See the lawn-mowing view →
Not ready for a demo? Tell us what breaks with the tools you use today — we read every response and the roadmap is built against them. Share your struggles →
JHA, schedule, evidence, accounting export — one immutable chain of custody per job
every safety and closeout event hashed and timestamped, append-only after sign-off
transparent pricing — 20% margin on cost, published math, no extractive tiers
The system
Most trades run their business on a calendar, a spreadsheet, Xero, WhatsApp, and memory. Aviaur replaces that stack with four tightly integrated pillars that share a single ledger.
Digital JHAs with template packs for each trade, hazard rules, SDS, and incident reporting — attached to the job, not scattered across drives and inboxes.
Respects real availability, travel feasibility, predecessor/successor work, and who actually holds the competency to do the job. Recurring work auto-populates.
Track equipment, parts, materials used on a job, and what's on the truck.
Every JHA, approval, and closeout is hashed, timestamped, and append-only. If someone asks “was this job done safely, by a competent person, and can you prove it” — you can.
The loop
Every step is attached to the same job record. The JHA is not a PDF on someone's phone; the schedule is not a whiteboard; the week's costing is not reconstructed from memory on a Sunday before you can invoice from Xero.
Request comes in — customer, property manager, or recurring schedule.
JHA + competency gate — right people, right tickets, right controls before work starts.
Schedule — real availability, route density, travel feasibility respected.
Mobile job run — crew sees the job, captures evidence, materials, and time.
Closeout — accounting exports with evidence attached. One record, one source of truth.
Integrity of record
Every JHA, approval, and closeout event is hashed at creation. Append-only after sign-off. Corrections are new entries that reference the original — the original is never mutated.
Get started
Design-partner cohort gets 90 days free in exchange for weekly feedback and real jobs on the system. Founding customers lock in cost × 1.1 for 24 months.