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.
FinePrint notes
2026-09-17 weekly rotation. Auditor attested by Blake Tyra, Information Security Specialist, LOGIS (titled "Analyst" on the 2022 report). Report signed 2024-12-19 — two years to the day after the 2022 report, and the same seven controls, same 5-page format, same zero-exception result. That pairing is itself the template pattern this project tracks. No fieldwork/testing date and no audit period stated, so both left empty rather than inferred from the signature date. Vendor not named in this report; the 2022 report identifies the system as BOSS and the 2020 OSA joint report as PIPS Technology, so System/Vendor is left empty here rather than carried over. Tested Live System left UNCHECKED — policy review, interviews and screenshots, with no statement that LOGIS reached the live console or audit logs. Audit Depth Substantive per the Coon Rapids LOGIS precedent; Independence Flag checked per LOGIS convention (consortium auditing its member-funders). Rochester's full record now reads: 2018 Backbone (clean), 2020 Office of the State Auditor (clean for Rochester), 2022 LOGIS (clean), 2024 LOGIS (clean). Four audits, four zero-finding sheets, three different auditors. Next biennial audit is due in the 2026 cycle and nothing has been filed as of this run — worth re-checking the 2026 LRL folder later this year before calling it a gap.
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.
FinePrint notes
2026-09-17 weekly rotation. Auditor attested by Blake Tyra, Information Security Analyst, LOGIS. Report signed 2022-12-19; no fieldwork or testing date is stated anywhere in the report, so Audit Conducted Date is deliberately left empty rather than filled with the signature date (Orono/251707 precedent). No audit period stated either. Tested Live System left UNCHECKED: the report describes reviewing policy, interviewing staff and reproducing system screenshots, but never states that LOGIS accessed the live console or audit logs itself. Audit Depth set to Substantive to stay consistent with the Coon Rapids LOGIS row (251347), which is the same auditor, same 5-page format, and was rated Substantive on the strength of configuration screenshots evidencing actual settings rather than assertions. If that precedent is ever revisited, these two Rochester rows should move with it. Independence Flag checked per LOGIS convention — LOGIS is a joint-powers consortium of Minnesota local governments auditing its own member-funders. NOTE ON SOURCE HOST: this doc lives under leg.mn.gov/docs/2022/Mandated/ (capital M) rather than the lrl.mn.gov/docs/<year>/mandated/ pattern the rest of the table uses. leg.mn.gov appears to mirror the same collection; lrl.mn.gov/docs/2020/mandated/201205.pdf returned a robots.txt error this run while the leg.mn.gov paths fetched fine. Worth normalizing Source URL hosts table-wide at some point.
Auditor
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.
FinePrint notes
2026-09-17 weekly rotation, Part 2 hunt. Placeholder replaced. Rochester PD turned out to have FOUR filed ALPR audits, none of them previously in the table: 2018 Backbone Consultants (LRL 191267), this 2020 Office of the State Auditor joint engagement (LRL 201206), 2022 LOGIS (221647) and 2024 LOGIS (241731). Each is its own row. CORRECTION LOGGED: an earlier version of this note called Rochester a multi-cycle compliance gap on the assumption that 2020 was its last audit. That was wrong — the 2022 and 2024 audits exist and are filed; they simply sit in LRL folders the table had never swept. Rochester is current through the 2024 cycle. The only open question is the 2026 cycle, where nothing is filed yet; the 2022 and 2024 reports were both signed on December 19, so a late-2026 filing would be on pattern. Re-check the 2026 folder in Q1 2027 before calling anything a gap. SYSTEMIC DATASET GAP — this is the escalation-worthy finding. The three Rochester audits missed here were all findable from a single web search, and the Filing Year select only offered 2024-2027 before this run. Prior notes in this table refer to having "checked all 61 statewide ALPR filings," but that sweep was evidently limited to the 2025 and 2026 LRL folders. The 2019, 2020, 2022 and 2024 mandated-report folders look substantially unswept, which means per-auditor clean rates and the audit-mill math are all computed over a truncated window. A dedicated back-sweep of pre-2025 filings should probably jump the rotation queue. About this report specifically: the OSA is the most structurally independent auditor anywhere in the table — a state constitutional office, no fee relationship with the audited agency, no LE alumni network, and it actually extracted data and reviewed audit trails (fieldwork 8/11 and 8/13/2020) rather than working from screen prints. It also recorded an exception, against Olmsted County's policy. Set against Rochester's own record of four consecutive zero-finding sheets from three auditors, that is a useful contrast case. Vendor at the time was PIPS Technology (mobile units), pre-dating both the BOSS system named in 2022 and the Flock era. New select options created this run: Auditor = "Office of the State Auditor" and "Backbone Consultants", Auditor Type = "State oversight office", System/Vendor = "PIPS Technology", Filing Year = 2019, 2020, 2022. references/schema.md in segalreport/fineprint needs updating to match.
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.
FinePrint notes
2026-09-17 weekly rotation, Part 2 hunt. Located via web search; LRL doc 191267 verified — cover names Rochester Police Department, 101 4th St SE, Rochester MN 55904, and the report cites 2017 Minn. Stat. 13.824 (ALPR, not body-worn camera). Earliest audit in the table by several years. Fieldwork Feb 9, 2018; filed to LRL in the 2019 folder. No audit period is stated — the report assesses compliance as of the fieldwork date — so Period Start/End left empty rather than inferred. Vendor and device count are not stated in the report; the 2020 OSA joint report (LRL 201206) shows Rochester running 10 PIPS Technology mobile units two years later. New auditor for this table: Backbone Consultants, Minneapolis — an IT/security audit firm, not part of the Lembcke/MNSec/Axtell police-audit network. Only one ALPR audit on record so far; worth a search for other Backbone filings in the 2019 and 2020 LRL folders before drawing any conclusion about their output pattern. Auditor LE Background left unchecked (unresearched, not established as false).
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