−50%

50% off your first month on any paid plan · code WELCOME50 · until Nov 30

Start free →
Guide

Cron Every Quarter: Scheduling Jobs for Q1, Q2, Q3, Q4

Scheduling a cron every quarter sounds straightforward until you try to write the expression. There's a <code>*/3</code> shorthand that technically works, but spelling out the months is safer. The correct expression is <code>0 0 1 1,4,7,10 *</code>, and it comes with a few decisions most tutorials skip over.

The cron every quarter expression#

To run a cron every quarter, you need to list the four quarter-start months explicitly:

0 0 1 1,4,7,10 *

Minute 0, hour 0, day 1, months January, April, July, October. Four runs per year, one at the start of each calendar quarter. This is the standard cron expression quarterly teams use for reports, renewals, and compliance tasks. The month field doesn't support a step value that aligns with fiscal quarters, so you spell out the four months explicitly.

Why not 0 0 1 */3 *? Because */3 in the month field means months 1, 4, 7, 10, which happens to match calendar quarters. It works, technically, but it's less readable, and anyone maintaining your crontab six months later will need to count on their fingers to verify which months that hits. We switched to the explicit list on our own servers after a teammate misread */3 as "every third month starting from the current one" and expected the schedule to shift depending on when the crontab was installed.

Choosing the right day and time#

Day 1 at midnight is the obvious default for a cron job every 3 months. But is it the right one?

If your quarterly job generates a report covering the previous quarter, running at 00:00 on the 1st means it fires before any data from the last day of the previous quarter has finished processing. A batch job that closes out at 23:59 on December 31st hasn't completed when the January 1st cron fires at midnight. We saw this with a revenue reconciliation script that consistently undercounted the last day of each quarter by about 12% because late-arriving transactions hadn't been committed yet.

Two fixes work well here. Run on the 2nd instead:

0 6 2 1,4,7,10 *

Alternatively, run on the 1st but later in the day:

0 9 1 1,4,7,10 *

Either gives your pipeline time to finish closing out the previous quarter. The 6 AM or 9 AM start also means failures happen during working hours when someone can actually respond, not at midnight when the on-call engineer is asleep.

Fiscal quarter offsets#

Not every organization runs calendar quarters. Fiscal years starting in March, June, or other months need different month lists. Adjust the months to match your fiscal calendar:

  • Fiscal year starts March: 0 0 1 3,6,9,12 *
  • Fiscal year starts June: 0 0 1 6,9,12,3 *

Note that a fiscal year starting in January, April, July, or October lands on the same months as calendar quarters (1, 4, 7, 10), just labeled differently. Cron doesn't care about the order of values in the month field. 1,4,7,10 and 10,1,4,7 produce identical schedules. But writing them in fiscal-year order makes the crontab self-documenting for the next person who reads it.

Why quarterly jobs are high-stakes#

A job that runs four times a year has exactly four chances to work. Miss one and you've lost a quarter of your annual runs. Compare that with a daily job where one failure out of 365 barely registers.

Quarterly jobs also tend to be the important ones. Tax filings, compliance reports, board-ready financial summaries, license renewals, audit log exports. These aren't cleanup scripts. They feed processes with hard deadlines, and "we'll catch it next quarter" is rarely an acceptable answer.

The failure modes are predictable. The script worked last quarter, nobody touched it, but the database credentials rotated in between. Maybe the disk filled up because three months of data accumulated since the last run. Or a dependency updated and broke something, and nobody noticed because the job only runs four times a year. We've seen all three on production systems, always discovered after the deadline had already passed.

Testing your cron every quarter setup#

You can't wait three months to find out if your crontab every quarter actually works. But you can verify the pieces separately.

First, confirm the expression fires when you expect. Use the cron expression validator to check the next four execution dates. You can also build it visually and verify the schedule looks right.

Second, run the script manually with the same environment cron will use. Cron doesn't load your shell profile, so paths, environment variables, and locale settings may differ. You can test with this command:

env -i /bin/bash -c '/opt/scripts/quarterly-report.sh'

This strips your environment and runs the script in a bare shell, closer to how cron executes it. Cron itself sets a minimal PATH, HOME, and LOGNAME, so env -i is actually slightly more restrictive, but if your script works here it'll work in cron too.

Monitoring a cron job every quarter#

A quarterly job that fails silently is the worst kind of failure. Three months pass before anyone expects the next run. Would you remember to check the log file on April 1st?

Cron job monitoring catches this the same day. Your script pings a URL on completion, WatchCron expects the ping on the 1st of each quarter month, and any missed ping triggers an alert through Slack, email, Telegram, or 16 other channels. For quarterly jobs we set the grace period to 2 hours, long enough for heavy end-of-quarter data processing but short enough to alert before the business day ends.

And if your quarterly task is an HTTP request, Cloud Cron can run it for you on the quarterly schedule with monitoring built in. No server-side crontab to maintain, no silent failures to worry about.

For other scheduling patterns, see our guides on cron on the first of each month, cron on the last day of the month, or the full cron jobs overview.

Frequently asked#

The expression is 0 0 1 1,4,7,10 *. It runs at midnight on the 1st of January, April, July, and October — the start of each calendar quarter. You can also write 0 0 1 */3 *, which produces the same schedule but is less readable.

Change the month list to match your fiscal year start. For a fiscal year beginning in March: 0 0 1 3,6,9,12 *. For June: 0 0 1 6,9,12,3 *. Note that fiscal years starting in January, April, July, or October use the same month set as calendar quarters.

If the job runs at midnight on the 1st, it fires before late-arriving data from the previous day has been processed. Schedule it for later in the day (0 9 1 1,4,7,10 *) or on the 2nd (0 6 2 1,4,7,10 *) to give your pipeline time to close out.

Run the script manually in a stripped environment with env -i /bin/bash -c '/path/to/script.sh' to simulate cron's execution context. Use a cron expression validator to confirm the next execution dates before deploying.

Use cron job monitoring with a heartbeat ping. Your script pings a URL on completion, and WatchCron alerts you if the expected quarterly ping doesn't arrive. Set a 2-hour grace period for heavy end-of-quarter processing.

Written by Vitalii Holben

Founder of WatchCron. Full-stack developer building monitoring tools that help teams keep cron jobs, uptime, and SSL certificates under control. Based in Europe, shipping code since 2014.

Start monitoring in under 2 minutes.

Free plan includes 20 checks · No credit card required
Pricing Docs
Log in Start free →