Digital Waste Tracking for waste carriers: what changes in 2027?

The government's published development plan separates mandatory Digital Waste Tracking into phases. The receiving-site phase is now mandatory in England and Wales from 1 October 2026, with Scotland and Northern Ireland following on 1 January 2027.

For the next phase, GOV.UK currently plans private beta activity for waste collectors from autumn 2026, public beta from spring 2027 and mandatory use for waste collectors from October 2027.

Carriers sit in the middle of the waste movement. They already handle information about the customer, collection, vehicle, driver, material, destination and handover. If that data is structured and connected today, future digital reporting is less likely to become a separate administration exercise.

• Standardise customer, collection-site and receiving-site records.
• Keep carrier, vehicle and driver details structured rather than only in free text.
• Use consistent waste descriptions and classification codes.
• Create one movement or load reference that follows the job from assignment to receipt.
• Record handover, arrival, acceptance, rejection and incident events as they happen.
• Keep evidence of corrections and exceptions instead of overwriting the operational history.

Even before the collector phase becomes mandatory, receiving sites need carrier and movement information to complete their current reporting obligations. That means poor carrier data can already create delays or manual follow-up for customers and receiving facilities.

Carriers that provide clean, consistent movement information are therefore preparing for their own future obligations while also making the current receiving-site process easier for the organisations they work with.

The later collector phase is still being developed. Do not assume that every field, user journey or technical requirement used for receiving sites will be identical for carriers.

• Do not replace current legally required records purely because a later digital phase is planned.
• Do not build a process around an unconfirmed future field set.
• Do build clean operational records that can adapt as the collector service moves through beta and final guidance.

The useful work now is operational rather than speculative: identify where movement data is created, remove duplicate entry, standardise references and make sure office and field teams are working from the same job and load information.