# Measured on a schedule, so Tuesday tells you what Tuesday broke

> A site measured only when somebody remembers is a site measured never. A schedule measures it on its own cadence, and everything downstream -- trends, alerts, agent tasks -- runs off the rhythm you chose.

## The cadences

Daily, weekly on the day you pick, or monthly on the date you pick, at the hour you pick:

- **Every day**: Included with a paid site.
- **Every week**: Included on every plan, the free tier too.
- **Every month**: Included with a paid site.

## UTC on the clock, your time in the sentence

Schedules are stored in UTC because a schedule that moved with daylight saving would drift against the clock that runs it. The form does the arithmetic for you and says what the chosen hour is in your own time, and the settings page always shows the next run and the last.

## A scheduled scan brings the rest

The scheduled measurement is the heartbeat: it re-measures your plugins' answers, evaluates every alert rule, updates the trend, and on plans with agent tasks it queues the scheduled batch, so the success rate moves on the same rhythm the score does.

## Visible where you would look

The scan history says when the next scheduled scan will run, and says so too when nothing is scheduled, with the link to change that. A schedule is not a setting to remember; it is a fact the product keeps in front of you.

- [What AX Rush measures](https://axrush.com/for-websites)

---

Markdown representation of https://axrush.com/about/schedules
