Law Enforcement Accountability Investigation
Legal & Rights

Law Enforcement Accountability Investigation

Skip to main content
Table of Contents
< All Topics
Print

Law Enforcement Accountability Investigation

Last updated: November 15, 2026

Instructions

You run an investigation into how a law-enforcement agency, or people acting for it, used its power: police departments, sheriff’s offices and jails, and the federal agents of immigration enforcement (ICE, CBP, Border Patrol). The output is a sourced working file and, when the editor asks, a draft in _drafts/. This skill never publishes.

MANDATORY GATE — step 1, before any research on a person. Rank-and-file officers and agents are not public officials in the inclusion gate’s sense. Naming one needs a non-speech anchor, like any private person. Every deputy, patrol officer, jailer, ICE officer, CBP officer or Border Patrol agent who is not an elected official or a Senate-confirmed appointee must pass patriot-private-citizen-inclusion-gate (Sections 1–2) before their name is researched, written down or published. A fail, or a result that is unclear, means the person is not named. The investigation of the agency, the policy and the pattern goes on without the name.

Use a different skill when:

  • the question is what a person’s rights are during a stop, a raid or detention: use fourth-amendment-legal-expert, immigration-know-your-rights-expert or immigration-detention-rights-expert;
  • the subject needs a durable, published accountability profile: use accountability-profile-builder (after this skill’s gate);
  • the task is a congressional-style investigation of an agency as a whole: use Citizen Analyst’s oversight-investigation method (scope, records requests, chronology, staff report);
  • the task is scoring damage to a federal institution: use agency-damage-assessment.

Ground every factual or legal claim through scripts/ca_research.py and cite it. Never state a legal status, a holding or a policy from memory. Never state a legal conclusion yourself (that force was excessive, that an officer is immune, that a death was preventable): state what a court, prosecutor, medical examiner or oversight body found, with its record.


1. Classify every officer and agent: the gate

Who Classification (gate Section 1) What it takes to name them
Elected sheriff, sitting or former Public official Proceed: conduct in office is in scope
Senate-confirmed head of an agency, sitting or former Public official Proceed
Appointed chief, field-office director, acting head not Senate-confirmed Not an official in the gate’s sense Gate. Usually Anchor E or D
Deputy, patrol officer, jailer, ICE or CBP officer, Border Patrol agent, a local officer deputized under 287(g) Private person for this test Gate. Usually Anchor A or E

How the anchors usually apply here:

  • Anchor A (criminal charge or conviction): the charging document or judgment, with the court, docket and date.
  • Anchor E (use of an official non-elected position): the anchor is the documented conduct, not the badge. It needs an official record, a court finding, congressional testimony, or Tier 2 journalism documenting that the officer used the position to do the thing at issue. Holding the job is not the anchor.
  • Anchor D (voluntary public figure): an officer who gave interviews or held press conferences about their own role in the incident.
  • A civil lawsuit naming the officer is an allegation. The gate treats a civil action as a weaker form of Anchor A: document it carefully and separately, and never let it stand alone.

When in doubt, classify at the more protective level. On a fail: write not named: gate with the role, and keep the role in the story (“a deputy”, “a Border Patrol agent”). An agent a court filing calls “John Doe” stays unnamed until the record names them.

Never identify a masked or unnamed officer or agent by face search, reverse-image search, a people-search site or a data broker. Identity comes from the record: a court filing, an agency release, an official roster. osint-identity-researcher applies the same gate first.


2. Which legal regime applies: route, do not conclude

Who the officer works for, and under what authority they acted, decides which law and which record matter. Hand the analysis to the legal skill named; this table only tells you where to send it.

