The first three posts covered the ground DWT is built on — the three parties and two transfers of any movement, what a transfer note records, and the blind spot in the regulator’s current quarterly-return visibility. This post is about the first wave of the rollout: Phase 1. Who’s in it, when it bites, and — the part that matters most if you run a site — what you actually have to do about it.
Who’s in Phase 1 and when
Phase 1 starts at the end of the chain, with permitted and licensed receiving sites. If you hold a permit or licence to receive waste — a transfer station, a treatment facility, a materials recovery facility, a landfill — you’re in the first wave.
The dates:
- England, Wales and Northern Ireland: October 2026
- Scotland: January 2027
Carriers, brokers and dealers are not in Phase 1. They come later, in Phase 2 (October 2027). Until then the existing paper duty-of-care system carries on for the carrier side of a movement — which creates a slightly odd transitional situation where the receiving site is reporting carrier details into a digital system the carriers themselves aren’t yet obligated to use.
The whole thing rests on Section 58 of the Environment Act 2021, with each of the four nations laying the secondary legislation that actually switches the mandate on. The service opened in public beta in late April 2026, so the run-up to October is a window to get on it voluntarily before it’s a legal obligation. Sites operating under a registered exemption rather than a full permit or licence are not caught in Phase 1 — they come in later.
Why start at the receiving end?
It seems backwards to start tracking a journey at its destination rather than its origin. DEFRA’s logic is practical: there’s a known, finite, registered population of permitted and licensed sites — on the order of twelve thousand across the UK — and the regulators already know which of them are operational, because those are the sites filing the quarterly returns from the last post.
So you start with a population you can actually enumerate and hold to account, make each of those sites report every movement they receive — including the carrier who delivered it — and in one move you’ve gone from “aggregate tonnage from the receiver” to “every inbound movement, with the carrier named, as it happens.” It’s the fastest way to light up the blind spot without first having to corral every carrier and producer in the country.
Every load gets reported
Here’s the headline, and it’s simpler than most of the commentary makes it sound: every load of waste arriving at a receiving site has to have a digital record in the DWT service. Every movement, in — regardless of the type of waste. There’s no threshold, no carve-out, no “this kind counts and that kind doesn’t.” If it arrives at your gate, it gets logged.
What actually gets recorded
For each inbound movement, the record falls into three areas:
- What the waste is — its description, EWC code, quantity, and a POPs indicator where relevant.
- What happened before it arrived — chiefly the carrier who delivered it (more on the limits of that below).
- Where it is now and what happens next — the receiving site itself, and the onward treatment or disposal route.
That’s the spine of every record. Hazardous loads carry additional fields on top — hazard indicators, consignment-note detail and the like — but the structure is the same record, not a separate system. So you don’t need to think of it as “the haz process” and “the non-haz process.” It’s one record per load, with a bit more to fill in when the load is hazardous. Most of what any of it asks for is information you’re already capturing on the paperwork you keep today.
The receiving site reports what it knows — which is the carrier, not always the producer
This is the part that trips up a lot of the commentary, and it’s worth being precise about, because it explains the whole shape of Phase 1.
At a receiving site’s gate, only one transfer is actually taking place: carrier to receiver. That’s the handover the site is a party to, the one it witnesses, and the only one it can document first-hand. The earlier transfer — producer to carrier — happened somewhere else, earlier, and the receiving site wasn’t there for it.
Most of the time that’s fine, because the carrier delivering a load can tell you where it came from. But not always, and the man-and-van case is the clearest example. A small collection round picks up waste from a string of different producers across a day — a few trade counters, a couple of domestics, a builder’s job — tips the lot at the transfer station as one load, and hands over one transfer note covering that single carrier-to-receiver movement. The receiving site genuinely does not know, and has no reliable way to know, the individual producers behind that mixed load. From the gate’s point of view it’s one delivery, from one carrier, full stop.
That’s not a failing of the site or a gap to be scolded about — it’s just how aggregated collections physically work. And it’s exactly why Phase 1 pins the obligation on the carrier as the legal handover party, not the producer. The receiving site reports the party it actually dealt with. Producer-level identity is something the system can only capture reliably when the obligation reaches back to the producer-to-carrier transfer — which is precisely what Phase 2 does. Until then, asking a receiving site to certify producer detail it never saw would just manufacture inaccurate data.
So in practice: where the carrier provides clean producer information, by all means record it — it’s useful to you and it’ll matter later. But the load-bearing identity in a Phase 1 record, the one the system is built around at the receiving end, is the carrier. That’s the party the receiving site can always vouch for.
You almost certainly already hold this data
This is the reassuring part, and it’s worth saying plainly because the noise around DWT makes it sound like a from-scratch burden. It mostly isn’t.
Most receiving sites already run software — a weighbridge system, a waste management package, something that already records what comes in, from whom, carried by whom, in what quantity. The information DWT wants is, in large part, information these systems already hold in some form. The job for these sites isn’t to start recording from nothing. It’s to get on to your existing software provider and confirm they’re building the DWT submission into the product — embedding the connection to DEFRA’s service so that a record you’re already creating gets submitted automatically as part of your normal intake process. The serious vendors are already working on this; the thing to do now is make sure yours is one of them, and find out what their timeline and approach is well before October.
For sites that don’t have software, there’s a genuine choice of routes:
- New purpose-built tools. A wave of new software has appeared specifically to handle DWT submission for receiving sites — lighter and more focused than a full waste management system, built to get a movement logged and submitted quickly. If you’ve been running off paper and a spreadsheet, this is the moment the market is catering to.
- Manual spreadsheet submission. DEFRA also provides a manual route — submitting the data via a spreadsheet — for operators who don’t have software in place. It’s the fallback rather than the destination: it’s intended as a temporary bridge while operators acquire proper software, and it’s the most labour-intensive of the options because it’s hand-keyed per movement with no automation behind it. Workable for a low-volume site, painful at any real throughput.
The right answer depends on volume and on what you’re already running, but for the bulk of permitted sites it comes down to a single early action: call your software provider and pin down how they’re handling DWT. Everything else follows from that conversation.
The bits that make it workable
Two features of Phase 1 take the pressure off the obvious objections.
It’s not strictly real-time — yet. A movement doesn’t have to be reported the instant the lorry tips. The current rule is that the record goes in as soon as reasonably possible, and in any case within two working days — so a site with patchy connectivity at the weighbridge can log and sync within that window without breaching. Full real-time reporting is something DEFRA expects to phase in only after the service has been running for a couple of years.
Each movement gets a unique reference. Logging a movement returns a reference number from the central system. In Phase 1 this mainly does one job: it confirms the record was submitted and accepted. Its bigger purpose — being the single shared thread that links a movement across all the parties to it — only really comes into its own in Phase 2, when carriers are also reporting and there’s another party to link to. For now, treat it as a submission receipt; we’ll come back to what it’s really for in the next post.
There’s also a cost worth flagging: a service charge of £26 a year is payable by any legal entity creating or editing records in the service once it’s mandatory. Modest, but real, and your software provider can’t pay it on your behalf.
What it doesn’t change
Worth restating, because it’s the thread running through this whole series: Phase 1 does not retire your duty of care, and it does not retire the transfer note or the consignment note. DEFRA has been explicit that, at least through the transition, the existing obligations all stay live — you still complete and keep written descriptions of waste, still keep your transfer and consignment notes, still file your quarterly site returns and hazardous waste consignee returns. DWT reporting sits on top of all of that for now. The intention is that the digital record eventually replaces several of those paper obligations, but that’s a future state, not October 2026. For the time being it’s dual running, and that overlap is precisely why getting the submission embedded in software that’s already doing the other jobs is the sane play.
What to actually do about it
If you run a receiving site, the practical position is this. Every inbound load — hazardous or not — needs a digital record in the DWT service from your start date. The data it wants is, for the most part, data you already capture. The real question isn’t whether you have the information — it’s whether it’s structured to be submitted automatically rather than re-keyed by hand.
For most sites that means one phone call: to your existing software provider, to confirm DWT submission is being built in and on what timeline. For sites without software, it means choosing between the new purpose-built tools and the manual spreadsheet route, and the choice mostly comes down to how many movements you handle. Either way, the deadline is firm and the population is known — the regulator already has the list of who should be reporting — so starting on real movements during the beta, before October 2026 (or January 2027 in Scotland), turns this from a scramble into a routine software change.
In the final post we’ll look ahead to Phase 2 — carriers, brokers, dealers and the producer end of the chain — and what it means when the tracking extends all the way back to the point waste is produced.
Next in this series: DWT Phase 2 — extending the chain back to the producer.