Ilana Borkenstein

Your Hospital Bought Scheduling Software. Why Are Managers Still in Spreadsheets?

Your hospital invested in scheduling software. It went live. And your managers are still in spreadsheets.

If you walk onto any unit and ask a department manager how she builds her schedule, there's a decent chance she'll pull up a spreadsheet.

I hear this constantly.

It comes up across every clinical department. The problem isn't specific to one role. It's structural.

The system exists. The contract is signed. And the workaround is still running in parallel.

This isn't a failure of your team. It points to a specific and solvable problem: most scheduling platforms were never built to handle the full complexity of shift-based clinical staffing. They handle parts of it. The rest still falls on your people.

At M7, we've activated over 140+ hospitals across 29 states. What we see consistently is the same dynamic: well-run organizations with committed leaders, still working around the very tools they invested in.

The two steps that get used (and the five that don't)

Ask a clinical manager which parts of her scheduling system she actually uses day-to-day, and the answer is usually the same. Two things get used.

Staff submit time-off requests through it. And she posts the finalized schedule through it so everyone can see their shifts.

That's where the system's involvement ends.

Everything in between is manual. Balancing the schedule. Filling open shifts. Managing callouts. Floating staff across units and departments. Reconciling what actually happened with payroll.

Spreadsheets. Printed binders. Group texts. Phone calls down a list.

The system was purchased, implemented, and is technically "live." But it only touches the beginning and end of the workflow. The middle, the part that actually consumes hours every week, is still fully manual.

Why this keeps happening

Most large workforce management platforms weren't built for clinical scheduling. They were built for payroll, timekeeping, and general HR management. Scheduling was added later, and it shows.

What these platforms do reasonably well: take in time-off requests, and post a finalized schedule so staff can see their shifts.

What they typically don't handle: the dynamic, real-time work that happens after the schedule is posted.

The moment a schedule goes live, it starts becoming outdated. Staff call out. Patient census spikes. Someone requests a swap. A supervisor needs to float someone to cover another unit. These aren't edge cases. They are the daily reality of staffing a hospital. And they require a system built to handle them, not a workaround.

The result is a parallel workflow. The official schedule lives in the system. The actual operational reality of staffing the hospital lives in spreadsheets, binders, and the department manager's head.

The implementation problem nobody warns you about

Even when a health system chooses to implement one of the large enterprise workforce platforms for scheduling, the implementation itself can take a year or more. By the time it's live, the clinical environment has shifted. Departments have changed. Staffing models have evolved. And the platform, which was never purpose-built for clinical scheduling to begin with, still doesn't account for the realities of how shift-based clinical work actually operates: the credential-based float rules, the department-specific coverage requirements, the real-time judgment embedded in every staffing decision.

These platforms were engineered for enterprise HR scale. They were not engineered for the clinical complexity behind every shift.

So health systems spend a year in implementation, go live, and then discover what clinical managers already knew: the system doesn't reflect how this work actually gets done. The spreadsheet comes back out.

It's one of the most common things I hear from leaders who've been through a major platform rollout. The technology was supposed to solve the problem. It took eighteen months and a seven-figure implementation contract to find out it didn't.

The open shift problem

Open shift management is one of the clearest examples of where the gap shows up.

Most scheduling platforms have some version of an open shift feature. But in practice, health systems find that staff stop using it, or that managers stop trusting it because it broadcasts every available shift to every employee regardless of credential, department, or availability. The volume of notifications makes the feature unusable.

So what happens instead? The charge clinician or house supervisor starts making calls. Texts go out. Someone checks a binder. The open shift gets filled eventually, but it took 45 minutes of someone's time and probably went to whoever answered the phone first, not whoever was most qualified or most cost-effective.

Every open shift filled reactively is a chance to create inequity, miss the right match, and quietly drive the kind of scheduling frustration that makes clinical staff leave.

What the actual workflow should look like

A scheduling system that covers the full workflow doesn't stop when the schedule is posted. It actively manages what happens after.

When a shift opens, qualified and available staff are automatically notified, filtered by department, credentials, and hours worked, through a mobile app rather than a phone call. The manager reviews and approves. The schedule updates in real time.

A house supervisor has a live view of staffing across every department. Not a report she has to request, but a dashboard she can check at any moment to see where she's short and who's available to float.

When someone calls out at 5am, there's a process that doesn't require the charge nurse to spend the first hour of her shift on the phone.

And when the shift ends, the system knows what actually happened: who worked, in what role, in which department. Reconciliation with payroll becomes a data transfer, not a manual audit.

That's what we built M7 to do. M7 is an AI-powered workforce operations platform built for the realities of clinical staffing. It forecasts demand, auto-balances schedules, and deploys the right staff to fill any gap before a health system has to resort to premium labor spend. And it integrates with the payroll, timekeeping, and HRIS systems health systems already have. It's not a rip-and-replace. It sits on top of what you've already built.

M7 started in nursing because that's where the complexity is highest. But the problem turns out to be universal. Every shift-based clinical team is running some version of the same workaround.

How to know if you're still in spreadsheet mode

If any of these sound familiar, the system isn't covering the full workflow:

Managers balance schedules in Excel or on paper before uploading the final version
Open shifts are filled primarily through phone calls, texts, or a whiteboard
The house supervisor's day-of staffing system is a printed census sheet and a binder
Callout coverage requires manual calls down a list
Reconciling scheduling data with payroll requires a separate manual process each pay period

These are signs that the technology in place wasn't built to solve these problems, and that a good team has found ways to work around it.

The workarounds work until they don't. They create overtime. They create inequity. They burn out clinical managers. And they make it harder to see whether the hospital is actually staffed safely at any given moment.

What changes when the workflow is covered

When a platform handles the full workflow, the most immediate change is time. Health systems using M7 report a 60% reduction in administrative scheduling burden. Most see that impact within the first schedule cycle, not after a year of rollout. Shifts get filled earlier, with the right staff, before overtime is needed. Floating decisions are made based on data, not instinct. Clinical staff feel like their preferences are actually heard and reflected in their schedules.

And leadership gets visibility they've never had before. A real-time view of staffing across every department and every shift. Not a report that's already out of date by the time it's generated. The ability to act before problems escalate, not after. Health systems see measurable impact within the first schedule cycle.

The spreadsheet doesn't disappear because someone mandated that it should. It disappears because there's finally a system that makes it unnecessary.

The spreadsheet workaround is a symptom. The fix is a system that actually covers the full workflow. If you want to see what that looks like at your hospital, explore the platform, run the numbers, or reach out directly at founder@m7health.com.

FAQ

Why do clinical teams still use spreadsheets even when scheduling software is in place?

Most enterprise scheduling platforms only automate a portion of the workflow, typically time-off requests and schedule posting. The balancing, open shift management, and real-time staffing adjustments that happen in between are left to manual processes. Spreadsheets fill the gap.

What should purpose-built clinical scheduling software actually automate?

A complete platform should handle preference-based schedule building and auto-balancing, mobile-first open shift broadcasting with credential-based filtering, real-time house view for day-of staffing decisions, float pool and cross-department deployment, and integration with payroll and HRIS for accurate reconciliation.

How is M7 different from the enterprise platforms that haven't solved this problem?

Most enterprise workforce platforms were built for general HR scale and had scheduling added on. M7 was built from scratch around the clinical realities of shift-based staffing: credential-based floating, department-specific coverage rules, open shift management that actually gets used, and real-time visibility across the entire facility. The difference isn't just features. It's the underlying design logic.

How do you move away from manual scheduling without disrupting departments?

The key is implementation that actually moves fast and meets managers where they are. M7 goes live within a single schedule cycle, not over the course of a year-long rollout. Every department manager gets a dedicated onboarding lead who configures the platform to their specific clinical requirements before go-live, so the system reflects how that department actually staffs from day one.