Skip to content

AI uses for records

Waste management service exception data: what explains a failed pickup?

By SourceX Editorial · Updated

9 sections

Short answer

A failed waste pickup is explained by four linked records: the service the customer was owed, the truck's stop event at that address, the driver's reason code with timestamped photos, and the later stop event that proves collection or a documented reason it did not happen. A closed complaint ticket shows none of this. Build each case around one ID that joins billing, routing, onboard and customer service records.

Agent run

Waste management service

This page covers waste management service exception data: what explains a failed pickup.Illustrative

Key takeaways

  • A closed missed-pickup ticket records the request's state, not what happened at the curb.
  • Join billing, routing, onboard computer, driver tablet and customer service records under one case ID.
  • Set-out deadlines, contamination tags and documented-refusal rules decide whether an event is a failure at all.
  • Prove outcomes with a later stop event and photo, never with the ticket status or the reply to the customer.
  • Mask households, drivers and anything visible in photos, and check municipal or franchise contracts before sharing.

What evidence should explain a failed waste pickup?

A failed pickup is explained by four linked records, not by the complaint ticket: the service the customer was owed, what the truck recorded at the stop, the reason code and proof the driver or system logged, and the completion event that shows the waste was finally collected or why it legitimately was not. If any link is missing, the case shows a complaint and a closure, not a cause.

Haulers hold these records in different places. The service agreement and container details sit in billing or customer software, the stop events and GPS trail in route and telematics systems, the photos and exception codes on the driver's tablet, and the complaint and callback in the customer service queue. Waste management service exception data becomes useful for AI work, and for the hauler's own analysis, only when one case ID joins them.

This guide shows how to build that joined case, which reasons and constraints a generic example would get wrong, and what to remove before a case leaves the company.

Why does a closed missed-pickup ticket not say what happened?

Because the status field records the state of the request, not the outcome at the curb. A ticket closes when the customer is collected, when the customer was at fault, when the report duplicated another, or when the account was not due service that day.

The Open311 GeoReport v2 specification, used by many city service request systems, makes this concrete. Its status field has two values, open and closed, where closed means the request has been resolved. A separate optional status_notes field explains why the status changed, and the specification's own sample response closes one request with the note Duplicate request. The updated_datetime of a closed request is the date it was closed, and an optional expected_datetime may reflect a service-level agreement.

Private hauler software is often richer than this, but the pattern holds: if a training example takes the closed status as the label, it teaches that every complaint is resolved the same way. The real signal is in the reason, the evidence behind it and the event that followed.

Which exception reasons does a hauler actually need to tell apart?

At minimum, separate customer-side causes, access and safety causes, and hauler-side causes, because each has a different correct response. The table lists common reasons and the evidence that distinguishes them.

Which exception reasons does a hauler actually need to tell apart?
ReasonEvidence that proves itUsual correct responseCommon mislabel
Not set out in timeStop arrival time and photo of the empty set-out point, against the published set-out deadlineCollect on next service day or a special collection, depending on policyDriver skip
Access blockedPhoto of a parked vehicle, locked gate or construction, with GPS showing the truck at the stopReturn if access is restored the same day; otherwise next serviceCustomer not set out
ContaminationContamination tag code and photo of the cart or bin contentsLeave the container with a tag and collect after the customer corrects itMissed collection
Overfilled or lid openPhoto showing the lid or overflow, and the container size on the agreementCollect what fits or tag; offer an extra-capacity serviceMissed collection
Prohibited or hazardous itemDriver note and photo of the item, such as batteries or hazardous liquidsRefuse the item with instructions for proper disposalContamination
Truck or route not completedNo arrival event at the stop, plus a breakdown, weather or staffing note on the routeDispatch a recovery truck or run the stop on the next dayCustomer not set out
Not due serviceService day, frequency or account status in the billing recordExplain the schedule; no truck dispatchedMissed collection
Duplicate reportEarlier open or closed request for the same address and dateLink to the original request and closeSeparate missed collection

Which operating rules would a generic training example miss?

Set-out deadlines, reporting windows, documented refusals and contamination policies decide the correct answer, and they differ by city, contract and hauler. A generic example that says send a truck back for every complaint is wrong most of the time.

