Look, I get it — you’re a small team, you don’t want another $20/user/month SaaS just to rotate who gets woken up at 3 a.m. Maybe you’re already using Notion for docs, and you think, “How hard could it be?”
Spoiler: it’s not hard. It’s also not… *good*. But it’s cheap, and it keeps you out of another vendor’s ecosystem. Let’s walk through the basic setup and where it will inevitably break.
First, you’ll need a table. Let’s call it “On-Call Schedule.”
- Properties: `Engineer` (person), `Start Date` (date), `End Date` (date), `Primary` (checkbox), `Backup` (checkbox).
- You can add a `Rotation Order` (number) if you want to get fancy.
Then you create a view filtered to show only the current primary:
```plaintext
Filter: "Start Date" is on or before today
AND "End Date" is on or after today
AND "Primary" is checked
```
Now you’ve got a page that shows who’s on call right now. Share the link in your team channel. Congrats.
The problems start immediately:
- No integrations. Your alerting tool won’t ping the right person automatically. You’ll be manually updating a Slack channel or, heaven help you, sending an email.
- No escalation. If the primary doesn’t acknowledge, nothing happens unless you build a whole other process.
- No history or metrics. Good luck calculating pager‑fatigue or figuring out why Alice is always on call during holidays.
Is this a “professional” on‑call solution? Absolutely not. But if you’re allergic to lock‑in and your budget is zero, it’s a functional stopgap. Just don’t come crying when someone misses a page because you forgot to update the date.
—L
Every cloud has a dark cost.
Oh, this is really helpful. I've been thinking about setting up an on-call thing for my small team. So you're saying the big catch is there's no automation?
I was hoping maybe there was a way to link it with a Slack webhook or something. Do you think using a calendar view would help, or does that have the same problem with alerts not going out? Just trying to see if there's any workaround.