A small on-call app with one-click shift swaps

The problem

On-call schedules often live in a spreadsheet, a calendar export, or a pinned chat message. When something breaks, people have to hunt for who is on call. Swapping a shift usually means a round of direct messages, and afterward nobody is sure the change was agreed to or written down. We build one place that answers those questions.

What we’d build

• •Login for your team with two roles: engineers, who see schedules and request swaps, and admins, who manage the rotation and the user list.
• •A home screen showing the current on-call engineer and how to reach them.
• •An upcoming shifts view, with a personal list of your own shifts and a full team calendar.
• •A one-click swap request: the engineer picks a shift and a teammate, and the teammate accepts or declines. Accepted swaps update the schedule automatically.
• •Up to two integrations, for example email notices for swap requests and a webhook that posts accepted swaps to your chat tool.
• •Up to 10 screens in total, delivered on your domain or ours, with a hosted link and full source code.

A concrete example

Picture an eight-person platform team that keeps its rotation in a shared spreadsheet. We build eight screens: login, who is on call now, my shifts, team calendar, request a swap, incoming requests, an admin shift editor, and an admin user list. The admin enters or edits the rotation once, and engineers sign in to see their schedule. When someone requests a swap, the teammate gets an email and can accept or decline from the app. Both integrations fit within the two allowed: email for notices and a Google Sheets import so the admin can load the schedule from the existing spreadsheet. The team gets three rounds of tweaks to adjust wording, layout, and rules, plus 30 days of bug fixes after delivery.

Frequently asked