Kansas’s certification file covers 15,125 officers who appear in its records between 1979-09-01 and 2025-01-13, across 454 agencies, in 24,740 employment records.
2025-01-13
coverage through
1979-09-01
earliest record
15,125
officers
454
agencies
24,740
employment records
latest separation date
coverage basis
The coverage date is computed from the file itself — the basis is the latest separation date. The publisher states December 2024. The file holds records newer than the date its publisher states. Source: NPI published bucket. Retrieved 2026-08-29.
More than a terabyte of documents taken in a 2024 ransomware attack contained a credibility-disclosure list naming 62 current and former officers, with allegations including dishonesty, harassment, excessive force and false arrest. Some remained employed. The department’s position is that such lists are confidential personnel records.
In Kansas the list became public only through a crime. That is the transparency baseline.
Decertification in Kansas does not bar corrections work, because jail and prison staff sit outside the certification system. About half of US states certify corrections officers; Kansas does not — so the state file misses where decertified officers actually go.
What this data does not say
It never asserts that anyone is currently employed. The supported statement is that a person is listed as employed at an agency as of 2025-01-13, with no separation recorded.
Records are state-scoped. Kansas certification numbers are issued by its own board, so someone certified in two states appears in two files and is never merged into one history.
Measured across the 26 published files as of 2026-08-29, 69,683 officer records are open at two or more agencies at once — a genuine dual appointment, or a separation the board never recorded. Counted per file, never across states. The data cannot tell the two apart, so neither is asserted.
Where this comes from, and how to correct it
This page presents what NPI published bucket made available, as it was released. Some files reach us directly from the reporting agency and some through intermediaries that obtained them under public-records law; either way the content is the agency’s, not ours. CaseParity does not investigate, verify, correct or vouch for any individual record, and takes no responsibility for the accuracy or completeness of what a reporting agency published.
A correction to the record itself is made by the certifying agency that issued it — that is the only route that changes it at the source, and therefore everywhere it appears, here included. If what this page shows does not match that agency’s file, write to hello@caseparity.com and say which record and which field. No response time is promised, and nothing here substitutes for going to the agency.