Why Spreadsheets Create Readiness Gaps

It usually comes up during an audit or a request for information. An auditor or FIOA request asks for documentation on a certification, training, equipment, or something similar, and leadership discovers that information is harder to find and gather than previously thought.

Or, even worse, that information is housed in spreadsheets and the cell is blank, or it says a date that’s clearly wrong, or the tab that was supposed to get updated after the last renewal cycle never was.

Maybe it’s an officer who never finished their in-service training and nobody caught it because the renewal date lived in a column that hadn’t been touched since the previous cycle. Maybe it’s a telecommunicator who completed a required training session, but the completion never made it from the sign-in sheet into the tracker, so it looks like it never happened. Or maybe it’s faulty equipment that never got logged or reported to maintenance and an injury occurs during an arrest. Unfortunately, none of these scenarios are out of the ordinary. They happen and when they do, they expose the agency and the employees to considerable risk and liability.

The reality is that even when everyone is doing their best, there are still situations in which manual tracking processes fail.

The person who normally updates that sheet was out for two weeks and the person filling in wasn’t aware of it. Or perhaps a new hire was added to one tab but never made it onto the other one that tracks recertification dates. The result is a gap that nobody meant to create, and nobody noticed until someone went looking for it.

This is what a readiness gap usually looks like in practice. Not a dramatic failure, not a crisis moment, just a quiet assumption that something was handled because if everything went according to plan 100% of the time, it would be. But, as anyone who works in public safety knows, the best-case scenario isn’t typically how things shake out in reality.

What Spreadsheets Are Actually Good At

It’s worth being fair to the spreadsheet here, because the criticism isn’t that spreadsheets are inherently bad. For a lot of agencies, especially smaller ones, they were the right tool for a long time. [As was IBM’s Lotus 1-2-3 prior to Microsoft’s Excel hit the market in the early 1980s.] They were cheap and flexible enough to track almost anything.

Plenty of well-run agencies started out on spreadsheets and continued with them for years because it was the easiest and best way at the time. However, times have changed and agencies are having to manage more, increase breadth of services they offer, and as a result, the complexity of the organization is increasing.

That’s when spreadsheets, which were never designed to catch gaps, start quietly missing them. The spreadsheet doesn’t get worse but the gap between what it’s being asked to do and what it was ever built to do just gets wider.

Where the Gap Typically Shows Up

The readiness gap that spreadsheets create doesn’t show up as one big failure. It tends to show up in a few specific, recurring ways:

• Updates depend on one person’s process. A spreadsheet only stays accurate if someone remembers to open it, find the right tab, and enter the right information at the right time. Vacation, illness, a busy week, or injury, and a myriad of other normal occurrences can interrupt the process and there’s nothing built into the spreadsheet itself that notices when an update didn’t happen.
• There’s no forward visibility into gaps. A spreadsheet can show you what’s true right now, if it’s current, but lacks the ability to warn you about what’s coming. Most agencies don’t find out about an expiring certification because the spreadsheet flagged it. They find out because someone happened to scroll to the right column, or because the expiration already happened and now it’s a compliance conversation instead of a routine renewal. The same is true for scheduling, equipment management, conduct tracking, and much more.
• Institutional knowledge walks out the door with a retirement or transfer. The person who’s been maintaining the spreadsheet for years usually knows the ins and outs of it, but when that person retires, transfers, or moves to a different role, that knowledge often goes with them, and whoever inherits the spreadsheet is left reconstructing logic that used to live in one person’s head.
• Spreadsheets silo information. When data is connected rather than siloed, public safety agencies gain a real-time, department-wide view of readiness. Command staff can instantly see which officers are qualified for specialized assignments, which certifications are approaching renewal, potential gaps in shift coverage, and much more. That visibility turns previously disconnected data points into a tool that supports informed decision making and increased operational readiness.

None of these three things are really about the spreadsheet failing. They’re about how much of the system’s reliability depends on a person remembering, noticing, and knowing things that were never written down anywhere a system could catch them. The risk those liabilities create sit quietly in the background for months, sometimes years, until an audit, a transfer, or an incident forces someone to go looking.

This Isn’t Really a Technology Problem

The point of tracking certifications, training hours, and coverage was never only the tracking itself. The bigger concern is making sure nothing falls through a crack that a system should have caught. Tracking is just the mechanism to achieve that goal, whereas reducing liability is the actual goal.

Seen that way, a missed update isn’t really a spreadsheet failure. It’s a moment where the system that was supposed to catch a gap didn’t, because it was relying on a person to catch it manually, and people are busy, human, and fallible in exactly the ways spreadsheets can’t compensate for.

This reframe matters because it changes what the fix looks like. If the problem is “our spreadsheet is outdated,” the fix is a new spreadsheet, or a slightly better version of the same underlying approach. If the problem is “we’re asking people to be the safety net for things a better system should catch,” the fix looks different and is more about creating a system that can be its own safety net.

Systems Should Carry the Part That’s Trackable

Beginning to fix the problem starts with recognizing which parts of readiness are genuinely trackable and letting a system carry that weight automatically, so the humans in the building have their attention free for the parts of the job that actually need judgment.

A spreadsheet asks a person to be the check, but a connected system built for this purpose does the remembering and noticing on its own, and flags what needs a person’s attention before it becomes a problem instead of after. That doesn’t remove people from the process, it just means the parts of readiness that can be tracked automatically are actually being tracked. As a result, the people responsible for readiness can spend their time on the parts that benefit most from their attention, like coaching a struggling recruit, having a hard conversation about performance, or making a judgment call a spreadsheet never could.

Instead of asking “who’s responsible for remembering to update this,” the question becomes “what’s the earliest point a system could have flagged this, and why didn’t it.” That question tends to point toward the actual gap much faster than reviewing someone’s individual diligence.

That’s the shift worth making this September. Not because spreadsheets are a moral failing, but because readiness shouldn’t depend on any one person’s memory holding up indefinitely.

Building Readiness That Doesn’t Depend on Memory

National Preparedness Month is a good moment to ask an honest question about your own agency. That question? If someone went looking today, the way an auditor might, would every certification, every training record, every equipment inspection, all conduct documentation, etc. hold up??

It’s worth sitting with that question for a minute rather than answering it too quickly. Most agencies, if pressed, would probably say their records are in decent shape. But “decent shape” and “would hold up to someone checking today, without warning, without a chance to go clean anything up first” are two very different standards. The gap between those two answers is usually exactly where a spreadsheet-dependent process starts to show its limits.

This is the first post in a series we’re running throughout September examining readiness at public safety agencies. Keep checking back to read more and discover other aspects of readiness that your agency may need to reconsider.

Vector Solutions has partnered with Frontline Public Safety Solutions to provide a suite of industry-leading software solutions including training management systems, online training courses, FTO and live skill evaluations, academy automation, asset and fleet management, shift scheduling, body-worn camera audits, community policing engagement, policy management, early intervention and professional standards, performance management, and accreditation management.