# Nudges and escalation

> Nudge timings, working hours, high priority, and what happens when a review stalls.

A nudge policy sets when reviewers are reminded and what happens if a review stalls. Every workspace starts on **Standard**. Change it on **Nudges**, starting from a preset or setting your own timings.

## Presets

| Preset | First nudge | Then | High priority | Nudges | If nobody responds |
| --- | --- | --- | --- | --- | --- |
| Gentle | 24 hours | Daily | 4 hours, then daily | 5 | Tell your escalation contacts |
| Standard | 4 hours | Daily | 1 hour, then every 4 hours | 3 | Tell your escalation contacts |
| Urgent | 1 hour | Every 2 hours | 30 minutes, then hourly | 4 | Reassign to the next reviewer |

All presets skip drafts. **Gentle** also waits for passing checks before nudging.

## Working hours

Nudges are only sent inside working hours: Monday to Friday, 9:00 to 17:30, in the workspace’s time zone. You can change the days, hours and time zone, or turn working hours off.

## High priority

Pull requests labelled `urgent` or `hotfix`, or waiting a long time, are scored higher priority and follow the faster high-priority timings. You can also set a pull request’s priority by hand.

## Escalation

After the policy’s number of nudges with no review, Nudge escalates in one of two ways:

-   **Tell your escalation contacts** by email and Slack. You choose who on **Nudges**; if you choose nobody, it’s the workspace’s owners and admins.
-   **Reassign** to the next reviewer in the pool, who starts their own nudge timeline. The earlier reviewer stays requested, and a review from either completes it.

Escalated pull requests are marked **Escalated** in the dashboard and on My reviews.

> **Reassigning needs someone to reassign to**
>
> If nobody else in the pool can take the review, Nudge tells your escalation contacts instead. See [How many people a pool needs](https://nudgepr.dev/docs/reviewer-pools#size).
