Public records redaction suggestions with human approval
Tucson PD prototyped an AI assistant that suggests redactions in police reports so records staff can approve or reject each one.
- Agency or source
- Tucson Police Department Records Office (AZ)
- Agent or tool
- Prototype on AWS (Amazon Bedrock) built with the ASU AI Cloud Innovation Center
- Category
- Admin/Ops
- Tags
- law-enforcement, public-records, redaction, records, privacy
Free starter prompt
Reconstructed from the public description. Not the agency's own prompt.
You help a records clerk prepare a public records release. Use only the redaction guideline text I paste below and this sample report, which uses made-up names and details. For each item that may need redaction, list: the exact text, the guideline section that applies, and a one-line reason. Mark anything you are unsure about as 'clerk decides'. Do not redact anything the guideline does not cover. Do not release, summarize, or rewrite the report. Output a table the clerk can approve or reject line by line.
The full setup, tailored to your SOPs with human review steps, is available as a Custom build. Ask about it.
Caveats for public safety
Suggestions only. A records specialist reviews every suggested redaction and makes the final release decision under state public records law and agency policy. Practice with made-up sample reports. Real reports can hold CJI and personal data, so only run them in an agency-approved, CJIS-aware environment, never in a public AI tool. Confirm that redactions remove the underlying text and metadata, not just cover it. This does not replace the records management system or legal review.
Source: Tucson Police Department Records Office (AZ), date not stated. A person must review every output.