Beacon Scheduler

A real clinic was rebuilding next week's schedule by hand every week — dragging the same names around a grid, then re-checking everyone's hours by eye. I wanted to give them that afternoon back.

Scheduling is a constraint puzzle wearing a friendly face: every provider owes hours, blocks can't collide, and a human still has to be able to override the machine. On top of that it had to run entirely offline — patient-adjacent work shouldn't depend on someone else's server.

I built the week board so a person is always holding the pen: Autofill packs the week as a first draft, and a live Attention panel sits next to it flagging who's short hours or unassigned. That pairing is the trick — the machine does the tedious first pass, the panel tells you exactly what's still wrong, so you trust it without handing over the last word. The whole thing runs in the browser with no backend.

It's live at beaconscheduler.quiettools.dev, runs with zero network, and was built for an actual pediatric behavioral-health clinic to plan real weeks. Autofill drafts, the Attention panel keeps it honest, and nobody's data leaves the machine.