Question 1

How does Thrawn's call schedule automation actually work?

Accepted Answer

Programs send Thrawn their scheduling constraints — resident preferences, ACGME duty hour rules, rotation requirements, vacation requests, night float structures, and coverage requirements. Thrawn's proprietary Scheduling Programming Language (SPL) encodes all of these as mathematical constraints and generates a finished, optimized call schedule. Chief residents and program directors receive the completed schedule for review rather than building it themselves. There is no software to operate and no conflicts to manually resolve.

Question 2

How is this different from rule-based scheduling tools we already use?

Accepted Answer

Rule-based scheduling tools flag violations and conflicts **after** you have already built the schedule, leaving the resolution work to the chief resident. Thrawn's optimization engine works differently at a fundamental level: it generates schedules from constraints, meaning violations cannot exist in the output. The schedule is finished, balanced, and compliant when it arrives. Competitors would need to rebuild their scheduling engines from the ground up to replicate this approach — it is not a feature difference, it is an architectural one.

Question 3

What happens to compliance and fairness when a resident calls out unexpectedly?

Accepted Answer

When an unplanned absence occurs, Thrawn re-optimizes the affected portion of the call schedule with all original ACGME and fairness constraints still active. The resulting schedule remains compliant and equitable — it does not simply shift burden onto the nearest available resident. This is meaningfully different from manual coverage decisions made under time pressure, which frequently introduce new violations or fairness imbalances.

Question 4

How does the system handle complex structures like night float and jeopardy?

Accepted Answer

Night float and jeopardy coverage are modeled as first-class scheduling structures inside the SPL, not as manual overrides or exceptions. This means coverage chains across float rotations are mathematically guaranteed to remain intact across the academic year. When residents transition on or off float blocks, the system accounts for all associated duty hour implications without requiring manual patching or auditing from the chief resident or program coordinator.

Question 5

What do programs say about using Thrawn for their scheduling needs?

Accepted Answer

Programs across 19 departments at 14 hospitals in leading academic health systems have transitioned to Thrawn's managed call scheduling service. As one clinical fellow put it: *"Scheduling can be one of the most stressful and time-consuming parts of the role, but Thrawn made the entire process seamless. I would highly recommend their services to any program looking for a reliable and efficient way to build equitable schedules!"* — Dr. R. Kapoor, Clinical Fellow, Neurocritical Care Fellowship at a leading academic medical center.

Residency Call Schedule Automation Fair and ACGME-Compliant

Why Call Scheduling Breaks Chief Residents

Why Call Scheduling Breaks Chief Residents

Fair Call Distribution Across Every Resident

ACGME Duty Hours Enforced at Generation

Night Float and Jeopardy Handled Natively

Undesirable Shifts Distributed Without Complaints

Backup and Coverage Call Always Filled

Automate Your Call Schedule

Common Questions