Resources
Field notes for the person building the call schedule.
Things I made for the senior resident, the chief, the fellow, or the one partner in the group who got handed the spreadsheet and is now spending every other weekend on it.
How to make a call schedule with AI, free.
Connect Claude Code or Codex to the free PostCallMD app through its MCP server, or point it at the open-source solver on your laptop. A real constraint solver does the assigning, so nothing is invented. Eight steps, one prompt to paste, and a sample schedule you can drag around.
Read the walkthrough →How an anesthesia call schedule actually gets built.
The rules every group has that don’t fit on a spreadsheet: post-call rest, partner allocation, weekend fairness, vacation routing, the local exceptions that turn into eight-line emails. Written from inside the work, not above it.
Read the article →If you are comparing options.
Longer pages on how PostCallMD works, who it fits, and where something else is the right answer.
Anesthesia call scheduling, built from your rules.
What we actually build for a group of 14 to 40 clinicians. Your post-call rest, your site coverage, your weekend pairings, written into a solver instead of a settings screen. Includes what the first month looks like and who does what.
Read how it works →Free anesthesia scheduling software.
What the free app does, feature by feature: requests, call and the daily board, post-call protection, fairness reports, the phone app, import, your own agent, export. Custom when your rules outgrow the spreadsheet.
Read the overview →QGenda, Amion, a spreadsheet, or us.
An honest side-by-side for anesthesia call scheduling. QGenda is a platform you configure. We build a solver around your rules and you keep the schedule. Where QGenda is the right answer for your group, the page says so.
Read the comparison →More on the way. If there’s a piece you want me to write (the rule you don’t think a computer can handle, the part of your process that always slips), email [email protected] and tell me. I write to questions, not in a vacuum.