Defended schedule
Call, nights, PTO, holidays, and coverage status live in one view, so residents can trust the schedule instead of decoding it.
Built for residents. Sold to programs.
The first scheduling tool that defends the schedule it shows you.
Callboard keeps the schedule simple enough for a PGY-1 on their phone and rigorous enough for a chief resident running the month. Time off, fairness, coverage, and calendar export are not side quests. They are how the schedule earns trust.
UCLA Anesthesiology
May 4-8, 2026 · bird's-eye
AllCallPTO
Member
Mon 4
Tue 5
Wed 6
Thu 7
Fri 8
Sadeghi
PGY-2
CALL
PTO
PTO
DAY
Patel
PGY-1
NF
CALL
Kim
PGY-3
DAY
CALL
BU
Okafor
Fellow
DAY
NF
Time off balance
Vacation14 / 20d
Sick2 / 10d
Wellness1 / 3d
Coverage flow
Patel posts CALL on May 18.Okafor taps to cover. Admin approval optional.Schedule updates without losing the audit trail.
24 residents · 5 day preview · sample dataSaved 2s ago
UCLA TMS tier-1 readinessLaunch paths are being hardened before external program rollout.
Schedule UX liveBird's-eye, by-shift, and resident calendar views are in app.
iCal, time-off, coverage shippedThe resident protection loops are visible, exportable, and usable.
The hinge
Resident protection is the program operating system.
| Resident-protective | Program-operational |
|---|---|
| Time-off allotments visible at all times in My Calendar | Bird's-eye view: see the whole month at once |
| ACGME baseline displayed alongside program's own values | Paste-from-spreadsheet member import |
| Holiday fairness ledger (transparent, not hidden) | Customizable shift types, colors, theme |
| One-tap Google/Apple/Outlook calendar subscription | One-click print for posting in workrooms |
| Coverage requests are 1-tap, no manager-as-bottleneck | Optional admin approval per workflow |
| Wellness day labels are configurable ("mental health," "wellness," etc.) | CSV/iCal export |
| Bereavement, jury duty, parental leave categories built in | Member directory, role assignment |
| Calendar integrations work on personal devices | No vendor lock-in: schedule data exports cleanly |
What ships in v1
The workflows that make call survivable.
No AI scheduler and no black-box rule engine. Just the views, exports, and resident protections programs need before launch.
Time-off balance
Programs keep their own policy labels and allotments, while residents can always see what is used, pending, and remaining.
Coverage without Slack chaos
A resident posts a shift, another taps to cover, and programs can decide whether approval is required.
External pilots
Launch a real program, then let the residents tell you whether it earned trust.
Start setup as the pilot contact path: create one program, paste the member list, ship calendar subscriptions, and watch whether residents actually use the schedule after week one.