Calerity vs. Thrawn: Comparing Managed Scheduling Services for Residency Programs

Key Takeaways

• Rule-based scheduling services help you build a compliant schedule, but mathematical optimization delivers a complete, finished schedule for review.
• Optimization solves key residency pain points by building in ACGME compliance to prevent violations and creating provably fair assignments to reduce resident complaints.
• Simultaneously optimizing block, call, clinic, and attending schedules as a single system eliminates the "domino effect" where one change forces a complete rebuild.
• Programs struggling with fairness complaints, compliance anxiety, and knowledge loss during chief transitions can receive finished, mathematically optimized schedules with Thrawn's managed service.

You've already decided that building residency schedules in Excel isn't good enough. You've found Calerity — a managed scheduling service with a real track record — and you're wondering if there's a newer, better option. That's exactly the question this article answers.

Both Calerity and Thrawn operate as managed services for residency and fellowship programs. But their underlying philosophies — and the outcomes they produce — differ in meaningful ways. This is a transparent, side-by-side comparison of what each service actually does, where they differ, and how to think about the choice for your program.

Why Residency Scheduling Is More Than a Spreadsheet Problem

Ask any chief resident what the hardest part of the year is, and scheduling comes up immediately. One chief resident noted that it was "the worst part of being chief — worse than residency itself." Another called it "a pretty thankless job."

The frustration isn't just the volume of work. It's the complexity underneath it. Every schedule has to simultaneously balance:

• Core rotation requirements
• Program coverage needs
• Individual preferences and vacation requests
• Accreditation Council for Graduate Medical Education (ACGME) duty hour limits

And as residents in that same thread noted, "Everyone complains, no one is happy."

Three problems make this especially hard to solve:

• The domino effect. Block, call, clinic, and attending schedules are deeply interdependent. One swap request or unplanned absence can cascade through the entire schedule, forcing a near-complete rebuild.
• Fairness complaints. Without a systematic, provable approach to equity, residents will always perceive bias — too many weekends, not enough elective time, someone always getting the short end. Chiefs are left defending subjective decisions.
• ACGME compliance anxiety. Program Directors (PDs) bear ultimate responsibility for duty hour compliance. A violation found during accreditation review can trigger probation. Most programs track this manually, which is slow and error-prone.

Managed scheduling services exist to address exactly these problems. The question is how well each one does it.

Calerity vs. Thrawn: A Head-to-Head Breakdown

Calerity has a decade-plus track record serving Graduate Medical Education (GME) programs. Thrawn is newer — founded in 2023 — but built around a fundamentally different technical approach. Here's how they compare across the dimensions that matter most.

The Scheduling Engine: Rule-Based vs. Mathematical Optimization

This is the most important architectural difference between the two services.

Calerity, like most established scheduling platforms, uses a rule-based engine. Rules are configured upfront (e.g., "no resident can work more than 80 hours per week," "each resident must complete X rotations"). The system then helps construct a schedule while flagging violations of those rules. It's a meaningful improvement over spreadsheets, but conflict resolution typically still requires human judgment.

Thrawn is built differently. Its proprietary Scheduling Programming Language (SPL) is rooted in mathematical programming and operations research — the same field that underlies supply chain logistics and defense resource allocation. Rather than flagging conflicts for you to fix, the SPL takes your program's constraints as inputs and produces a complete, mathematically optimal schedule as output.

The practical implication: chief residents using Thrawn review schedules instead of building them. The finished schedule arrives; their job is to confirm it meets expectations, not to resolve cascading conflicts by hand.

The Service Model: Onboarding and Knowledge Retention

Both services operate as managed models rather than self-serve software. But how each handles onboarding — and what happens every July — is different.

Thrawn assigns a dedicated scheduling specialist to each program. That specialist conducts structured constraint-gathering sessions: rotations, rules, preferences, ACGME requirements, institutional quirks. There's no software to learn, no configuration burden on the program, and no training involved.

The more critical differentiator is knowledge retention. When a chief resident graduates, their understanding of how the schedule works — all the informal rules, the edge cases, the historical workarounds — typically walks out with them. The incoming chief starts from scratch.

Because Thrawn retains that institutional knowledge within its specialist team, the incoming chief doesn't inherit a blank slate. The constraint library and scheduling logic persist across transitions. That's a structural advantage no self-serve tool can replicate.

Fairness and Equity: Mathematical Proof vs. Manual Balancing

Fairness in scheduling is one of the most politically loaded issues in any residency program. Chiefs who manually balance night shifts, holiday call, and coveted elective rotations are always working from a subjective starting point — and residents know it.

Thrawn's Fairness & Equity Engine treats fairness as a mathematical constraint built into the optimization itself. The SPL provably distributes desirable and undesirable assignments — nights, weekends, holidays, coveted rotations — across residents with measurable equity. That's not a promise about outcomes; it's an architectural property of how the schedule is generated.

When a chief can show that the distribution was mathematically balanced rather than manually eyeballed, it changes the conversation around complaints entirely.

ACGME Compliance: Prevention vs. Detection

Most scheduling tools check for ACGME duty hour violations after a schedule draft is produced — a post-hoc audit. That means a violation is possible to miss, especially in complex programs where block, call, and clinic schedules interact.

