The Spreadsheet Running Your Practice (That You Don't Know About)

A 4-location podiatry practice in Ohio lost three weeks of billing reconciliation when their office manager of 12 years retired. By Wednesday of her final week, reconciliation stopped entirely. Not slowed down. Stopped.

Here's what happened: every morning, she'd spent 90 minutes manually matching patient data across three separate systems—the EHR, the billing platform, and the practice management software. None of them talked to each other. So she built a 47-row spreadsheet that did. It was updated by hand each day, color-coded by location, and contained the only accurate record of which claims had been submitted, which were pending, and which had fallen through the cracks.

When she left, no one else knew it existed.

The Hidden Cost of Workarounds

When they finally found the spreadsheet on her shared drive, they had no documentation of her logic, no backup system, and three weeks of unreconciled claims worth roughly $14K in delayed reimbursement. The cost to replace her—recruiting, training, and lost productivity while the new person figured out the systems—ran another $22K.

This isn't unique to podiatry. In 2019, a Fortune 500 manufacturing plant discovered their $2M ERP system wasn't actually running the shop floor. A production scheduler had been doing it for 14 years on a hand-built Excel model. When she retired, the company realized the spreadsheet was the real operating system. Three weeks of halted production cost them $8.7M before they could rebuild her logic into the actual software.

The spreadsheet isn't a workaround. It's the actual integration layer—doing the job the software was supposed to do, and doing it for free as long as one person doesn't leave.

Why Your Systems Aren't Actually Connected

Most practices run 4-7 disconnected tools: EHR, scheduling, billing, credentialing, patient portal. Each vendor sells you the story that their system is the "hub." None of them actually built the integration layer that would make that true. They assume someone else will handle it. Or that you will.

A 3-location GI group had a similar setup: their office manager was manually pulling patient lists from the EHR, cross-referencing them against the scheduler, and flagging no-shows to the billing team because the scheduler and billing system weren't connected. She'd been doing this for seven years. When she took a two-week vacation, the practice lost track of 47 missed appointments and the associated revenue.

The vendors all promise integration. What they don't promise is that you'll have to fund it with staff time instead of software features.

What to Do This Week

Ask yourself: what would break if your office manager left tomorrow? Not what would be inconvenient. What would actually break?

Document those processes. Write them down. If a human is manually moving data between systems, you've found your spreadsheet. Map where patient information actually lives, where it needs to go, and who's moving it. You'll probably find three or four of these workflows.

When you're evaluating new software, ask vendors this question: "How does this system sync with our current billing/EHR/scheduler?" If they say "manually" or "we have an integration," ask for a live demo of that integration with your actual data. Watch them pull real information from your current system. If they can't do it in the demo, they can't do it in production.

The average cost to replace a practice manager is $18K to $25K in recruiting and training. Add lost productivity and billing delays, and you're looking at $36K to $57K per key staff departure. That's not a reason to keep someone in a job they've outgrown. It's a reason to stop relying on them to be your integration layer.

Before you add another software tool, map where your office manager's spreadsheets actually live—because they're probably solving a problem your vendors are charging you to ignore.