
Key Takeaways
If you're a program director or chief resident, you already know the drill with GME scheduling software. Every scheduling cycle, you're staring down 40+ hours of work — cross-referencing block rotations, call assignments, and clinic slots while manually checking every decision against Accreditation Council for Graduate Medical Education (ACGME) duty hour rules. One swap request from a resident cascades into three broken assignments. A PGY-1 accidentally gets slotted past their 16-hour shift cap. You catch it at 11pm.
This isn't a software problem. It's a logistics problem — and most GME scheduling software tools on the market were built for the former, not the latter.
The tools below represent the full spectrum of what's available for residency programs today. Some are schedule viewers. Some are schedule builders. A select few actually deliver finished schedules. Each is evaluated on the same rubric: ACGME compliance method (rule-based detection vs. constraint-based prevention), automation depth, schedule types supported, and if the tool shifts work to you or eliminates it. Before diving in, it helps to understand the two fundamentally different philosophies in this space.
Scheduling assistants are tools you operate. They give you a better interface than Excel, sometimes flag duty hour violations, and leave you responsible for building, balancing, and fixing the schedule. Scheduling owners are services that take the entire workload off your plate — you send constraints, you receive a finished schedule for review. The distinction matters more than any feature comparison.
The list below moves from the most capable managed services down to widely-used self-service tools. The right choice depends entirely on how much of the scheduling workload your program can afford to own.
Thrawn isn't GME scheduling software in the traditional sense — it's a managed scheduling service that delivers finished Block, Call, Clinic, and Attending schedules to your inbox. You send constraints (resident preferences, rotation requirements, vacation requests, ACGME duty hour rules, educational goals), and Thrawn's team delivers complete, optimized schedules ready for your review. Chiefs and program directors stop being schedule builders. They become schedule reviewers.
The engine behind this is Thrawn's proprietary Scheduling Programming Language (SPL) — a domain-specific mathematical optimization system built by a team of MIT-trained mathematicians, computer scientists, and logistics experts. Unlike rule-based detection tools that flag violations after a schedule is already built, Thrawn's SPL treats ACGME duty hour rules as hard constraints at generation time — violations don't appear in the output because they can't. That's a structural difference, not a feature gap.
What separates Thrawn from every other option on this list is cross-schedule simultaneous optimization. Most tools build block, call, and clinic schedules sequentially — meaning a single change in one schedule sends a domino effect through the others.
Thrawn treats all schedule types as one interconnected system and optimizes them simultaneously. The result: no cascading edits, no domino effect, and a Fairness & Equity Engine that distributes assignments with mathematical balance rather than tribal knowledge.
Thrawn currently serves 19 departments across 14 hospitals at multiple top-20 academic health systems. One clinical fellow put it plainly: "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.
Scheduling Wizard is a well-established managed scheduling service for academic medical centers, and the closest peer to Thrawn in terms of model. Programs submit constraints and receive finished, ACGME-compliant schedules — chiefs aren't building from scratch each cycle.
One of Scheduling Wizard's strongest attributes is its handling of the "July problem." Because the service retains all program logic, rotation rules, and historical preferences year over year, the annual chief resident transition doesn't reset institutional scheduling knowledge to zero. That continuity alone saves programs dozens of hours annually.
Where Scheduling Wizard differs from Thrawn is at the engine level. Scheduling Wizard's compliance approach is well-established and service-oriented, but it doesn't operate on the same constraint-based mathematical optimization architecture that Thrawn's SPL provides. For programs that want a capable managed service with a long track record, Scheduling Wizard is a credible choice.
QGenda is an enterprise-level workforce management platform used across large health systems. It's powerful, deeply configurable, and built for organizations that have dedicated administrative staff to operate it. For residency-specific GME scheduling, it's a different kind of tool.
QGenda's ACGME compliance approach is reactive detection — the platform surfaces duty hour violations after the schedule has been built, leaving the user responsible for identifying and manually resolving each conflict. According to residents and program administrators on r/emergencymedicine, QGenda is "great but often expensive and enterprise-focused," which makes it a difficult fit for individual residency programs managing annual chief rotations.
Amion is one of the most widely recognized names in GME scheduling software — and one of the most commonly misunderstood. It's a schedule publishing and viewing tool, not a scheduling engine. Users build schedules in Excel or another system, then upload them to Amion for display and distribution.
That means Amion provides zero automated ACGME compliance checks. The entire burden of maintaining duty hour adherence sits with the person who built the underlying spreadsheet. Residents on r/Residency describe it as familiar but "clunky," and its limitations become obvious fast when programs try to use it as a full scheduling solution. Amion works best as a communication layer on top of schedules built elsewhere.
Calerity is built specifically for GME — that focus shows in its feature set. The platform uses AI to assist with assignment distribution and fairness, and it's designed around the workflows chief residents actually deal with: vacation requests, rotation rules, and equitable shift distribution.
Where Calerity fits in the market is as an AI-assisted self-service tool. It automates parts of the scheduling process, but you're still operating the software — configuring rules, reviewing outputs, and resolving flagged conflicts. As noted in Thrawn's residency scheduling overview, Calerity uses a rules-based system that requires user management to produce a finalized, compliant schedule. It's a meaningful step up from Excel, but the workload doesn't disappear — it gets lighter.
Calerity's decade-plus head start in the GME space gives it real depth in program-specific features. For programs that want more automation than legacy tools but still prefer direct control over the scheduling process, it's worth evaluating.
Chiefly is designed with the chief resident experience in mind, offering a cleaner and more intuitive interface than spreadsheet-based approaches. If a chief is going to build the schedule manually, Chiefly is a more pleasant environment to do it in.
That's also the ceiling. Chiefly improves the experience of manual scheduling — it doesn't fundamentally change the equation. ACGME compliance is still the user's responsibility. Institutional knowledge still walks out the door when the chief rotates. The July problem doesn't get solved; it just happens in a nicer interface. For small programs with motivated chiefs who want direct hands-on control, it's a usable option. For programs wrestling with compliance risk or chief burnout, it isn't designed to help.
Lightning Bolt, now part of PerfectServe, is a self-service scheduling platform with one of the stronger rules engines among traditional GME scheduling software. It's mobile-friendly, configurable, and reasonably well-regarded for shift management in clinical departments.
Like QGenda, Lightning Bolt's compliance approach is reactive: the rules engine tracks ACGME requirements and flags violations, but the user must configure those rules correctly upfront and manually resolve any conflicts that surface. According to Thrawn's tool comparison, even with AI-driven features, Lightning Bolt still requires significant user effort to produce a finished, compliant schedule. It's a capable tool for departments with staff who can invest time in configuration and ongoing management.
The GME scheduling software you choose should match the problem you actually have — not the one a vendor's sales deck describes. Here's a clear way to self-identify.
You need a scheduling assistant if:
You need a scheduling owner if:
The distinction isn't about sophistication — it's about where the work lives. Scheduling assistants shift work to the user with better tools. Scheduling owners eliminate the work entirely.
Before committing to any GME scheduling software or service, ask these questions directly, adapted from Scheduling Wizard's ACGME compliance guide. The answers will reveal if a vendor's compliance claims hold up.
Per ACGME requirements, each of these rules carries real accreditation weight. A tool that answers these questions with "we flag it after" is telling you something important: you're still doing the compliance work, just with a faster highlighter.
The honest question isn't which GME scheduling software has the best interface. It's whether your program should be operating scheduling software at all.
For most residency programs at academic medical centers, the scheduling workload is a structural problem — not a workflow problem. No amount of better software changes the fact that block, call, and clinic schedules are an interconnected optimization problem with dozens of overlapping constraints, and that solving it correctly requires mathematical infrastructure that most scheduling tools simply weren't built to provide.
The tools in the scheduling assistant category — QGenda, Lightning Bolt, Chiefly, Amion — serve real use cases. They're appropriate when programs have the administrative capacity to operate them and the tolerance for ongoing manual management. But for programs where chiefs are burning out on scheduling, where ACGME violations surface post-build, or where every July resets the clock to zero, a better tool isn't the answer. A different model is.
Scheduling Wizard offers that model with a strong track record. Thrawn offers it with a mathematically superior engine — one that treats ACGME duty hour rules as generation-time constraints, optimizes block, call, clinic, and attending schedules simultaneously, and delivers finished schedules that programs review rather than build. Serving 19 departments across 14 hospitals at multiple top-20 academic health systems, Thrawn is the only managed scheduling service built on true constraint-based mathematical optimization rather than rules or heuristics.
If your program is ready to stop spending weeks per cycle on a problem that can be solved overnight, book a free consultation with Thrawn to see what it looks like when scheduling is done for you.
A scheduling assistant is software you operate to build and fix schedules yourself. A scheduling owner is a managed service that takes your constraints (rules, requests) and delivers a complete, finished schedule for you to review. The key difference is who does the work — you or the service.
You provide all your scheduling inputs: rotation requirements, ACGME rules, vacation requests, and resident preferences. The service then uses its engine and specialists to build a fully optimized schedule. You receive a finished draft for review and approval, eliminating the manual building process entirely.
Constraint-based systems like Thrawn's build schedules where ACGME duty hour violations are mathematically impossible from the start. Rule-based tools only detect violations after a schedule is built, leaving you to manually find and fix the errors. Prevention eliminates compliance work and risk.
With a managed service, you simply report the unplanned absence. The system can rapidly re-optimize the schedule to find the best possible compliant solution, minimizing disruption. This avoids the chaotic domino effect of manual swaps and maintains continued fairness and ACGME compliance.
A managed service acts as your program's long-term memory for scheduling. All rules, preferences, and institutional knowledge are retained within the system. This solves the "July problem," creating a smooth transition and preventing new chiefs from having to learn scheduling from scratch.
Leading managed services can handle all major GME schedule types, including Block, Call, Clinic, and even Attending schedules. The most advanced systems, like Thrawn, optimize these simultaneously to prevent cross-schedule conflicts and ensure a single, cohesive plan for the entire program.