A collection handover that can be checked later

Connect the physical removal of materials to an accountable operations record.

Record the transition

At collection, capture site, equipment, operator, time, container or batch reference and any exception. Agree how the receiving party confirms the handover. A machine counter and a collection receipt answer different questions.

Handle unusual cases

Plan for a partially full container, contaminated stream, damaged bag or failed scan. Give staff a way to record why the standard route was interrupted without rewriting history.

Report only what is known

Show collected counts or weights only when measured in the specified workflow. Downstream recycling and environmental outcomes require separate evidence from the responsible processor.

Make a missed collection visible

Record the station or container ID, seal or batch reference where applicable, removal time, person handing over, receiving party and any discrepancy. If a collection was scheduled but not completed, keep the open task visible and define who rearranges it. A machine-level item count and a downstream weight may differ for legitimate reasons; note the units and measurement points instead of forcing them to match.

Rehearse the route with a full container

The route that looks easy on a plan may cross a busy lobby, a locked loading area or a doorway that narrows when a trolley is present. Walk it with the people who will perform the collection. Confirm the access window, where a full container can be staged and what the collector does if the receiving party is absent. If the route cannot be used safely during ordinary opening hours, change the schedule or position before relying on it.

Keep the three records distinct

The machine can record what it accepted. A collection log records what left a station. A receiver can record what arrived at the next step. Each may use a different unit and time. Link them with a station and batch reference where the workflow supports it, but do not make one figure masquerade as all three. When a discrepancy appears, preserve the original records and add a resolution note. That history lets the team identify whether the issue came from a missed collection, a damaged container or a reporting definition.

A practical handover sheet does not need dozens of fields. It needs enough to identify the material, the people, the time and the exception. Test the sheet during one real collection and remove fields no one can complete reliably. Then agree who reviews unresolved handovers and how soon they need an answer.

For a project brief, share the collector’s current form or data fields and the proposed removal route. Discuss the service handover or review the reporting guide.