Situation What governs (sourced below) Route to
Force during a stop or arrest The Fourth Amendment’s objective-reasonableness test from the perspective of a reasonable officer at the scene (Graham v. Connor, 1989), over the totality of the circumstances (Barnes v. Felix, 2025); deadly force on a fleeing suspect (Tennessee v. Garner, 1985) fourth-amendment-legal-expert
A state or local officer is sued 42 U.S.C. § 1983 lets individuals sue state officials; qualified immunity shields conduct that does not violate clearly established rights (Harlow v. Fitzgerald, 1982); courts may take its two questions in either order (Pearson v. Callahan, 2009) fourth-amendment-legal-expert
A local officer acting under a 287(g) agreement 8 U.S.C. § 1357(g)(8): treated as acting under color of federal authority for liability and immunity from suit; § 1357(g)(7): a federal employee for Federal Tort Claims Act purposes. So the federal-officer row below may be the one that applies fourth-amendment-legal-expert, immigration-detention-rights-expert
A federal agent (ICE, CBP, Border Patrol) No statute lets individuals sue federal officers as § 1983 does for state officers. The Bivens damages remedy is now confined: no Bivens claim for a Border Patrol agent’s alleged excessive force (Egbert v. Boule, 2022), nor an Eighth Amendment excessive-force claim against federal prison officials (Goldey v. Fields, 2025). The usual route is an FTCA claim against the United States; its law-enforcement proviso in 28 U.S.C. § 2680(h) modifies only the intentional-tort exception (Martin v. United States, 2025) fourth-amendment-legal-expert
Force or conditions in a jail or detention centre For pretrial detainees, force is judged by an objective standard under the Fourteenth Amendment (Kingsley v. Hendrickson, 2015). Immigration detention is federal and civil, not criminal punishment; how force and conditions claims are analysed there is in the two skills on the right eighth-amendment-legal-expert, immigration-detention-rights-expert
A workplace raid Worksite enforcement law and workers’ rights immigration-workplace-enforcement-expert
A department-wide pattern The Justice Department announced on 21 May 2025 that it would dismiss the Louisville and Minneapolis consent-decree suits and close those investigations. Check the Special Litigation Section’s case page for any agency’s current status; never assume a decree or investigation is still in force government-oversight-mechanisms

What a reporter can say from this table: which forum and which record to look for. What a reporter cannot say from it: that a claim would win or lose.


3. The records: where each fact lives

Every source is either a record (the holder of the fact speaking) or a lead (a compilation, a score, a tip). A lead tells you where to look; only a record is cited for the fact.

Source What it is Record or lead How to use it
ICE 287(g) participating agencies ICE’s own roster of signed 287(g) Memoranda of Agreement, one row per agreement, under three models: Jail Enforcement (JEM), Warrant Service Officer (WSO), Task Force (TFM) Record, as of the file’s date scripts/ca_research.py api api.ice_287g ", " --agent . Offline: a human downloads the spreadsheet from ice.gov and saves it as ice_287g_.xlsx; the client says so when it is missing. Put the state in the subject: two agencies with one name in two states are refused, never guessed. The signed date is the agreement’s date, not the day officers began using the authority
Local votes and contracts City-council and county-board matters, agendas and votes on 287(g), sheriff contracts and jail budgets Record (the clerk’s text) scripts/ca_research.py api api.legistar "287(g)" --extra client= --agent , where is the first label of the city’s .legistar.com address. As of 2026-11-13 the CLI refuses --extra client=… (the key is not in its allowed list), so until that is fixed search the city’s site instead: scripts/ca_research.py search "287(g) sheriff" --domains .legistar.com --agent . A matter’s title is the clerk’s text, not a finding of what a measure does
Deportation Data Project 287(g) dataset (released 16 Oct 2026) 3,153 agreements signed from 2 July 2002 on, active and historical, with the jurisdictions where deputized officers may act Lead for history; cross-check every current agreement against ICE’s list Scope, not arrests: an agreement says what officers may do, not what they did. scripts/ca_research.py api api.deportation_data ", " --extra dataset=287g --agent (Section 3.1). A human downloads the file; never script around a bot challenge
TFM money ICE’s 287(g) brochure lists possible Task Force Model reimbursement: $7,500 for equipment per trained officer, $100,000 for vehicles per agreement, salary and benefits per trained officer, overtime up to 25% of salary Record of the offer, not of payment Follow it to the county’s budget, the board vote and the payment record before saying an agency was paid
Police Scorecard (policescorecard.org) Scores policing outcomes for over 16,000 municipal and county agencies Lead. A derived score Point readers to the website; cite the underlying agency or state data for any fact. There is no CA client: its API is not open for this use
National Police Index (Invisible Institute) Officer employment histories from state POST certification boards, 24 states at last read Lead for identity, record of what the state released Only after the gate passes. Names are common: one name in two states is not one officer. Confirm with the state POST board’s own record. Some states assert a statutory bar on releasing this data
ICE detainee death reports (ice.gov) Congress requires ICE to make in-custody death reports public within 90 days (FY2018 on) Record of deaths in custody ICE Directive 11003.7 (2 June 2026) dropped reporting of deaths within 30 days of release. A death after release will not be on the page; its absence proves nothing
CBP Assault and Use of Force Statistics CBP operations only; off-duty incidents excluded; earlier figures are revised after internal review and National Use of Force Review Board decisions Record, as of its edition Say which edition a figure comes from; never set it beside a figure from an earlier edition as if both were current
DHS civil-rights oversight DHS ran a reduction in force at the Office for Civil Rights and Civil Liberties and the Office of the Immigration Detention Ombudsman from 21 March 2025; GAO examined the RIFs under the Impoundment Control Act (B-337366) Record of the change No CRCL or OIDO finding is not evidence that nothing happened. Report the oversight gap as its own fact
NLEAD (federal misconduct database) Created under EO 14074 (2022); EO 14148 revoked that order on 20 Jan 2025 and the Justice Department decommissioned the database — Not a current source. Do not cite it as if it can be checked
Court records Complaints, dockets, opinions, settlements Record of what was alleged, ordered or agreed scripts/ca_research.py cl search "" --agent (CourtListener, metered). A complaint is an allegation; a settlement is not a finding of fault; a dismissal on immunity is not a finding that nothing happened
Complaint, use-of-force, internal-affairs and body-camera records The agency’s own files Record By records request: public-records-research-specialist, foia-and-sunshine-laws, and a drafted request that a human files. When an agency publishes a simple chart of misconduct data, assume a detailed database sits behind it and request that
Scanner audio (Broadcastify, OpenMHz) Live and archived police radio Lead only, human listening Never publish names, plates or addresses heard on air, and never the location or timing of a live enforcement operation. Silence on an open channel proves nothing

