The Federal Vacuum and State-Specific Alternatives

If your officer-background research still starts with a federal police misconduct database, it's starting in a graveyard. The National Law Enforcement Accountability Database (NLEAD) was decommissioned in early 2025, and DOJ has confirmed no further reports will be published. Where you look now depends entirely on where your case is venued.

NLEAD launched on December 18, 2023 under Executive Order 14074 as a centralized repository of misconduct records, commendations, and awards. It produced exactly one BJS report, covering 2018 through 2023, before EO 14148 revoked its authorizing order on January 20, 2025. The Bureau of Justice Statistics now confirms that report is the last artifact you'll get from the federal government. The Prison Policy Initiative reads the shutdown as part of a deliberate pattern: the federal government is actively eliminating its own accountability initiatives.

That leaves state and local databases as your working tools, and several are genuinely mature. The catch is that they're siloed, so your first step is matching the database to your jurisdiction.

• California: PRAP. The Police Records Access Project holds roughly 1.5 million pages covering about 12,000 misconduct and use-of-force cases across nearly 700 agencies, searchable by officer name, agency, county, case type, and date. Its build team used generative AI to organize records, though searches return only literal text matches, per CalMatters reporting.
• New York City: LELU. The Legal Aid Society's Cop Accountability Project contains over 500,000 records and has been used in litigation against the NYPD.
• Louisiana: LLEAD. LLEAD pulls data from more than 600 law enforcement agencies and was originally built to help identify wrongful conviction cases.
• Multi-state checks: the National Police Index aggregates employment histories from POST and certification boards in 24 states, useful for spotting officers who moved states after trouble.

Two cautions before you take a hit into court. First, there's no national unique officer ID, so a name match proves nothing. The Invisible Institute's guidance is blunt: you can't assume someone with the same name and birth year is your officer. Verify through a POST employment records request before you assert a match. Second, treat database hits as leads for public records requests, not endpoints. Absence from a database is not absence of records.

And move fast when you find something. Access is contracting: Montana now restricts employment data and faces an April 2026 records lawsuit, Idaho decided in February 2026 to conceal records that had exposed misconduct, and Wisconsin's DOJ reversed a release decision in December 2025 after police-group pushback.

If you want a repeatable process for turning these hits into Brady and Giglio material, Evidence Copilot's Brady list research workflow walks through the jurisdiction-matched lookup, identity verification, and records-request steps in one place.

Navigating Identity Verification and 'Wandering Officer' Risks

Your client's arresting officer has the same name as an officer fired for misconduct in another state. Is it the same person? With no national unique officer ID, you cannot assume so, and a wrong match can sink a credibility attack at trial.

This is the core problem with any police misconduct database search in 2026: names and birth years are not identifiers. The Invisible Institute, which runs the National Police Index, is blunt about it: without a unique ID, one cannot assume someone with the same name or even birth year is the same officer. The Index aggregates employment histories from state POST and certification boards across 24 states, so it is the best available tool for spotting a "wandering officer" who moved jurisdictions after a termination or resignation. But a hit is a lead, not a match.

Verify before you impeach. The verification workflow is document-driven:

• Request the officer's employment record from the state POST board where the misconduct occurred.
• Request any record showing transfer from another state, which ties the two employment histories together.
• Compare dates of hire, separation, and certification status across both states before asserting the match in a Giglio motion.
• Preserve everything you obtain. Access is contracting: Montana now restricts employment data it once released, Idaho decided in February 2026 to conceal records that had exposed misconduct, and the Wisconsin DOJ reversed a release decision in December 2025.

That last point matters more than it used to. The Invisible Institute and The Pulp filed a public records lawsuit against the Montana POST Council in April 2026 over the new restrictions. Records you can pull today may not be pullable next year, so document what you have and when you got it.

Also treat database silence as inconclusive. These projects are built almost entirely from public records requests, and coverage is uneven by design. Six states (Illinois, Massachusetts, Minnesota, Ohio, Oregon, and Texas) release subsets through their own lookup tools, while the rest appear only through the Index. If your officer's name returns nothing, that is a gap in the data, not proof of a clean record.

Practically, identity verification work pairs well with the rest of your Brady research. When you're running a Brady list research workflow, keep a named-party record for each officer with aliases and every mention across your notes, so that when the POST records come back weeks later, you can connect the employment history to the specific bodycam footage and reports in the case without re-litigating who is who.

