Bill
HB 754
Requires the Department of Public Safety to create and maintain a central, publicly accessible database of officer misconduct records to boost transparency and public oversight.
Status and procedural timeline
- Title: "Trust in Law Enforcement Act"
- Introduced: November 12, 2024
- Committee status: Died in Committee (did not advance)
- Classification/Subjects: Bill; Appropriations A, Judiciary B
Purpose and intent
- The bill’s stated purpose was to increase public transparency and accountability for law enforcement by requiring the Department of Public Safety (DPS) to create and maintain a publicly accessible database documenting officer misconduct-related records.
What the bill would require (core requirement)
- Establishment of a centralized, public database maintained by the Department of Public Safety that contains information about law enforcement officer misconduct.
- The database requirement is the principal, explicit obligation described in the bill title and bill summary information provided.
Important caveats about available materials
- The documents supplied with this request include multiple, unrelated legislative texts and fiscal notes from different jurisdictions and topics (e.g., Harford County alcoholic beverage notices, an internal auditor provision for a Georgia school board, and unrelated bills from other states). No complete bill text for HB 754 (the "Trust in Law Enforcement Act") was included.
- Because the full bill language was not provided, specific statutory definitions, the exact data elements required, exemptions, timelines for reporting, data-retention rules, privacy protections, funding/appropriation provisions, enforcement mechanisms, or appeal procedures could not be confirmed.
Likely key provisions typically found in bills of this type (items to look for in the bill text)
- Definitions (e.g., what constitutes “misconduct” and which categories of officers are covered).
- Specific records to be posted (allegations, internal investigation findings, sustained complaints, disciplinary actions, resignations/terminations, use-of-force incidents).
- Timeframes for reporting and posting; procedures for updating or removing records.
- Privacy, confidentiality, and redaction rules (e.g., for ongoing investigations, minors, or protected personal information).
- Appeal, correction, or challenge processes for officers.
- Data format and public-access standards (searchable, machine-readable).
- Funding or appropriation language and whether the DPS must allocate staff/resources to build and maintain the system.
- Penalties or remedies for noncompliance by agencies.
Who would be affected
- Department of Public Safety: primary administrative responsibility to create/maintain the database.
- State and local law enforcement agencies: required to report records, cooperate with DPS, and update information.
- Current and former law enforcement officers: their personnel and disciplinary records (to the extent defined by the bill) could be published.
- General public, journalists, civil-rights organizations, and defense counsel: would gain access to consolidated misconduct information.
- Legal system and unions: possible increase in litigation or collective-bargaining issues related to privacy and disciplinary record disclosure.
Potential impacts and considerations
- Transparency: central public database could improve public oversight and policy research by making misconduct records readily accessible.
- Privacy and due process: publication of allegations before full investigation or in absence of sustainable findings can raise legal and fairness concerns; the bill’s specific handling of these issues would be determinative.
- Operational and fiscal: creating and maintaining a secure, searchable database may require staffing, IT resources, and ongoing appropriations. The Appropriations subject classification suggests fiscal implications were considered; however, no fiscal note for this specific bill text was provided.
- Legal challenges: disclosure of personnel records may prompt legal challenges under state public records laws, privacy statutes, collective bargaining agreements, or employment law.
Next steps / recommended documents to review
- Obtain the bill’s full statutory text and any committee substitute to confirm definitions, required data fields, timelines, exemptions, and enforcement mechanisms.
- Review the bill’s fiscal note and any DPS impact analysis for implementation costs.
- Review committee reports and hearing testimony to understand stakeholder positions (law enforcement agencies, unions, civil-rights groups).
- If reintroduced, monitor amendments that address privacy, redaction, reporting timelines, or funding.
If you want, I can:
- Draft a concise “plain-language” one-page explainer based on the bill text if you can provide it, or
- Produce a checklist of specific language and policy trade-offs to look for when reviewing the bill’s full text.
Compiled from official sources — confirm details with the bill’s official record.
Sign in to ask a question.
