Earthworks logistics managed as a connected operation, not a set of calls and spreadsheets.
Project-based work, variable demand, and reporting obligations that don't suit generic TMS tools
Earthworks logistics is fundamentally different from regular bulk haulage. The work is project-based rather than route-based — demand is tied to where the excavation is at, not a timetable. When the excavator opens up a new face, spoil removal ramps up fast. When fill placement starts, the requirement shifts. The same project can have spoil running out in the morning and fill going in that afternoon.
Your tipper fleet is the core capacity. But on earthworks projects — particularly for head contractors with aggressive programme schedules — your own tippers are rarely enough during peak excavation. Sub tippers fill the gap. Coordinating a mix of six owned tippers and twelve subcontracted tippers across two active sites, while the head contractor's project manager wants to know how many loads have moved today, is not something a spreadsheet handles reliably.
Head contractor reporting is a specific pressure in earthworks. The head contractor is running a programme with milestones tied to earthworks completion. They need quantity confirmation — not an estimate, not a phone call, but a record they can use in their own reporting. The challenge is giving them that visibility without exposing your subcontractor rates or internal cost structures.
Typical earthworks project parties
- Earthworks logistics manager — coordinates tippers, manages sub overflow, reports to head contractor
- Own tipper drivers — core spoil and fill capacity on site
- Subcontractor tippers — overflow capacity when excavation surges
- Head contractor project manager — needs quantity and progress visibility for programme management
- Site supervisor — controls loading and tipping locations, signs off on loads
- Your accounts team — invoices head contractor from completed jobs
Charging models in earthworks
- Per tonne (spoil) — most common for spoil removal; billed against recorded or weighed quantities
- Per load (fill) — used where volume is consistent and weighbridge is not used
- Hourly — for slower or waiting-heavy work, or when tippers are on standby
- Project day rate — less common; used when the head contractor contracts tippers per day regardless of volume
Where earthworks logistics operations break down without the right system
Surge demand when excavation accelerates
When the excavator opens a new face, spoil volumes spike. Your own tippers fill first. Then you're calling sub tippers on the phone, hoping someone is available, and tracking who took what load in a WhatsApp group. By the time the day is done, you can't reconstruct which sub ran how many loads.
Coordinating multiple sub tippers across sites
When you have four subcontractor companies running tippers across two sites on the same day, keeping track of who is where, what they have completed, and what remains is a full-time communication task. Missing a sub going to the wrong site costs programme time and relationship capital with the head contractor.
Head contractor visibility without internal rate exposure
The head contractor wants to see load counts and quantity delivered — but you can not show them your subcontractor pay rates or the margin on the job. Paper dockets sent by email don't solve this. The head contractor needs a real-time view; your rate structure needs to stay private.
Dockets needed for quantity verification
Earthworks quantity disputes are common — the head contractor's count of loads differs from yours, or the fill volume recorded doesn't match what site says was placed. Without digital dockets with timestamps and GPS positions per load, these disputes are resolved by negotiation rather than evidence.
Quantities vary by project stage
Early earthworks might move 200 tonnes per day. During structure work it drops to 30. Then drainage requires another surge. Managing tipper allocation — own and sub — against a programme that changes daily requires the ability to scale dispatch up or down without rebuilding your coordination system.
Invoice reconciliation for project reporting
Head contractors often require invoice reconciliation against programme milestones. When your invoices are raised from job data in the system, reconciliation is straightforward. When they are raised from memory, spreadsheets and paper dockets, the reconciliation process becomes an argument.
How HaulageOps handles the earthworks logistics workflow
Project setup with site instructions
Create the project in HaulageOps with the head contractor as client, set the per-tonne spoil and per-load fill rates, and attach site-specific instructions for drivers — loading point, tipping location, site access notes. Instructions go to all drivers and subs assigned to the project.
Daily tipper dispatch — own and sub
Each morning, assign your own tippers to jobs. When your capacity is exceeded, delegate overflow loads to subcontractor companies via the sub portal. Subs see their job queue, accept the allocation, and start moving without a phone call from your dispatcher.
Live status for all tippers on one board
Own tipper GPS positions and sub tipper updates appear on the same dispatch board. The dispatcher sees load count, current status (loading, en route, tipping, returning) and any delays. No phone calls needed to know where the tippers are.
Digital dockets per load
Drivers capture a digital docket at the tipping point — or photograph the paper docket if the site issues paper. Site supervisor signature is captured on the driver's phone. Each load gets a timestamped, GPS-tagged docket record attached to the job.
Head contractor portal — quantities, no rates
The head contractor project manager logs into the Client Portal. They see load count and quantity delivered for their project, job status, and POD documents. They do not see your subcontractor pay rates or margin. Your rate card with that head contractor is visible to them in their portal — nobody else's.
Invoice from project job data
At billing cycle, the completed job data — tonnes, loads, hours — is the source for the invoice. No manual counting of paper dockets. The invoice syncs to Xero. The head contractor sees it in their portal. Disputes are resolved from digital records rather than paper piles.
Screenshot: Admin Panel showing an earthworks project. Left side shows project summary: client (head contractor name), site address, spoil tonne rate, fill per-load rate, today's load count (14 loads / 280 tonnes) vs project target (1,200 tonnes). Right side shows active dispatch — 3 own tippers (blue, showing status: 2 en route, 1 tipping) and 5 sub tippers from 2 sub companies (orange, showing accept/decline status). One sub tipper expanded showing last docket timestamp and GPS position.
HaulageOps features most used in earthworks operations
Subcontractor Portal
When your own tippers are at capacity during peak excavation, sub tippers fill the gap via their own dedicated portal. No second HaulageOps subscription needed for your subs. They accept the job, see the site instructions, and update load progress independently.
- Dedicated login per sub company — free for the sub to access
- Accept/decline individual jobs with reason
- Mapbox-powered site maps for unfamiliar locations
- Load history and documentation per sub
Client Portal
Head contractors get self-service visibility into their project's delivery progress — load counts, quantities, POD documents and invoices — without seeing your internal cost structure or subcontractor details.
- Live job status and load count per project
- POD documents and docket access
- Invoice history and current invoice status
- Client-specific — no cross-client data visible
Subcontractor Coordination
Managing multiple sub tipper companies across earthworks sites requires structured delegation, not group chats. HaulageOps gives you a defined job delegation workflow with confirmation, live updates and a complete audit trail.
- Delegate by sub company, not individual driver
- Real-time acceptance confirmation
- Sub status on the same dispatch board as own fleet
Rate Management
Earthworks often runs mixed rate structures within a single project — spoil at per-tonne, fill at per-load, standby tippers at hourly. HaulageOps handles all three rate types on the same job, with separate charge rates to the head contractor and pay rates to your subs.
- Mixed rate types within one project
- Separate client charge rate and sub pay rate
- Rate card version history — historical invoices stay correct
Earthworks logistics questions about HaulageOps
How do I manage multi-site earthworks projects in HaulageOps?
Each project in HaulageOps can have multiple delivery or work locations. Jobs within the project are created per site, with site-specific instructions, loading and tipping locations, and individual rate settings where they differ by site. The dispatch board lets you filter by project, so you can see all tippers across all sites for a single project in one view, or narrow to a specific site when coordinating that location. Load counts and quantities roll up to the project level for reporting to the head contractor.
Can the head contractor see live quantity delivered without me exposing my subcontractor rates?
Yes. The Client Portal is designed for exactly this situation. The head contractor logs in and sees the quantities and load counts recorded against their project, along with POD documents and job status. They see the rate card you have agreed with them — that is, the charge rate you bill at. They do not see your subcontractor pay rates, which subcontractor companies you use, or any of your internal cost data. RBAC controls what each portal user can see — and that is set at the operating company level, not by the client.
How do I handle tipper overflow when excavation surges unexpectedly?
You maintain a roster of subcontractor companies in HaulageOps. When surge demand hits, you open the dispatch board, create overflow jobs, and delegate to one or more sub companies. The sub portal notifies them immediately — they can accept or decline from their phone. Once accepted, they appear on your dispatch board and their drivers begin updating progress. This replaces the phone-around and WhatsApp-group approach, and the full record of what was delegated, accepted, and completed is logged automatically.
How are digital dockets different from paper dockets in earthworks?
Paper dockets in earthworks end up in the cab, get rained on, pile up, and then have to be matched to jobs manually at billing time. Digital dockets are captured at the point of delivery — the driver photographs the site docket or captures a digital record in the app, the site supervisor signs on the driver's phone, and the docket is immediately attached to the job record in the system. When accounts go to invoice, the docket is already there. When the head contractor queries a quantity, you have a timestamped, GPS-tagged record for every load — not a pile of soggy paper.
How does HaulageOps handle spoil removal and fill placement on the same project day?
A single project can have multiple concurrent job types running simultaneously. Spoil removal jobs use per-tonne rates (or per-load if preferred), fill placement jobs use the fill rate, and any standby or slow-moving work goes on hourly. Tippers are assigned to jobs by type. The dispatch board shows both job types active at the same time, with each tipper's current assignment visible. Quantities for each job type are tracked separately and roll up to the project total.
Can my subcontractor tippers use the system without subscribing to HaulageOps?
Yes. The Subcontractor Portal is free for your subcontractors to access. Only your operating company pays a subscription. Each sub company gets a dedicated login to their portal — they see the jobs delegated to them, accept or decline, update progress, and access their job history. They do not see other subcontractors' jobs or your internal operations. This means you can bring subs onto the platform without asking them to pay for software.
What reports can I give the head contractor at project completion?
The Client Portal gives the head contractor access to their project's full delivery history — load-by-load records with timestamps, quantities per load, POD documents, and invoices. At project end, this data is available as a complete delivery record. The reporting covers what was moved, when, by which job (without sub detail), and what was invoiced against it. For head contractors requiring milestone-based reporting, the quantity-per-period data is accessible through the portal without you having to compile it manually from paper dockets.
Related industries and features for earthworks operators
Civil Construction
Civil construction logistics shares many earthworks characteristics — mixed owned and sub fleets, principal contractor reporting, and compliance obligations across all operators.
View pageTipper Fleets
If tipper fleet management — vehicle availability, driver allocation and document compliance — is your primary operational challenge, the tipper fleet page covers that specifically.
View pageSubcontractor Portal
The detailed breakdown of how the Subcontractor Portal works — what subs see, how acceptance flows, and how their updates reach your dispatch board.
View pageSubcontractor Coordination
The structured approach to coordinating multiple sub tipper companies across earthworks sites — delegation workflow, confirmation, and live status without group chats.
View page