Due Dates vs Training Expiry
When to use course due dates for chasing completion versus expiry and renewals for certificate validity
The decision
Due dates answer "complete this by Friday" — they drive reminders, overdue status, and chasing. Expiry answers "this certificate is valid until next March" — then learners need to renew or get re-assigned after the certificate lapses.
Mixing them up leads to the wrong reports: you look at At-Risk / overdue when you meant expiring certificates, or you set expiry when you only needed a first-completion deadline.
Choose A when / Choose B when
| Choose | When |
|---|---|
| Due dates (deadlines) | New starters must finish induction soon; you want approaching / overdue reminders; managers chase incomplete work |
| Training expiry & renewals | Compliance must be retaken on a cycle (annual GDPR, fire safety); certificates expire; you need renewal windows and re-assignment |
| Both | Mandatory annual courses: a due date for this assignment cycle, plus expiry so last year’s completion does not count forever |
Tip
Configure due dates and expiry on the course (Edit Course / course details). Assignment still decides who receives the training.
Common mistakes
- Using only a due date for annual recertification — people finish once and never renew
- Using only expiry when you need urgent chasing of not-started assignments
- Reading Expiry & At-Risk reports without knowing which clock they use
Recommended setup
- For first-completion chasing, configure Course Deadlines & Reminders
- For recertification, configure Training Expiry & Renewals
- Assign via a Dynamic Group where membership should stay current — see Dynamic Groups vs Static Groups vs Individual Assignment
- Monitor with Expiry & At-Risk Reports
Related guides
- Course Deadlines & Reminders — due dates and reminder ladder
- Training Expiry & Renewals — validity, renewal window, re-assignment
- Expiry & At-Risk Reports — reporting views