The valuable half of an on-call schedule is the part where you are not on it, and that half only exists if the boundary is real.
Calling people in order is not a rotation
Before the rotation, we had four people running the primary infrastructure and a simple escalation order. Call the first person. If no answer, the second. Then the third. Then the fourth.
That arrangement looks fair on paper and it is not. Person one takes almost every call and gets destroyed. Person four is almost never reached and learns nothing.
The worse problem is what it does to the other three. Any of them might be next, so all four keep their phones on them all the time. Four people carry the burden and only one gets the calls.
One person, one week
Nothing else to it. During your week you are the one who gets called. During the other weeks you are not.
Nobody found this appealing at first. My team hated it, because what they saw was a week where every call was theirs with no one to pass it to.
The week they were on had become harder. That part of their reaction was correct.
Then they worked out the other three weeks
Off rotation, they did not have to keep their phones with them. They did not have to answer. They could go somewhere without coverage, have dinner without checking, and sleep without listening for anything.
That had never been available under the old arrangement, and none of them had noticed it was missing until they got it.
An on-call week is a cost. Three weeks of genuine freedom is what you buy with it, and the trade is a good one as long as the freedom is real.
The escape hatch has to exist and stay shut
I put procedures in place so a real disaster could still reach anybody. Not everything is survivable by one person on duty, and a rotation that pretends otherwise will be broken quietly on the first bad night, which destroys it permanently.
The distinction I drew is the part that makes it work. Off-rotation people did not need to be on call and did not need to be in a position to answer.
They might get reached. They were not required to be reachable. That is a different thing and it is the whole difference between a rotation and a schedule that exists on paper.
Used for real emergencies, the hatch costs nothing. Used because the person on duty was unsure and wanted company, it teaches everyone that off weeks are not real. Two or three casual uses and the rotation is decoration.
Protecting that boundary is the manager’s job and it costs something. Occasionally the person on duty struggles alone with something a colleague could have solved faster, and that is the price of everyone else having a real week off.
It matters more than pay
Nobody leaves over the night they got called. They leave over two years of never being able to put the phone down.
The particular Tuesday is not what wears people out. The absence of any period where the phone does not matter is what does it.
A team with genuine weeks off can sustain a hard on-call week indefinitely. A team where every week is a low-grade on-call week runs down slowly and nobody can point at when it started.
For a small company this is one of the few retention levers available that costs no money. A rotation with a real boundary is a scheduling decision and a discipline, and it changes how the job feels considerably more than a raise does.
One practical note. A rotation among specialists who cannot cover for each other is four separate permanent on-call assignments. The rotation and the cross training have to arrive together.
The full article is on my site: https://thewritingking.com/the-weeks-you-are-not-on-call/. It runs longer, carries the diagrams, and answers the questions readers ask most.
These are AI-made summaries of longer articles on my site, written with AI assistance from my own interviews and my own career. Nothing goes out that I have not read and approved.