The wandering-officer problem is not going away. Until a national identifier exists, the attorneys who win credibility fights will be the ones who treat every database hit as the start of a records request, not the end of one.

From Database Hits to Impeachment Evidence

A database hit is a lead, not impeachment evidence. The record you found still has to be verified, pulled in full, and preserved before it can support a Brady or Giglio argument in court. That means treating every search result as the start of a public records workflow, not the end of your research.

Start with identity verification, because there is no national unique officer ID. The Invisible Institute, which runs the National Police Index covering 24 states, is blunt on this point: one cannot assume that someone with the same name, or even the same birth year, is the same officer. Before you use a cross-state hit, request the officer's employment record from the state POST and any record showing a transfer from another state.

Then verify the hit itself. California's Police Records Access Project, which holds roughly 1.5 million pages covering nearly 700 agencies, is explicit that its searches return only documents with a literal match to your search terms in the source text. A hit means the words matched. It does not mean the incident is what you think it is, and a miss does not mean the record does not exist.

Your workflow from hit to evidence:

• Confirm identity through POST employment records and any out-of-state transfer records before asserting the match.
• Draft a public records request to the originating agency for the complete underlying file, since public records requests remain the core collection method behind these databases.
• Preserve everything you obtain immediately, with the source URL and retrieval date documented.
• Compare the verified record against the officer's report and testimony in your case before drafting cross or a Giglio motion.

The preservation step is not optional anymore. Access to misconduct records is actively contracting: Montana now restricts officer employment data, prompting a records lawsuit in April 2026, while Idaho decided in February 2026 to conceal records that had exposed misconduct, and the Wisconsin DOJ reversed a release decision in December 2025 after police-group pushback. A document you can request today may be unavailable by the next hearing date. Save it now.

Once you have verified records in hand, the rest is ordinary case work: pairing the officer's file against the police report and bodycam in your discovery, and building the impeachment from both sides of the record. Evidence Copilot's Brady list research workflow handles the in-case half, keeping the officer's record, your discovery, and your notes connected with citations back to the exact source, so the database research and the evidence review live in one place.

Integrating Misconduct Data into Case Review Workflows

A misconduct hit is only as useful as your file discipline. If an impeachment gem surfaces three weeks before trial and sits in a folder nobody reopens, you've done the research for nothing. The fix is tying your police misconduct database research directly into case prep, so Brady and Giglio material moves through the same workflow as the bodycam, the 911 call, and the police report.

Start by verifying identity. There's no national unique officer ID, and the National Police Index is blunt about this: you can't assume someone with the same name or birth year is your officer. Request the officer's POST employment record and any transfer documentation before you assert a match in a Giglio motion. A wrong-officer impeachment attempt costs you credibility with the judge you'll see for the rest of your career.

Then jurisdiction-match your search. California cases run through PRAP, which covers nearly 700 agencies and about 12,000 misconduct and use-of-force cases, searchable by officer name, agency, county, and date. New York City has LELU's 500,000+ records. Louisiana has LLEAD across 600+ agencies. A hit is a lead, not a conclusion: follow it with a public records request, because absence from a database is not absence of records.

Your working file for each testifying officer should track:

• Identity verification: POST employment record, badge number, any out-of-state transfers
• Database hits with source, search date, and a saved copy of the underlying document
• Open records requests, dates filed, and responses received
• How each item maps to a specific witness, statement, or report language in your discovery

That last item is where most offices fall down. The misconduct record matters only when it connects to something in the case file, a prior inconsistent statement, a report-vs-bodycam discrepancy, a pattern of the same conduct at issue here.

Because access is contracting in several states, Idaho concealed records in February 2026, Montana now restricts officer employment data, and Wisconsin's DOJ reversed a release decision in December 2025, preserve everything you obtain the moment you obtain it. Document what you asked for and when. Records that were available at arraignment may not be available at trial.

A structured Brady list research workflow keeps this from becoming a stack of sticky notes: every officer hit gets logged, verified, tied to a witness, and flagged against your evidence inventory before preliminary hearing prep, not after. Discipline beats memory when you're carrying 40 open files.

The goal isn't more research. It's making sure no impeachment evidence goes unused because it lived in a different folder than the cross-exam draft. Barry Scheck has called public misconduct databases critical for every stakeholder in the system, including public defenders. Critical only counts if it reaches the courtroom.