What Your Credentialing Spreadsheet Won't Catch (Until It's Too Late)

If you're tracking RBT credentialing on a spreadsheet, it probably looks fine right now. Names down the side, dates across the top, maybe some color coding for what's coming due. It looks like a system. And for a while, it works, right up until it doesn't, and by the time it doesn't, you usually don't find out from the spreadsheet. You find out when someone's certification has already lapsed.

That's not a knock on whoever built it or whoever maintains it. Spreadsheets are good at holding numbers still. They're bad at the parts of credentialing tracking that actually matter, which is noticing when something changes and telling somebody. Here's where that gap actually shows up.

The “which version is current” problem

Somebody downloads a copy to work on it during a slow afternoon. Somebody else has it open in an email attachment from three weeks ago because that's what was in front of them when they needed to check a date. A third copy lives in a shared drive folder that autosaves, except the person checking it on their phone is looking at a cached version from yesterday.

None of this is anyone being careless. It's just what happens to a file that has to be accessed by more than one person, on more than one device, over more than a few months. The live version and the version someone's actually looking at drift apart quietly, and there's no alert that tells you they've drifted. You just find out the hard way, usually when two people are confidently looking at two different answers to the same question.

The gap that opens the moment nobody remembers to close it

A new RBT gets hired. Somebody adds their name to the sheet, hopefully the same week, hopefully with the right hire date. A technician's supervision arrangement changes mid-cycle. Somebody updates their row, if they remember to, and if they know updating that row was even their job.

A spreadsheet has no forcing function for any of this. It doesn't know a new hire exists until a person tells it. It doesn't flag a missing row the way it would flag a typo. The gap between “this happened” and “this got recorded” is invisible right up until the moment it matters, which in this case usually means someone's credential status was never being tracked at all, and nobody knew that until they went looking for it.

Manual date math, done by hand, over and over

The current RBT recertification cycle runs two years, with a supervision-hour requirement that has to hit a minimum 5% threshold and be documented, not just completed. That's two different kinds of math running at once for every RBT on staff. One is a countdown. The other is a running percentage that has to be recalculated as new supervision hours come in.

Do that by hand, across a full roster, across months, and you're going to be right almost every time. Almost every time is the problem. A renewal date that's off by a few weeks, or a supervision percentage that's slightly stale because it wasn't recalculated after the last update, sits there quietly looking correct until the exact moment it's checked against reality. Small arithmetic slips don't announce themselves. They just wait.

No real record of when something actually happened

Say a technician completes a CEU course, but the proof doesn't get logged into the sheet until three weeks later, because that's when someone got around to it. The spreadsheet doesn't know that. It just shows the CEU as logged, with no distinction between “logged the day it happened” and “logged whenever someone remembered to enter it.”

Most of the time that doesn't matter. But if a credential ever gets questioned, whether internally or by someone outside the clinic, “when did we actually know this” is a real question, and a plain spreadsheet usually can't answer it. There's no audit trail built in. There's just the current state of the cells, with no memory of how or when they got that way.

None of this is a discipline problem

Every clinic running this on a spreadsheet has people who care and are trying to keep it accurate. That's not what's failing. What's failing is asking a tool with no memory of its own and no alerting to do a job that's fundamentally about noticing things and following up on them. A spreadsheet holds data. It doesn't watch it.

That's the actual gap automation closes here, and it's a narrower fix than it might sound like. It's not about replacing the tracking or handing your credentialing over to some black box. It's making the tracking self-checking: expiration dates that raise a flag before they matter instead of after, new hires and mid-cycle changes that get caught instead of assumed, supervision-hour math that recalculates itself instead of waiting for someone to redo it by hand, and a real record of when something was actually logged instead of just what it currently says. Here's what that actually looks like.

Where this fits

If any of that sounded familiar, that's exactly the kind of gap we map out in the first call. Not a sales pitch, just a straight look at where your current tracking is quietly exposed and what's realistically fixable given where you're standing today.

Tell us about your practice and we'll walk through it together.