How jobs work in Aviaur
This is the full end‑to‑end job flow — written in plain English. Aviaur is not a marketplace and it does not employ contractors. It is a shared record and workflow so everyone can see what was requested, what was approved, what changed, and what was completed.
1) A job begins as a record, not a message
A job starts when a customer or property manager creates a job record. This record is the anchor for everything else. It contains the location, the requested work, any access notes, and the service type (what trade or category the work belongs to). If photos or documents are needed, they attach to the same record. This is deliberate: if the job lives in texts or emails, the history is fragile. When the job lives in a record, the history stays connected and retrievable.
2) Scope is agreed before work proceeds
Aviaur supports both quoted work and charge‑up work (time and materials). Regardless of which model is used, the record stores what was agreed and who approved it. That approval step is a protection for everyone: customers can see exactly what they approved; contractors can see that approval is recorded before they proceed. If the work changes later, the variation is captured as a change to scope that is approved before the extra work begins.
3) Scheduling respects real constraints
Contractors define their service area and availability constraints, and scheduling is built around those constraints. This is not a diary that assumes unlimited time; it is a constraint system that prevents over‑promising. Recurring work is stored as a Job Series — a pattern — so repeat visits are predictable and don’t have to be re‑created each time. A schedule that matches reality reduces missed visits and prevents scramble‑mode rescheduling later.
4) Variations are explicit (no surprises)
If a new issue is discovered on site, it must be recorded before the additional work proceeds. That becomes a variation to the job. The variation is attached to the same job record, so the approval trail is clear. This is the single most effective way to prevent “I didn’t approve that” disputes. It also protects contractors when the scope expands beyond what was originally agreed.
5) Safety evidence stays with the job
Safety documentation (including digital JHAs where required) is stored with the job record. Aviaur does not replace legal responsibilities: contractors remain responsible for licensing and working within scope; customers and managers remain responsible for disclosing hazards and providing accurate site information. The platform’s role is to store the evidence and keep it attached to the work so audits and disputes can be resolved without guesswork.
6) Completion closes the record
When the job is complete, the record is snapshotted: what was done, what was approved, what changed, and what evidence exists. Some records are intentionally immutable after completion to preserve audit integrity. If a correction is needed, it is added as an append‑only adjustment rather than a silent edit. This is what makes the job record trustworthy later — for insurance questions, disputes, compliance checks, or portfolio handover.
7) Records remain accessible and exportable
Aviaur is designed for long‑lived records. Jobs, messages, approvals, variations, completion snapshots, and safety artefacts remain linked to the job record. Exports are available for operational reporting and accountability (jobs/time/ledger where available). Records are retained in line with published retention periods; they are kept for accountability — not resale.
What this means for you
If you are a customer, you get clarity: what was approved, what changed, and what was completed. If you are a contractor, you get protection: approvals and variations are recorded before work proceeds. If you are a property manager, you get a durable, repeatable workflow that survives staff changes, disputes, and audits. The system does not remove responsibility from the people involved — it makes the record reliable.
What Aviaur does not do
Aviaur does not choose who you hire, does not employ contractors, and does not set rates. It is not a lead‑generation marketplace and it does not replace licensing or insurance obligations. The platform keeps the workflow and the record together, but responsibility still sits with the people doing and commissioning the work. If you need legal or regulatory advice, you should seek it separately; Aviaur is not a regulator or certifier.
Beta expectations
In beta, you can expect the core workflow — job records, approvals, scheduling, safety documentation, and completion snapshots — to be stable and auditable. You should also expect iteration: we are refining onboarding and documentation based on real‑world usage. If something is unclear, that is a signal we need to improve the system and its explanations. We want feedback from people running actual maintenance work.