Was the Container Collected? Resolving Missed-Pickup Disputes

The customer reports a full container. The route system shows the truck at the address. Dispatch closes the complaint because the location looks right, but the customer is still waiting and nobody has checked whether the gate was locked or the correct container was emptied.

Separate arrival, attempted collection, completed collection, and remedy. A collection-exception packet should assemble the scheduled service, identified container, actual event records, and customer report so an authorized person can resolve the disagreement. This is a service-evidence problem, not simply a route-planning problem.

Define what completed service means

The service agreement may specify container, material stream, frequency, access arrangements, and an agreed service window. Use that definition when reviewing completion. A truck passing nearby does not establish that the agreed container was collected, and a lift event may need identity and context before it can be matched to the customer's complaint.

Record attempted service separately when an obstruction or other exception prevents collection. Preserve what the driver observed, when, and which container or access point it concerned. A generic blocked code without location or explanation may be too weak to resolve a dispute later.

Local providers have specific reporting and response procedures. Seattle Public Utilities' missed-collection page is one example of an operator-defined process, not a deadline or remedy that applies to every commercial account. Configure the workflow from the actual service arrangement.

Assemble evidence without treating one source as conclusive

Useful records can include the scheduled stop, vehicle event, container identifier, driver note, permitted service photograph, equipment event, and later customer report. Show which system produced each record and whether the clocks and identifiers can be reconciled.

An absence of a lift event might mean no collection, an equipment logging failure, or a bad match. A photograph might show an access obstruction but not establish how long it was present. Keep plausible explanations separate from findings until the responsible person reviews them.

Limit access to customer locations, images, and vehicle history. Dispatch needs enough information to investigate the stop, not unrestricted access to every movement of a driver or every image captured on the route. Retain evidence according to a defined business practice and applicable requirements.

Resolve a gated loading bay complaint

Consider an illustrative commercial account with a weekly collection from container C-28. The customer portal records a missed-pickup complaint. The service-event application is the operational source of truth, while vehicle telemetry and the driver's notes remain linked evidence.

The truck location matches the address, but the driver record says gate inaccessible. A permitted image shows the gate closed at the recorded attempt. There is no confirmed collection event for C-28. The dispatcher classifies the record as attempted, not completed, and checks the agreed access arrangement before deciding the next action.

The customer reports that a different gate should have been used. Dispatch compares the current instructions and finds that a recent access update was not acknowledged by the route team. The supervisor arranges a permitted revisit and records who must update and acknowledge the service instruction. The system does not automatically charge for the revisit or issue a credit; those decisions follow the agreement and authorized review.

After the revisit, the evidence packet links the new completion event to the original exception. Suppose a hypothetical week had 50 reported disputes: 32 confirmed completed, 11 confirmed attempted but blocked, and seven still unresolved. The seven unknown cases must not be counted as completed simply to improve the service percentage. The categories tell managers which failures need instruction changes, evidence repair, or further investigation.

Build a collection exception board

Use a compact packet with these fields:

• Expected service: account, container, material stream, date, service window, and current access instruction.
• Observed events: arrival, attempted service, collection evidence, times, identities, and source references.
• Conflict: what the customer reports, what the driver reports, and what does not yet reconcile.
• Decision: completed, attempted, skipped, incorrectly recorded, or unresolved, with a reviewer and reason.
• Remedy: approved revisit, customer communication, contractual review, or other agreed next action.
• Closure: evidence that the remedy occurred and any instruction correction reached the people affected.

Keep reopened cases linked rather than creating a fresh complaint that loses the earlier history. If an integration is unavailable, staff should retain the complaint and investigate through the available authorized channels instead of rejecting it for lack of telemetry.

Use automation to prepare the answer

Basic software can match known identifiers, highlight missing events, and keep follow-up owners visible. AI can summarize conflicting records and draft a question for dispatch or a customer response for review. It should not infer service completion from proximity, determine fault from a single photograph, or authorize billing changes.

Pilot the process on recent disputed stops rather than an entire fleet rollout. Track unresolved cases, repeat complaints, time to an evidence-backed response, and remedies actually completed. A good system can tell a customer what happened and what will happen next, including when the honest answer is that the company is still investigating.