# Lapsed Qualification Notifications Source: https://docs.astalty.com.au/guide/notifications/lapsed-qualification-notifications > Get alerted when a rostered worker will not meet a required qualification at the start of an upcoming shift. Scheduling add-on - This feature requires the Scheduling add-on, which is available on Astalty Premium. See How to enable Scheduling. ## Overview A worker can be perfectly qualified when you build the roster, and no longer qualified by the time the shift comes around - their First Aid expires in the meantime. **Lapsed Qualification Notifications** catch exactly that. A daily check looks ahead at upcoming shifts and alerts your team when a rostered worker will not meet a [required qualification](https://docs.astalty.com.au/guide/settings/users-settings/qualifications) at the shift's start time. A record that is current today but expires before the shift can trigger the alert, giving you time to arrange a renewal or reassign the shift. ## Finding the notification Head to the [Notifications](https://app.astalty.com.au/notifications) page in Astalty and click **Lapsed Qualifications** under the **Scheduling** group, or go straight to [Lapsed Qualification Notifications](https://app.astalty.com.au/notifications/qualification-lapse). It appears when both Scheduling and Qualifications are turned on for your account. Only Admins can manage these notifications. This can't be changed per user. ![The Notifications page with lapsed typed into Search notifications, showing the Lapsed Qualifications row under Scheduling with Admin User as the recipient and both delivery methods.](https://docs.astalty.com.au/assets/lapsed-qualification-notifications-find.png) ## Creating the notification Click **Create Notification** and complete the drawer. ![The Create Lapsed Qualification Notification drawer with Notify this many days ahead of the shift set to 14 and the User Groups list open, showing Admin selected and the Manager, NSW Team, QLD Team, Team Member and Clinical Care groups with their member counts.](https://docs.astalty.com.au/assets/lapsed-qualification-notification-create.png) ### When would you like to be notified? Set **Notify this many days ahead of the shift** - how far in advance you want the warning. It defaults to **7** days, and accepts anything from 1 to 90. The section explains it as: > A daily check alerts the selected recipients when a worker on an upcoming shift no longer holds a required qualification, so the shift can be reassigned. ### Notification recipients Choose who gets told, using **User Groups**, **Users**, or both. You must select at least one recipient. The **All Users** and **Support Worker** groups aren't offered. Deactivated users are skipped. ### Notification methods Choose **Within Astalty**, **Email**, or both. **Email** is ticked by default and **Within Astalty** is not. You must select at least one method. Click **Add Notification** to save. ## What recipients see Notifications are a **digest** - one message covering every affected worker, not one message per worker. In Astalty, the notification is titled **Lapsed Qualifications**. By email, the subject is **Lapsed qualifications on upcoming shifts**. Both open with a summary: > 3 support workers no longer hold a required qualification for upcoming shifts. Then one line per worker: > Jane Citizen - First Aid and Manual Handling (3 shifts from 4 Aug 2026) A **View Schedule** button takes recipients straight to the schedule to reassign the work. Both **Warn**-level and **Block**-level requirements are included, and Participant-based requirements are included as well as role-based ones. ## How the daily check works The check runs **once a day, at 9:15am AEST (Brisbane time)**. Each time it runs, it looks at **one single day** - the day that falls exactly your chosen number of days ahead. With a 7-day lead time, a check running today looks only at shifts 7 days from now. That's what stops you being alerted about the same shift over and over: each shift passes through the window on exactly one day, so in normal use you get **one alert per shift, per notification**. > **Changing the lead time can cause repeat or missed alerts** > > Because the check looks at a single day rather than tracking what it has already sent, the "alert once" behaviour depends on your settings staying put. > > If you **change the lead time** - or your organisation's timezone changes - the window moves. Shifts you've already been alerted about can be alerted again, and shifts can slip past the window entirely without ever being alerted. > > Set your lead time deliberately and leave it alone. If you want two different warnings, add a second notification rather than editing the first. There are two other gaps worth knowing about: - **A day the check doesn't run is never revisited.** If the check misses a day, the shifts that fell in that day's window aren't picked up later. - **Later changes are not checked again.** If a record is declined, removed or given an earlier expiry after the shift's window day, that shift is not revisited. A known expiry before the shift is already considered during the original check. Neither replaces the [Qualifications Compliance Report](https://docs.astalty.com.au/guide/reports/qualifications-compliance-report) as a periodic check. ## Who's included The check covers assigned shifts, excluding unpaid breaks and cancelled supports. Any worker who isn't deactivated is in scope. > **Wider coverage than the compliance report** > > The compliance report only covers workers who are rosterable and neither Restricted nor Deactivated. > > Lapse notifications cover anyone who isn't deactivated - so a restricted or non-rosterable worker who still has shift assignments can trigger a lapse notification while never appearing on the report. ## Managing notifications The list shows each notification's **Notice** (how many days ahead), **Delivery** and **Recipients**. Use the row menu to **Edit**, **Clone** or **Delete** a notification. Cloning is handy for creating a second warning at a different lead time. ![The Lapsed Qualification Notifications page listing one notification 18 days before the shift, delivered within Astalty and by email to Admin User, with an actions menu at the end of the row.](https://docs.astalty.com.au/assets/lapsed-qualification-notifications-list.png) **Edit** reopens the same fields, so you can change the lead time, add or remove recipients, or switch the notification methods. **Delete** at the bottom left of the drawer removes the notification altogether. ![The Update Lapsed Qualification Notification drawer with 18 days ahead of the shift, Admin User selected under Users, Within Astalty and Email ticked, and Delete, Cancel and Update Notification at the bottom.](https://docs.astalty.com.au/assets/lapsed-qualification-notification-edit.png) ![The Update Lapsed Qualification Notification drawer with the Users list open, showing Admin User selected and other users such as Sierra Runolfsson, Helena Grimes and Stella Lesch to choose from.](https://docs.astalty.com.au/assets/lapsed-qualification-notification-edit-users.png) You can create as many as you like. For example, one at 14 days for planning and another at 3 days as a final check. ## Related guides - [Required Qualifications in Settings](https://docs.astalty.com.au/guide/settings/users-settings/qualifications) - set up which records are required for rostering. - [Qualification Checks When Rostering](https://docs.astalty.com.au/guide/scheduling/qualification-checks) - what schedulers see at the time they roster. - [User Record Notification](https://docs.astalty.com.au/guide/notifications/user-record-notification) - alerts on record expiry generally, not just those required for rostering.