aceModerate evidence
Published recordCrimeProblem Space
More
Artificial intelligence, accountability mechanisms, and the transformation of street-level enforcement style: experimental evidence from frontline policing
- Truvace record
- TRV-2026-2523raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Randomized controlled trial
- Sources
- 1 sourcePeer-reviewed
- sha256
- f27d86d610d6…check it
Artificial intelligence (AI) is increasingly used to support street-level enforcement, yet its impact on bureaucrats’ enforcement style under different accountability mechanisms remains understudied. To achieve this, we conducted a preregistered survey experiment in the context of honking violations with a representative sample of 356 street-level police officers. Results show that AI-supported enforcement shifts bureaucrats toward a more formal and coercive style while diminishing its educational component. Pro…
The problem
In a preregistered survey experiment with 356 street-level police officers handling honking violations, AI-supported enforcement shifted officers toward a more formal and coercive style and reduced the educational part of their approach.
What this doesn’t fix
The evidence comes from a survey experiment on honking violations, so it measures officers' responses to a scenario in one enforcement context rather than real-world enforcement outcomes.
Sources
1 on file- Global Public Policy and Governancedoi:10.1007/s43508-026-00146-y
Cite this record
v1Truvace Impact Record TRV-2026-2523, v1: “Artificial intelligence, accountability mechanisms, and the transformation of street-level enforcement style: experimental evidence from frontline policing.” Truvace, 2026-11-12. /record/TRV-2026-2523 (accessed on the day you copy it). sha256 f27d86d610d62887…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2523 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.