This article walks a receiving site through a full inbound load in LoadSnap, from the vehicle arriving at the gate to the movement landing in DEFRA. It maps the legal record set onto what you actually do on the weighbridge.
Before the vehicle arrives
A compliant inbound record needs to know what the waste is, where it came from, who carried it, and where it is going next. With LoadSnap most of that arrives with the vehicle, on the carrier's QR code, so you are confirming data rather than typing it.
The weighbridge flow
The driver shows the carrier's QR code. The site, customer, EWC code and transfer note are already on screen.
Weigh the loaded vehicle in to capture the gross weight.
After tipping, weigh the empty vehicle to capture the tare. The net is calculated for you.
Confirm the record and print the receipt. It carries a QR and a tracking ID.
Screenshot goes here: the weighbridge screen after a carrier QR has been scanned, showing the prefilled site, customer, EWC code and transfer note, with the gross weight field ready.
Screenshot goes here: the printed or on screen receipt showing the gross, tare and calculated net weights, the QR and the DEFRA tracking ID.
Checks that happen for you
As part of the same flow, the carrier's licence is checked against the Environment Agency register, and if the waste is hazardous the record feeds the consignee return. You do not run these as separate jobs.
Screenshot goes here: the carrier licence check result, showing a verified or flagged status against the EA register.
What reaches DEFRA
On confirmation, LoadSnap files the movement to DEFRA's Receipt of Waste API and stores the returned tracking reference against the record. That satisfies the receiver duty for that load, well inside the two working day rule.
Related: What you must record under Digital Waste Tracking. The two working day rule. Recording and submitting a rejected load.