Maryland police employment records

Maryland’s certification file covers 15,777 officers who appear in its records between 1900-01-01 and 2025-11-18, across 167 agencies, in 41,206 employment records.

2025-11-18: coverage through
1900-01-01: earliest record
15,777: officers
167: agencies
41,206: 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 August 2022. The file holds records newer than the date its publisher states. Source: NPI published bucket. Retrieved 2026-08-29.

Reporting

The reporting on Maryland’s police records

The Daily Record · April 2026

Maryland court: public has a right to officer names in police use-of-force records

An appellate panel held that officer names in use-of-force reports are not exempt personnel records under the state public information act, and ordered a department to release them. The case was brought by The Washington Post and filed in January 2023. It is binding precedent unless appealed.

The Daily Record · April 2026

Montgomery County judge denies police union’s challenge to transparency law

A judge rejected a police union’s constitutional challenge to Anton’s Law, the 2021 statute requiring disclosure of most police disciplinary records, and separately struck down a county–union agreement imposing a 10-day delay before records reached the public.

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-11-18, with no separation recorded.
Records are state-scoped. Maryland 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.

← All states·Coverage table·Methodology

CaseParity is not a law firm and does not provide legal advice.