Deployment blueprint
Household waste behaves nothing like medical, and construction debris nothing like liquid. Run as separate programmes they produce data that will not add up. We make the lifecycle itself the data model, so a load stays the same object from the bin to the invoice.
Built for this scale
The challenges
Each stream has its own contractors, vehicles, facilities, and regulator. Managed as separate programmes, none of it reconciles.
Challenge
Medical waste and agricultural by-product share almost nothing operationally, so each stream grows its own tooling and process. The result is incompatible data, duplicated effort, and enforcement that depends on which spreadsheet a manager happens to trust.
Challenge
Live vehicle positions exist for some streams and not others. Weighbridge data sits in the facility's local software, collection data in the operator's, regulatory returns somewhere else again. Joining them by hand produces a figure nobody fully believes.
Challenge
For medical and liquid streams, a compliance failure is a health incident rather than a contractual one. Self-reported logs and next-day imports cannot meet the evidence cadence those streams actually require.
Challenge
Service providers hold the tickets, the billing, and the complaints in their own systems, so at programme level nobody can see whether service quality is improving or which customers are about to churn.
How it would work
Planning happens before anything moves: the service provider submits a monthly plan — vehicle allocation, driver assignment, frequency, washing schedule — and a contract manager approves it. Optimised routes then reach the driver app, while telematics, in-cab video, engine data, and behaviour metrics stream back. At the facility, weighbridge readings, classification, and pricing are recorded against the same trip that produced them. Billing and customer service read from that record rather than from an export of it.
The architectural point
Because the stages are one record, there are no inter-stage integrations to maintain and no reconciliation window to reason about. A stream keeps whatever specialism it needs — medical waste can demand a chain-of-custody rule that household waste does not — without becoming a separate build. And because the customer layer sits on the same stack, a dispute is resolved by opening the load rather than by comparing two systems' versions of it.
Streams live
6
Loads today
3,940
Awaiting classification
112
Custody breaks
0
Lifecycle · load 48-2213
liveCollected · District 9
06:14 · Veh. 1180 · 42 points
Weighed in · transfer station
07:52 · 9.4 t · classified
Medical stream · custody check
Awaiting facility confirmation
Tonnage by stream · last 12 days
Illustrative console view — sample data, not a live operation.
Platform capabilities
Plan, collect, weigh, classify, bill, and analyse — six streams running through one operating model.
Work plans, vehicle allocations, driver assignments, and washing schedules are reviewed and approved before the month starts, so scoring runs from day one instead of being retrofitted.
Daily routes, geofenced zones, supervisor QA inspections, and geotagged incident logs across every stream, on one map.
ExploreWeighbridge capture, volume estimates, manual verification, classification, stockpile tracking, and pricing — tied upstream to the contract that authorised the load.
Tickets, customer records, invoicing, and online payment on the same stack as operations, so a billing query resolves against the operational trace.
Dashboards spanning operations, contracts, facilities, and billing, built for renewal decisions and process change rather than monthly reporting theatre.
Medical and hazardous loads carry stricter custody, temperature, and containment rules without a separate deployment — the same engine, a different rule set.
ExploreHardware in the field
Telematics, in-cab video, bin sensors, and facility weighing — every signal landing in the same lifecycle record.
Position, engine data, and driver-behaviour metrics from the whole collection fleet, device-agnostic across suppliers.
ExploreVideo for QA, exception evidence, and coaching, attached automatically to the compliance event it belongs to.
ExploreFill and weight at the collection point, weighbridge sensors at landfill and recycling sites — both writing into the same load history.
ExploreNavigation, dispatch, and proof-of-collection for drivers; QA checklists and incident logging for supervisors, on shared records.
ExploreIntegrations
Connected to the customer, financial, and regulatory systems already in play — including those run by the service providers inside the programme.
Existing service-provider customer systems connect through the integration gateway, making service quality measurable at programme level.
Invoice generation and payment flows reconcile to the lifecycle record automatically rather than through a monthly import.
Stream-specific returns for medical, liquid, and hazardous waste are produced from the same records that ran the operation, with the audit trail intact.
Authority staff, contract managers, provider users, and inspectors all resolve to the existing directory with scoped permissions.
FAQ
Short answers here — the detailed version is a conversation whenever you're ready.
Discuss your deployment
Sovereign-data-friendly. Enterprise multi-org architecture. Built to integrate with the devices, SIM providers, and back-office systems you already run.
