

Spotlight: meet Giang Tran, our first design intern
How a Waterloo Co-Op Student of the Year designed billboards that lit up Times Squares in her internship with Rootly.
On-call support only works when policies protect sleep, recovery, and mental health as rigorously as they protect uptime. A healthy on-call policy reduces interruptions, compensates restricted freedom, enforces recovery time, and treats human capacity as a reliability requirement.
Modern organizations rely on 24/7 availability, yet many still design on-call as if people were interchangeable components. That gap is costly. When we ignore sleep, recovery, and the psychological load of availability, we increase errors, attrition, and long-term risk.
This article reframes on-call as a human system, explains the real health and performance impacts, and lays out practical policy designs that keep support sustainable.

On-call work is availability under constraint, not just time spent responding to . The restriction of personal freedom creates measurable stress and sleep disruption.
On-call is often described as “being available if something breaks,” but that framing misses the core issue. Availability limits how people sleep, travel, socialize, and mentally disengage.
Even when nothing happens, the requirement to be reachable changes behavior. People check phones at night. They avoid deep sleep. They stay half-alert. That constant low-grade vigilance is work. It carries a cost regardless of whether a pager goes off.
Organizations typically use a mix of models, each with different wellbeing implications.
Problems arise when expectations are unclear or when escalation quietly becomes constant.
Many teams lack a written policy that clearly defines boundaries. Response expectations are assumed rather than stated. Cultural pressure rewards immediate replies even when policy allows delay.
Over time, on-call quietly expands into a 24/7 expectation. Without clear definitions, people default to over-availability to avoid blame.
Anticipating an on-call alert disrupts sleep quality even when no alert occurs. Sleep fragmentation impairs cognition, judgment, and reaction time.
Sleep is structured in cycles. Deep sleep and REM sleep are critical for memory, emotional regulation, and decision-making. On-call disrupts those cycles in two ways.
First, alerts wake people abruptly, fragmenting sleep. Second, anticipation alone prevents deep sleep. When the brain expects interruption, it maintains a lighter sleep state. The result is shorter, poorer-quality rest even on quiet nights.
This is why people often report feeling exhausted after “uneventful” on-call weeks.
Acute sleep loss has immediate effects that matter in high-stakes support roles.
Ironically, the moments when teams need clarity and precision are often when people are least cognitively equipped.
Repeated sleep disruption compounds over time. Chronic on-call exposure is associated with higher rates of burnout, anxiety, and depressive symptoms.
Physical health suffers as well, with increased risk tied to long-term sleep deprivation. Resilience is not an unlimited resource. It erodes when recovery is insufficient.
On-call does not affect only the person holding the phone. It spills into shared spaces and shared lives.
Partners often experience disrupted sleep from alerts or restless behavior. Family plans are adjusted around availability. Even when physically present, people remain mentally tethered to work. Over time, this creates strain that no amount of “thank you” can offset.
The emotional labor is subtle but persistent. People feel guilty for missing calls and guilty for prioritizing personal needs. That tension accelerates burnout and disengagement.

A healthy on-call policy prioritizes predictability, fairness, and recovery. It treats human limits as non-negotiable design constraints.
Flexibility sounds attractive, but unpredictability is stressful. Human-centered policies emphasize advance scheduling. People should know when they are on-call well ahead of time so they can plan sleep, family commitments, and recovery.
A common best practice is publishing schedules at least two weeks in advance. More is better when possible.
Fairness is not just about equal rotation length. It is about equal burden. Some weeks are quiet. Others are brutal.
Teams should track on-call load, including number of alerts and overnight interruptions, and adjust rotations accordingly. When the same people repeatedly absorb the hardest shifts, resentment and attrition follow.

Scheduling determines stress more than individual resilience.
Effective rotations limit consecutive on-call periods and separate primary and secondary responsibilities. Weekly rotations are often more humane than daily swaps because they reduce constant context switching.
However, weekly rotations require stronger recovery policies. Teams should define maximum consecutive on-call weeks and enforce cooldown periods.
For global teams, follow-the-sun scheduling dramatically reduces overnight disruption. Coverage is handed off across regions so that on-call occurs during local daytime hours whenever possible.
This model requires coordination and trust, but it pays dividends in sleep quality and long-term sustainability.
Life happens. Human-centered policies allow easy, visible shift swapping without stigma. Guardrails matter to prevent quiet overwork, but autonomy reduces stress and increases perceived fairness.
On-call restricts personal freedom and must be compensated even when no call occurs. Time-off after disruption is a safety requirement, not a benefit.
Compensation acknowledges that availability has value. Common approaches include flat stipends per on-call period, additional pay for primary coverage, or incident-based bonuses.
The exact model matters less than the signal it sends. Unpaid availability communicates that human cost is invisible.
Money alone does not restore sleep. Recovery time is essential. Many teams provide a half-day or full day off after a week of primary on-call, with additional time granted after overnight incidents.
Some organizations implement mandatory rest periods after severe disruptions. This removes the burden of self-advocacy and protects performance.
Fatigued people make more mistakes. Recovery time reduces incident recurrence, improves decision-making, and lowers attrition. Treating time-off as optional undermines its effectiveness.
Sleep loss cannot be instantly reversed. Policies must support multi-day recovery when needed.
After overnight calls, people should have flexibility to start later, skip meetings, or take a dedicated sleep day. Rigid schedules force people to choose between health and appearing committed. Clear guidelines remove ambiguity and guilt.
Sleep debt accumulates across nights. One good night does not erase several bad ones. Managers should recognize that productivity may dip temporarily after heavy on-call weeks and plan workloads accordingly.

Reducing alerts improves wellbeing more than speeding up response times. Every unnecessary alert erodes trust and sleep.
Alert fatigue occurs when systems generate noise rather than actionable signals. False positives, low-severity alerts, and poorly tuned thresholds train people to expect interruption without value. Over time, this degrades response quality and increases stress.
Healthy systems distinguish between issues that require immediate action and those that can wait. Techniques include severity thresholds, business-hours deferral for non-critical issues, and automation that resolves known failure modes. Every alert should justify the cost of waking a human.
On-call boundaries protect rest and prevent cultural creep.
Policies should explicitly state when people are allowed to disconnect. Devices should be silenced when not on-call. Escalation paths should respect these boundaries. When boundaries are vague, people assume constant availability.
Rest periods should be guaranteed and enforced. This includes minimum downtime between shifts and protection from retaliation for using recovery time. Culture must support the policy, not undermine it.
Leadership behavior determines whether policies work.
On-call systems should evolve to reduce human cost over time.
Organizations often stumble in predictable ways.
Avoiding these traps requires intentional policy design and leadership commitment.
At Rootly, we see every day how on-call policies shape how people sleep, think, and live. When organizations treat availability as free and recovery as optional, reliability eventually suffers. When systems are designed with real human limits in mind, both people and platforms perform better over time.
From our perspective, sustainable support is not built on faster responses alone. It is built by reducing unnecessary interruptions, compensating restricted freedom, and enforcing recovery as a core safety control. That is the human side of support, and it is the foundation of long-term reliability.