Compliance & Audit

Compliance built into how you run every job, not how you prepare for an audit.

Comprehensive audit trail on every action. Document management in Azure Blob Storage. Driver and vehicle document expiry alerts. Break and rest recording in the driver app. Contract lifecycle with auto-expiry. RBAC controls who can see and edit compliance records.

Full audit trailAzure document storageExpiry alertsBreak & rest recordingContract lifecycle
Every action
logged with user + timestamp
Azure Blob
secure document storage
Expiry alerts
licences, medicals, rego
Break records
driver app timestamps
RBAC
access control per role
Audit export
management pull logs directly
What compliance means in haulage

Compliance in haulage is not a filing exercise. It is a daily operational requirement.

Haulage operators face compliance obligations across multiple areas simultaneously: driver licences and medical certificates must be current, vehicle registrations and inspection records must be maintained, fatigue and rest obligations must be recorded, contracts and insurance must not lapse, and every operational decision must be traceable. Preparing for an audit by pulling this information together from filing cabinets, email threads and spreadsheets is a sign that compliance is not embedded in operations — it is bolted on afterwards.

HaulageOps builds compliance into the daily operational workflow. The audit trail is generated automatically by the platform — dispatchers do not create it, managers do not maintain it. Document expiry alerts are generated from the records stored in the system. Break records are created by drivers as part of their normal job workflow. There is nothing extra to do to be compliant — compliance is a byproduct of running your operations through the platform.

Audit trail

Every action taken in HaulageOps is logged automatically: job created, driver assigned, status changed, POD uploaded, invoice generated, document uploaded, user logged in. Each log entry records who, what, and when — with no ability to edit or delete log entries.

Document management

Driver licences, medical certificates, vehicle registrations, permits, contracts, insurance certificates and delivery dockets — all stored in Azure Blob Storage, linked to the relevant entity in the system, and accessible to authorised users without searching filing cabinets.

Expiry alerts

Document records carry expiry dates. When a driver licence, medical, vehicle registration or insurance certificate is approaching expiry, the system generates an alert. Operators can act on expiring documents before compliance lapses — not after the fact.

The audit trail

Every action. Every user. Every timestamp. Immutable and immediately accessible.

The HaulageOps audit trail is comprehensive — not selective. It does not require anyone to remember to log an action. Every operation performed through the platform generates a log entry automatically. Management and directors can pull audit logs directly from the system without asking anyone to compile a report.

What the audit trail records

  • Job created — user, timestamp, job details at creation
  • Driver assigned or subcontractor delegated — who made the assignment, when
  • Job status changed — driver or dispatcher, stage, timestamp
  • Rate applied or overridden — user, rate value, timestamp
  • POD captured — driver, type of capture (photo/document/signature), timestamp
  • Invoice generated, sent, paid, or voided — user, action, timestamp
  • Document uploaded — user, document type, linked entity
  • User login and access events — who accessed the system, when
  • Contract created, approved, amended or expired
  • Break period started and ended — driver identity, timestamps
HaulageOps — Audit Log View
JOB-2026-04471All usersAll actionsAny dateExport to CSV
TimestampUserActionDetail
14:32:07M. Clarke (Finance)Invoice GeneratedINV-2026-0847 created from job
14:28:55K. Patel (Dispatch)Job CompletedStatus updated to Completed
13:41:02T. Wilson (Driver)POD CapturedPhoto + customer signature uploaded
13:40:18T. Wilson (Driver)Status: At DeliveryLocation recorded
11:03:44T. Wilson (Driver)Status: In TransitEn route to delivery site
09:17:22K. Patel (Dispatch)Job DispatchedAssigned to T. Wilson
09:12:05K. Patel (Dispatch)Job CreatedClient: Laing O'Rourke, Material: Type 1 Limestone

Chronological from most recent to oldest. Filter by user, action type or date range.

Document management

Driver records, vehicle documents, contracts and dockets — stored in Azure, linked to the entity, accessible to authorised users.

HaulageOps uses Azure Blob Storage for all document storage. Documents are uploaded through the platform and linked to the relevant driver, vehicle, client, contract or job record. Authorised users can retrieve any document directly from the system — no email chains, no shared drives, no filing cabinets.

