Digital Waste Tracking software provider checklist
Use this buyer-side checklist before assuming that a DWT software product covers the waste receipts and scenarios your site actually handles.
1. Is the software integrated with the Receipt of Waste API?
Defra says software used for the Report receipt of waste service must be able to record and submit the legally required waste movement data and send it through the service API. A general waste-management package is not enough merely because it stores similar fields.
2. Has the provider passed the production approval tests?
Defra requires software providers to demonstrate 14 Production Approval Test scenarios. The GOV.UK compatible-provider list is the first place to check whether the supplier has reached the required production status.
3. Ask about PAT exemptions
A provider may have an exemption for scenarios its product does not support. GOV.UK gives hazardous-waste scenarios as an example. That does not automatically make the software unsuitable, but it means you need to compare the exemption with the waste streams and movements your own site receives.
4. Check the operational failure path
Ask what happens when a receipt is rejected, a required field is missing, the API is unavailable, or a record must be corrected. A polished submission screen does not prove that your underlying facts are complete.
5. Keep an independent preflight separate from submission
RegEvidenceHub does not replace the software provider and does not submit to Defra. Its role is narrower: structure supported receipt facts, surface missing information and evidence boundaries, and give you a second check before you rely on the record.
Related DWT guides
2-working-day deadline
Understand the submission clock for receiving sites.
Receiving-site checklist
Review the data categories to have ready.
Submission errors
Separate original submission errors from later corrections.
Official source
GOV.UK — Report receipt of waste: choose a software provider