High-frequency aggregate haul cycles need a system that works at the speed of the pit.
High-frequency, short-cycle, and dependent on quantity accuracy
Aggregate haulage from quarry to site is structurally different from most other haulage work. The distances are often short — sometimes under 20 kilometres — but the daily load count per truck is high. A truck running ten loads per day at 25 tonnes per load delivers 250 tonnes before it parks up. Across six trucks, that is 1,500 tonnes. The quantity accuracy of the day's run is the difference between a correct invoice and a dispute.
Material types vary by quarry and by project: crushed rock, road base, gravel, sand, drainage aggregate, topsoil and screened fill all run the same basic cycle — load at the pit, deliver to site, photograph the docket or get a signature, return. The difference is in the rate (sand and road base often price differently even from the same quarry) and in the site requirements at delivery.
Loading at the pit face is another operational variable. Trucks queue behind the excavator or loader. Load times vary. Trucks don't always get equal loads. When billing is per-tonne, the quantity recorded per load matters — and that quantity record has to be captured per event, not estimated at the end of the day.
Common aggregate materials and job types
- Crushed rock and road base — the highest-volume aggregate type in civil and road construction
- Drainage aggregate and gravel — coarser material for subgrade drainage layers
- Sand — finer-grain material for bedding, filling and landscaping
- Topsoil — used for final cover on earthworks and landscaping projects
- Screened fill — variable composition; used for bulk fill in structures
- Concrete aggregate — sized material delivered to concrete batch plants
Charging models in quarry haulage
- Per tonne — most common; billing tracks actual tonnes delivered per load event
- Per load — used where consistent truck capacity substitutes for weighbridge evidence
- Hourly — used for slow, waiting-heavy operations or when truck is held at the pit
The specific points where high-frequency quarry haulage outgrows paper and phone
Manually tracking loads per truck per day
A dispatcher tracking six trucks running ten loads each is managing sixty events per day, manually. If the count comes from driver memory or end-of-day calls, it is wrong before the driver gets home. The invoice built from that count is disputed before it is paid.
Dockets pile up in the cab
At a quarry, the pit operative hands the driver a paper docket at the loading point. The driver stacks them in the cab. By Friday, there are 50 dockets in the passenger seat across the fleet. Accounts can't invoice until they receive them. Drivers don't always deliver them intact.
Invoice disputes about quantities delivered
The client says 850 tonnes. Your count says 920 tonnes. The difference is worth real money. Without a digital record per load — with timestamp, GPS position, and driver signature — the dispute is resolved by whoever negotiates better, not by evidence.
Poor signal at the pit face
Quarries are often in areas with limited mobile coverage. An app that requires connectivity to record a load is useless at the face. Drivers default to paper when the app fails offline — which means you're back to dockets in the cab.
Driver downtime at the scales
When a weighbridge is in use, trucks queue. That queue time is unproductive but real. Capturing scale weight accurately — and attaching it to the right load record — requires either OCR integration or a reliable manual process. Currently HaulageOps supports photographed scale tickets; automatic OCR capture is on the roadmap.
Rate card errors across material types
When a client has different rates for road base, drainage aggregate and sand from the same quarry, an invoice raised manually against a spreadsheet rate card will use the wrong rate eventually. Per-load volumes and rates need to be attached to the job at creation, not looked up at invoicing time.
Each load captured, each docket stored, each invoice built from the run record
Job created with material and rate
Dispatcher creates the job with the quarry as origin, delivery site as destination, material type (road base, aggregate, sand) and the per-tonne or per-load rate from the client's rate card. Multiple material types within one project get separate rate lines.
Driver receives job on the app
Firebase push notification goes to the driver's phone. The driver accepts the job, sees the quarry loading point address, delivery point, site instructions and material type. The app opens with the run ready — no phone call from the dispatcher needed.
Load recorded at the pit — offline if needed
The driver records each load in the app at the loading point. If there is no signal at the pit face, the app records the event offline. Load data queues locally and synchronises when the driver returns to coverage — typically as soon as they leave the quarry entrance. No load is lost because of connectivity.
Docket photograph and delivery signature
At the delivery site, the driver photographs the paper docket from the pit operative (the record of what was loaded). The site contact signs on the driver's phone to confirm delivery. Both the docket photo and signature are stored in Azure, attached to the specific load record.
Quantity tracked across all loads
As each load completes, the quantity accumulates against the job. The dispatcher sees total tonnes or loads delivered today, per truck and across the fleet. The client can see their project's running total in the Client Portal without calling the office.
Invoice from job quantity — sync to Xero
At billing time, total tonnes delivered and the per-tonne rate are already in the system. The invoice is created from the job record — no manual count, no transcription from paper dockets. It syncs to Xero. Each docket is attached as evidence if the client queries the quantity.
Screenshot: Driver mobile app showing offline mode indicator (grey signal icon, "Working offline — will sync when connected" banner). Active job shown: client name, quarry loading point, delivery site. Load count for the day: 7 of estimated 10 loads. Bottom: "Record Load" button — tapped to log each load event. Below that: "Photograph Docket" and "Capture Signature" actions. Last recorded load shown: 11:42 AM, 23.4 tonnes, photographed docket thumbnail visible, pending sync indicator.
Honest about current capability and what is on the roadmap
What works today
HaulageOps handles the complete quarry haul cycle as it operates now: job creation with per-tonne rate cards, offline-capable driver app for load recording at the pit face, docket photograph capture, customer signature on delivery, quantity tracking across loads, and invoice generation from the job record synced to Xero.
The driver app operates offline with local data queuing — this is confirmed behaviour, not a roadmap item. Quarry environments with poor signal at the pit face are a known use case the app is tested against.
Multiple quarry sites are supported. Each site operates as a separate origin in the system, with site-specific instructions, loading point details and separate job records per site. Rate cards can be set per client, per material type, and per effective date.
What is on the roadmap
There are two capabilities that quarry operators frequently ask about that are not yet available in the current platform:
OCR scale ticket capture: Automatically reading the weighbridge ticket to extract the recorded weight and attach it to the load record. Currently, drivers photograph the scale ticket and the image is stored — the weight is entered manually or estimated. Automatic OCR extraction is on the roadmap.
Weighbridge integration: Direct data feed from the weighbridge system into HaulageOps, eliminating manual ticket capture. This is also on the roadmap and subject to scope discussion for specific installations.
We include this because buying software on the basis of roadmap promises creates problems later. If OCR or weighbridge integration is a hard requirement for your operation today, the current platform handles it with photographed tickets — and we are direct about what that means for your workflow.
Features that apply most directly to quarry and aggregate operations
Driver App
iOS and Android. Offline-capable — confirmed. Drivers record each load, photograph dockets, and capture signatures without needing signal at the quarry face. Data synchronises when connectivity returns. Push notifications via Firebase FCM for job assignments.
- Offline load recording with local queue
- Photo docket capture per load event
- Customer signature capture on mobile
- GPS position recorded per load event
Digital Dockets
Each load from the quarry gets a digital docket record — driver, time, GPS position, photographed pit docket, and delivery signature. At invoice time, all dockets are already in the system attached to their load events. No searching through cab piles.
- Per-load docket capture — not end-of-day batch
- Stored in Azure Blob Storage
- Attached to job record, available at invoice time
- Accessible by client in the Client Portal
Rate Management
Set per-tonne and per-load rate cards per client, with different rates per material type. When a client has road base at one rate and drainage aggregate at another, both rate lines sit on the client's card and attach to the correct job type at creation.
- Per-tonne and per-load rate types
- Material-type-specific rates per client
- Effective dating for rate changes
- Separate client charge rate and sub pay rate
Billing & Invoicing
Total quantities per job — tonnes or loads — are already in the system when you go to invoice. The invoice is built from recorded load events, not from a manual count. Xero sync means the invoice goes straight to your accounting system without re-entry.
- Invoice built from recorded load quantity
- Xero OAuth2 sync — no re-entry
- Dockets attached to invoice as evidence
- Invoice visible to client in their portal
Quarry and aggregate transport questions about HaulageOps
What happens if the driver has no signal at the pit face?
The driver app is offline-capable. Load events, docket photographs and signatures are recorded locally on the driver's phone when there is no signal. The data queues and synchronises automatically when the device regains connectivity — typically as the truck leaves the quarry site and returns to normal coverage. This is confirmed behaviour built for exactly this environment. Drivers do not need to do anything differently when offline; the app handles the queue transparently.
How do I invoice for multiple loads in a single day?
Each load is recorded as a separate event in the system, with its own quantity, timestamp and docket. At the end of the day or billing period, the total quantity across all load events is aggregated against the job. The invoice is built from that total — you do not need to count load events or add up quantities manually. If you are billing per load rather than per tonne, the system counts load events rather than summing tonnes. Either way, the invoice comes from the system record, not from end-of-week counting.
Can I manage multiple quarry sites in HaulageOps?
Yes. Each quarry is set up as a separate origin location in the system with its own address, access instructions, loading point details, and any site-specific notes for drivers. Jobs are created from the relevant quarry origin. Reporting can be filtered by origin site, so you can see load counts, tonnes and revenue by quarry separately. Rate cards can be client-specific and can include different rates for different material types, regardless of which quarry they come from.
Does HaulageOps integrate with weighbridge systems?
Not currently as a live integration. Drivers photograph the weighbridge ticket and the image is stored in the job record. Weight entry from the ticket is currently a manual step. Direct weighbridge integration and OCR scale ticket capture are both on the roadmap — but we are direct about the fact that they are not available in the current platform. If weighbridge integration is a hard requirement for your operation today, speak to us about the roadmap scope and timeline for your specific situation.
How does per-tonne billing work when I don't have a weighbridge on every run?
Per-tonne billing in HaulageOps uses the quantity recorded by the driver at each load event. Where a weighbridge ticket is available, the driver records the weight from the ticket. Where a weighbridge is not used, the driver records the estimated or agreed load weight (for example, the rated capacity of the truck). The rate applies to whatever quantity is recorded. If your client has agreed a standard load tonnage per truck type, that can be set as the default load quantity to make recording faster for drivers.
Can clients see aggregate delivery quantities without calling the office?
Yes. Clients with access to the Client Portal can see running delivery quantities for their project, along with job status, docket records and invoices. This is useful for project managers who need to track aggregate volumes against a project specification or supply contract. They see the numbers directly in the portal — no call to the dispatcher required.
Does HaulageOps work for subcontracted aggregate haulage as well as own fleet?
Yes. Subcontractor aggregate hauliers access the Subcontractor Portal — a dedicated login for external operators. You delegate jobs to them from the dispatch board. They accept, run the loads, and update progress through their portal. Their completed job data feeds into your quantity records and invoicing. The subcontractor does not need to subscribe to HaulageOps — only your operating company pays the subscription. This is the same model used for tipper overflow in earthworks and other high-demand periods.
Related industries and features for quarry transport operators
Driver App
The offline-capable iOS and Android app that handles load recording, docket capture and signatures at the quarry face — even without signal.
View pageDigital Dockets
Per-load docket capture replaces the cab pile. Each load gets a timestamped docket record attached to the job before you invoice.
View pageRate Management
Per-tonne and per-load rate cards per client, per material type, with effective dating. The rate is on the job at creation — not looked up at invoicing.
View pageBulk Haulage
Most quarry transport operators also run general bulk haulage. The bulk haulage page covers the full per-tonne workflow including subcontractor and client portal.
View page