On-Call Stipend vs Callout Fee: What's the Difference?

When engineering teams start formalising on call pay, two terms come up almost immediately: stipend and callout fee. They sound similar, they sometimes appear in the same policy, and they are frequently confused with each other. This guide explains exactly what each one covers and when to use them.

The on call stipend

A stipend (sometimes called an availability allowance or on call allowance) is paid simply for being on the rota. The engineer does not need to receive any incidents to earn it — the payment compensates for the fact that being on call restricts their freedom.

When you are on call, you typically cannot drink alcohol, must stay within a certain travel distance from your laptop, and have to remain alert enough to respond at any hour. That restriction has a real cost — and the stipend is designed to acknowledge it, even on quiet shifts.

• Paid per day (or per shift) of on call availability
• Earned regardless of incident volume
• Usually higher for weekends and bank holidays than weekdays
• Appears on payslips as a regular allowance, not as overtime

The callout fee

A callout fee (sometimes called a call-out payment or incident fee) is triggered by an actual page — a specific moment when the engineer is alerted to an incident and has to respond. Unlike the stipend, it only applies when something actually happens.

The callout fee compensates for the disruption of being interrupted — particularly outside of normal working hours. Being woken at 2am has a real cost beyond the minutes spent resolving the incident, and the callout fee is the mechanism for recognising that.

• Paid per incident the engineer acknowledges and responds to
• Applied on top of the stipend — they are additive, not alternatives
• Sometimes excludes incidents during normal business hours
• Often comes with a minimum-hours rule (e.g. the callout counts as at least 1 hour of work)

How they work together

Stipend and callout fee address different things, which is why most mature on call policies include both:

• Stipend alone — fair to the engineer on a quiet shift, but undercompensates someone who gets paged ten times overnight.
• Callout fee alone — rewards active incidents but ignores the general burden of being available. An engineer on a quiet rotation earns nothing for a week of restricted freedom.
• Both together — the stipend covers availability, the callout fee covers disruption. An engineer on a busy shift is compensated for both dimensions.

Adding hourly rates

Some policies add a third layer: an hourly rate for active work during incidents. This is most common in organisations where incidents require sustained technical work over hours rather than a quick fix. In these cases, the structure is typically:

• Stipend — for availability
• Callout fee — for each incident trigger (covers the disruption)
• Hourly rate — for actual work time beyond the minimum

Not every organisation uses all three. Simpler policies often use just stipend plus callout fee and find that sufficient. The right combination depends on your incident load and the typical duration of incidents in your system.

Common mistakes when combining them

• Treating them as alternatives rather than additive components — engineers should receive both if your policy includes both
• Forgetting to define what counts as a callout (auto-resolved alerts? low-priority pages?)
• Not accounting for business hours — most policies exclude callout fees for incidents during the working day, since the engineer is on salary
• Applying the same callout rate to a 3am Saturday page and a Monday lunchtime page — some teams differentiate by time and day