Instant Checkmate
Criminal-record and social-profile search option.
View Records Sponsored partner optionUtah’s Government Records Access and Management Act provides the legal framework, but it does not centralize every police report. The record stays with the agency that created or maintains it, so the first search question is which police department, sheriff, or DPS unit handled the event.
Use GRAMA as the access framework and agency custody as the routing rule.
Utah police reports are requested under GRAMA from the government entity that maintains the record. Utah DPS provides a records-request route for DPS material, but a city police or county sheriff report remains with that local agency. A GRAMA request should identify the specific incident and record type instead of treating “Utah police reports” as one statewide database.
A Utah police-report request combines two concepts: GRAMA determines the public-record framework, while agency custody determines where the request is submitted. Utah DPS offers a public records route for the records it maintains, but the existence of a statewide department does not make it the custodian for every city or county police file.
Identify the responding agency from the incident location or report number before drafting the request. Then name the record product: incident report, accident record, dispatch information, audio, video or another agency record. If the research goal is a person’s broader criminal history, move to the relevant criminal-history and court systems rather than treating a single police report as a statewide background record.
GRAMA is the legal route, not a statewide report warehouse.
Use the DPS records-request system for reports and public-safety records maintained by Utah DPS.
Use the local police or sheriff records office when that agency created the incident report.
Request the specific recording and event because release review can differ from a written narrative.
Keep event records separate from repository or court research.
The best request is tied to a specific record and agency.
Use the incident location, responding unit or report number to identify the agency.
Name the report, log, audio, video or other record rather than asking for a general background file.
Use DPS for DPS records and the local agency for local law-enforcement files.
The agency applies GRAMA and other confidentiality rules to the responsive record.
These details help the agency identify a discrete record.
| Field | Purpose |
|---|---|
| Agency or department | Establishes the likely custodian |
| Report / incident number | Targets the exact police file |
| Date and place | Confirms the event |
| Requested format | Distinguishes report text, audio, video or another record type |
Ask for each medium explicitly.
The written narrative is usually the first record to request for an identified police event.
A narrow time window and incident reference help locate responsive recordings.
Footage can require additional privacy, investigative and redaction review.
A responsive police file can include both public and restricted information.
| Issue | Potential effect |
|---|---|
| Protected or private information | Specific fields can be withheld or redacted |
| Active investigation | Access may be restricted while disclosure would interfere with the case |
| Wrong agency | A request can be redirected to the actual record custodian |
| Recorded media | Video and audio may require a separate, more detailed review |
Route by the agency that made the record.
External sources are marked nofollow.