How Small Teams Handle On-Call Compensation
There's no universal standard for paying on-call — even Google's own guidance on being on-call focuses on structuring the rotation itself rather than prescribing how to pay for it. Every small team ends up reinventing this decision from scratch, usually after someone's already been carrying a pager for a few months unpaid and starts wondering why. A handful of models keep showing up across small engineering teams, though, and each one solves a slightly different problem.
Flat stipend per rotation
The simplest model: a fixed amount for taking a week (or whatever the rotation length is) of on-call, regardless of how many pages actually come in. This is easy to budget for and easy to explain. It treats the compensation as payment for availability rather than payment for work done. That's arguably the more accurate framing — being reachable and ready is the actual constraint on someone's time, whether or not anything fires that week.
The downside: it doesn't distinguish between a quiet week and a genuinely brutal one, which can feel unfair to whoever draws the bad week.
Per-incident pay
Pay a set amount for each page actually responded to, on top of or instead of a base stipend. This directly compensates for the actual disruption — being woken up, having to context-switch away from personal time. It scales naturally with how bad a given week actually was, rather than treating a quiet week and a brutal one the same.
The downside is the opposite of the stipend model. It's harder to budget for, and it can create a subtle incentive problem if a team isn't careful. Nobody should feel like they benefit from noisy alerting. This model works best paired with an active effort to reduce alert volume, not alongside indifference to it.
Time off in lieu
Instead of direct pay, a rotation earns a set amount of additional PTO. This is common on teams where the engineering culture already leans toward flexible time over cash bonuses. It also sidesteps some of the payroll complexity of the other two models. It works less well for anyone who doesn't have much flexibility to actually take that time off — worth checking rather than assuming.
Time off in lieu also tends to work better as a supplement to one of the pay-based models than as a full replacement for it. It compensates for the general burden of the rotation reasonably well, but it does little to soften a genuinely bad week. Someone who got paged eleven times in six nights and someone who wasn't paged at all walk away with the same banked PTO — that undersells the actual disruption in the bad case.
A hybrid: base stipend plus per-incident top-up
Many teams land here after trying one of the pure models first: a modest base stipend for taking the rotation, plus a smaller per-incident amount for pages actually responded to outside business hours. This captures both halves of the real cost. It covers the availability constraint and the actual disruption, without the full budgeting unpredictability of a pure per-incident model.
Should weekday and weekend on-call pay the same?
No, not usually — most teams that pay for on-call at all end up paying more for weekend and holiday coverage than for a weekday night. A weekday rotation still leaves normal daytime hours mostly undisturbed. A weekend rotation asks someone to stay tethered for two full days that would otherwise be entirely their own. That's a heavier ask than the raw page count alone suggests. A common adjustment is a higher stipend rate for Friday evening through Monday morning, plus a separate smaller stipend for statutory holidays, layered on top of whichever base model a team already uses. It doesn't need to be complicated — even a flat 1.5x multiplier on the weekend portion of a rotation captures most of the fairness gain, without turning payroll into a spreadsheet project.
Whatever the model, measure what you're paying for
Regardless of which model a team picks, the underlying data needed to apply it fairly is the same: how many pages fired during each rotation, when, and who responded. A stipend-plus-top-up model is impossible to run fairly without an accurate count of after-hours pages per person. A pure per-incident model needs the same data just to calculate what's owed.
A proper delivery audit log matters for a reason that goes beyond incident review: it's also the source of truth for on-call compensation, if a team wants to pay fairly rather than by guesswork. PingParrot logs every page with who was notified and when. That record is enough to run any of these models without needing a separate tracking spreadsheet nobody keeps up to date.
The conversation matters more than the model
No compensation model survives being imposed without discussion. The teams that get this right treat it as an open conversation with whoever's actually on the rotation — the practitioner essays in Increment's On-Call issue make clear how differently that conversation plays out from one company to the next. They revisit it periodically as the team and the alert volume change. The alternative is setting a policy once and leaving it untouched for years, while the actual on-call burden quietly grows around it.