Core Operations

Every haulage job created once. Managed end to end.

The job record is the unit of work that every other part of HaulageOps connects to. Origin, destination, material, quantity, schedule, rate, assigned party and instructions — set at creation and carried through to the invoice without re-keying.

Rate confirmed at creationFull audit timeline on every jobPOD attached at completionDispatcher and driver see the same job
6-step lifecycleCreate to Invoice, fully recorded
One recordRate, assignment, POD, invoice, audit
Job templatesRecurring work created in seconds
Bulk creationMultiple jobs from a single action
Zero re-keyingFrom job creation to Xero invoice
The Job Record

Every field your operation needs. Nothing you don't.

When a job is created in HaulageOps, you fill in the fields that matter for bulk haulage: where it starts, where it ends, what material is being moved, how much, when, and at what rate. That information travels with the job record through its entire lifecycle — it does not need to be re-entered at dispatch, re-confirmed at invoicing, or hunted down from a separate spreadsheet when a client queries a charge.

Core job fields

  • Originpickup location with Google Maps address autocomplete
  • Destinationdelivery site with routing distance calculated
  • Materialwhat is being hauled (configurable material types)
  • Quantitytonnes, loads, cubic metres or other unit
  • Scheduledate and time window for the movement
  • Rate typeper-tonne, per-load, hourly or fixed fee
  • Rate valueconfirmed from the client rate card at creation
  • Assigned partyowned driver/vehicle or named subcontractor
  • Instructionssite-specific notes for the driver
  • Job referenceyour internal or client purchase order reference

What attaches to the record over its life

  • Status historyevery status change timestamped and attributed
  • Driver updatesen-route, on-site, loaded, delivered
  • POD documentsphotos, dockets and customer signature from the driver app
  • Docket imagesuploaded from site or captured in the driver app
  • Invoice referenceonce invoiced, the invoice links back to the job
  • Audit eventswho created, edited, reassigned, or completed the job and when
  • Subcontractor pay recordseparate cost rate stored alongside client charge rate
  • Documentsany supporting files attached by dispatch or management
Platform View

The dispatcher's view and the driver's view — the same job.

Dispatchers see the full job record including rate, assignment history and all attached documents. Drivers see the same job through the mobile app: origin, destination, material, instructions and POD requirement. No information is re-entered at either end — what dispatch creates, the driver receives.

HaulageOps — Job Record Detail

Full job detail view in the Admin & Dispatch Panel showing: job header (origin → destination, material, quantity, rate), assignment section (driver name, vehicle, subcontractor if applicable), status timeline (Created 09:12 → Assigned 09:15 → En Route 07:44 → Delivered 11:02), POD attachments section (3 photos, 1 signed docket), and linked invoice reference. Sidebar shows client name and job reference number.

Job Lifecycle

Create → Price → Assign → Track → POD → Invoice

A haulage job in HaulageOps moves through a defined lifecycle. Each step is recorded. No step requires data from outside the system — the information set at creation follows the job all the way to billing.

01

Create

Dispatcher or operations manager creates the job. Origin, destination, material, quantity, schedule and instructions entered once. Google Maps address autocomplete reduces errors on site names.

02

Price

Rate confirmed at creation from the client's rate card. Rate type (per-tonne, per-load, hourly, fixed) selected and value locked in. Subcontractor pay rate set separately if the job is being delegated. No rate negotiation happens at invoice time — it was agreed when the job was booked.

03

Assign

Job assigned to an owned driver and vehicle, or delegated to a named subcontractor. The assigned party receives the job immediately — driver through the mobile app push notification, subcontractor through their portal. Dispatcher does not need to call either to confirm.

04

Track

Status updates flow from the driver app to the dispatch board without phone calls. En route, on site, loaded, delivered — each status change is timestamped on the job record. Dispatchers see the board updating live via real-time connection.

05

POD

At delivery, the driver captures proof of delivery through the mobile app: photos of the load, the delivery docket, and customer signature. All POD is attached to the job record and stored in Azure. The docket is already there when you go to invoice.

06

Invoice

From the completed job record, an invoice is generated with rate and quantity already populated. Sent to the client portal and synced to Xero via OAuth2. The job record links to the invoice — no double-entry, no hunting for the rate that was agreed three weeks ago.

Recurring Work

Job templates and bulk creation for work that repeats.

Job templates for recurring runs

If you have a site supply run that goes from the same quarry to the same construction site every day, you do not rebuild that job from scratch each morning. Save the job as a template — origin, destination, material type, rate and instructions are stored. When the work recurs, load the template, confirm the date and assign the driver. Done in under a minute.

Templates are particularly useful for operators managing long-running site contracts where the same movement repeats across days or weeks. They reduce data-entry errors on repetitive work and ensure the rate applied is consistent with the agreed contract rate.

  • Save any job as a reusable template
  • Templates store all core fields except date and assignment
  • Create a new job from a template in seconds
  • Templates can be updated when contract rates change
  • Useful for daily site supply, quarry to plant, regular materials runs

Bulk job creation

When a large site contract requires creating many jobs at once — multiple trucks running the same route on the same day, or a week of work assigned to different drivers — bulk job creation allows a dispatcher to generate multiple job records from a single action rather than clicking through the creation form repeatedly.

