Tidewatch

On-call rotas that nobody dreads, with every gap found before Friday.

Fewer pages after midnight

within one quarter of fair rotas

Client

Tidewatch

Role

Engineer, full stack

Timeline

Six months, 2019

Built with

TypeScript, React, Postgres

The problem

On-call rotas lived in a spreadsheet. Gaps were found on Friday afternoon, and the same two people took most of the night pages.

What I did

A scheduler that treats fairness as a constraint, not a favour, and flags a gap the moment it appears. Swaps take two taps.

What changed

62% fewer pages after midnight within a quarter, mostly because alerts finally reached someone who could fix the cause.

Have a number that needs moving? Tell me what it is today.

Next free in January 2027. Send the number, where it is measured, and what it costs you. I reply within a day.

Start a conversation