Thrawn builds ACGME duty hour compliance in as a generation constraint. The SPL will not produce a schedule that violates duty hour rules. Violations are prevented at creation, not discovered after the fact.

For PDs who are primarily responsible for compliance during site visits, this distinction matters. There's a meaningful difference between "we check for violations after building the schedule" and "violations are structurally impossible in the output."

Scope: Integrated vs. Siloed Schedules

Most scheduling tools — and many managed services — handle each schedule type (block, call, clinic, attending) as a separate workflow. Even when the same platform manages all four, they're often optimized independently, leaving the program to manually resolve conflicts where schedules intersect.

Thrawn's SPL treats all four schedule types as one interconnected optimization problem — a capability Thrawn calls Cross-Schedule Simultaneous Optimization. Block rotations, call assignments, clinic sessions, and attending coverage are generated together, as a system. A constraint violation in one schedule is automatically accounted for across all others.

This is what truly eliminates the domino effect. Not by reducing its frequency — but by making it structurally impossible.

What the Research Says About Automated Scheduling

The benefits of optimization-based scheduling aren't just theoretical. A study in PLOS ONE evaluated an automated scheduling tool called AIMS at the Yale New Haven Hospital Internal Medicine Residency Program, and the results were notable:

• First-choice rotation assignments improved from 30.5% to 80.5% for residents, and from 69.4% to 96.0% for interns.
• Average satisfaction with schedules increased from 3.3 to 4.0 on a 5-point scale.
• Perceived fairness rose from 3.3 to 4.2.

These numbers reflect what happens when systematic optimization replaces manual schedule-building: dramatically better preference matching, higher resident satisfaction, and a stronger perception of equity. The evidence base for moving beyond rule-based tools is strong.

A Chief Fellow's Experience With a Done-for-You Model

To understand what the managed service experience actually looks like, consider the process described by Dr. R. Kapoor, a Clinical Fellow in a Neurocritical Care Fellowship:

"We provided the team with the vacation requests of our clinical fellows and scheduling requirements for various rotations, and Thrawn quickly followed up with a couple of clarifying questions. Within such a short time, our yearly block fellowship schedule was complete!"

The experience Dr. Kapoor described reflects exactly what Thrawn's model is designed to deliver — programs provide the "what," Thrawn handles the "how." As Dr. Kapoor 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!"

This is the core value proposition of a done-for-you managed service: chief residents stop building and start reviewing.

Making the Right Choice for Your Program

The comparison between Calerity and Thrawn ultimately comes down to a philosophical question: do you want a service that helps you build a compliant schedule within a set of rules, or a service that takes your constraints and delivers a mathematically optimal finished schedule?

Calerity brings a long-established track record in GME scheduling. For programs that value proven history and an existing ecosystem of clients, that matters.

Thrawn is the right fit for programs that want to go further — specifically those dealing with:

• Persistent fairness complaints that can't be resolved through manual balancing alone.
• ACGME compliance anxiety where detection after the fact isn't sufficient reassurance.
• The domino effect across block, call, clinic, and attending schedules that are currently managed in separate workflows.
• Annual chief transitions where scheduling knowledge gets lost every July.

The architectural difference between rule-based scheduling and mathematical optimization isn't a feature gap. It's a different category of tool — one that competitors would need to fundamentally rebuild their engines to match.

Thrawn currently serves 19 departments across 14 hospitals at multiple top-20 academic health systems, with specialties including Neurocritical Care, Neurology, and Family Medicine. Pricing is personalized based on program size and needs, with no public rate card — programs schedule a consultation to discuss their specific requirements.

If your program is still absorbing the scheduling burden onto a chief resident every year, a consultation with Thrawn is worth the conversation.

Frequently Asked Questions

What is the difference between rule-based and optimization-based scheduling?

Rule-based systems help users build a schedule by flagging violations. Mathematical optimization systems take all constraints as inputs and produce a complete, finished schedule for review. Instead of resolving conflicts, program leaders simply approve the final, optimal result generated by the service.

How does the service ensure fair schedule assignments?

Fairness is treated as a mathematical constraint, not a manual balancing act. Thrawn's optimization engine provably distributes desirable and undesirable assignments like nights, weekends, and holidays equitably across all residents. This provides objective proof that the schedule is balanced.

How does Thrawn prevent ACGME duty hour violations?

ACGME duty hour rules are built in as a core generation constraint. The scheduling engine will not produce an output that violates these rules, making violations structurally impossible. This shifts the compliance model from post-hoc detection to proactive prevention, providing greater assurance to PDs.

What happens when a resident is unexpectedly absent?

The schedule can be rapidly re-optimized. When a program notifies Thrawn of an unplanned absence, the service treats it as a new constraint and quickly generates a new, fully compliant and balanced schedule. This eliminates the "domino effect" that forces manual rebuilds in spreadsheets.

How does a managed service handle chief resident turnover?

A managed service retains a program's institutional knowledge. Your dedicated scheduling specialist documents all rules and preferences, so this critical information isn't lost when a chief resident graduates. Incoming chiefs inherit a proven system, not a blank spreadsheet and a manual.

What types of schedules does Thrawn create?

Thrawn generates Block, Call, Clinic, and Attending schedules. All schedules are optimized simultaneously as a single interconnected system, not as separate silos. This cross-schedule optimization eliminates the cascading conflicts that arise when a change in one schedule impacts another.