Six Steps for Reliable Digital Waste Tracking at Receiving Sites
By [email protected] 479 views
Clear roles, checked data and a daily workflow can help receiving sites submit accurate waste records and resolve errors on time.

Digital waste tracking depends on a chain of people and decisions: someone records each receipt, someone checks the details, and someone confirms that the submission has been accepted. For receiving sites, preparing that chain is as important as choosing reporting software.

At a webinar hosted by CIWM with Vaste, attendees identified staff training and process changes as their leading concerns. Vaste founder and CEO Evans Chelal and chief technology officer Michael Coll discussed how receiving teams can prepare. Their practical guidance comes down to six steps.
1. Confirm which sites are covered and assign responsibility
Mandatory reporting for covered receiving sites began in England and Wales on 1 October 2026. Scotland and Northern Ireland are scheduled to follow on 1 January 2027. The timetable and site requirements are available in Defra’s reporting guidance.
Start by reviewing each site’s activities against the scope guidance for received waste. Permitted or licensed sites that receive controlled waste are the starting point, but teams should check the specific exclusions that may apply.
Responsibility rests with the permit holder, Chelal said. Where a contractor handles site operations, set out who collects the information, checks it, submits records and follows up on problems. Written arrangements help both organisations understand where each task sits.
2. Set up organisational access and permissions
Registration should use the organisation’s Government Gateway or GOV.UK One Login account; Defra says personal Government Gateway accounts must not be used. Organisations reporting through an API receive a unique connection code. One organisation can use its code across its sites, while separate organisations need separate codes. Defra explains the process in its account instructions.
Once the organisation is set up, check that its sites and permits appear correctly in the reporting system. Decide who can prepare a draft, who reviews the entry and who is authorised to submit it. Chelal described this work as carrying existing governance controls into the digital system.
Plan for staff absence as well. A colleague providing cover needs the right access and clear instructions to pick up the task without relying on one person’s memory.
3. Verify the information before submission
Trace a recent waste receipt from arrival through the records used to prepare its report. Identify where each detail comes from, who can confirm it and what should happen when information is unclear.
Reported details include the waste classification, carrier and receiving site, along with information on hazardous waste or persistent organic pollutants where relevant. In the software demonstration, Coll stressed that teams must submit the required information.
Some systems can limit the waste codes available at a site to codes associated with its permit. That can reduce selection errors, but it cannot determine whether a code accurately describes the waste in a specific load. Staff still need to check the details and raise discrepancies with someone who can resolve them.
4. Choose a reporting method that fits the work
Defra provides a spreadsheet route, software that connects through an application programming interface, or a combination of the two. The spreadsheet option is temporary and is currently expected to remain available until at least October 2027. The service development plans describe the current arrangements.
Assess the method against the work your sites actually handle: how often information is entered, whether it arrives from several systems, the time needed for checks, and how processes vary between sites. The demonstration included individual entries, batch imports and links with existing software. These are useful scenarios to ask providers to show using examples that resemble your operation.
For API software, check its integration and production approval status and whether any exemptions affect your waste movements. Defra’s provider guidance sets out what to check. If using the spreadsheet route, use Defra’s template without changing it, and start a fresh spreadsheet after each submission.
Ask how the system handles reviews, failed submissions, amendments, user access and support. A representative demonstration should clarify what staff still need to do around the software.
5. Make reporting part of the shift
Coll recommended that teams make reporting a daily task, at the end of a shift. That routine can leave time to check entries and investigate missing information before deadlines approach.
In England and Wales, the standard reporting deadline is two working days, beginning the day after receipt; weekends and bank holidays are excluded. For a receipt on an ordinary Monday, the report and its unique reference are due by 11:59pm on Wednesday.
Agree when staff will gather, review and submit information. Keep unfinished work visible and distinguish records awaiting clarification from those that are ready but have not yet been submitted. Assign someone to monitor each queue and follow up when work builds up.
6. Check acceptance and handle corrections
Staff need to recognise the difference between a draft, a failed submission and a record accepted by the service. Keep the returned tracking reference with the corresponding receipt. Acceptance confirms that the record was received; it does not, by itself, confirm that every detail is accurate or that all obligations have been met.
Coll demonstrated updating an existing record while retaining its reference. Ask the provider how it confirms amendments and lets colleagues review a record’s history. Current England and Wales guidance says errors must be corrected promptly and within one month of discovery. If the service identifies a submission error, correction is due within the original two-working-day window.
Digital reporting also sits alongside existing documentation duties, including applicable transfer and consignment notes and required waste returns. Teams can check the relevant reporting and documentation requirements.
Test the workflow with the people who use it
A supervised walkthrough can reveal gaps before they affect routine work. Include a receipt with an uncertain detail, an amendment and a handover to a colleague covering an absence. Record what needs resolving, who owns the next step and when they will follow up.
Give each participant a practical task: explain where carrier information comes from, show how to flag a discrepancy, or find out whether a submission succeeded. Include the operational colleagues who provide information, so the team can test the whole path from arrival to confirmed submission. Use a suitable training environment, keep short instructions close to the work and revisit them when the system changes.
Chelal’s readiness questions are direct: “Do you have your teams in place? Have you started training?” Clear answers, backed by a walkthrough, give receiving sites a practical way to turn digital reporting requirements into a routine staff can follow.