Seattle Public Utilities is a useful public reference because its rules are written down. Its guidance asks residents to set carts out by 7:00 a.m. on collection day, and its missed-collection page asks customers to report after 6:00 p.m. on that day and within two business days, says a fix is scheduled within 24 hours of the report, and says missed collections are reviewed to determine cause and solution, with a possible charge when the cause is customer error. Its recycling guidance describes tags left on carts with a problem, such as garbage in the recycling, that the customer should fix before the next service day.

Commercial collection can be stricter about documentation. New York City's adopted Commercial Waste Zones customer service rule treats a carter's refusal to collect as a missed collection if the reason is not documented that day. The city's records and reporting rule requires awardees to report non-collections and the reasons for them monthly, and to keep required records for five years. Those rules mean the reason code and its proof are not optional fields; they decide whether an event counts as a failure at all.

Safety adds another layer. The U.S. Environmental Protection Agency warns that lithium-ion batteries put in trash or recycling can be damaged or crushed during collection or processing and cause fires, and directs people to specialized recyclers or household hazardous waste collection instead. A driver who leaves a bin because of a visible battery made the correct decision, and the case should be labeled that way.

The route service and resolution case specification

Use this specification to assemble one case per failed or disputed service event. Each field group names where the data usually lives and the check that must pass before the case is complete. Keep the field names your systems use and map them to these groups.

At a glance

The route service and resolution case specification

The route service and resolution case specification
Field groupFields to includeUsual sourceCompleteness check
Case headerCase ID, service date, line of business (residential, commercial, roll-off), stream (trash, recycling, organics)Customer service or dispatch systemOne case ID joins every record below
Service owedAccount status, service day and frequency, container type and size, set-out location notes, applicable policy versionBilling or customer management softwareThe stop was due service on the case date
Route contextRoute ID, planned stop sequence, truck ID, crew role code, route start and end times, route notesRouting and dispatch softwarePlanned and actual route both exist for the date
Stop eventArrival and departure time, GPS point, service status code, lift or weight event if recordedOnboard computer or telematicsArrival event exists, or its absence is explained in route notes
Exception evidenceReason code, driver note, photos with timestamps, tag issuedDriver tablet or photo storeEvery non-service code has at least one photo or a documented reason
Customer contactReport time and channel, what the customer said, duplicate linksCall, portal or email queueReport time falls within the published window, or the exception is noted
DecisionAction chosen (return trip, next service, refuse, credit, education), who decided, rule appliedDispatch or supervisor notesThe decision cites a reason and a policy, not just a status
Resolution eventCompletion stop event, photo, or the documented reason no collection followedOnboard computer, driver tabletOutcome is evidenced by an event, not by the ticket status
Follow-throughRepeat reports for the same address within a set window, account adjustments, coaching or route changeCustomer service and billingThe window has passed before the case is labeled resolved
Rights and privacy flagsContract restrictions, residential vs commercial, people or plates in photos, call recordingsContracts and the de-identification logEach flag is reviewed before the case leaves the company

Worked case (illustrative): a restaurant's recycling container left full

This case is illustrative and invented to show the specification in use; it is not a real customer. A restaurant on a commercial route has a recycling container serviced three times a week. On a Tuesday afternoon its manager reports that the container was not emptied.

Starting state: the billing record shows an active account due service that day, and the route plan places the stop eleventh on the morning route. Linked evidence: the onboard computer logs an arrival at the stop at 6:42 a.m. and a service status of not serviced; the driver's tablet shows a contamination code and two timestamped photos of loose food waste and plastic film on top of the recycling, and a tag issued.

Applicable rule: the hauler's commercial contract, like many municipal programs, allows a contaminated container to be left with a tag. Under a documented-refusal rule such as New York City's, the same-day reason code and photos are what keep this from counting as a missed collection. Decision: the supervisor does not send a return truck, calls the manager to explain the tag and offers a special collection once the contents are corrected.

Verified outcome: the next scheduled service on Thursday logs a completed lift with no exception code, and no repeat report arrives for the address in the following two weeks. The case is labeled resolved by customer correction, with the Thursday event as proof.

Counterexample: the same complaint on another day, but the onboard computer has no arrival event at the stop and the route notes record a hydraulic failure at 6:15 a.m. Here the cause is hauler-side, the correct decision is a recovery truck the same day, and a model that learned contamination from the first case would be wrong. Keeping both cases, with their evidence, teaches the distinction.

