INDUSTRY FIELD GUIDE
Solid waste pickup completion and service exception data for AI
A scheduled stop, a route exception and a completed recovery can appear under the same service reference.
NAICS 562111 · Solid Waste Collection
A scheduled stop, a route exception and a completed recovery can appear under the same service reference. EPA’s transfer station manual describes the role of local collection and transfer. A collection operator can test whether software preserves the status and handoff evidence for each stage. EPA waste transfer station manual
Build three invented route events for a dummy service address. Mark the first visit missed and create a separate recovery visit with signed completion. Add a generic transfer receipt that supports a load reaching a facility without identifying the individual stop. Ask which record supports service at the dummy address and what the facility receipt can establish independently.
Use fabricated locations and inert identifiers. Keep route traces, household images, customer records and worker footage out. Get permission for any separately submitted capture.
Describe a fictional collection exception sample
Original Fiund exercise
A recovery-visit completion supports a stop while a facility receipt supports only its load
Three fictional route events use a dummy service location and inert references. No actual route trace, household, worker footage or collection operation is represented.
| Record | Source | What it records |
|---|---|---|
| WP1 | Scheduled stop S | Day 2 visit V1 marked missed with exception E. Schedule alone contains no completed service event. |
| WP2 | Recovery visit | Day 3 V2 explicitly references S/E; signed mock completion confirms the recovery stop. |
| WP3 | Transfer receipt | Facility receipt acknowledges aggregate load L on day 3. No stop-level contents or S-to-L membership supplied. |
Question for the model
Which record supports service at the dummy stop, and what separate fact can the facility receipt establish?
Show the reference answer and checks
WP2 explicitly links V2 to the missed stop S and exception E, supporting a completed recovery visit on day three. WP1 remains the original missed event. WP3 independently documents receipt of load L, but lacks a stop-level map and cannot prove S's service by itself. Preserve the original exception, recovery and aggregate handoff as separate events rather than use a facility load receipt to imply every scheduled stop was completed.
- Overwriting a missed visit with a later recovery instead of preserving both events.
- Using an aggregate facility receipt as proof of an individual stop's completion.
Fields to preserve
- Stop, visit and exception reference
- Defines the service history.
- Recovery link and signed completion
- Supports the later event.
- Load receipt and membership scope
- Limits aggregate attribution.
Test another case
Remove V2's S/E link while retaining the same date. Require the recovery attribution to become unresolved despite a plausible sequence.
Use invented locations and original records. Exclude actual routes, households and customer data; clear any separate capture rights in advance.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.