Turning Training Data Into Readiness Intelligence for Federal Agencies

Part one of this series, The Question Beyond Training Completion: Are They Actually Ready, made the case that completion isn’t the same as readiness. The natural next question leaders ask is: okay, so how do we get there?

That’s what Part 2 will dig into, relating back to a recent conversation between Sgt. Doug Kazensky (ret.) and Supervisory USBP Agent Jonas Edwards (ret.). Here’s what they covered.

The Data Isn’t Missing

Most organizations aren’t short on data. As Edwards put it from his DHS experience: data was never the problem. The hard part was knowing where it lived, if it was accurate, and how to get it back out.

That’s the operational gap in a nutshell. The data exists, but it’s scattered across systems that don’t communicate with each other. Nothing connects training to real readiness. Closing the gap before an incident forces the question is the whole point of building a connected system.

Where Does Your Data Sit? A Maturity Curve

Kazensky walked through a rough maturity curve most organizations recognize themselves in somewhere:

1. Ad hoc tracking: paper, binders, spreadsheets, maybe an old Access database. Works fine until it doesn’t: the moment a public disclosure request or an incident review forces you to prove what someone completed and when.
2. A centralized system of record: better than scattered spreadsheets, but it mostly tells you what happened, not what your current status is.
3. Connected data: training history, qualifications, and authorizations are packaged together into a picture, but pulling it out still isn’t easy or fast.
4. The decision layer: enough intelligence flowing into one place that when the moment of truth arrives, you already have the answer.

Neither Kazensky nor Edwards started at the top of that curve. Both talked about running training on paper and Excel earlier in their careers. The point isn’t to feel behind. It’s to know honestly where your agency sits today, because that determines the next step.

A Self-Assessment Before You Build Anything

Before investing in new tools or dashboards, Kazensky suggested asking a few honest questions about the system you already have:

• Can I see readiness in real time, or am I looking at a snapshot of what already happened?
• Can I drill into the data without submitting a request — a form to IT, a wait for someone else to pull a report?
• Is the information reaching the right role — the person who’s positioned to make the call — at the right time?
• Is the data secure and governed enough to trust? One bad data entry, one duplicate record, one ungoverned spreadsheet emailed to fifty people, and the credibility of the whole system is at risk.

That last point matters more than it might seem. Edwards described a federal agency whose graduation numbers never added up — it turned out two different naming conventions were causing the same students to get entered into multiple classes. The dashboard wasn’t wrong; the data feeding it was. A dashboard is only ever as good as what’s going into it.

[Callout Quote] A dashboard is only ever as good as what’s going into it.

Two Real Examples of the Gap in Action

Edwards offered two contrasting moments from his own career that make the stakes concrete:

• Early in his career: when agents were flexed from one Border Patrol station to another, their certifications traveled with them in a literal envelope. Supervisors were left trying to track down, confirm, or sometimes reconstruct paperwork by hand — slow, and hard to trust.
• During COVID: with a centralized system of record in place, the Border Patrol Academy redeployed over 300 instructors to northern border stations in under 48 hours — pulling certifications, issuing firearms and equipment, and confirming eligibility, all from one place. Edwards noted that with today’s automation and dashboards, that same task would likely take less than 24 hours now.

Same organization, same kind of decision — but a completely different speed and confidence level depending on where the data lived.

What “Insights in Practice” Looks Like

The second half of the session got specific about how this shows up day to day, using a couple of real dashboard examples:

• Annual law enforcement certification tracking — a quick view of how many people are certified, how many hold exemptions (injury, military leave, etc.), and how many still need to complete their annual requirement, all drillable down to the individual record.
• Fit testing for respiratory equipment — color-coded status (expired, expiring within 30–60 days, current for the next 180 days) so a manager fielding a last-minute request for 20 people can immediately see who’s truly eligible to deploy, not just who’s “trained.”

A helpful concept underneath both examples: a data lake — essentially a periodic snapshot of your system of record, queried separately from your live production data. It lets you run heavy reporting and dashboards without slowing down the people actively using the system day to day, and without changing the underlying data itself.

The Takeaway

• Tracking activity and supporting a real-time decision are two different jobs. Most systems were built for the first one.
• Fix your data before you build your dashboard. Clean, governed, consistently-named data is the actual foundation — the visualization is just the last step.
• Know your maturity level honestly, then take the next step up, rather than trying to leap straight to a fully connected system.
• Readiness is about knowing what you have and being able to produce it under a short turnaround — that’s true whether you’re in law enforcement, fire, EMS, or education.

The systems and dashboards are a means to an end. The real goal is the same one from Part 1: being able to answer, with confidence, whether your people are ready — right now, not after a records request.

This article is based on insights from Vector Solutions’ webinar, “When Training Completion Isn’t Enough: Turning Data Into Readiness Intelligence,” featuring Doug Kazensky and Jonas Edwards, presented as part of FGDLA’s Government Learning and Technology Symposium Series. [Watch the full recording here]([recording link]).