LANSING, MI — A critical data processing error within the Michigan State Police (MSP) Criminal History Record system resulted in the wrongful expungement of 115 criminal convictions, pulling records off public databases that should have legally remained active.
The incident underscores the growing operational friction between state-level automated "Clean Slate" expungement initiatives and primary-source data integrity across the screening ecosystem.
Key Takeaways from the Reporting
- The Cause: According to the Detroit Free Press, a technical glitch within the automated Criminal History Record (CHR) platform miscategorized 115 non-qualifying convictions as set-aside/expunged, removing them from public background check views and state databases.
- Scope of Exposure: While state automated platforms process thousands of record changes daily under Michigan's automatic Clean Slate laws, the improper sealing of non-eligible offenses highlights the vulnerabilities of relying solely on automated algorithmic processing without manual court oversight.
- Remediation Underway: MSP officials identified the error and initiated steps to reverse the accidental set-asides, restoring the convictions to active public record status in the central repository.
Industry Implications for Background Screeners
For Consumer Reporting Agencies (CRAs) and court record retrievers, the incident serves as a stark case study on the risks of continuous automated data feeds versus primary-source verification:
- The "Clean Slate" Algorithmic Risk: As states automate expungement processes, proprietary algorithms deployed by state agencies often struggle with edge cases, misclassified dockets, or missing judicial dispositions, leading to over-inclusive expungement.
- False Negative Exposure: Background screeners relying exclusively on bulk digital state feeds during the window of the glitch risked issuing reports with missing conviction data—exposing employers to negligent hiring risks and vendors to compliance exposure.
- The Ground-Truth Standard: The MSP error reinforces why direct, primary-source court file verification remains the essential safeguard against systemic database errors, ensuring that public records match physical court dockets rather than flawed state database scripts.
