Skejuler builds the schedule for physician groups that run 24/7 coverage.
Someone has to build the schedule.
It shouldn't be you.
Skejuler learns how your group actually works — who's half‑time, who can't take Thursdays, who shouldn't be on service two weekends running. You explain it once, in plain English. It drafts every cycle from there. You check it and publish.
Talk to usThis week · ICU
| Mon | Tue | Wed | Thu | Fri | Sat | Sun | |
|---|---|---|---|---|---|---|---|
| Alderton | E | E | L | — | Call | — | — |
| Behrens | — | — | — | E | L | — | — |
| Okonkwo | Call | — | E | Call | — | D | D |
| Reyes | — | Call | — | L | — | Call | Call |
| Whitfield | L | L | Call | — | E | — | — |
E Early · L Late · Call Overnight · D Weekend day · every shift covered, all 7 days
You train it once
Next cycle, it already knows.
The first time, you tell it the things that live in your head — the clinic days, the part‑time lines, the two people who can't cover together. You don't tell it again. Every cycle starts from every rule you've given it.
What it already knows · cycle 4
Alderton — no Thursdays (clinic)
Nights spread evenly across the year
Behrens 0.5 FTE — half the load
Never two weekends back to back
Learned in cycle 1. Not re-entered since.
Say it in English
Say the rule. See exactly what it became.
Every rule you give it becomes a constraint you can read, edit, or switch off. Nothing about your schedule is settled in a conversation: the AI reads your English, and a deterministic solver places the shifts.
What you say
“Alderton shouldn't do more than two nights in a row, and never a night before her clinic day.”
Compiled — 2 constraints
HARDmax 2 consecutive nights · Alderton
HARDno night before clinic day · Alderton
Editable. Inspectable. Your rules live here, not in a chat.
20 minutes. You'll talk to someone who can actually answer.
A real schedule
Coverage first — every slot, every day.
Early, late, call, weekends, across sites. It builds against the coverage you actually have to fill, and it leads with what it couldn't fill rather than burying it. Nothing publishes until the gaps are closed and you've said so.
Sample data, invented names. Real divisions run 24/7 coverage across multiple sites.
Here's how we computed this
We show the arithmetic. You decide what's right.
Load is measured against each provider's own share — hours weighted by FTE, weekends counted on their own clock. Every number opens up to the arithmetic behind it, and each doctor's share comes from the FTE you set. We don't tell you what's fair. That was always your call.
Where we actually are
A working product, in use today.
- Every draft built against live coverage, every gap explained before you see it.
- Assist, not autopilot — a human verifies every cycle before it publishes.
- We onboard a few groups at a time, on purpose. Each one gets built around before the next.