GPS tells you the truck drove past the address. XWaste proves the cart was serviced, what the load weighed, and exactly what happened at the curb — one timestamped record, retrievable by address in seconds, ready for the resident, the risk manager and the council.
XWaste Core — operate for as little as $4 per truck, per day Curb capture, service verification, routing and the record — one platform, one line item.
Written once. Retrievable by address, route, truck or date.
Not because the trucks aren’t tracked. Because a breadcrumb on a map is not evidence, and by the time the call comes in, the only record left is the driver’s memory.
The breadcrumb shows the truck on the street. It cannot show whether the cart was out, whether it was serviced, or whether it was blocked by a parked car.
The claim arrives long after the footage has rolled over. With nothing to review, the cheapest path is to pay it — and the loss history follows the fleet into renewal.
Route tonnage and transfer-station tickets disagree. Nobody can say which routes, which trucks, or whether it is a scale problem or a service problem.
Overtime is climbing and the explanation is anecdotal — traffic, a heavy week, a new driver. None of it is measured, so none of it can be fixed.
XWaste does not infer service from proximity. The lift, the weight and the image have to line up before the stop is written — and when they don’t, the exception is raised at the curb, not at the complaint desk three days later.
Hopper, side and curb cameras trigger on the arm cycle rather than on a timer. The frame is bound to the GPS fix, the service address and the second it happened — so the proof is created by the work itself, not reconstructed afterwards.
Per-lift capture, route 14, last eight stops.
Onboard weighing reads each container as it is tipped. Gross, tare and net land against that address, so tonnage is a measured line item rather than a route total divided by a stop count at the end of the day.
Record #14-0741 · sealed 07:41:56
Every stop writes a single record — location, time, weight, images, driver, truck and route — and closes it. Retrieval is by street address, so a customer-service rep answers the call on the first try instead of routing it to operations.
Fleets already have GPS. What they don’t have is the thing that ends the argument: a record that was created at the moment of service, that nobody can quietly edit, and that a resident, an adjuster or a council member can be shown without a caveat. That is the whole product.
Cameras record for human review. XWaste performs no automatic analysis of video footage. Screens shown are the product interface with representative data.
The rep searches the address, sees the curb image and the timestamp, and answers the resident while they are still on the line — or schedules the return with the reason already on file.
Footage around the location and minute is preserved on flag instead of rolling over, so a claim is answered with what happened rather than settled because nothing was kept.
Per-lift weights roll up by route, truck and day and reconcile against scale-house tickets, turning a month-end variance into a specific route on a specific afternoon.
Planned versus actual, stop by stop — service time, idle, deviation and re-runs — so route changes are argued from measurement instead of from the loudest recollection.
The same event as the resident’s call, the driver’s cab and the operations floor see it. Representative data, real interface.
The call comes in at 9:04. The rep does not open a ticket, page dispatch, or promise to call back — she searches the address.
Answered on the call. No ticket opened.
The driver confirms nothing. Service is logged by the lift.
Exception queue, not a map of dots.
A homeowner says the truck took out a mailbox on the 6th. There is no incident report, because the driver never knew.
Search by address and date. No SD cards, no depot visit.
Packet is the record as written, not a summary of it.
On a residential route, that is either the wrong container, a contaminated load, or an account that has outgrown its service level.
Flagged automatically. The driver keeps moving.
Each row opens the image that created it.
Evidence goes with the notice, so it is not a dispute.
Scale-house tickets and route tonnage are off. The question is not whether — it is which routes, which days, and by how much.
Per-lift capture, not a route total divided by stops.
One afternoon, one truck, one scale reading.
XWaste runs on Prometheus Orchestrator, so routing, fleet health, fuel and compliance are modules of the same system rather than four vendors and four logins.
The day as an exception queue. Verified stops clear themselves; what is left is the short list that needs a person — blocked carts, weight exceptions, missed lifts, incidents.
Deliberately quiet. Service logs itself from the lift, so the tablet exists for the three things a driver actually needs: the next stop, the exception tap, and the pre-trip.
Pre-trip complete 05:52 · DVIR filed
Address in, answer out. The rep who takes the call is the rep who closes it, without a ticket, a callback, or a message to operations.
Twelve months of history, one search.
The XShield engine applied to refuse: continuous multi-camera recording, retrieval by address and minute, and a preservation hold that survives the retention window.
Refuse trucks are the hardest-worked, most expensive assets a department owns. The same telemetry that verifies service also runs maintenance, fuel and hours.
The same platform, configured around what each side has to defend — a public-records request on one side, a renewal and a margin on the other.
Departments are measured on complaints, diversion and cost per household — and every one of those numbers has to survive a public meeting.
For a hauler, the same record is a billing instrument and an insurance argument. Both show up on the P&L.
Evidence that can be edited is not evidence. Everything below is a design constraint, not a setting.
Service records are sealed at the moment they are written and hash-chained in sequence. A correction is a new entry with its own timestamp — the original stays where it was, which is exactly what a records request or a deposition needs.
XWaste performs no automatic analysis of video footage. Cameras capture; people decide. There is no behavioral scoring of drivers from video and no biometric identification of residents or passers-by.
Retention is configured to the jurisdiction’s schedule, with legal hold to keep a clip past it. The records belong to the agency, and full export in open formats is available for the life of the contract and at the end of it.
Hardware is installed on existing trucks — municipal, contracted or mixed. Prometheus is a certified Geotab platform partner and operates the telematics layer directly, so crews never touch a second system to do their day.
Not because the fleet works differently, but because every disputed moment already has a record attached to it before anyone picks up the phone.
The rep sees the curb image and the timestamp while the resident is still on the line. No ticket, no callback, no hand-off to operations.
Footage is preserved on flag instead of ageing out, so a third-party claim is answered with what happened rather than settled because nothing was kept.
Planned against actual, stop by stop. Re-sequencing and overtime are argued from service times instead of from the loudest recollection.
Per-lift weights roll up by route, truck and day, so a month-end variance narrows to one afternoon instead of a spreadsheet argument.
Core covers the record that ends the arguments — curb capture, service verification, routing and the evidence desk — with hardware, connectivity and support included for the term. Onboard weighing, additional camera views and compliance modules are configured to the fleet.
A missed-pickup complaint you couldn’t answer, a claim you paid, or a route that ran long. We will show you what the record would have said.