Auditors bill to formalize special reviews and access leadership data raises privacy concerns in committee

Representative Quam brought forward a bill on March 11, 2025, to establish a formal special reviews division within the Office of the Legislative Auditor (OLA), clarify when agencies must report possible misuse of public resources to OLA, and to authorize OLA to request data from Minnesota IT Services (MNIT) in certain leadership-level inquiries. The House State Government Finance and Policy Committee voted to re-refer the measure to the Judiciary Committee.

The bill, described by Legislative Auditor Judy Randall as largely "housekeeping," would (1) elevate an existing special reviews unit to a statutory division, (2) expand OLAs authority to conduct special reviews in response to allegations of noncompliance with legal requirements beyond strictly financial matters, (3) authorize follow-up special reviews, (4) clarify agency reporting obligations about suspected misuse of public money or unauthorized disclosure of data, and (5) set a process for OLA to obtain certain communications or other data from MNIT when inquiries involve agency leadership. Randall also proposed repealing Minnesota Statute 16B.045 because its IT-audit language is redundant with OLA's existing authorities in statute 3.971 subdivision 6A.

Why this matters: supporters said the changes would modernize OLAs ability to respond to complaints and make internal processes consistent; critics said some provisions, especially language about direct production of leadership-level emails and other data, risk insufficient guardrails and could create privacy or oversight concerns if not narrowed.

What the auditor told the committee

Judy Randall, Legislative Auditor, walked the committee through the bills provisions and examples. She said the special reviews authority would let OLA examine nonfinancial legal compliance when there are allegations such as a licensing board not following statutory complaint rules. On data access, Randall said the change is about process: "When the allegation involves leadership ... we are reluctant to notify leadership that we want their emails, and then rely on them to give it to us. It's just not good audit practice." She told members she had discussed the language with agency officials and MNIT and that MMB would be asked to develop an implementation policy.

Concerns from members

Several members raised questions about how narrowly terms like "leadership" and "data" would be defined. Representative Freiberg asked whether "leadership" would be limited to commissioners and top general counsel/CIO types; Randall said she envisioned "the commissioner, the general counsel, probably a CIO" but was open to tightening the language. Representative Bonner warned the committee that, as written, lines 3.11to3.14 could be read as a "carte blanche" to search systems without clear scope or transparency: "...literally, any auditor could go in and rifle through anything with no definition of scope...and maybe you have that I don't know but I I have serious serious concerns." Randall and Representative Quam said OLA already has statutory access to data in audits and that the provision is narrowly intended for a limited class of audits of agency leadership and to rely on MNITs production process rather than asking agency leadership to produce records themselves.

What passed today

Representative Quam moved to re-refer the bill to the Judiciary Committee; the motion carried by voice vote. The committee did not adopt any amendments on the floor; several members urged follow-up work to narrow or clarify terms, to add explicit process guardrails and to define the scope of data production and oversight before the bill advances further.

Discussion versus decision

- Discussion: Committee debate focused on definitions ("leadership," "data"), the process for MNIT to produce requested records, and the potential need to add explicit procedural checks (e.g., defined scope, independent oversight or probable-cause standards). Members noted the existing professional standards and internal controls at OLA but asked for statutory clarity. - Direction/Assignment: Multiple members and the auditor agreed to continue off-line drafting and to consult nonpartisan staff and MNIT about tighter language and implementation details. - Formal action: Representative Quams motion to re-refer House File 1240 to the Judiciary Committee carried.

Clarifying details

- Repealer: Bill would repeal Minnesota Statute 16B.045 (an older IT-audit provision) as duplicative of existing authority in Minnesota Statute 3.971 subdivision 6A, per Judy Randall. - Intended scope for leadership-level data: Randall described the access as intended for senior leadership (commissioner, general counsel, CIO) but said she would work with members to narrow definitions. - Process: Randall emphasized that OLA would use MNITs process to request production of records rather than relying on agency leadership to produce them, to avoid tipping off subjects of an inquiry.

Speakers

- Judy Randall, Legislative Auditor (first referenced at 00:25:15, transcript segment) - Representative Quam, bill author / mover (first referenced at 00:24:10, transcript segment) - Representative Freiberg (questioner) - Representative Bonner (questioner) - Representative Jones (commenter) - Chair Nash (presiding)

Authorities referenced in committee

- statute: Minnesota Statute 16B.045 (referenced for repeal) - statute: Minnesota Statute 3.971 subdivision 6A (referenced as existing OLA authority)

Searchable tags: legislative auditor, OLA, data access, MNIT, privacy, House File 1240, Judiciary referral, special reviews