Which linked record proves the decision and the outcome?

The decision is proved by the reason code plus its contemporaneous evidence, and the outcome is proved by a later stop event, not by the ticket closing or by a courteous reply to the customer.

At a glance

Which linked record proves the decision and the outcome

Treat these as the proof hierarchy for labeling cases:

  • Strongest: a timestamped stop event on the onboard computer, with a photo, at or after the decision.
  • Strong: a driver exception code with photos taken at the stop and GPS that places the truck there.
  • Supporting: dispatcher or supervisor notes that name the rule applied and the action chosen.
  • Weak: a customer service note that says resolved, or a closed status with no linked event.
  • Not proof: the final message sent to the customer, which can be polite and wrong.

What must be removed before exception cases leave the hauler?

Remove or mask anything that identifies people who are not parties to the license, and check contracts before sharing anything from municipal or franchise service. Photos are the riskiest part of the case.

Residential addresses and customer names identify households; replace them with stable pseudonymous IDs and coarsen locations to a level the use case tolerates. Driver names and employee IDs should become role codes. Photos can show people, license plates, house numbers and the inside of private property, so either blur them or replace them with structured descriptions of what they showed. Call recordings and free-text notes often contain phone numbers and personal details and need the same review.

Municipal contracts and franchise agreements may also limit how service data can be used or shared, and some data may belong to the city rather than the hauler. A rights review should confirm, contract by contract, which routes and customers can be included.

Can a hauler license its service exception records?

It can, if the hauler controls the records, the contracts allow it and the cases are de-identified. Exception cases with linked stop events and photos are more useful than ticket exports alone, because they show how a decision was made under real operating rules.

SourceX takes haulers' selected records through rights review, contracting, preparation and delivery as licensed AI datasets. Haulers in the U.S., Canada and the EU that peaked at 50 or more full-time employees, not counting contractors, can qualify. Haulers in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia can be considered when the records they offer are at least 70 percent English, confirmed on the actual dataset. Whether a hauler qualifies is checked through a short company assessment with no uploads.

Frequently asked questions

Is a missed-pickup complaint log enough to train a service agent?

Usually not. The log shows that someone complained and that the ticket closed, but not why the container was left or whether it was collected later. Link each complaint to the stop event, the driver's reason code and photos, and the next service event.

How do we tell a driver miss from a customer who set out late?

Compare the stop arrival time and photo with the published set-out deadline. If the truck has no arrival event at the stop, the cause is on the route side; if it arrived after the deadline and the photo shows no container, the customer side is more likely.

Should contamination refusals be counted as missed collections?

Not when they are documented with a reason code and photo at the time, and the contract or local rule allows leaving the container. Some rules, such as New York City's commercial zone rule, treat an undocumented refusal as a missed collection, so the documentation decides.

Are driver photos safe to share with an AI developer?

Only after review. Photos can show people, license plates, house numbers and private property. Blur or replace them with structured descriptions, and check that contracts allow the images to be shared at all.

What counts as proof that a failed pickup was resolved?

A later stop event showing a completed service, ideally with a photo, and no repeat report within a set window. A closed ticket or an apology email is not proof.

Sources

  • The Open311 GeoReport v2 specification defines a service request status of open or closed, an optional status_notes field explaining status changes (its sample closes a request as a duplicate), an updated_datetime that is the closing date for closed requests and an optional expected_datetime that may follow a service-level agreement. Source
  • Seattle Public Utilities asks residents to set carts out for collection by 7:00 a.m. on their collection day. Source
  • Seattle Public Utilities asks customers to report missed collections after 6:00 p.m. on collection day and within two business days, schedules a fix within 24 hours, reviews each miss for cause and may charge when the cause is customer error. Source
  • Seattle Public Utilities leaves tags on carts with a problem, such as garbage in the recycling cart, which the resident should fix before the next service day. Source
  • New York City's adopted Commercial Waste Zones customer service rule treats a refusal to collect as a missed collection if the carter does not document the reason that day. Source
  • New York City's Commercial Waste Zones records and reporting rule requires monthly reporting of non-collections and their reasons and five-year retention of required records. Source
  • The EPA says lithium-ion batteries placed in trash or recycling can be damaged or crushed during collection or processing and cause fires, and should go to specialized recyclers or household hazardous waste collection. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies