Back to Incident Management guides

4 On-Call Schedule Templates (With Benefits and Downsides)

Jenda Tovarys
Updated on February 22, 2024

First time building an on-call schedule? Don’t reinvent the wheel. Just start with what works and adjust it as you go.

Here are the most popular on-call templates with pros and cons to use them.

  1. Workweek and weekend
  2. Workweek and weekend with a backup
  3. Follow the sun
  4. Rotating / fully customized

Workweek and weekend

Engineers are on-call during the workweek and weekend — 7 days in a row. The on-call week is intense. However, the rest of the month is on-call free. This practice is used in Google and is also doable for teams of any size.

Depending on your team size, you have several options.

  • Workweek and weekend (monthly): One workweek and weekend every month, then the rest of the month free. For this, you’ll need at least four team members.
  • Workweek and weekend (bi-weekly): One workweek and weekend, then one week and weekend off. You can do this with only two people in a team.

Xnapper-2023-10-31-17.16.45 (1).png

Necessary team size: 2+ team members


  • Simplicity: Weekly rotation is easy to understand, set up, and manage.
  • Works for any team size: This schedule accommodates teams from two team members.
  • Rest time: For larger teams (at least four people), this schedule allows each engineer to have three weeks with no on-call responsibilities, allowing for rest time.


  • Night shifts: Simplicity comes here at the cost of working 24/7 for a whole week.
  • Intense: Being ready to respond for a whole week in a row can be tiring, especially when incidents pile up.
  • Inflexible: When team members have specific on-call requirements, such as not working during some days, it won’t work.

Workweek and weekend with a backup

This is an improved version of the regular workweek and weekend (sometimes called primary and secondary schedule). It includes a secondary on-call calendar called a backup. If the regular (primary) on-call person doesn’t acknowledge the incident within a given timeframe, it’s escalated to the backup.

Again, you can go with either one week once a month setup if you have a larger team or a bi-weekly setup if you have a smaller team.

backup on-call (1).png

There is an option for a third on-call tier, which escalates to the team lead. If everything is set up correctly with the team, the escalation to the third tier should be only an infrequent occurrence event.

Necessary team size: 4+ team members


  • Security: Every team member has a backup in the rare case that they can’t respond. Making the incident response more secure in theory.
  • As well as simplicity, intensive, and inflexible, as explained above.


  • Needs a larger team: At least four people are necessary for two weeks. Since primary and secondary are both fully-fledged on-call duties, the second week will be used for rest by the first two team members and vice versa.
  • More management: The backup on-call must be treated equally to the primary on-call. It can be difficult to properly communicate that even on backup duty, people must be ready to respond immediately.
  • As well as Night shifts and rest time, as explained above.

Follow the sun

This model leverages the timezone difference between different team members. It allows all on-call engineers to have only business hours duties and avoid night shifts. It’s the most protective of a healthy sleep schedule.

Achieving a complete elimination of night shifts requires specific team locations across different time zones. The reality in most cases is that the follow the sun eliminates only some parts of the night shifts, but only rarely creates a smooth nine-to-five on-call schedule.

You can of course implement follow the sun model only with two people, given that they have a reasonable time difference, and eliminate at least some non-standard working hours.

Xnapper-2023-10-31-17.19.52 (1).png

If you want to see the overlaps of working hours across different time zones, use a tool like Worldtimebuddy.

Necessary team size: 2+ team members across specific time zones


  • No night shifts: You only solve incidents during work hours. No night-time work.


  • Responsibility switching: There are usually several people being on-call every day. If issues occur at the end of one team member's on-call time, passing over the investigation and resolution of the incident to another person can be complicated and stressful.
  • No free days: If you follow a basic schedule, you will be on-call daily. That’s why it is usually better to switch things around and have weeks without any on-call duties. It all depends on the size of the team. The larger the team, the more options you have.

Rotating / fully customized

This encompasses any fully customized schedule, and it usually includes rotations that can occur daily, weekly, or monthly.

The rotating schedule is usually used by larger on-call teams (20+), allowing for a fully tailored on-call setup, gaining benefits from all of the previous three schedules.

It usually prefers the follow-the-sun practice to minimize night shifts, but it also combines it with monthly or bi-weekly rotations, so team members get free days. The team size can also accommodate individual team preferences like people taking 24-hour shifts for the whole weekend once a month and then not being on-call for the rest of the month.

Monetary and days off incentives are common in those setups to minimize the on-call downsides on the team's performance and maximize the system's resilience.

Necessary team size: Usually 20+


  • Flexibility: Since it’s fully customized, it allows for maximum team flexibility.
  • Performance: Maximizing the team's performance (incident response speed, troubleshooting speeds, and collaboration) is the goal of going for this lengthy custom setup.


  • Team size: A large distributed team is necessary to create it.
  • Planning and management: With complexity comes more management. And there is also the initial investment of planning based on individual team members’ preferences and capabilities.

Learn more

Still unsure about your optimal on-call setup? Read our guide on How to Create a Developer-Friendly On-Call Schedule in 7 steps and see what are all the things you should consider when building a good schedule.

If you want to understand the workings of incident management, start with our beginner’s guide.

Any questions or comments? Let us know at

If you’re working on a new on-call schedule, you can book a free consultancy call with us.

Author's avatar
Article by
Jenda Tovarys
Jenda leads Growth at Better Stack. For the past 5 years, Jenda has been writing about exciting learnings from working with hundreds of developers across the world. When he's not spreading the word about the amazing software built at Better Stack, he enjoys traveling, hiking, reading, and playing tennis.
Got an article suggestion? Let us know
Next article
On-call Compensation Models (and How to Solve On-Call Pay)
Licensed under CC-BY-NC-SA

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

Make your mark

Join the writer's program

Are you a developer and love writing and sharing your knowledge with the world? Join our guest writing program and get paid for writing amazing technical guides. We'll get them to the right readers that will appreciate them.

Write for us
Writer of the month
Marin Bezhanov
Marin is a software engineer and architect with a broad range of experience working...
Build on top of Better Stack

Write a script, app or project on top of Better Stack and share it with the world. Make a public repository and share it with us at our email.

or submit a pull request and help us build better products for everyone.

See the full list of amazing projects on github