0 9 * * 1-5
Cron reads this as: at 09:00, on day-of-week Monday through Friday.
Next 5 runs
Computed in your browser's local time zone. Cron itself evaluates against the server's zone, which on most cloud hosts is UTC — see time zones & DST if that distinction matters here.
- Calculating…
When to use this schedule
Monday through Friday at 09:00 — the standard schedule for a morning digest, a standup reminder, or a report that needs to be waiting when the team logs on. Day of week runs 0–6 with Sunday as 0, so 1-5 is Monday to Friday.
What to watch out for
Two things. First, MON-FRI is equivalent and more portable across schedulers, because Quartz and AWS number the days differently but agree on the names. Second, if a human is waiting for this output, the server's time zone matters — cloud hosts default to UTC, so 09:00 there may be the middle of the night for your team. Set CRON_TZ above the line, and leave the day-of-month field as *.
The crontab line
0 9 * * 1-5 /usr/local/bin/your-job.sh >> /var/log/your-job.log 2>&1Redirect the output somewhere you will actually read it — by default cron mails it, and on a host with no mail transport that means it is discarded. See the crontab guide for the surrounding syntax.
Related schedules
| Expression | Schedule |
|---|---|
0 9 * * MON-FRI | Same schedule, using names |
0 17 * * 1-5 | End of the workday instead |
0 9-17 * * 1-5 | Hourly through the workday |
Build your own
Need something this page does not cover? Compose it field by field in the visual builder, or paste an expression you already have into the explainer for a per-field breakdown. The examples library collects sixty schedules in one place, and the guides cover crontab syntax, time zones, troubleshooting and production practices.