> ## Documentation Index
> Fetch the complete documentation index at: https://signalschools.co.uk/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Reminders

> Set follow-up reminders on incidents so nothing gets missed. Assign a reminder to a colleague or leave it for the safeguarding team, and see everything that is due on your dashboard.

Reminders help you keep track of the follow-up actions a safeguarding case needs — a call to make, a meeting to arrange, a check-in in two weeks' time. You can add a reminder to any student incident, assign it to a colleague, and Signal makes sure it surfaces when it is due.

<Frame>
  <img src="https://mintcdn.com/signalschools-02f5aab3/sppl4yon0J8yThcC/reminders/incident-reminders.png?fit=max&auto=format&n=sppl4yon0J8yThcC&q=85&s=6965c2ad5bb4cd09852a77cec8e64912" alt="The Reminders section on an incident showing an overdue reminder and an upcoming reminder, each assigned to a staff member" width="608" height="198" data-path="reminders/incident-reminders.png" />
</Frame>

<Note>
  You need the **Contributor** role or above to add reminders.
</Note>

## Adding a reminder manually

<Steps>
  ### Open the student incident

  Open the student incident you want to set a reminder on. Reminders are available on student incidents only.

  ### Open the actions menu

  Open the incident's **More actions** (⋮) menu and select **Create Reminder**.

  ### Describe the follow-up

  Write a short **description** of what needs to happen — for example, "Call mum to arrange a meeting".

  ### Set a due date

  Choose the **due date**. Reminders due today or in the past are highlighted so they stand out.

  ### Assign it (optional)

  Assign the reminder to a specific member of staff, or leave it **unassigned**. Unassigned reminders are treated as a task for the safeguarding team and are visible to DSL-level staff.

  ### Save

  Click **Add Reminder**. It appears in the incident's Reminders section straight away.
</Steps>

## Who can complete, edit, and delete

* **Complete** — the assigned staff member, or any DSL-level user, can mark a reminder complete once the follow-up is done.
* **Edit and delete** — the person who created the reminder, or any DSL-level user, can change or remove it.

Marking a reminder complete removes it from the list of outstanding reminders and from any due-reminder views.

## Seeing what is due

Reminders assigned to you — and unassigned reminders for your school if you are a DSL-level user — appear in your **due reminders** so you can see everything that needs attention in one place. Overdue reminders are highlighted.

You will also see a summary of reminders that are due or overdue in your [daily digest email](/docs/notifications/daily-digest).

## Reminders from workflows

As well as adding reminders by hand, you can have Signal create them automatically. A [workflow](/docs/workflows/reminders) can add a reminder whenever a matching incident is recorded — for example, "Review this case in 7 days" on every high-priority incident. Automatically created reminders behave exactly like manual ones.