Reading the small print: what the September 2025 update actually changed

Every few months the digital waste tracking specification gets a revision. Most are housekeeping. This one isn't — and one change in particular will quietly add work for the smallest operators if they don't plan for it.

We went through the September 2025 update clause by clause against the previous version. Stripping out the typo fixes and re-numbering, there are three substantive changes worth your attention.

1. EWC codes now require a sub-classification at point of capture

Previously you could submit a six-digit EWC code and resolve the detail later. The update expects the hazardous/non-hazardous determination and, where relevant, the mirror-entry decision at the point the movement is recorded — not at month end.

In practice this means the person with the waste in front of them needs to make the call. For a transfer station with trained staff, fine. For a sole-trader carrier loading a mixed skip, this is exactly the kind of judgement that used to get deferred to the office.

2. Consignee returns get a tighter clock

The window for a receiving site to confirm a hazardous load has been shortened. The spec now expects the consignee return within a defined period of acceptance rather than the looser 'reasonable time' language from before.

• Receivers will need to generate returns faster — manual end-of-week batching gets risky
• The clock starts at acceptance, so the weighbridge record needs an accurate timestamp
• Rejected loads need an explicit, recorded reason inside the same window

What to do about it

If you're a receiver, the fix is to generate the return at the gate, automatically, the moment a load is accepted. That's how the operative portal is built — the return is a by-product of logging the load, not a separate task.

3. The change that'll catch out smaller operators

Here's the one. The update clarifies that every waste movement — including those under exemptions that previously sat outside digital tracking — will need a digital record once the mandate is fully in force. The 'we only do small loads' exception that many sole traders were quietly relying on is narrowing.

“The mandate was never going to stop at the big operators. If you move waste for payment, you're in scope — the only question is whether you're ready.”

— Adam Reid, LoadSnap

If you're a tradesperson carrying your own waste, or a one-van scrap operation, this is the line to read twice. The good news: the work to comply is small if you start now and tiny if you let software do it.

What we'd do if we were you

1. 01Start capturing movements digitally this month, mandate or not — build the muscle memory
2. 02Make the hazardous determination at the point of collection, not at the office
3. 03If you receive waste, generate consignee returns at the gate
4. 04Pick a tool that submits to the DEFRA API for you, so a spec change is our problem, not yours

We update LoadSnap's submission engine every time the spec moves. That's the whole point of buying rather than building — you get to ignore the redlines.