Driver document records

  • Heavy vehicle licence — stored with class and expiry date
  • Medical certificate — stored with expiry date and alert threshold
  • Induction records — site inductions, safety training completions
  • Any additional certification required by clients or contracts

Expiry alerts are generated ahead of the expiry date so licences and medicals can be renewed before they lapse. A driver record showing an expired licence is visible to management in the driver management module — dispatchers can be prevented from assigning expired-document drivers through RBAC configuration.

Driver Management

Vehicle document records

  • Vehicle registration — stored with expiry date and alert
  • Vehicle inspection records and service history
  • Permits — oversize, restricted access, route permits
  • Insurance certificates linked to fleet records

Fleet document records are maintained in the fleet management module. Expiry alerts for vehicle registrations and permits ensure vehicles do not operate outside their permitted compliance dates. Fleet availability and document status are visible to dispatch when assigning vehicles to jobs.

Document Management

Contract and compliance documents

  • Client contracts — full lifecycle with approval workflow and versioning
  • Subcontractor agreements — stored against subcontractor records
  • Insurance certificates — company-level and subcontractor-level
  • Delivery dockets and POD evidence — stored against job records

Contract management in HaulageOps includes creation, review, approval, versioning and auto-expiry alerts. When a contract approaches its end date, an alert is generated so renewal or renegotiation can begin before the contract lapses — reducing the risk of operating without a current agreement.

Contract Management

Operational delivery evidence

  • POD photos captured by driver at delivery site
  • Scale dockets and weigh tickets uploaded from the driver app
  • Customer signatures captured via the driver app signature pad
  • All POD linked to the specific job record

Delivery evidence is not a separate filing process — it is created as part of the driver's normal job completion workflow. Because it is stored in Azure and linked to the job record, it is immediately accessible to dispatch, finance, management and the client portal without any manual filing or distribution step.

Audit Trail
Break and rest recording

Drivers record breaks in the app. Records are timestamped and stored automatically.

The HaulageOps driver app includes break and rest period recording. Drivers start and stop break periods directly from the app during their shift. Each break is recorded with driver identity, start timestamp, end timestamp and duration. Break records are associated with the driver's work history and are accessible to management without requiring the driver to submit a separate timesheet or logbook entry.

What is recorded

Driver identity, break start time, break end time, duration, date, and which job or shift the break occurred during. All stored in the HaulageOps system and accessible in the management and compliance reporting view.

Relevance to fatigue compliance

Break records provide a structured digital record relevant to fatigue management obligations, including Chain of Responsibility frameworks where operators have duties as schedulers and employers. This supports — but does not replace — your formal fatigue management obligations and procedures.

Important limitation

The HaulageOps driver app is not an Electronic Work Diary (EWD) or Electronic Logging Device (ELD). An ELD/EWD capability is on the product roadmap. The break recording feature provides a digital record within the platform, not a certified EWD output. If your regulatory environment requires a certified EWD, that obligation exists separately.

See: Break & Rest Management for the full detail of how fatigue-relevant records work in HaulageOps.

Access control for compliance records

RBAC controls who can view, edit and export compliance information.

Not every user in HaulageOps should have access to every compliance record. A dispatcher needs to know whether a driver's licence is current — they do not need to view audit logs or contract approval history. A director needs full access to the audit trail without being able to edit operational records. RBAC in HaulageOps enforces these boundaries at the access control level.

Management and director access

  • Full audit trail access — filter by user, job, action type, date range
  • Export audit logs for external review or regulatory response
  • All driver and vehicle document records and expiry status
  • Contract lifecycle status and approval history
  • Driver break and rest records
  • Financial reporting and invoice history

Management can pull any compliance record directly from the system without calling anyone or waiting for someone to compile a report. This is particularly relevant when responding to a regulator request or preparing for a principal contractor audit.

Dispatcher and operational access

  • Driver document status — can see if a licence is current or expiring
  • Vehicle availability and compliance status
  • Job audit trail for jobs they have access to
  • Cannot edit compliance records or audit log entries
  • Cannot access contract approval history or financial audit data

Dispatchers have the operational visibility they need — whether a driver is compliant to work — without access to the broader compliance and financial audit records that are the domain of management.

Related platform features

Compliance connects to these platform areas.

Audit Trail

The comprehensive action log behind every job, user action, document upload and invoice event. Every entry carries user identity, action detail and timestamp. Immutable and exportable for regulatory or contractual purposes.

