How Season Tickets Interact With DWT
If you use season tickets for a recurring collection arrangement, it's worth being clear on one thing: the ticket itself is never what gets submitted to Digital Waste Tracking. Here's what actually happens.
The Ticket Is a Template, Not a Submission
A season ticket holds the agreed, recurring details for a collection arrangement — producer, carrier, receiver, waste type, EWC code, and typical schedule. It exists so you don't have to re-enter those details every time. It is not itself a transfer note and is never sent anywhere.
One ticket, many loads, many submissions
Each Load Is Its Own Submission
Every time a collection actually happens, you log a load against the season ticket. That load copies across all the ticket's agreed compliance details automatically — you typically only need to confirm the weight and date — and it's that individual load record that appears on the Digital Waste Tracking page and gets submitted, exactly like a standalone WTN would.
Renewals and Expiry
Season tickets carry a validity period. Loads logged while it's active submit normally. Once it expires, WasteBolt blocks logging further loads against it until you renew the ticket or set up a new one — this stops out-of-date carrier or permit details from being carried into new submissions by mistake.
Why Use Season Tickets at All
For a regular weekly or monthly collection with the same customer, carrier, and waste stream, a season ticket means each load takes seconds to log — no re-typing permit numbers, EWC codes, or addresses — while every single load still gets its own, fully compliant DWT submission.