When agencies or institutions publish their own lists (disclosure lists, decertifications, rosters), keep each list as it was published, with its own date and its own criteria, before you merge them. That is how ProPublica built its database of clergy deemed credibly accused: nearly 180 published lists, kept as released, combined into one searchable set.

3.1 Dataset loaders: cited inputs

Three loaders read a dataset and return findings. None fetches anything. A person downloads the file in a browser (two of the three hosts answer a script with a bot challenge) and saves it under a dated name in $CA_OSINT_DATASET_DIR, or ~/.cache/citizen-analyst/osint-api/datasets/ when that is unset. The date in the file name is the version stamp. A file saved without it is refused, so every figure says which release it came from. Where there are several, the newest date wins.

Cite the dataset and its date, never the tool. Write “ICE, 287(g) participating agencies, as of 12 Nov 2026”, not “api.ice_287g”. The loader is how you read the data; the dataset is the source.

api.ice_287g: ICE’s 287(g) participating agencies. Record.

  • Answers: which state and local agencies hold a 287(g) agreement today, under which model (JEM, WSO, TFM), and when each agreement was signed.
  • Run: scripts/ca_research.py api api.ice_287g ", " --agent , or name the state with --extra state=.
  • File: the “View 287(g) Participating Agencies” spreadsheet at https://www.ice.gov/identify-and-arrest/287g, saved as ice_287g_.xlsx with the date from the page’s “As of” sentence.
  • Caveats: one agency can hold several agreements, and each is its own finding. A signed date is the agreement’s date, not the day officers began using the authority. A spreadsheet whose header changed is refused rather than read.
  • Cite: ICE, with the as-of date. ICE asks that “appropriate byline/photo/image credit is given to ICE”.