Audit Trail

Document Management

Azure Blob Storage for all compliance-relevant documents: driver licences, medicals, vehicle registrations, permits, contracts, insurance, dockets and POD. Linked to entities, searchable, and accessible to authorised users only.

Document management

Break & Rest Management

Driver-initiated break recording in the mobile app. Structured digital records with timestamps, accessible to management. Relevant to fatigue compliance obligations — note: not an EWD.

Break & rest management

For operators in Australia: Chain of Responsibility — how HaulageOps audit trail, break records and document management relate to CoR obligations under the Heavy Vehicle National Law.

Frequently asked questions

Frequently asked about compliance and audit in HaulageOps.

Is HaulageOps an Electronic Work Diary (EWD)?

No. HaulageOps is not an Electronic Work Diary and does not provide a certified EWD output. The driver app records break and rest periods with timestamps as part of the normal job workflow, and these records are accessible to management through the platform. This provides a structured digital record of break activity within HaulageOps, but it is not equivalent to — and does not substitute for — a certified EWD under the relevant national heavy vehicle regulations. An EWD/ELD capability is on the HaulageOps product roadmap. If your operation requires a certified EWD, that obligation exists and must be fulfilled separately from HaulageOps.

Does HaulageOps handle NHVR requirements?

HaulageOps is not certified or approved by the National Heavy Vehicle Regulator (NHVR) and makes no claim to satisfy specific NHVR regulatory requirements. The platform provides operational records — audit trail, document storage, break records, driver and vehicle document expiry tracking — that are relevant to Chain of Responsibility (CoR) obligations. These records demonstrate that your business operates with structured processes and documented evidence. Whether those records satisfy a specific NHVR compliance requirement depends on the specific obligation. Operators should take independent legal advice on their CoR obligations and how their system of records supports compliance. See our Chain of Responsibility page for a more detailed discussion.

What records are kept in the audit trail?

The audit trail records every action performed in the HaulageOps system: job creation, driver and subcontractor assignment, job status changes, rate application and overrides, POD capture, invoice generation, sending, payment confirmation and voiding, document uploads, user login events, contract lifecycle actions (creation, approval, amendment, expiry), and break period records. Each entry contains the user identity (name and role), the specific action taken, any relevant detail (job ID, document type, invoice number), and the precise timestamp. Log entries cannot be edited or deleted.

Can I export audit logs for an external audit or regulatory response?

Yes. Audit logs can be filtered by date range, user, job, action type or entity and exported to CSV for external review. Management and director users have direct access to pull and export these records without requiring a system administrator or developer to run a query. This means if a principal contractor audits your operations, or a regulator requests records, you can produce a structured export from the platform directly.

How are document expiry alerts delivered?

Document expiry alerts are generated within the HaulageOps platform. When a driver licence, medical certificate, vehicle registration, permit or insurance certificate is approaching its expiry date, an alert appears in the relevant management dashboard. The alert threshold — how many days before expiry the alert triggers — is configurable during implementation. Management users can see a summary of all expiring documents without reviewing every individual record. Dispatch-level users can see driver and vehicle compliance status without accessing the underlying document records.

What happens to compliance records if we stop using HaulageOps?

Your operational data — audit trail, job history, documents, driver records, contract records — can be exported during offboarding. Audit logs are exportable to CSV and documents stored in Azure Blob Storage can be downloaded. HaulageOps does not hold your compliance records hostage. The offboarding process, data export timeline and format are covered as part of the standard implementation and terms of service. If data retention requirements for your industry extend beyond your subscription period, raise this during your demo conversation so we can discuss options.

Can the compliance module handle subcontractor compliance records?

Subcontractor compliance records — insurance certificates, operator licences, subcontractor agreements — can be stored against the subcontractor record in the HaulageOps admin panel. Document expiry alerts apply to subcontractor records as well as driver and vehicle records. This means you can track whether a subcontractor's public liability insurance is current, whether their agreement with you is still valid, and whether any permits they hold are about to expire — all from within the platform, without maintaining a separate spreadsheet of subcontractor compliance status.

See the audit trail and compliance features in a live demo.

Book a 20-minute session to see how the audit trail, document management, expiry alerts and break recording work together as part of daily operations — not as a separate compliance layer.