With mandatory Digital Waste Tracking arriving in October 2026, many AD plant operators are evaluating software for the first time — or reconsidering systems that were adequate for paper WTNs but won't scale to DWT. This guide focuses on what actually matters when choosing: the features you cannot compromise on, what to ask vendors before you commit, and how to match software capabilities to your plant's specific volume and feedstock mix.
Many AD plant operators have tried to manage compliance with spreadsheets, generic database tools, or even paper systems. These approaches share common failure modes that become increasingly costly as DWT approaches:
Spreadsheets
Paper WTNs
Not all features matter equally. The checklist below separates what is genuinely required for legal compliance from what adds operational value at higher volumes:
Compliance essentials — must have
Digital WTN creation
All five parts (A–E), fully structured, with every legally required field.
EWC code lookup and validation
Searchable catalogue with hazardous (asterisk) codes flagged.
Carrier registration check
Verify CBDU/CBDL numbers against the EA register before acceptance.
Digital signatures
Legally binding under the Electronic Communications Act 2000.
Cloud storage — 2+ year retention
Minimum two years for England/Wales/NI, three for Scotland. Ideally indefinite.
DEFRA DWT API — confirmed roadmap
Not "planned" — a confirmed integration timeline with the national DWT service.
Instant audit retrieval
Any record searchable by date, producer, waste type, or carrier within seconds.
High-volume AD plant features — strongly recommended
Weighbridge CSV import
Automatic ingestion from Globeweigh, Avery Weigh-Tronix, Mettler Toledo, Rice Lake, and others.
Season Ticket management
Create master Season Tickets with linked dockets for each delivery.
Pick lists and templates
Pre-saved EWC codes, waste descriptions, carrier details, and recovery codes per stream.
Multi-user access with permissions
Weighbridge operators, site managers, and admin staff with appropriate access levels.
Duplicate detection
Prevents the same weighbridge ticket being imported twice.
PDF and CSV export
Complete records in usable format for EA inspections and permit reporting.
Mobile WTN creation
Capture signatures, photos, and GPS location on-site from any device.
The DWT system requires specific data fields for every incoming waste movement. Your software must capture all of these at the point of intake — not retrospectively. Any software you choose must be able to populate all of the following:
| Data category | Required fields | Notes |
|---|---|---|
| Waste producer | Name, address, SIC code | SIC code identifies the industry sector generating the waste |
| Waste carrier | Registration number (CBDU/CBDL), vehicle reg | Must be verified against the EA public register before acceptance |
| Waste description | Written description, EWC code | 6-digit code required; hazardous codes (asterisk) require consignment note |
| Quantity | Weight (tonnes) or volume (m³) | Weighbridge data is preferred for accuracy |
| Your facility | Environmental permit number, address | The permit reference for the receiving AD plant |
| Transfer details | Date, time, DWT tracking ID | DWT system will assign a unique ID to each movement record |
| Recovery operation | R code (R3 for AD feedstock) | R3 = recycling/reclamation of organic substances |
Most AD plants accept feedstock from several distinct source types, each with different EWC codes, documentation requirements, and in some cases ABP obligations. Good software lets you build a customer database with pre-saved defaults for each supplier — so when a delivery arrives, the operator selects the customer record and the waste type, producer, and carrier fields pre-populate automatically.
Food waste — commercial
May contain Cat 3 ABPsSupermarkets, restaurants, hotels, caterers, food manufacturers
Agricultural waste
Cat 2 ABP rules applyCrop residues, silage, manure, slurry from farms
Industrial by-products
Breweries, dairies, distilleries, food processors
Fats, oils, and grease (FOG)
High biogas yieldUsed cooking oil, grease trap waste from hospitality
The key capability to look for is pick lists — configurable dropdown menus of your commonly-used EWC codes, waste descriptions, carrier details, and recovery codes. This prevents typos in data-critical fields and dramatically speeds up intake documentation for high-volume sites.
Accurate weights are essential for permit compliance (tonnage limits), invoicing, and DWT reporting. For any plant processing more than a few hundred tonnes per month, manual weight transcription from weighbridge tickets is where most data errors originate and where most admin time is wasted.
A busy AD plant processing 30 deliveries per day at 5 minutes manual entry each generates 2.5 hours of data-entry admin per day — over 12 hours per week spent copying numbers from a printed ticket into a form, creating transcription risk at every step.
What good weighbridge integration looks like:
Your weighbridge software saves a CSV file to a designated folder whenever a weighing completes. No manual action required.
Software monitors the folder and picks up new files within seconds. Using your pre-configured column mapping (Column G = Net Weight, Column B = Vehicle Registration, etc.), it maps the data to WTN fields automatically.
Parsed records are held for human review before being committed as WTNs. Any missing fields — a new customer not yet in the system, an unrecognised vehicle registration — are flagged for completion.
The system checks against previously imported ticket numbers, timestamps, and vehicle registrations to prevent the same load appearing twice — a common problem when CSV files are reprocessed after a system restart.
Compatible weighbridge systems
For AD plants with regular contracted feedstock suppliers, the choice between individual WTNs and Season Tickets has a direct impact on daily admin volume. The table below shows the practical difference for a plant with 10 contracted suppliers each delivering weekly:
| Metric | Individual WTNs | Season Tickets |
|---|---|---|
| Documents per supplier per year | 52 WTNs | 1 Season Ticket + 52 dockets |
| Signatures required per supplier | 156 (3 per WTN) | 3 (on master Season Ticket only) |
| Time per delivery | ~10 minutes | ~30 seconds (docket only) |
| Annual admin — 10 suppliers | ~87 hours | ~9 hours |
| Legally valid | Yes | Yes |
| DWT compatible | Yes | Yes |
Season Tickets are appropriate when the same waste type arrives from the same producer via the same carrier on a recurring basis. Any variation in carrier, waste type, or producer requires an individual WTN for that delivery.
For the full Season Ticket workflow, see the WTNs vs Season Tickets guide.
The DWT service will accept waste movement data through several channels. The right method depends entirely on your volume — but for any site processing more than a handful of deliveries per day, only the API route is practically sustainable:
| Method | Best for | Advantages | Limitations |
|---|---|---|---|
| API integration | Sites using waste management software | Fully automated — records submit directly from your software | Requires software with a confirmed, working DWT API integration |
| CSV upload | Batch submissions from spreadsheets | Works without specialist software | Manual formatting required for each submission; error-prone at scale |
| Government web portal | Low-volume sites or occasional records | No software required; free to use (£26/year service charge) | Manual entry for every movement; impractical for 50+ deliveries per week |
Most waste software vendors will claim DWT readiness and weighbridge compatibility. These questions separate genuine capability from marketing copy:
Is your DEFRA DWT API integration confirmed, or just "planned"?
Many vendors claim DWT readiness without having built anything. Ask for a specific integration timeline and whether they participated in DEFRA's developer programme.
Can you demonstrate weighbridge CSV import with my specific system?
Column mapping between weighbridge exports and WTN fields requires configuration. Ask for a live demo using a sample CSV from your own weighbridge before committing.
How is your pricing structured — per user, per WTN, or flat rate?
Per-seat pricing can become expensive when you have weighbridge operators, site managers, and admin staff all needing access. Flat-rate pricing is more predictable for AD plants.
What is your data export policy if we switch providers?
Your WTN records have a two-year (or three-year in Scotland) legal retention obligation. Ensure you can export all records in a usable format if you change software.
Do you support Season Tickets and linked dockets for individual deliveries?
Some basic WTN tools only support individual WTNs. For regular feedstock contracts, Season Ticket support is essential.
How quickly can any record be retrieved during an EA inspection?
During a surprise inspection you need to produce specific records immediately. The answer should be "within seconds by searching date, producer, or waste type" — not "we'll look through the folder".
The October 2026 deadline is fixed. Here is a practical sequence for AD plant operators who are not yet fully digital:
Review all current WTNs for completeness. Identify common problems: missing EWC codes, unverified carrier registration numbers, vague waste descriptions. These issues are easier to resolve before you migrate than after.
Select a platform using the checklist above. Allow four to six weeks for implementation, weighbridge configuration, pick list setup, and staff training before relying on it for live records. Do not leave this to Q3 2026.
Identify all contracted feedstock suppliers receiving regular, consistent deliveries. Create a Season Ticket for each. This reduces ongoing daily admin immediately and simplifies DWT submission — one Season Ticket reference submitted once, with docket data per delivery.
The government's public beta opens in spring 2026 for all permitted receiving sites. Voluntary participation now means your team learns the system without a compliance clock running. Identify data gaps while there is still time to fix them.
Do not assume your software vendor's API integration will be ready on 1 October 2026. Confirm a working, tested integration by August 2026 at the latest — leaving time to resolve issues before the mandatory deadline.
What software features do AD plants need for DWT 2026 compliance?
At minimum: digital WTN creation with EWC code validation, carrier registration verification, digital signatures, two-year cloud retention, and a confirmed DEFRA DWT API integration. For high-volume sites: weighbridge CSV import, Season Ticket management, pick lists per feedstock stream, and multi-user access with role permissions.
How much does waste management software for AD plants cost?
Entry-level digital WTN solutions start from around £20–50 per month. Mid-range platforms with weighbridge integration and Season Ticket support typically cost £50–150 per month. Enterprise solutions with full ERP integration are £200+ per month. Most providers offer free trials — test with your actual data before committing.
Can waste management software integrate with my weighbridge?
Yes, provided your weighbridge exports CSV files — which virtually all commercial weighbridge systems do. The key variable is column mapping: your software needs to be configured to match your specific CSV layout. Ask any vendor to demonstrate this with a sample file from your system before you sign up.
Should we use Season Tickets or individual WTNs for our regular feedstock contracts?
Season Tickets for contracted regular suppliers, individual WTNs for one-off or variable deliveries. The three conditions for Season Ticket eligibility are: same waste type, same carrier, same producer. If any of these changes for a particular delivery, an individual WTN is required for that load.
When does Digital Waste Tracking become mandatory for AD plants?
October 2026 for England, Wales, and Northern Ireland. January 2027 for Scotland. The public beta is available from spring 2026. Carriers face a mandatory deadline of October 2027.
What is the best way to submit data to DWT — API, CSV, or the government portal?
API integration via your waste management software is the only practical option for high-volume sites. CSV uploads work for batch submissions but require manual formatting. The government portal works for very low volumes but is impractical for sites with 20+ deliveries per week.
Related guides
WasteBolt
WasteBolt is used by anaerobic digestion facilities across the UK to manage feedstock intake records, Season Tickets, weighbridge CSV import, digestate WTNs, and DWT 2026 submission. Start your free trial and see how it fits your operation.
No credit card required · Cancel any time · DWT 2026 ready
Stay ahead of UK waste compliance
Get practical guides, regulatory updates, and the occasional WasteBolt discount — straight to your inbox. No spam, unsubscribe any time.
By subscribing you agree to receive marketing emails from WasteBolt. See our Privacy Policy. Unsubscribe any time.