Muckaway operations move fast. Your dispatch system needs to keep up.
What makes muckaway operations distinctly demanding.
Muckaway and spoil removal sits at the high-intensity end of tipper operations. The pace is set by excavation progress, not by your dispatch schedule — and the coordination complexity grows fast when you're running multiple excavation contracts simultaneously.
High-speed excavation removal
A busy muckaway contract might run a tipper every ten to fifteen minutes from a single excavation. Over a full day across multiple contracts, the number of individual load records, dockets and tip confirmations adds up quickly. A system designed for one or two loads per truck per day cannot keep up with this pace without creating a paperwork backlog by midmorning.
- Job templates for recurring excavation site + tip combinations
- Multiple load records per truck per day without manual re-entry
- Digital docket captured at tip — timestamped and geotagged
Multiple excavation contracts simultaneously
Most muckaway operators run multiple active contracts at the same time — different client sites, different tip sites, different tip materials, different billing rates. Coordinating drivers and sub tippers across all of these from a single dispatch point, while maintaining per-load traceability on each, requires a dispatch board that handles multi-site operations without needing a separate system per site.
- Dispatch board shows all active contracts and sites in one view
- Jobs tagged by client, site and tip destination
- Separate rate structures per contract — per load or per tonne
Sub tippers for surge capacity
Muckaway contracts frequently require more tipper capacity than an owned fleet can supply — particularly when excavation pace increases or multiple contracts hit a surge at the same time. Bringing in sub tippers needs to be fast, and visibility of their work needs to be maintained once they go offsite to the tip. Phone calls and WhatsApp are not a coordination system.
- Sub tippers receive jobs through the subcontractor portal
- Status updates and docket submission via portal mobile login
- Live GPS position on the dispatch board — no phone calls needed
Per-load verification at tip
Muckaway billing depends on load counts and tonnage verified at the tip site. The docket is the proof of what was tipped, when and by whom. Paper dockets work until they go missing, get wet, or arrive three days later. Digital dockets submitted by the driver at the point of tipping remove all three of those failure modes.
- Driver submits docket at tip through driver app or sub portal
- Photo, tonnage and timestamp stored against the load record
- Docket available to review and invoice against immediately
Where muckaway operations break down without the right system.
Coordinating multiple dig sites and tip sites
A muckaway operator running three active excavation contracts might have trucks cycling between four different dig sites and three tip sites — each with different clients, different billing rates and different tip acceptance requirements. Managing this across a whiteboard or a spreadsheet creates allocation errors, missed loads and invoicing disputes when the load count does not match the tip site records.
The HaulageOps dispatch board shows every active job, every driver and every site in a single view. Jobs are tagged by site, so load counts per excavation contract are tracked automatically as drivers submit dockets.
Losing visibility of sub tippers at the tip
Sub tippers are most opaque at the tip site — the point where load verification matters most. Without a digital docket workflow, you rely on the sub tipper to accurately report what was tipped and when. That relies on trust and memory, neither of which is an audit trail.
The subcontractor portal requires the sub tipper driver to submit a docket at each tip — photo of the tipped load, tonnage, timestamp and tip location. That submission is attached to the job record immediately and visible to your dispatch team in real time.
Invoicing contractor clients accurately
Muckaway contractors invoice by load count or by tonnage, sometimes both — and disputes arise when the client's own count does not match yours. Digital dockets with timestamps and photos create an auditable record that both sides can reference. Invoice disputes become verifiable rather than based on recollection.
Invoices in HaulageOps are generated from completed job records. The docket is already attached. The load count and tonnage are already in the system. The invoice matches the docket record exactly.
How HaulageOps handles the muckaway and spoil removal workflow.
Create jobs from excavation site templates
Set up a job template for each active excavation contract — dig site, tip site, billing rate. Creating a new load for the day takes seconds. Multiple loads of the same type are bulk-created against the template.
Assign to owned and sub tippers
Allocate loads to owned drivers and sub tippers from the dispatch board. Sub tippers receive their assignments through the subcontractor portal. Acceptance confirmation is visible on the board immediately.
Track loads between dig and tip
GPS tracking shows each tipper's position in real time. Status updates — loaded, in transit, tipping, returning — appear on the dispatch board as drivers update in the app or sub portal.
Digital docket at every tip
Driver submits the docket at the tip site — photo, tonnage, timestamp. The docket is stored against the load record immediately. Load count and tonnage accumulate automatically against the excavation contract job record.
Invoice contractor from job records
Pull the completed loads for a contract period, review the docket-backed load count and tonnage, generate the invoice. The docket evidence is attached. Disputes have an auditable record to reference.
Xero sync for payment tracking
Invoice pushes to Xero and payment status syncs back via real-time webhook. Paid and outstanding invoices visible in HaulageOps without switching between systems.
The HaulageOps features muckaway operators rely on.
Subcontractor portal — sub tipper coordination
The subcontractor portal gives each of your sub tippers a dedicated mobile login. They see their job queue, accept or decline assignments, view Mapbox maps for dig site and tip site locations, update status at each stage, and submit digital dockets at the tip. Sub tippers do not pay for portal access — only the operating company holds the HaulageOps subscription.
- Sub tippers access portal free — no separate licence required
- Accept/decline, status updates, docket submission from mobile browser
- Mapbox maps for dig site and tip site routing
Digital dockets — per load at tip
The digital docket workflow captures proof at the point of tipping: photo of the load, tonnage confirmation, GPS location of the tip site, and timestamp. This is stored in Azure Blob Storage against the load record and is available immediately for review, client reporting and invoice generation. No paper dockets to collect, photograph or re-enter.
- Photo, tonnage and timestamp at tip submission
- Stored in Azure Blob Storage — accessible from admin panel
- Docket attached to invoice automatically on generation
Dispatch board — multi-site muckaway view
The dispatch board shows all active excavation jobs across all sites in a single real-time view. Filter by site, by contract or by driver. Load count per contract accumulates live as dockets are submitted. GPS positions of owned and sub tippers visible simultaneously. No secondary tracking system required.
- Multi-site view with filter by contract or site
- Real-time load count accumulating per contract
- Live GPS — owned and sub tippers in one view
Job-to-invoice for contractor billing
The job-to-invoice workflow generates invoices directly from completed job records — the load count, tonnage and applicable rate are already in the system from the job records and dockets. The invoice matches the docket record. Disputes have a timestamped, photo-backed load history to reference rather than a spreadsheet count.
- Invoice generated from completed load records directly
- Docket package included with invoice for client reference
- Xero integration for payment tracking and reconciliation
Muckaway dispatch board in HaulageOps.
Dispatch board showing two active muckaway contracts side by side. Left panel: Contract A (basement excavation, City Road site) — 6 loads dispatched, 4 tipped and docketed, 2 in transit shown with GPS position. Right panel: Contract B (infrastructure dig, Highway site) — 4 loads dispatched, 2 tipped, 2 loading. Sub tipper section showing 3 sub drivers: 2 active with status, 1 returning from tip. Load counter at top of each contract panel showing running total: "Contract A: 42 loads today / 18.6 tonnes". Filter controls: by site, by driver, by contract status.
Common questions from muckaway and spoil removal operators.
Can I track load counts per excavation contract separately from total fleet activity?
Yes. Jobs in HaulageOps are created against a specific client and contract. Load records accumulate against that contract job. The dispatch board can be filtered by contract to show the running load count and total tonnage for a specific excavation job. At invoice time, the load count and tonnage for that contract are already in the system — no reconciliation of a separate tally sheet required.
We run tip sites with specific acceptance requirements — how does documentation work?
Document management in HaulageOps allows you to attach site-specific documentation to job records — tip site acceptance letters, environmental permits, waste classification records. These are stored in Azure Blob Storage against the job and accessible to drivers through the app. The digital docket submitted at tip is a separate capture — photo, tonnage and timestamp — that serves as per-load evidence of disposal.
How do sub tipper rates work when I'm billing the client per load?
Each job in HaulageOps carries two rate structures: the client charge rate (what you invoice the client) and the subcontractor pay rate (what you pay the sub tipper). Both are managed in the rate management system independently. When you invoice the client per load, the system uses the client rate. What you owe the sub tipper is tracked separately using the sub pay rate. Your margin per load is visible in reporting without manual calculation.
We sometimes need to redirect a tipper to a different tip site mid-day — how is that handled?
From the dispatch board, you can modify a live job to update the tip site destination. The driver receives the updated job details through a push notification on the driver app (Firebase FCM). If the tip site change also changes the applicable billing rate, the job can be updated to the correct rate before the docket is submitted. Changes to job details are logged in the audit trail with timestamp and user record.
Can clients see the load count and dockets for their excavation contract in real time?
Yes. The client portal gives each client a dedicated login to view job status, load history and dockets for their contracts. An excavation contractor who wants to know how many loads have moved today without calling your dispatcher can check the portal. Dockets are downloadable from the portal for the client's own site records.
We also do tipper hire work alongside muckaway contracts — can both run in the same account?
Yes. The same HaulageOps account handles both muckaway contracts (per-load and per-tonne billing) and tipper hire (typically hourly billing) simultaneously. Different rate structures apply per client and job type. The tipper fleets page covers the high-churn daily dispatch side of tipper hire operations — most operators running both will recognise their operation across both pages.
Related industries and platform features.
Earthworks
Earthworks operators managing cut-and-fill, excavation removal and site materials across multiple active contracts — with both owned plant and subcontractor tippers.
View pageTipper Fleets
High-churn tipper operations running multiple jobs per day across owned trucks and sub tippers — covering dispatch, docket and end-of-day invoicing at pace.
View pageSubcontractor Portal
The dedicated portal for sub tippers — job queue, accept/decline, Mapbox maps, status updates and digital docket submission from any mobile browser.
View pageDigital Dockets
How digital docket capture works in the driver app and sub portal — photo, tonnage, signature and timestamp, stored against the load record and attached to invoices.
View page