Bulk haulage operations: what actually happens from job creation to invoice.
What is bulk haulage?
Bulk haulage is the transport of loose, unpackaged materials in large quantities — typically by tipper truck, semi-tipper, walking floor or similar purpose-built vehicle. Unlike parcel delivery or general freight forwarding, bulk haulage deals in materials that are measured by weight (tonnes) or volume (cubic metres), not by item count or pallet.
The materials involved vary by industry but typically include: sand, gravel, road base and aggregates (quarry and construction supply); soil, clay, fill material and spoil (earthworks and civil construction); demolition waste, asphalt millings and concrete rubble (muckaway and recycling); agricultural bulk such as grain, fertiliser and feed; and heavy manufactured materials including steel, precast concrete and infrastructure components.
Operators in this sector typically run a mix of owned vehicles and subcontracted capacity. A 30-vehicle operation might own 15 tippers and subcontract another 20 from owner-operators or smaller haulage companies on a job-by-job or ongoing basis. Managing both cohorts on the same operation — with different rate structures, different communication methods and different levels of operational control — is the central challenge that makes bulk haulage operationally distinct from owner-operator transport.
Industries that run on bulk haulage
- Bulk haulage contractors — multi-client, multi-site, owned fleet + subs
- Earthworks companies — project-based, large volume, soil and fill movement
- Quarries and aggregate producers — supply chain from extraction to delivery
- Civil construction — materials delivery as part of broader construction programme
- Construction logistics — site supply, mixed material types, complex scheduling
- Tipper fleet operators — owner of fleet capacity sold to multiple clients
- Muckaway and spoil removal — excavation waste and spoil disposal
What these operations share: volume-based pricing, subcontracted capacity, multiple active jobs simultaneously, and a job-to-invoice process that depends on accurate delivery records.
How a haulage job moves through operations
Every haulage job passes through a sequence of states from creation to invoice. Understanding this lifecycle is what separates operators who can invoice quickly from those who spend weeks chasing paperwork.
Job creation
A job is created when a client requests a delivery or pickup. Key details recorded at this point: client, pickup location, delivery location, material type, quantity, scheduled date and time, rate to be applied. In many operations, this still happens via phone call or email — which means the information is captured manually into a spreadsheet or, in more organised operations, a TMS.
Job templates and recurring job scheduling reduce the manual effort when jobs repeat on the same route and rate. Address autocomplete (via Google Maps) speeds up location entry and ensures routing data is accurate from the start.
Rate and billing setup
Once a job is created, the billing rate must be determined. This should be automatic — pulled from an existing rate card for that client. In practice, many operations look up the rate manually, which is where billing errors begin. The applicable rate depends on: client, material type, route (sometimes), and rate effective date.
If the operator also uses subcontractors on this job, the subcontractor pay rate must be determined separately — the margin between what the client pays and what the subcontractor earns is the operator's revenue on that capacity.
Assignment and dispatch
The job is assigned to a driver (owned fleet) or delegated to a subcontractor. For owned fleet, the driver receives the job details via their mobile app — pickup location, delivery address, material, any site instructions. For subcontractors, the job appears in their portal where they can accept or decline. Accepted jobs appear on the dispatch board as confirmed.
Real-time dispatch boards give ops managers visibility of what is assigned, what is in progress, and what is unassigned. Without this, assignment happens via phone or WhatsApp — with no record of confirmation and no way to see the full picture at a glance.
Tracking and status updates
Once underway, the job progresses through status stages: en route to pickup, at pickup, loaded, en route to delivery, at delivery site, unloaded, complete. Each status update is timestamped and visible to the ops manager in real time. Clients with portal access see relevant updates without needing to phone.
GPS location tracking shows driver position on a live map. This is phone-based GPS in HaulageOps — the driver's mobile, not hardware telematics. Operators with existing GPS hardware keep it; HaulageOps sits above it as the operations layer.
Proof of delivery (POD)
When the delivery is complete, the driver captures proof. This is the docket — the delivery record that proves the job was done and the quantity delivered. POD capture in a digital system involves: photo of the delivery location or scale ticket, customer signature (if required on site), document upload for paper dockets or scale slips, and quantity confirmation.
All POD is stored in cloud storage, attached to the job record, and visible through the ops panel and client portal immediately. This is the point where paper-based operations most frequently fail — dockets get lost, arrive late, or are illegible when they finally reach the office.
Invoice generation
Once jobs are complete and POD is attached, invoices are generated. In a connected system: the job record contains the quantity, the rate card contains the price, and the invoice is built automatically — draft, reviewed, sent. The invoice attaches the relevant dockets so the client has delivery evidence alongside the bill.
Xero sync means invoices move directly into the accounting system without re-entry. Payment status updates come back via webhook when the client pays — keeping the operations platform current without manual reconciliation.
Rate structures in bulk haulage
Haulage rates are not one-size-fits-all. Most operations use different rate types for different job types, and managing this correctly across multiple clients and subcontractors is one of the areas where spreadsheets break down first.
Per-tonne rate
The most common rate structure in bulk haulage. The client pays a fixed price per tonne of material delivered. The actual charge on any given job depends on the weight delivered — confirmed by a scale ticket or docket weight.
Example: sand delivery at $18/tonne. A 20-tonne load invoices at $360. A 23-tonne load invoices at $414. The rate is fixed; the quantity varies.
Per-tonne rates work well where material weight is consistently measured (scale tickets at quarry or weighbridge) and where the client expects to pay on delivered quantity. They require accurate weight records to invoice correctly — which is why digital docket capture with photo evidence matters.
Per-load rate
A fixed price per trip, regardless of the exact quantity in the load. Used where loads are consistent and weighing is impractical, or where the client contract specifies a per-load arrangement.
Example: skip bin pickup and disposal at $85 per load. The driver collects the bin, disposes of the contents, and returns. Each pickup invoices at $85. Simpler billing — but requires accurate load counting, because each trip must be recorded to invoice correctly.
Per-load rates also work well for mixed material or demolition jobs where weighing each load is not practical.
Hourly rate
The client pays for time on site or on the road, not for quantity. Common in earthworks and civil construction where a tipper is on-hired to a site for the day or for a period of hours, rather than completing discrete delivery jobs.
Example: tipper on-hire at $145/hr. The driver starts the clock when they arrive on site and stops it when they leave. The invoice is the hours worked multiplied by the rate.
Hourly rate jobs require accurate time records — start time, end time, any breaks. Break and rest recording in the driver app feeds directly into this calculation.
Fixed price (day rate or job rate)
A single agreed price for a job or a day's work, regardless of quantity or hours. Used for straightforward contracts where the scope is defined and the client wants a predictable cost.
Example: site supply arrangement at $1,200/day — one truck on call for the site all day, delivering as required. The invoice is flat regardless of the number of loads completed.
Fixed price rates are simple to invoice but require the underlying job record to confirm the day was worked and completed — the job record and any POD serve as the delivery evidence.
For more on rate card structure and subcontractor pay rates, see the Rate Card Template and Rate Management platform page.
Managing subcontractors vs owned fleet
Most haulage operators with 15+ vehicles run a mix of owned trucks and subcontracted capacity. The coordination challenge — and where most operational pain lives — is managing both cohorts as if they were one operation.
Why subcontractor coordination is hard
Owned fleet drivers receive their jobs directly from the dispatcher. The operator controls their schedule, their route, and has visibility of where they are. Subcontractors are different — they are independent businesses, often working for multiple operators simultaneously, with their own schedules and their own administrative systems.
Without a dedicated subcontractor portal, the coordination chain typically looks like this: phone call or WhatsApp to confirm availability, job details sent via text, confirmation received informally, driver goes to site, calls or texts when done, sends a paper docket or photo at the end of the day. The operator re-enters all of this manually to track what was delivered and to build the invoice.
At 5 subcontractor jobs per week, this is manageable. At 50 per week across 10–15 subcontractors, it becomes the bottleneck that slows invoicing, causes disputes and prevents the operator from scaling further.
What makes it easier
A dedicated subcontractor portal gives each subcontractor their own login — completely separate from the operator's admin panel. They see only their jobs: assigned loads, pickup and delivery addresses, material, rate. They accept or decline jobs in the portal. When complete, they capture POD the same way an owned fleet driver would. The record flows back into the operator's job system automatically.
Critically: the subcontractor does not need to be a HaulageOps customer. They access the subcontractor portal as an invited user at no cost to them. The operator pays one subscription; the subcontractor gets access to their job queue and nothing else.
Dispatch board visual: two columns showing owned fleet drivers (left) and subcontractor companies (right), both assigned to jobs on the same live board. Subcontractor jobs show accept/decline status. Owned fleet jobs show GPS position. All jobs share the same status indicators: unassigned, assigned, in progress, POD pending, complete.
Read the Subcontractor Management Guide for a full breakdown of onboarding, rate management and compliance records.
Digital vs paper dockets
Why paper breaks at volume
A paper docket is a physical delivery record — typically a carbonless pad filled in by the driver or site contact. The driver keeps one copy, the client or site gets another, the office gets a third. In theory, this creates a complete paper trail. In practice, at any meaningful volume, paper dockets fail in predictable ways:
- Dockets left in the cab and not returned for days or weeks
- Illegible handwriting, missing quantities or wrong job details
- Dockets attributed to the wrong job, client or site
- Lost dockets that cannot be recreated — resulting in invoice disputes or write-offs
- Invoicing delayed until dockets physically arrive at the office
Each of these failures has a direct cash flow cost. If 50 jobs complete on a Friday and dockets arrive Monday or Tuesday, invoicing for those jobs cannot start until Tuesday. If the billing cycle runs weekly, those jobs slip to the following week's invoice run. For an operation turning over $500k/month, a consistent 7–10 day invoice delay represents significant working capital pressure.
What digital docket capture looks like
Digital docket capture replaces the paper trail with a structured digital record captured on the driver's phone at the point of delivery. The driver opens their mobile app, marks the job complete, and is prompted to capture: a photo of the delivery site or scale ticket, a customer signature (if required), and any additional documents such as a scale slip or site delivery docket.
The captured record is attached to the job immediately — visible to the ops manager, available to the client through their portal, and ready to include in the invoice the moment the job is complete. There is no waiting for paper to arrive.
For sites with poor mobile connectivity, the driver app works offline: the driver captures the POD without signal, and the record synchronises when connectivity returns. The job is not blocked waiting for a network connection.
For more on this topic, see the Digital Dockets Guide.
The job-to-invoice problem
The gap between job completion and invoice payment is the single most common cash flow problem in bulk haulage. Understanding what causes it is the first step to closing it.
Missing delivery evidence
Invoices cannot be sent without delivery evidence. If dockets are missing, late or disputed, the invoice is held until they are resolved. In paper-based operations, docket reconciliation before invoice runs is a weekly overhead that consistently delays billing by 3–7 days beyond job completion.
Manual data re-entry
Jobs logged in one system must be re-entered into the billing system. Every re-entry step adds time and introduces errors — wrong quantities, wrong rates, wrong client details. A single billing error that triggers a client query can delay payment by 14–30 days while the dispute is resolved.
Rate disagreements
If the client's rate expectation differs from the rate the operator applied, the invoice is disputed. Rate disagreements are most common where rates are managed informally — quoted by phone, agreed verbally, not documented in a system rate card. When the rate card is the system of record and visible to the client in their portal, disputes are resolved before the invoice, not after.
When job records, rate cards, POD and invoicing sit on one platform — and the invoice is built from the job record automatically — the gap between completion and invoice shrinks from days to hours. See Job to Invoice and Reduce Invoice Delays for more detail.
Chain of Responsibility in the bulk haulage context
Chain of Responsibility (CoR) legislation — particularly relevant in the Australian operating context — establishes that responsibility for road safety compliance in the transport chain is shared across all parties who have influence or control over transport activities. This includes not just drivers, but operators, schedulers, loaders and clients.
What operators are responsible for
Under CoR, operators are expected to demonstrate that they have systems in place to manage compliance — not simply that no incident occurred. The obligation covers:
- Driver fitness for duty — licence validity, medical fitness, fatigue
- Vehicle roadworthiness — registration, inspections, load capacity
- Scheduling — not directing drivers to work hours that create fatigue risk
- Loading — not directing loads that exceed vehicle capacity
- Documentation — maintaining records that demonstrate due diligence
The practical implication for operators managing subcontractors: you cannot simply delegate compliance responsibility to the sub. You have an obligation to ensure that the subcontractors you engage are operating appropriately, and to maintain records that demonstrate you have done so.
What records matter
The records that matter in a CoR context are those that show the operator had a system in place and was using it. This means:
- Driver licence records with expiry dates and verification evidence
- Medical fitness records and induction documentation
- Vehicle registration, inspection and permit records
- Break and rest records demonstrating fatigue management
- Job scheduling records showing realistic run times
- Subcontractor insurance and compliance documents
- An audit trail showing who did what, when, in the system
HaulageOps stores driver documents, vehicle records and break/rest records, and maintains a comprehensive audit trail of all actions. This supports compliance record-keeping — it does not guarantee compliance outcomes and does not constitute legal advice. See Haulage Compliance Guide.
What to look for in haulage software
Most haulage software evaluations go wrong because operators evaluate what vendors demo, not what they actually need. Here is a short buyer checklist — the full version is at Software Requirements Checklist.
Core operational requirements
- Does the driver app work offline (no signal at quarry or remote site)?
- Can subcontractors receive and accept jobs without being a paying customer?
- Does the client portal show live job status and invoices — not just reports?
- Can rate cards be set per client with effective dating?
- Does invoice generation pull directly from the job record — or require re-entry?
- Is Xero integration native (not via Zapier or manual export)?
Implementation and total cost
- What is the setup fee — and what does it include?
- Is there a free trial or demo environment with your own data?
- What does driver and admin training cover?
- How long does implementation take realistically?
- Is there ongoing support included or charged separately?
- Are subcontractor and client portals included in the subscription?
For the complete 40-question checklist: Haulage Software Requirements Checklist. For a guide on running vendor evaluations: Haulage Software Buyer's Guide.
The HaulageOps workflow in brief
HaulageOps is a transport management system built specifically for bulk haulage and construction logistics operators managing a mix of owned and subcontracted capacity. The platform connects five role-specific portals around one live job record:
- Admin and Dispatch Panel — job creation, dispatch board, rate management, billing, fleet and driver records
- Driver Mobile App — iOS and Android, offline-capable, GPS, status updates, POD capture
- Subcontractor Portal — dedicated login, job queue, accept/decline, delivery confirmation
- Client Portal — live job status, POD documents, invoices and rate cards
- Management Reporting — financial, operational and compliance visibility across all jobs
Standard setup is $1,500 and typically takes 2–4 weeks. Subcontractor and client portals are included — the portals are free for portal users. Only the operating company pays the subscription.
Platform overview diagram: five connected portals (Admin Panel, Driver App, Subcontractor Portal, Client Portal, Management Reporting) arranged around a central job record. Arrows show: dispatcher creates job, driver receives on app, subcontractor receives in portal, client sees status in portal, reporting aggregates across all jobs.
Common questions about bulk haulage operations
What is the difference between a docket and a scale ticket?
A docket is the general delivery record for a haulage job — it records that a delivery was made, typically including the date, driver, vehicle, material, quantity and delivery location. A scale ticket is a specific type of docket issued by a weighbridge or on-site scale that records the confirmed weight of a load. In many bulk haulage jobs, the scale ticket is the primary evidence for the per-tonne quantity billed. A job may have a docket (general) and a scale ticket (weight confirmation) as separate documents, both attached to the job record.
How do most operators manage subcontractors before using a TMS?
The typical pre-TMS approach is phone calls and WhatsApp. The dispatcher calls or messages the subcontractor to confirm availability, sends job details by text or message, receives confirmation informally, and then has no further visibility until the sub calls to say the job is done. Dockets arrive later — sometimes days later — by photo or physically. The operator manually re-enters delivery details to track the job and build the invoice. This works at small volumes but becomes the primary operational bottleneck as the subcontractor network grows.
Why does per-tonne billing require accurate docket records?
Per-tonne billing invoices on the quantity delivered, not the quantity ordered. If the docket says 18 tonnes were delivered but the invoice says 20 tonnes (based on an estimated or assumed load), the client will dispute it. If the docket is missing, the invoice may need to be held or estimated — both of which create delay or error. Accurate, attached docket records mean the invoice quantity matches the delivery evidence, reducing disputes and speeding up payment.
What is Chain of Responsibility and does it apply to subcontractors I engage?
Chain of Responsibility (CoR) is legislation in the Australian jurisdiction that distributes road safety compliance obligations across everyone in the transport chain who has influence or control over how transport is conducted. This includes operators, schedulers, loaders and clients — not just drivers. If you engage a subcontractor and direct them to complete jobs within your operation, you have CoR obligations in relation to that engagement. This does not mean you are directly responsible for every action the subcontractor's driver takes, but you are expected to have systems in place to verify that subcontractors you engage are operating appropriately. We recommend taking legal advice on your specific obligations. HaulageOps supports compliance record-keeping; it does not provide legal advice or guarantee compliance outcomes.
Is HaulageOps suitable for owner-operators with 5 trucks?
HaulageOps is purpose-built for operators managing 15–80 vehicles — typically a mix of owned fleet and subcontracted capacity. Owner-operators with a small number of trucks and simple billing requirements may find it more than they need. The platform is at its most useful when the operational complexity justifies it: multiple subcontractors, multiple clients with different rate cards, a high volume of jobs per week, and invoicing that depends on accurate POD collection. If you are in that range, it is worth a demo. If you are significantly smaller, we will say so.
What accounting integrations does HaulageOps support?
HaulageOps has a native Xero integration: OAuth2 connection, 6-hourly sync with real-time payment webhooks, invoice creation and payment tracking. MYOB integration is available as an add-on on request (subject to scope assessment). Sage and other integrations are on the roadmap but not currently live. If your accounting system is not Xero, contact us to discuss what is possible.
Does HaulageOps include GPS vehicle tracking?
HaulageOps tracks driver location via the driver's mobile phone (iOS or Android) — not via hardware telematics devices fitted to vehicles. If you already have GPS hardware in your fleet, you keep it — HaulageOps is the operations and management layer above the hardware, not a replacement for it. Hardware telematics integration is on the roadmap but is not currently live.
Continue reading
Subcontractor Management Guide
How to manage haulage subcontractors without losing control or visibility — from onboarding through to ongoing rate and compliance management.
Read guideDigital Dockets Guide
What digital docket capture involves, why it matters for invoicing speed, and how offline sync works for sites without reliable connectivity.
Read guideHaulage Software Buyer's Guide
How to evaluate haulage software without buying the wrong thing — including questions to ask vendors and how to run a meaningful demo.
Read guideAlso see: Software Requirements Checklist — Job to Invoice solution page — Digital Dockets solution page