api.deportation_data: Deportation Data Project (DDP). A compilation of ICE’s records. It is a lead for current agreements, which you confirm on ICE’s list. It is the source for history and counts that ICE does not publish itself.

  • Answers: pick the table with --extra dataset=.
  • 287g: every agreement since 2002, active and ended, with the jurisdictions where deputized officers may act.
  • facilities: detention facilities, with average daily population over the latest 365 days of ICE data.
  • arrests, detainers, detentions, removals: ICE’s FOIA releases, folded into counts per state (per ICE area of responsibility for removals). No individual row is ever listed.
  • Run: scripts/ca_research.py api api.deportation_data "" --extra dataset=
    --agent . Add --extra state= when a name exists in several states. For removals, name the area of responsibility in the subject. Without dataset, every DDP file present answers.
  • File: downloaded in a browser from https://deportationdata.org/data/ice.html (the four core tables) or https://deportationdata.org/data/processed/ice.html (287(g), facilities), saved as ddp_
  • _.xlsx (.csv, or a .zip holding one CSV, also work).
  • Caveats: every finding carries the project’s own caveats, quoted, and its snippet leads with the one that changes a reader’s conclusion.
  • 287(g) records scope, not arrests.
  • The core tables cover ICE Enforcement and Removal Operations only.
  • Arrest rows are arrests, not people.
  • A detainer is a request, not proof that a jail complied.
  • A detention row is one stint at one facility, and one person can have several.
  • The project reports that removals-data problems “reappeared in the October 2025, March 2026, and August 2026 releases”.
  • The full card is data-diary-and-reproducibility §6.1.
  • Cite: the data are CC0. Use the project’s wording with the release date: “government data provided by ICE in response to a FOIA request to the Deportation Data Project and analyzed by [your organization]” for the core tables, or “government data published by ICE, collated by the Deportation Data Project, and analyzed by [your organization]” for 287(g) and facilities.
  • api.mapping_police_violence: Mapping Police Violence (MPV), Campaign Zero. Lead.

    • Answers: fatal police encounters, matched by agency, city or county. Each answer gives a count, the span, the commonest uses of force and up to four recent incidents by MPV id.
    • Run: scripts/ca_research.py api api.mapping_police_violence "" --extra state= --agent . An agency with incidents in several states, such as a federal agency, is refused until you name one state.
    • File: open https://mappingpoliceviolence.org/methodology in a browser, follow “View the data”, choose “…” and then “Download CSV”. Save it as mpv_.csv with the date from the page’s “Data last updated” line.
    • Caveats:
    • It counts deaths, not misconduct findings.
    • On 13 July 2026 MPV recoded its fields (use_of_force, allegedly_armed_with, threat_perception, call_for_service, incident_footage). A file with the old header is refused, and a field coded before July 2026 does not compare like for like with one coded after.
    • MPV states no formal licence. It states an intent (“should be public and free to access”) and asks to be cited. An editor confirms reuse before publication.
    • No victim or officer name is read from the file. Identify an incident by its MPV id, date, place and agency, and gate anyone you would name (Section 1).
    • Cite: “Mapping Police Violence,” Campaign Zero, [date accessed], https://mappingpoliceviolence.org/, for the pattern. For each fact about an incident, cite the record it points to: a medical examiner, a court, an agency release or an ICE death report.

    Not inputs. Vera Incarceration Trends and the National Police Index have no loader and are not cited as inputs. Under the 14 Nov 2026 licence ruling, Vera’s licence allows only academic, nonprofit and research use, and the National Police Index publishes no terms for its data. The Section 3 row for the National Police Index stays a lead: it says where to look, and the state POST board’s record is what you cite.


    4. The investigation, in order

    1. Gate (Section 1) for every person who might be named. Record the result before any search on that person.
    2. Scope the system, not only the officer. Look for systemic failures and policy choices rather than only the “bad apple” officer. Investigate the investigators: is internal affairs measured by outcomes or by the number of cases closed?
    3. Authority. For any immigration-enforcement question, establish what the local agency is authorised to do: api.ice_287g for the agreement, the local vote (Section 3), then the MOA text ICE links.
    4. Incident reconstruction. Build a timeline from records: 911 and dispatch timestamps against video, CCTV from businesses near the scene, and witness video located in time and place. Verify every clip with media-verification-specialist and geolocation-verification-specialist before it carries weight.
    5. Records. Request complaint, use-of-force, internal-affairs and body-camera records; pull dockets; log what each record says against what was alleged.
    6. People. Only for those who passed the gate: employment history (National Police Index, then the state POST board), prior suits, discipline.
    7. Law. Route each legal question by Section 2. Write what the record shows and what a body found, never a verdict of your own.
    8. Reply. Put every finding about an agency or a named person to them before publication, and report the answer or the refusal.

    Sources

    Read through scripts/ca_research.py on 2026-11-13.

    • ICE, “Delegation of Immigration Authority Section 287(g)”, https://www.ice.gov/identify-and-arrest/287g (the three models); ICE 287(g) brochure, https://www.ice.gov/doclib/about/offices/ero/287g/287gBrochure.pdf (TFM reimbursement).
    • 8 U.S.C. § 1357(g)(7)–(8), https://uscode.house.gov/us/usc/t8/s1357.
    • Deportation Data Project, “New dataset: ICE 287(g) agreements and jurisdictions”, 16 Oct 2026, https://deportationdata.org/news/2026-10-16-287g-release.html.
    • Graham v. Connor, 490 U.S. 386 (1989); Tennessee v. Garner, 471 U.S. 1 (1985); Barnes v. Felix, 605 U.S. ___ (2025), https://supreme.justia.com/cases/federal/us/605/23-1239.
    • Harlow v. Fitzgerald, 457 U.S. 800 (1982); Pearson v. Callahan, 555 U.S. 223 (2009), https://supreme.justia.com/cases/federal/us/555/223.
    • Constitution Annotated, essay on Barnes v. Felix (42 U.S.C. § 1983 and Bivens), https://constitution.congress.gov/browse/essay/intro.9-3-9/ALDE_00000151.
    • Egbert v. Boule, 596 U.S. 482 (2022), https://www.supremecourt.gov/opinions/21pdf/21-147_g31h.pdf; Goldey v. Fields (per curiam, 30 June 2025), https://www.supremecourt.gov/opinions/24pdf/24-809_9o6b.pdf.
    • Martin v. United States, 605 U.S. 395 (2025), https://www.supremecourt.gov/opinions/24pdf/24-362_mjn0.pdf.
    • Kingsley v. Hendrickson, 576 U.S. 389 (2015), https://supreme.justia.com/cases/federal/us/576/389.
    • U.S. Department of Justice, Office of Public Affairs, dismissal of the Louisville and Minneapolis police investigations and proposed consent decrees, https://www.justice.gov/opa/pr/us-department-justices-civil-rights-division-dismisses-biden-era-police-investigations-and; NPR, 21 May 2025; Special Litigation Section case summaries, https://www.justice.gov/crt/special-litigation-section-case-summaries.
    • Police Scorecard, About, https://policescorecard.org/about.
    • Invisible Institute, National Police Index, https://invisible.institute/national-police-index.
    • ICE, Detainee Death Reporting, https://www.ice.gov/detain/detainee-death-reporting; Immigration Policy Tracking Project on ICE Directive 11003.7, https://immpolicytracking.org/policies/ice-policy-on-detainee-deaths-under-trump-20.
    • CBP, Assault and Use of Force Statistics, https://www.cbp.gov/newsroom/stats/assaults-use-force.
    • CBS News, “DHS gutting offices that offer civil rights and immigration liaison services”, 21 Mar 2025; GAO, B-337366, https://www.gao.gov/products/b-337366.
    • Bureau of Justice Statistics, National Law Enforcement Accountability Database, https://bjs.ojp.gov/national-law-enforcement-accountability-database; CRS Insight IN12515.
    • GIJN, “10 Tips for Investigating Police Misconduct” (Rowan Philp, 2 Nov 2020), https://gijn.org/stories/10-tips-for-investigating-police-misconduct.
    • Section 3.1 (the loaders, added 14 Nov 2026): the loaders’ own source notes in scripts/lib/osint_api/{ice_287g,deportation_data,mapping_police_violence}.py, which quote the pages read on 2026-11-13. ICE site policies, https://www.ice.gov/site-policies (“Copyright”). Deportation Data Project FAQ, https://deportationdata.org/docs/ice.html#faq, and processed-data page, https://deportationdata.org/data/processed/ice.html, read through Internet Archive snapshots because the site challenges scripts. Mapping Police Violence, methodology, https://mappingpoliceviolence.org/methodology, read through the Internet Archive’s 2026-10-23 snapshot.
    • ProPublica, “We Assembled the Only Nationwide Database of Priests Deemed Credibly Accused of Abuse. Here’s How.”, https://www.propublica.org/article/we-assembled-the-only-nationwide-database-of-priests-deemed-credibly-accused-of-abuse-heres-how.

    Cross-references

    • patriot-private-citizen-inclusion-gate: step 1, the classification and the Non-Speech Anchor Test.
    • fourth-amendment-legal-expert: stops, arrests, force, warrants, § 1983, Bivens and the FTCA.
    • eighth-amendment-legal-expert: jail and detention conditions, force on people in custody.
    • immigration-detention-rights-expert: immigration detention, deaths and conditions in ICE custody.
    • immigration-workplace-enforcement-expert: worksite raids.
    • public-records-research-specialist, foia-and-sunshine-laws (requests are drafted for a human to file): complaint, force, internal-affairs and body-camera records.
    • media-verification-specialist, geolocation-verification-specialist: video and image evidence.
    • data-diary-and-reproducibility: the caveat card and number trace for any figure taken from the Section 3.1 loaders.
    • osint-identity-researcher: people research, after the gate.
    • accountability-profile-builder: a published profile, after the gate.

    Safety

    • The gate is mandatory. No officer or agent who fails it, or is unclear on it, is named, not even in a draft.
    • No unmasking. Never identify a masked or unnamed officer or agent through face search, a people-search site or a data broker.
    • No doxxing. No home addresses, family members or personal contact details of any officer, agent, victim or witness.
    • Live operations. Never publish the location or timing of an enforcement operation in progress.
    • Allegation, finding, charge, settlement. Say which one every fact is, every time.
    • Leads are not records. A score, a compiled list or a scanner transmission points to the record; it is never cited for the fact.
    • Not legal advice. Route legal questions to the legal skills and, for a person’s own situation, to counsel.
    • Symmetry. The same sourcing standard applies to an agency’s account and to a complainant’s.
    Was this article helpful?
    0 out of 5 stars
    5 Stars 0%
    4 Stars 0%
    3 Stars 0%
    2 Stars 0%
    1 Stars 0%
5
Please Share Your Feedback
How Can We Improve This Article?