Call scheduling software for independent anesthesia groups
Make the call schedule in minutes. Keep your weekends.
We write custom scheduling code for independent anesthesia groups. We sit down with your doctors to learn your rules, then build them into PostCallMD. Each month, we tune it until you can finish your schedule in minutes.
“Scheduling used to involve two partners working nights and weekends with pencil, paper and Excel. Now, I can knock it out in minutes from my phone.” Partner at an independent anesthesia group, Charleston, SC
PostCall Protection
Protecting the post call, one annoying pop-up at a time.
Nothing causes a bigger scheduling snafu than making someone work post call. And every group has watched the rule bend when coverage gets tight.
PostCall Protection puts friction exactly where the rule bends. You can still schedule a doctor post call. But the reason gets logged, the physician's name has to be typed in to confirm, and their post-call count does not go unnoticed.
Fairness stops being a feeling and becomes a number.
| Doctor | Sun121/1 | Mon131/2 |
|---|---|---|
| Dr. Fishman | ||
| Dr. Snook | CALL | |
| Dr. Echols | CALL |
Try it. Schedule a post-call doctor.
| Date | Clinician | Shift | Reason | Post-call YTD | Overridden by |
|---|---|---|---|---|---|
| Oct 13 | Dr. Echols | OR | 2 | You |
Request Hub
Every schedule request in one place, even the messy ones.
Doctors ask for days off from the app on their phone, or they just email the way they always have. Either way it lands in one queue.
The emails don't have to be tidy. The AI agent reads “hey, any chance I could get the 14th, and also swap my Friday with Echols if he's ok with it” and turns it into two clean requests with dates attached. The admin taps approve or deny.
No more digging through June's texts and emails looking for October requests.
Call Wizard
Far from perfect, but built for your group and better every cycle.
We learn your rules from the doctors who make the schedule. I use Claude and Codex to help write the code for your practice.
The scheduling engine1 uses those rules to build a draft. Your doctors review the result and decide what to change.
There is no configuration on your end, and no settings page with four hundred toggles. You get a button.
Each cycle we take your feedback and dial the solver in.
You review the draft with your group and publish it when it is ready.
- Cardiac days take two cardiac-capable docs, neither post call Hard
- Non-partners get all contracted shifts while partners split the remainder prorata Hard
- Vacation never starts post call Hard
- Dr. Cherry and Dr. Brown never work the same weekend Hard
- At least four days between call shifts Soft
- No back to back weekends Soft
1. The engine under the button is CP-SAT, the constraint solver in Google's OR-Tools. Operations research, not operating room. It is the same open-source solver Google built for its own scheduling and routing problems, and it evaluates millions of schedules against every rule on the sheet before it hands you one.
Draft Runner
The vacation draft, without the reply-all.
If your group drafts vacation or holidays, you know the loop: update the sheet, email the next doc, wait for a reply, maybe send a reminder, update the sheet, email the next doc, wait, repeat... None of it is hard. It's just tedious. You're stuck in the loop.
With Draft Runner, the draft runs itself. Set it up once. It emails each doctor when their turn comes, shows them what is still open, and locks picks as they are made. Selections land in the database in order, so they are ready for scheduling.
The draft that used to keep you trapped in the loop now runs itself.
- 1Dr. Fellertook Thanksgiving off
- 2Dr. Rosetook Christmas Eve
- 3Dr. Echolspicking now · emailed 8:02a
- 4Dr. Cherryup next
- 5Dr. Brown
Mobile first
The best schedules are made by docs who work them.
That is why everything in PostCallMD works from a phone. Publish a schedule from the OR or the carpool line.
(But yes, there is still a full desktop app.)
We know every one of our doctors by name
My name is Moultrie Ball, and I am the nerd behind PostCallMD.
PostCallMD was built to help my friend with their call scheduling problem. Long story short, the doctor who made the schedule was stepping down. The group hired me to sit with the scheduling doctor and turn his process into a “computer program.”
While PostCallMD has outgrown that simple Python script, one part is still very much the same: me.
When you come on board, you will work directly with me. To start, I meet with a few doctors to learn what makes a good schedule. After I learn about your group, I build your solver and generate your first schedule. Zero configuration on your end. Then, every month, we dial in your solver until good schedules take minutes, not weekends.
I guess the downside to working with a small company is that we only take on two new groups each month. It is how we make sure every new practice has a smooth transition. And hey, it gives us time to learn every one of our doctors by name.
When you are ready to learn more about scheduling with PostCallMD, fill out the form or shoot me an email. I will ask a few questions about your practice and send you a quote.
I appreciate you,
Moultrie Ball (mole-tree)Twenty minutes, and you leave with a quote
Pricing is per group. It depends on how many doctors, how many sites, and how gnarly the rules are, so quotes happen in a conversation, not a rate card. The conversation is with me, Moultrie Ball. I built PostCallMD and I build every solver, so you will not be talking to sales. You leave with your number, what onboarding would look like, and no follow-up drip if the answer is no.
Not ready to change how your group makes the schedule?
Fair enough. When you are, remember PostCallMD.