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.
- 2022 NAICS
- 562111
- Practice pack
- Example and answer key (JSON)
- Updated
What this guide tests
Which record supports service at the dummy stop, and what separate fact can the facility receipt establish?
See the specimen and fields · Work through the fictional records
Task and source context
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.
Industry research
The U.S. Census Bureau’s industry definitions establish which activities these codes cover. The workflow sources in this guide describe the task or record type. Fiund’s pilot below uses fictional material to test a specific decision within that scope.
562111 · Solid Waste Collection
This U.S. industry comprises establishments primarily engaged in one or more of the following: (1) collecting and/or hauling nonhazardous solid waste (i.e., garbage) within a local area; (2) operating nonhazardous solid waste transfer stations; and (3) collecting and/or hauling mixed recyclable materials within a local area.
Build a pilot sample
Set up this pilot
Create mock waste pickup and recovery events for one stop. Attach a facility receipt for the load and grade stop-level completion only through the recovery link.
Prepare the test packets
- Start with the worked case. Use the fictional record types below as a guide to the source files you need. Give each packet a stable ID and save its source versions with it.
- Change one fact. Make one packet with enough evidence to answer the question and one where the evidence points to a different answer. Keep the other fields fixed so a reviewer can tell what changed.
- Remove the decisive evidence. Give the reviewer a third packet with a plausible near-match in its place. Have them write what can still be established and what evidence would resolve the rest.
Fields the reviewer needs
- 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.
Use Build an AI evaluation sample for service handoffs to turn the specimen into a brief with a defined task, source and review owner.
Fictional 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 ID | 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
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.
How to check the result
Ask for the answer, the record IDs that support it and any fact the evidence leaves unresolved. Have a reviewer compare the response against the reference before deciding whether the sample is ready to expand.
Errors to flag in this case
- 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.
Change the inputs and run it again
Remove V2's S/E link while retaining the same date. Require the recovery attribution to become unresolved despite a plausible sequence.
Score the decision and the evidence separately
Save the reviewer’s expected answer, supporting record IDs and unresolved fields in a separate answer key. Score the model on the decision, its citations and its handling of the deliberate gap. A correct answer citing a different case counts as an evidence error.
Before expanding collection, have a second reviewer run the same checks on the held-out packet. Keep related versions, views and exports of the same case together so they stay on one side of the training and evaluation split.
Check permission and scope
Use invented locations and original records. Exclude actual routes, households and customer data; clear any separate capture rights in advance.
Exclude hazardous operations, real site coordinates and restricted records. Use inert objects in a visual exercise.
Describe an authorized archive through Fiund’s existing-data assessment, or describe a new capture capability through the collection brief. The contributor agreement covers the terms for participation.
Sources and further reading
Resources for this workflow
Company and program reviews
Use these reviews to compare sourcing, capture or evaluation approaches. Confirm the applicable program, accepted sources and terms with the provider.
Compare the approach
micro1 review for experts, trade footage and company data
Compare the prerequisites for an approved recording project before planning a contribution.
Compare the approach
Sama review for computer-vision labeling and model evaluation
Review labeling scope for visual state and exception checks in staged footage.
Related industry examples
Industry guide · NAICS 562112
Hazardous waste collection manifest handoff records for AI
EPA’s manifest system tracks applicable hazardous waste shipments and includes roles for generators, transporters and designated facilities.
Industry guide · NAICS 562211
Hazardous waste treatment receipt and closeout records for AI
A receiving facility can document that a shipment arrived before any treatment record exists.
Industry guide · NAICS 562119
Brush and rubble removal tickets and acceptance records for AI
A debris removal operator may have a service order and a receiving receipt that tell different parts of the story.