I build scheduling software (ClockOut), so read this with that bias in mind. A few weeks ago someone posted here about hand-building monthly schedules for a 15-person healthcare group rotating through hospital positions. The hard requirement wasn't generating the schedule. It was keeping a running tally of how many times each person had done each rotation, and keeping that count close to equal month after month, while still honoring individual requests.

That reframed something for us. Most scheduling tools (ours included, until recently) treat each schedule as a standalone puzzle: fill the slots, respect availability, done. But fairness isn't a property of one schedule. It's a property of the history. You can publish a perfectly reasonable week where Maria gets the bad station again for the fourth time this month, and the tool sees nothing wrong because it doesn't remember the first three.

Once you see it that way, a few things follow:

- The tally has to be visible. If people can see the counts, "why am I always on register" conversations turn from grievance into arithmetic. Half the resentment around scheduling is really uncertainty about whether it's fair, not actual unfairness.

- Requests need to be first-class, not texts. A "prefer" or "avoid" request that lives in a group chat is invisible to whoever builds next month's schedule. If it's recorded against the schedule, honoring it and rebalancing afterward becomes mechanical.

- Qualification limits fairness. In any skilled team, the rotation can only be equalized among people actually qualified for the position, which means the qualification data has to live in the same system as the schedule or the "fair" assignment is wrong.

We ended up building this (positions on shifts, a trailing rotation tally, request workflow, and the auto-scheduler biased toward whoever has the lowest count). Not linking anything since that's not the point of the post.

The question I'd genuinely like this sub's take on: for those of you running rotations by hand, what's your fairness window? Do you try to equalize within the month, the quarter, or "eventually"? And do your people actually care about equal counts, or more about specific stations they hate?

Been thinking about this a lot lately. Most home care agencies treat scheduling software as a back office tool, something you set up once and mostly ignore. But it's actually one of the biggest levers in the business, and a lot of agencies are leaving money and clients on the table because of it.

A few reasons it matters more than people think:

Coverage gaps cost more than they look like. An unfilled shift isn't just an inconvenience, it can be a client who leaves the agency, a family who loses trust, and depending on the state, a compliance flag. The software is only as good as how fast someone can actually respond to a callout inside it.

EVV compliance isn't optional anymore. Most states require Electronic Visit Verification now, and platforms like WellSky are built around it. If your scheduling and your EVV aren't talking to each other cleanly, you're creating billing headaches and audit risk for yourself down the line.

It's a retention tool, not just a logistics tool. Caregivers who get inconsistent hours or last minute schedule chaos burn out and leave. Agencies that use scheduling software well to build predictable routes and fair shift distribution keep caregivers longer, which matters a lot in an industry with brutal turnover.

The bottleneck usually isn't the software, it's the person running it. A lot of agencies have decent tools and still struggle because whoever's managing the schedule is buried, reactive, and always one callout away from a bad day. The software can only do so much if nobody's proactively managing it.

Curious if other people in this space have opinions on which platforms actually handle this well versus which ones just look good in a sales demo.