Chiefly scheduling alternative built for residency programs

Chiefly is a self-serve SaaS tool that gives chief residents automation assists while they still build the schedule themselves. Thrawn is a fully managed service — your program sends its constraints and receives a finished, optimized schedule for review. The architectural difference is fundamental: Thrawn's Scheduling Programming Language produces complete schedules from constraints using mathematical optimization, not rule-based suggestions that require human intervention to finalize.

Yes. ACGME duty hour compliance is enforced at the point of schedule generation, not detected afterward. Every schedule Thrawn produces automatically satisfies the 80-hour weekly limit, shift length caps, required rest periods, and day-off requirements. Your program does not need to audit for violations after delivery — they are prevented before the schedule is ever created.

The transition is managed entirely by Thrawn. Dedicated scheduling specialists work with your program to capture your existing rules, rotation requirements, resident preferences, and constraints. Your team does not need to learn new software or migrate data manually. The onboarding process is designed to minimize disruption so your first optimized schedule can be delivered without operational interruption.

Yes. Resident vacation requests, elective preferences, and individual scheduling constraints are factored directly into Thrawn's mathematical optimization. Rather than creating a separate reconciliation step for your team, preferences are treated as constraints within the scheduling engine, so the finished schedule already reflects resident input without any manual coordination required from chiefs or coordinators.

Thrawn produces Block, Call, Clinic, and Attending schedules for residency and fellowship programs. These four schedule types are optimized simultaneously as one interconnected system — not built separately and then reconciled. This cross-schedule approach eliminates the cascading conflicts that occur when block, call, and clinic schedules are managed in separate tools or built sequentially.