# Incident Deadline Notifications

Source: https://docs.astalty.com.au/guide/notifications/incident-deadline-notifications

> Set up reminders before an incident's reporting deadline, choose who receives them, and understand when alerts stop.

Astalty Premium - This feature is part of the Astalty Premium plan. See What Premium includes.

Set up **Incident Deadlines** notifications to alert your team before a reportable incident's reporting deadline. Each rule can warn about the **24-hour notification** and **5-day report**, where those deadlines apply to the incident type recorded in Astalty.

Only Admins can manage these notifications. Before relying on a reminder, check the incident's reportable status, type and awareness time in [Incident Follow Up](https://docs.astalty.com.au/guide/incidents/incident-follow-up).

## Create A Deadline Notification

1. Open [**Notifications**](https://app.astalty.com.au/notifications), then choose **Incident Deadlines** under **Forms**.
2. Select **Create Notification**.
3. Enter **Hours**, from 1 to 72. The default is 4 hours before each deadline.
4. Optionally add **Notification email content**, such as your team's follow-up instructions. This appears in emails only.
5. Choose at least one recipient under **Notification recipients**.
6. Choose **Within Astalty**, **Email**, or both under **Notification methods**. **Within Astalty** is selected by default.
7. Select **Add Notification**.

The rule appears in the list. Use its actions menu to **Edit**, **Clone** or **Delete** it. You can create separate rules for different lead times or recipients.

## Choose Recipients

- **Assigned user** sends the warning to the incident's assignee.
- **Primary Coordinator** includes the Primary Coordinator of each Participant involved in the incident.
- **Service Coordinator** includes the coordinators of Services on each involved Participant's current plan.
- **User Groups** and **Users** send the warning to the staff you select directly.

The assignee and coordinator options are all off by default. If an incident has no assignee or involved Participant with a coordinator, those options have nobody to notify. Include a responsible user or group so an unassigned incident still reaches someone. The **All Users** and **Support Worker** groups are not offered.

Deactivated users are skipped. Someone selected in more than one way receives one warning per rule and deadline.

## When Warnings Are Sent

Astalty checks hourly. A warning is sent when an unmet deadline is within the rule's lead time and is still in the future. For example, a 4-hour rule can warn when fewer than 4 hours remain, even if the incident was entered after that window began.

Each rule sends once for each deadline on an incident. It does not send repeated countdown reminders, and changing the rule's lead time does not resend a warning already sent. If several rules match, each can send its own warning.

Warnings stop for a deadline when its reporting details have been recorded. Resolved and archived incidents are excluded. See [Incident Follow Up](https://docs.astalty.com.au/guide/incidents/incident-follow-up) for how the incident type and reporting fields affect its clocks.

> **Overdue deadlines do not trigger a catch-up warning**
>
> If the deadline has already passed when Astalty checks, this notification does not send. Review the incident's deadline badges as well as notifications, especially when entering an incident late.

## Complete The Reporting Step

Open the incident from the warning, check what is due, and complete the reporting step. Recording a Commission reference or submission date in Astalty tracks your progress; it does not submit a report to the NDIS Commission. Follow the [NDIS Commission's reportable incident guidance](https://www.ndiscommission.gov.au/rules-and-standards/reportable-incidents-and-incident-management/reportable-incidents) for the reporting requirements and portal.

For reminders about incidents that have stayed in the same status, use [Incident Follow Up Notifications](https://docs.astalty.com.au/guide/notifications/incident-follow-up-notifications).