
Crime Incident Report Standardization
Extract & standardize crime incident data into UCR-compliant reports
What You Can Do
Convert raw incident descriptions into standardized administrative crime reports that meet state UCR requirements and federal database specifications. Claude extracts key data elements (offense type, location, victim/suspect details, circumstances), validates them against coding standards, flags missing or inconsistent information, and generates audit documentation showing all standardization decisions. This eliminates manual reformatting, reduces data entry errors, and accelerates report processing while maintaining compliance documentation.
Features
Extracts critical data elements (offense codes, locations, dates, parties involved) from unstructured incident descriptions
Cross-checks extracted data against Uniform Crime Reporting standards to ensure coding accuracy and completeness
Automatically populates standardized report templates with extracted and validated information
Identifies missing required fields, inconsistencies, or ambiguous narratives that need human review
Documents all extraction decisions and standardization actions for compliance and quality assurance
Adapts standardization rules to state-specific UCR requirements and departmental formatting standards
Handles multiple incident reports sequentially with consistent output formatting
Example Output
Input Narrative: "Officer responded to 423 Oak St around 11:30pm. Store owner reported merchandise missing from shelves estimated $2,400 value. No signs of forced entry. Suspect described as male, black jacket, fled scene before arrival."
Generated Standardized Report:
- Offense Code: 23D (Shoplifting)
- Location: 423 Oak Street, Precinct 4
- Date/Time: [Current Date] 23:30 hours
- Property Value: $2,400
- Suspect Description: Male, wearing black jacket, fled on foot
- Entry Method: Unknown/No forced entry observed
- UCR Compliance Status: ✓ Complete (all required fields populated)
- Audit Note: Offense code inferred from merchandise loss + no forced entry; recommend officer clarification on suspect direction of flight
Input Narrative: "Hit and run on Maple Ave near intersection with 5th. Blue sedan, license partial JKL. Victim transported to Metro Hospital. Witness says vehicle heading east."
Generated Standardized Report:
- Offense Code: 26A (Hit and Run - Injury)
- Location: Maple Ave & 5th Street, Precinct 2
- Vehicle Description: Blue sedan, partial plate JKL***
- Victim Status: Transport to Metro Hospital (injury reported)
- Direction of Flight: Eastbound
- UCR Compliance Status: ⚠ Incomplete (victim identity missing, hospital info pending)
- Audit Note: Requires follow-up on victim name/age for UCR demographic field; partial plate flagged for BOLO circulation
What's Included
- SKILL.md instruction file with complete standardization framework:
- UCR coding reference: Standard offense codes and required field mappings
- Report template: Standardized incident report structure (markdown/JSON formats)
- Data extraction checklist: Critical elements to identify in narratives
- Audit trail template: Documentation format for compliance records
Who It's For
- Crime analysts — Administrative professionals standardizing incident reports for state/federal submissions
- Records management specialists — Converting legacy case files into compliant electronic formats
- Police administrative staff — Processing incoming patrol officer narratives into standardized formats
- Compliance officers — Preparing crime statistics submissions and audit documentation
- Multi-precinct supervisors — Harmonizing reporting formats across jurisdictions
Best For
- Processing incoming incident reports with narrative-only submissions from patrol officers
- Converting legacy case files into standardized UCR-compliant electronic formats
- Preparing crime statistics submissions for state databases and federal reporting requirements
- Clearing backlog of unstructured historical reports requiring standardization
- Validating that all critical UCR elements are present before database submission







