Four steps: 1 when it came in, 2 which wagon brought it, 3 what was in it, 4 press Save for the spreadsheet. Everything else is already set — the carrier, the registration number, your permit, your site and the disposal code all fill themselves in.
Four steps: 1 when it came in, 2 which wagon brought it, 3 what was in it, 4 press Save for the spreadsheet. Everything else is already set — the carrier, the registration number, your permit, your site and the disposal code all fill themselves in.
Each load must reach Defra within 2 working days, counted from the day after it came in. A load in at 9am Monday is due by 11:59pm Wednesday.
| Ref | Received | Due | Carrier | EWC | Where it is |
|---|
| Received | Tracking ID | Carrier | Vehicle | EWC | Weight (kg) | Ref | Status |
|---|
If Send to Defra ever stops working, tickets still get to Defra this way: build Defra's own spreadsheet here, upload it on gov.uk, then drop the file they hand back into step 2.
When it has downloaded, take it to Report receipt of waste →
| Reference | Received | Deadline | Carrier | EWC | Weight | Status |
|---|
Drop the spreadsheet Defra hand back here. Waste tracking IDs (column B) are stored against each record, anything rejected (column A) is marked so you can fix it and build again.
One row per build. Once a load is on a spreadsheet it lives here and is never built again, so nothing can reach Defra twice. Lost the file? Download again gives you the very same spreadsheet. Built one that was wrong? Discard puts its records back on the waiting list for the next build, then delete the wrong file from your Downloads folder. Records Defra have already accepted are never touched.
| Built | Records | Waiting on Defra | Accepted | Rejected | References |
|---|
Every waste type, most first
Which sizes came back, and what was in them
Average a day
Who brought it in
How the numbers were got, and where it all goes
The yard's Defra details live here. Once they work, leave them alone unless Defra send new ones. The API code names the yard and rides on every ticket (it is in the gov.uk account, under Manage my API code). The client ID and secret are what let this app through Defra's door. Paste in whatever has changed, press Save it, then Test the connection: Send to Defra only switches on once Defra accept them. A box left empty keeps what is already saved.
Defra issue these to whoever writes the software. Once saved they are never shown again, only the start and end of the ID, so type the whole thing when replacing one.
This goes on every load you record and on the Defra spreadsheet. Type it once and it sticks — including on everything already saved.
Presets fill the form in one click. Save a carrier from the New tracking ticket tab, or a waste type from any waste item.
| Type | Name | Used | Detail |
|---|
Before Defra hand over the live client ID and secret, they want to see this app send each of their 14 test tickets to their test environment, then an email with the tracking ID for each one. This sends all 14 in one go with Defra's test client ID and secret and one of their dummy API codes, so nothing reaches the real register, the movement log or the spreadsheet list, and the app stays exactly as it is for real tickets. Defra's own checker then marks each one.
Every load starts as R12: back to the yard, separated and sorted, then out on tip runs. The weight follows the load weight above. Change the code only if this one was different.