New: AI-native post-mortems are here! Get a data-rich draft in minutes.

We've all done it: "that'll be simple, I'll just write a quick script and..."
In the case of calculating on-call pay, we really have done it before: our team have built the on-call pay scripts for several companies, and each attempt was a painful, error prone process.
While we believe everyone on-call should be paid for their inconvenience, relying on someones side-project or back-of-napkin maths to calculate pay leads to mistakes, frustration, and wasted time.
So today we’re making our on-call pay calculator free for everyone to use, regardless of whether they use incident.io or not: https://incident.io/on-call/
Unlike a home-grown solution, our calculator:
Here’s what some of our users have said after using it:
We tested the calculator for May’s payments and it matches exactly (actually, it found a 10p mistake I made) our manual count, that took me ages 😅 and an elaborate spreadsheet. Will definitely be using going forward!
amazing that it has to come from outside PagerDuty - but this is such a great step forward for the industry. It should be trivial to pay people for participating in on-call
I signed up to use your On-call pay calculator (it was going to be a future hackathon project of mine!) and it’s fantastic. My life just got so much easier!
If you’d be interested in giving it a go, check out these instructions.


Migrating your paging tool is disruptive no matter what. The teams that come out ahead are the ones who use that disruption deliberately. Strategic CSM Eryn Carman shares the four-step framework she's used to help engineering teams migrate — and improve — their on-call programs.
Eryn Carman
Model your organization once, and let every workflow reference it dynamically. See how Catalog replaces hardcoded incident logic with scalable, low-maintenance automation.
Chris Evans
Post-mortems are one of the most consistently underperforming rituals in software engineering. Most teams do them. Most teams know theirs aren't working. And most teams reach for the same diagnosis: the templates are too long, nobody has time, nobody reads them anyway.
incident.ioReady for modern incident management? Book a call with one of our experts today.
