Albion Environmental Limited

What Digital Waste Tracking Actually Is and The Blind Spot It’s Built To Close

The first two posts in this series stayed on familiar ground: three parties, two transfers, one record per transfer, and what that record has to contain. All of that is the system as it stands today. This post is about what’s changing — but to understand what Digital Waste Tracking adds, you have to understand what the regulator can and can’t currently see. Because that’s the whole reason DWT exists.

 

What the regulator sees today

Here’s the part that surprises people. For all the paperwork that rides along with a load of waste, the regulator doesn’t routinely receive most of it.

A permitted or licensed receiving site — a transfer station, a treatment facility, a landfill — has to submit a data return to its regulator, quarterly or annually depending on what its permit says. In Scotland that’s the Licensed/Permitted Site Return to SEPA; the Environment Agency runs an equivalent regime in England. One return per licence or permit held.

And what’s in that return is essentially a tally. Tonnage in, broken down by EWC code and by what was done with it — recovered, disposed, treated. It’s an aggregate. “Over this quarter, this site received X tonnes of 17 01 07, Y tonnes of 20 03 01,” and so on. It tells the regulator what a site took in and roughly what happened to it, at the level of totals over a three-month window.

That’s genuinely useful for national waste statistics. It’s how Scotland and England build their picture of how much of what is being managed where. But notice what it is: a sum.

 

What the regulator doesn’t see

The return is a column of tonnages. It carries no information about the individual movements that made up those tonnages. Specifically, it doesn’t tell the regulator:

Who produced the waste. The return says a site took in 400 tonnes of mixed construction waste. It says nothing about which producers that came from, or how many of them, or where they were.

Who carried it. There’s no carrier identity in the return. The registered carrier who physically moved every one of those loads — the party whose licence is the actual control point for whether waste is being moved legitimately — doesn’t appear anywhere in what the regulator receives.

How it links to anything upstream. Remember from post one that a producer keeps their copy of the transfer note and a receiver keeps theirs, and nothing automatically connects them. The site return doesn’t connect them either. It’s the receiver’s totals, reported by the receiver, with the producer and carrier ends of every movement left entirely out of the picture.

So the regulator’s routine line of sight stops at the gate of the receiving site, and even there it only sees a quarterly sum. The transfer notes that contain the producer and carrier detail exist — both parties are legally holding them — but they sit in filing cabinets and inboxes, only ever pulled together by hand if someone launches an investigation and goes looking for them.

 

Why that’s the problem worth solving

This is the blind spot waste crime lives in.

If your routine data is the receiver’s aggregate tonnage, then a load that leaves a producer and never arrives anywhere legitimate simply doesn’t show up. There’s no return that was supposed to mention it, because the producer doesn’t file movement-level returns and the carrier doesn’t either. The only records that would have caught it are two halves of a transfer note held by parties who, in a fly-tipping or illegal-export scenario, have no interest in surfacing them.

The honest operators are carrying a real compliance burden — keeping notes, applying codes correctly, filing returns — while the system they’re complying with can’t actually see the movements that the dishonest ones are hiding. The data the regulator routinely holds is the wrong shape to catch the thing it most wants to catch.

 

What DWT changes

Digital Waste Tracking closes that gap by changing what gets reported and when. Instead of the receiver filing an aggregate tally every quarter, each movement gets reported into a central DEFRA service at the point it happens — and the report carries the movement-level detail the quarterly return never did: the producer it came from, the carrier who moved it, the waste type, the quantity, the receiving site.

The shift is from sum to movement, and from periodic to at the point of transfer. The regulator stops seeing a column of quarterly totals and starts seeing the individual journeys — who handed what to whom, and where it ended up — as linked digital records across all three parties.

Two things are worth being clear about, because they’re easy to get wrong:

This is in addition to the duty of care, not instead of it. As established in the earlier posts, the transfer note doesn’t disappear. You still record each transfer between the parties. DWT is a reporting obligation laid on top — the movement now also gets reported centrally.

It doesn’t replace the site return either, at least not in how you should think about it. The point isn’t that you swap one form for another. The point is the regulator’s routine visibility moves from “quarterly aggregate from the receiver only” to “every movement, as it happens, with all three parties named.” That’s a different order of visibility entirely.

 

What this means for receiving sites

If you run a receiving site, you sit at the centre of this. You’re the party DWT turns to first — receiving sites are in the first phase of the rollout, ahead of carriers and brokers — and you’re the one who’ll be reporting movements in. The aggregate return you’ve always done captured none of the producer and carrier detail; the movement reports will capture all of it, on every single load.

That’s a real change in workload if you’re starting from a spreadsheet and a filing cabinet. It’s a much smaller change if the information’s already structured — because the data DWT wants is a defined subset of what’s already on the transfer note you’re holding anyway.

In the next post we’ll get into Phase 1 specifically: who’s in scope from October 2026 (and January 2027 in Scotland), what a receiving site actually has to report, and why the real submission is a great deal smaller than the headline paperwork makes it look.

 

Next in this series: DWT Phase 1 — who’s in, what’s required, and when.