Two pages in **Assure** help you keep an eye on things without opening every site. **Assure → Reviews** is a short summary of your monitored sites. **Assure → Schedules** lists every audit schedule in your subscription, so you can see what runs when, run one now, and choose who hears about the results.

## Before you start

- **Reviews** needs site monitoring in your package and permission to view monitoring. See [Monitoring your sites](/assure-and-diagnose/monitoring).
- **Schedules** needs audits in your package and permission to view audit schedules, with separate permission to create or change them. See [Package and add-ons](/account-and-access/package-and-add-ons) and [Users, teams, groups and permissions](/account-and-access/users-teams-groups-and-permissions).
- A schedule runs against an audit target. Create the target first, or add a repository, which creates one for you. See [Audits, targets and health reports](/assure-and-diagnose/audits-and-findings) and [Repository audits](/assure-and-diagnose/repository-audits).

## Reading the Reviews page

Go to **Assure → Reviews**. The **Monitoring Overview** shows:

- A **Sites** card with the number of monitored sites, their average response time and how many incidents there are.
- A **Sites** section with **Total sites**, **Healthy**, **Degraded**, **Failing**, **Average response time** and **Recent incidents**. The current slowest site is named under **Recent incidents**.
- A short list of your sites with their domains, current status and latest response time. Select a site to open it.

Select **Open Sites** to go to the full monitoring page, or the refresh button (**Refresh overview**) to update the figures. If you have no sites yet, you'll see "No sites found".

## The Schedules page

Go to **Assure → Schedules**. Each schedule shows its name, target, trigger, status, and when it will next run and last ran. For each schedule you can:

- select **Run now** to start it straight away. The run's health report opens.
- select **Latest report** to open the report from its most recent run.
- select **Edit** to change it.

If you've set up a repository audit schedule, it appears here as **Repository schedule** under that repository's target. Change it from the repository's own page so its check groups stay in step. See [Repository audits](/assure-and-diagnose/repository-audits).

## Creating a schedule

1. Go to **Assure → Schedules** and select **New**. You can also open a target on **Diagnose → Targets** and select **Add schedule** in its **Schedules** section, which chooses the target for you.
2. Under **Schedule**, check the **Status** is **Enabled**, enter a **Name** and choose the **Target**.
3. Choose a **Trigger**:
   - **On a schedule** runs at set times. Choose **Daily**, **Weekly** or **Monthly** under **Audit schedule** (each runs at 22:00), or **Advanced** to enter a **Cron expression**, such as `0 22 * * 0` for Sundays at 22:00. Then choose the **Timezone**.
   - **When a security advisory matches** runs when a newly published security advisory affects software on one of the target's servers, or a package in its repository.
   - **On demand** only runs when someone selects **Run now**.
4. Under **Modules**, leave **Layers**, **Packs** and **Steps** empty to run every check that applies to the target. To run less, choose the layers, packs or individual steps you want.
5. Under **Alerts**, choose when to be told about results (see below).
6. Select **Save**.

A schedule's target can't be changed after it's saved. Create a new schedule for a different target instead.

Scheduled runs are queued and start one at a time, so a run may begin a little after its set time. On-demand checks that are billed separately, such as a UX review, are never included in a schedule.

## Choosing alerts

**Alert on findings of** decides whether you're told as soon as a run finishes:

- **Any severity**: an alert for every finished run.
- **Low and above**, **Medium and above**, **High and above** or **Critical only**: an alert when the run failed, or when it left an outstanding finding at or above that severity.
- **No alerts**: no immediate alerts, not even when a run fails.

New schedules start at **High and above**.

**Digest** adds a summary of the runs the schedule finished: **Daily digest**, **Weekly digest** or **No digest**.

Alerts go to your subscription administrators as a Portal notification and an email, and to the person who started the run if they selected **Run now**. You can choose how you receive **Audit Results** notifications in your profile. See [Your profile and notifications](/getting-started/your-profile-and-notifications).

## Notes

- To stop a schedule without deleting it, set its **Status** to **Disabled** and select **Save**.
- Findings from scheduled runs are gathered with all your other findings. See [Managing findings](/assure-and-diagnose/managing-findings).

## Troubleshooting

- **Run now shows an error.** The message explains why the run couldn't start. A common cause is that nothing in the schedule's modules applies to the target's parts. Check the target's parts, or clear the **Modules** fields.
- **A schedule never runs.** Check its **Status** is **Enabled** and its target is enabled. A **When a security advisory matches** schedule only runs when an advisory affects the target, so it can go a long time without running.