Recurring Schedules
Set up weekly, fortnightly, or monthly collection templates that automatically generate scheduled jobs.
1. Open Schedules→
2. Click + New Schedule→
3. Set title and frequency→
4. Set start date and day→
5. Assign driver, customer, and site→
6. Add waste details→
7. Save — recurring jobs are generated automatically
1. Schedule Details
The core fields that define the recurring pattern.
New Recurring Schedule
Create a repeating collection template
Monday skip collection — City Centre
Choose a descriptive name so the schedule is easy to identify in the list.
Weekly▾
Fortnightly generates every other week. Monthly requires a day of the month.
Shown when: Required when frequency is Weekly or Fortnightly
Monday▾
Required for Weekly and Fortnightly schedules.
Shown when: Required when frequency is Monthly
15▾
Required for Monthly schedules. If the month is shorter than the selected day, the last day of the month is used.
2026-03-17
The first date from which collections will be generated.
2026-12-31
Leave blank for an open-ended schedule with no end date.
07:30
2. Assignment
Assign the recurring schedule to a driver, customer, site, and optionally link it to a season ticket.
New Recurring Schedule
Create a repeating collection template
Acme Builders Ltd▾
City Road Transfer Station▾
James Hartley▾
ST-2026-001▾
Only signed season ticket notes appear in this list.
3. Waste Details
Pre-populate waste information that will be inherited by each generated collection.
New Recurring Schedule
Create a repeating collection template
e.g. General commercial waste
e.g. 20 03 01, 15 01 01
Enter as comma-separated values, e.g. 20 03 01, 15 01 06.
e.g. 500 kg
4. Additional Notes
A notes field for any additional instructions or context about the recurring schedule.
New Recurring Schedule
Create a repeating collection template
Any additional notes about this schedule...
Create Schedule
Cancel
Link a season ticket for paperless recurring transfers
If you have a season ticket agreement in place with a regular customer, link it to the recurring schedule. Each generated collection will reference the season ticket, reducing the paperwork required per visit.
Day of Week and Day of Month are frequency-dependent
The Day of Week field only appears for Weekly and Fortnightly frequencies. The Day of Month field only appears for Monthly frequency. Both are required when visible — saving without them will show a validation error.
Recurring schedules and one-off collections are separate
Changes to a recurring schedule template do not retroactively update generated collections that already exist. Edits to the template only affect future generated collections.
Common Mistakes
• Not setting the Day of Week for a Weekly schedule — this will trigger a validation error on save.
• Setting an end date in the past — the schedule will not generate any future collections. Leave the end date blank for open-ended schedules.
• Entering EWC codes in a wrong format in the recurring schedule form — codes must be comma-separated (e.g. 20 03 01, 15 01 01). The form does not use the EWC code picker — it is a plain text field.
Field Reference
| Field | Required | Description |
|---|---|---|
| Title | Yes | Human-readable name for the recurring schedule. |
| Frequency | Yes | How often the collection repeats. |
| Day of Week | Yes | Which day of the week the collection takes place. |
| Day of Month | Yes | Which day of the month the collection takes place. |
| Start Date | Yes | The date from which the recurring schedule becomes active. |
| End Date | No | Optional end date. Collections are generated up to and including this date. |
| Preferred Time | No | Optional preferred time of day for the collection — free text. |
| Customer | No | Customer whose waste is collected on each run. Populated from your saved clients. |
| Site | No | Transfer site for the collection. Populated from your saved sites. |
| Driver | No | Driver assigned to this recurring schedule. Each generated job will have the same driver. |
| Season Ticket | No | Link a season ticket to this schedule. The linked ticket is referenced on each generated collection. |
| Waste Description | No | Description of the waste stream for this recurring collection. |
| EWC Codes | No | EWC codes for the expected waste types. Comma-separated in the recurring schedule form. |
| Estimated Quantity | No | Estimated waste quantity per collection run — free text. |
| Additional Notes | No | Notes applied to the recurring schedule record. Not automatically copied to each generated collection. |
Related Articles
Scheduling Overview
Plan and manage waste collections, transfer runs, and recurring pickups for your drivers.
Creating Collections
Schedule a one-off waste collection or transfer run, assign a driver, and specify waste details.
Driver Assignment
Assign drivers to scheduled collections so jobs appear in their driver app and are correctly attributed.