Compliance

Compliance is where Onyx records the checks drivers and staff complete on their handset — the Driver Test (fitness for duty), the pre-start on each vehicle, and anything else you define — and the faults those checks find.

It has its own section in the sidebar, COMPLIANCE, with five pages:

Page	What it answers
Overview	Who is overdue, who is blocked, which trucks are grounded, what failed today. Start here each morning.
Checks	What each check asks, when it comes due, and what happens if it is skipped or failed.
Submissions	Every completed check and every answer in it, plus which questions fail most.
Defects	Faults a check found, worst first, and their status until someone closes them.
Overrides	Temporarily relax a check — with a reason and an expiry, on the record.

The checks Onyx starts with

Six checks are set up and live, carried over from iDrv4:

• Driver Test (DRIVER-FFD) — the driver’s fitness for duty.
• Vehicle Pre-Start Check (VEHICLE-PRESTART)
• Rigid & Ute Pre-Start (RIGID-PRESTART)
• Trailer Pre-Start (TRAILER-PRESTART)
• Forklift Pre-Start (FORKLIFT-PRESTART)
• Staff Fitness for Duty (STAFF-FFD) — for warehouse and office staff on the staff app. It is never put in front of a driver.

Words used on these pages

• Check — a set of questions with rules for when it is due. Each check has numbered versions; only one is live at a time.
• Submission — one completed check. Its outcome is worked out by Onyx from the answers. The handset cannot claim a pass.
  • pass — nothing failed.
  • pass_with_defects — every critical question passed, but something was raised that needs fixing.
  • fail — a critical question failed, or a required one was not answered.
  • abandoned — started and not finished. It is kept, not deleted.
• Critical question — one wrong answer fails the whole check.
• Defect — a fault raised by a failed answer. Severity is minor, major or critical. A driver can raise the severity of a fault they report, but cannot lower it.
• Enforcement — what an outstanding check costs: stop the work (block), warn the driver, or just record it (the office sees it, the driver does not).

What actually stops work

• A check set to stop the work that is due and not done stops the driver in the app until they complete it.
• A truck with an open critical defect (status open, acknowledged or in repair) cannot start a run. The driver app refuses the start. Deferring or closing the defect lifts the block.

Who can change things

Operations and Admin users can create and publish checks, update defects, and put overrides in force. Other users see the pages read-only, without the edit buttons.