Rochester Police Department
4 audits on file. Next audit expected 2026, on the two-year cycle in Minn. Stat. § 13.824, subd. 6.
Auditor
Auditor type
Government consortium
Result
Compliant - no findings
Findings
None recorded
Audit depth
Substantive
Tested live system
Not stated
Retention found
60 days
Report pages
5
What the audit said
Zero exceptions. Seven controls tested, "No exceptions found" against each; the conclusion reads "It demonstrates that the security, public accountability and administration of the RPD ALPR program is in compliance with MN Statute §13.824." Evidence cited is policy documentation (RPD Policy 427), staff interviews, and system screenshots showing the 60-day retention setting and the "Reason for Action" requirement. No recommendations, no observations, no mid-audit corrections, no ghost-finding language.
Auditor
Auditor type
Government consortium
Result
Compliant - no findings
Findings
None recorded
Audit depth
Substantive
Tested live system
Not stated
System / vendor
BOSS
Retention found
60 days
Report pages
5
What the audit said
Zero exceptions. Seven control areas tested, "No exceptions found" against each; the report concludes that "the security, public accountability and administration of the RPD ALPR program" is "in compliance with MN Statute §13.824." BOSS ALPR system; 60-day retention evidenced by a system-settings screenshot. No recommendations, no observations, no mid-audit corrections, no ghost-finding language.
Auditor type
State oversight office
Result
Compliant - no findings
Findings
None recorded
Audit depth
Substantive
Tested live system
Yes
System / vendor
PIPS Technology
Devices / cameras
10
Retention found
60 days
Report pages
5
Conducted
August 11, 2020
Period covered
August 13, 2018 to August 13, 2020
What the audit said
No exception recorded against Rochester PD. This is a joint agreed-upon-procedures engagement by the Minnesota Office of the State Auditor covering Olmsted County SO and Rochester PD together under Minn. Stat. §§ 13.824 and 626.8472; the single exception in the report is against Olmsted County's policy, not Rochester's (see the companion Olmsted row for the same doc number). The report notes Rochester PD's summarized public log "only contains data from the previous 60 days" — recorded here as an observation, not scored as a ghost finding, because a 60-day log window tracks the statutory destruction schedule rather than describing a deficiency. Worth a human read of the raw PDF before treating it either way.
Note on this record
The Office of the State Auditor extracted data and reviewed audit trails directly on August 11 and 13, 2020, rather than working from screen prints. The engagement's one exception was recorded against Olmsted County's policy, not Rochester's. Rochester was running PIPS Technology mobile units at the time.
Auditor
Auditor type
Private consultant
Result
Compliant - no findings
Findings
None recorded
Audit depth
Checklist
Tested live system
Not stated
Retention found
60 days
Report pages
6
Conducted
February 9, 2018
What the audit said
Zero exceptions. The report runs 25 control objectives and records "No exception Noted" against every one, concluding that "the Rochester Police Department's Automated License Plate Reader (ALPR) program reasonably complies with the 2017 Minnesota Statute 13.824." 60-day retention: "Data obtained from the license plate readers systems are destroyed within 60 days, unless part of a criminal investigation." No recommendations, no mid-audit corrections, no ghost-finding language.
Note on this record
Fieldwork was February 9, 2018. The report states no audit period, vendor, or device count; the 2020 State Auditor report shows Rochester running 10 PIPS Technology mobile units two years later.
Recorded findings appear in green because a finding is evidence the auditor actually examined the program. A report with nothing at all appears in red.
Every agency operating an ALPR in Minnesota must arrange an independent audit every two years under Minn. Stat. § 13.824, subd. 6.
← All agencies and auditors