Built and running · not yet generally available
KarmaSchedule
Software that builds your schedule
A row per shift, a column per date. The people over the board are every candidate being scored for that day — the ones a rule blocks break apart, the six who are chosen drop into their shifts, and the tally beside it levels because the schedule levelled it.
One person builds it in a spreadsheet over several evenings. Everyone else takes the fairness on trust.
KarmaSchedule builds it instead. Describe the rules your department already works by, and it generates a schedule that meets them.
Three things that make it hard
-
It takes hours, every cycle
- Twenty people, call, weekends, clinic blocks, three kinds of leave.
- More valid schedules than anyone can compare.
- So you build a schedule that works, then chase swaps by email.
-
Fairness is invisible
- Staff see their own shifts, never the distribution behind them.
- Nobody can show they worked three of the last four holidays.
- Nobody can prove they did not.
-
Nobody sees the pressure building
- Consecutive days, night density, weekend load.
- The gap between the most- and least-burdened person.
- All knowable. Almost never known — until somebody resigns.
What KarmaSchedule does about each
Generate
It generates, rather than collects
- Set the rules once: rest between shifts, consecutive days, who is eligible, how call is shared.
- Hard rules it will not break.
- Soft preferences it meets where it can, and flags where it cannot.
- Rules can be plain English — “no more than four nights in a row” becomes an enforceable rule you read back before it takes effect.
Show
It shows the fairness it used
- A tally on every schedule: call, weekends and holidays per person.
- Over any window you choose.
- Staff see their numbers against the group's. Admins see the spread.
- Asking to be excused from a holiday is a different conversation when both people see the same table.
Absorb
It handles the churn without the inbox
- Swaps, time off and open shifts run in the product, against the same rules that built the schedule.
- A swap that breaks a rest requirement is refused, with the reason.
- An open shift goes to everyone eligible, first come.
Built for the hardest settings
Call schedules, duty-hour limits, multi-day shifts and your own staff categories — first-class, not worked around.
Where things stand
If you run a schedule like this, we would like to hear about it.
Already using it? Sign in.