Bulk creation maintains the same field completeness as single job creation. Each job generated carries its own rate, assignment and schedule. They appear individually on the dispatch board and can be managed independently once created.

  • Generate multiple jobs in a single action
  • Each job is an independent record on the dispatch board
  • Assign different drivers to each job in the bulk creation flow
  • Useful for large site mobilisations and week-ahead planning
  • All generated jobs appear in the job history with full audit trail
Audit & History

Complete job history with a full timeline on every record.

Every job that passes through HaulageOps — created, completed, cancelled or edited — is retained in the job history. Dispatch can search and filter job history by date range, client, driver, subcontractor, material or status. Management reporting draws from the same history for financial and operational analysis.

Status timeline

Every status change on a job is recorded with a timestamp and the identity of who triggered it — whether the driver through the app, the dispatcher from the admin panel, or the system automatically. The timeline is visible on the job record and cannot be edited retroactively.

Edit history

If a job is edited after creation — a rate correction, a change to the assigned driver, a destination update — the change is logged in the audit trail. The previous value and the new value are both recorded alongside the user who made the change and when.

POD and document archive

All proof of delivery attachments, signed dockets and job documents are retained on the job record in Azure Blob Storage. They do not expire. A job from two years ago still has its POD accessible — useful when a client queries a delivery from a prior period.

HaulageOps — Job History View

Job history table in Admin Panel. Columns: Job ID, Client, Origin, Destination, Material, Quantity, Rate, Driver/Sub, Status (colour-coded: Completed green, Cancelled grey, In Progress blue), Date. Filter bar above: date range picker, client dropdown, status filter, driver filter. Clicking any row opens the full job record detail view. Pagination at bottom shows 50 jobs per page.

Connected Platform

The job connects to everything else in HaulageOps.

Job management is the foundation. The other modules in HaulageOps work because the job record is the shared source of truth they all read from and write to.

Dispatch Management

The dispatch board shows every active job in real time. Assign, reassign, prioritise and monitor all jobs from a single view. Live status updates flow in as drivers move through their route.

Job Scheduling

Plan forward work on the scheduling calendar. Use job templates to recreate recurring runs. View driver and subcontractor availability before locking in assignments. Schedule a week of work without calling anyone.

Rate Management

Client rate cards and subcontractor pay rates are stored in the platform. When a job is created, the applicable rate is pulled in automatically from the rate card — no manual rate lookup, no rate disputes at invoice time.

Also see: Haulage Dispatch solution | Job to Invoice workflow | Billing & Invoicing

Common Questions

Job Management — frequently asked questions

How many jobs can the system handle?

HaulageOps is built for operators running between 15 and 80 vehicles. Operators in that range typically create hundreds of jobs per week. The platform does not impose a per-job limit — job history is retained indefinitely and the dispatch board is designed for the volume a fleet of that size generates. If your operation is significantly outside that range, discuss your requirements during a demo.

Can I edit a job after it has been dispatched to a driver?

Yes. A dispatcher can edit job fields — destination, instructions, rate, assignment — after a job has been sent to a driver. The driver's app will reflect the updated information. All edits are logged in the job's audit trail: what was changed, the previous value, the new value, who made the change, and when. This gives you an honest record of what happened rather than hiding corrections.

How do job templates work? Can any dispatcher use them?

Any user with dispatcher access can create a job from a template. Templates are created from any completed job — you save the origin, destination, material, rate and instructions, then give the template a name. When creating a new job, you select the template and it pre-fills the form. You still confirm the date and make the assignment before saving. Templates are visible to all dispatchers in your organisation, so a template one person creates is available for the whole team.

What happens to a job's rate if the rate card changes mid-contract?

Rates are locked at job creation from the active rate card at that time. If you update a client's rate card, existing created jobs retain the rate that was set when they were created. New jobs created after the rate card update will pull in the new rates. This avoids accidentally applying new rates to work that was already booked and agreed at the prior rate. Rate cards in HaulageOps support effective dating — you can set a future start date for a new rate so it activates at the right time.

Do subcontractors see the client rate when I assign them a job?

No. The client charge rate and the subcontractor pay rate are stored as separate fields on the job record. When a job is delegated to a subcontractor via their portal, they see the job details — origin, destination, material, instructions, schedule — but not the client charge rate. They see only the pay rate agreed for their portion of the work. This is a deliberate design: your margin stays internal.

Can clients see job details before the job is completed?

Yes. Clients with access to the client portal can see their jobs in progress — status, estimated completion, driver assignment if you choose to share it, and location updates. You control what level of detail clients see through the portal settings. Once completed, the job record is visible in their portal with POD attached and a link to the invoice when raised.

Is there a mobile view for dispatchers, or is job management desktop-only?

The Admin & Dispatch Panel is a browser-based application accessible on any device. Dispatchers who need to create or manage jobs from a tablet or phone in the field can do so through the browser. The experience is optimised for desktop workflows because dispatch management at scale — viewing many jobs simultaneously, bulk creation, scheduling — benefits from a larger screen. The Driver App (iOS and Android) is the mobile-native experience designed for drivers, not dispatchers.

See job management working in a live demo.

We'll walk through creating a job, dispatching it, tracking it to completion and generating the invoice — your actual workflow, not a slide deck.