Minneapolis Government Transparency: Open Records and Public Data

Minneapolis government transparency rests on a legal framework that gives residents the right to inspect and obtain government records held by the City of Minneapolis and related public bodies. This page covers the definition and scope of open records obligations under Minnesota law, the mechanics of submitting and processing data requests, common scenarios in which residents and journalists invoke these rights, and the decision boundaries that determine what records are released, redacted, or withheld. Understanding this framework is foundational to meaningful civic participation in Minneapolis government.

Definition and scope

Minnesota's Government Data Practices Act (Minn. Stat. § 13), administered statewide by the Minnesota Department of Administration's Information Policy Analysis Division (IPAD), establishes the default rule that government data are public unless a specific statute classifies them otherwise. Minneapolis, as a statutory city operating under the Minneapolis City Charter, is a "government entity" fully bound by this act. The city's obligation covers data collected, created, received, maintained, or disseminated by all city departments, including but not limited to the City Clerk's Office, the Minneapolis Police Department, the Minneapolis City Attorney's Office, and all city departments.

The Act distinguishes among three data classifications:

Public data — available to any person on request, without requiring the requestor to state a reason or identity.
Private data — accessible only to the subject of the data, their authorized representative, or government entities authorized by statute.
Confidential data — accessible only to government personnel with a specific statutory need; not releasable to the data subject.

This classification structure applies to paper records, electronic databases, video footage, audio recordings, email, and geographic data systems maintained by the city.

Scope, coverage, and limitations

This page addresses public data obligations that apply specifically to the City of Minneapolis as a municipal entity within Hennepin County and the State of Minnesota. It does not cover:

Hennepin County records, which are governed by the same state Act but administered separately by Hennepin County — see Hennepin County's relationship with Minneapolis for context.
Metropolitan Council records, which fall under the same Act but are managed at the regional level — see Minneapolis and the Metropolitan Council.
Minneapolis Public Schools records, which are administered by the Minneapolis School Board as a separate governmental entity.
Federal records held by agencies operating in Minneapolis, which fall under the federal Freedom of Information Act (5 U.S.C. § 552) rather than Minnesota law.
Private contractors performing city services — data created by private vendors may or may not be government data depending on whether the city "receives" it under Minn. Stat. § 13.05, subd. 11.

How it works

A data request under the Minnesota Government Data Practices Act requires no special form, no statement of purpose, and no identification from the requestor when seeking public data. The City of Minneapolis accepts requests through the City Clerk's Office, through department-specific channels, and through its online 311 portal (Minneapolis 311 Services).

Once a request is received, the city must respond within a defined timeframe. Under Minn. Stat. § 13.04, the response must be "immediate" for requests made in person during normal business hours when the data exist and are readily available. If the data require assembly or review, the city may charge a fee reflecting actual costs of searching, retrieving, and copying, but only for requests requiring more than a minimal effort.

The Minneapolis Auditor and Inspector General plays a role in monitoring compliance with transparency obligations across city operations, including data practices. IPAD, at the state level, functions as the interpretive authority — issuing advisory opinions that bind government entities on how to classify and release data.

The Minneapolis Public Comment Process operates as a parallel transparency mechanism: agendas, supporting documents, and meeting minutes for the Minneapolis City Council and the Minneapolis Boards and Commissions are posted publicly in advance of and following open meetings, as required by Minnesota's Open Meeting Law (Minn. Stat. § 13D).

Common scenarios

Residents, journalists, attorneys, and researchers invoke the Government Data Practices Act in predictable patterns:

Police records requests: Body-worn camera footage, incident reports, and use-of-force data are among the highest-volume request categories. Some footage is classified as private or confidential under Minn. Stat. § 13.82, depending on whether an investigation is active or closed. The Minneapolis Police Department Oversight structure generates additional records subject to disclosure.
Budget and financial data: Expenditure records, vendor contracts, and payroll data for city employees are generally public. The Minneapolis Budget Process produces budget documents that are published proactively on the city's website.
Zoning and permits: Applications, approvals, inspection reports, and correspondence related to Minneapolis Zoning and Land Use decisions are public data accessible through the Department of Community Planning and Economic Development.
Personnel records: Employee names, job titles, salaries, and dates of employment are public under Minn. Stat. § 13.43. Performance evaluations and disciplinary records have a mixed classification depending on outcome — final disciplinary action resulting in discharge, demotion, or suspension is public; preliminary investigative data is private while the investigation is ongoing.
Civil rights complaints: Data held by the Minneapolis Civil Rights Department regarding discrimination complaints follows a private classification during investigation, shifting to public upon completion of the proceeding for certain findings.

Decision boundaries

The central decision boundary in Minneapolis public data practice is the question of classification at the time the data were collected. The following distinctions govern whether data are released in full, released with redactions, or withheld:

Active vs. closed investigative data: Under Minn. Stat. § 13.82, subd. 7, active criminal investigative data are protected from disclosure. Once an investigation is closed — either through prosecution or a decision not to prosecute — the classification of specific data elements shifts. This distinction is critical in police records requests.

Public vs. private personnel data: The city must distinguish between what Minn. Stat. § 13.43 designates as public personnel data (name, salary, job title, work location) and private personnel data (home address, medical records, performance evaluations prior to final action). Releasing private data about a city employee to a third-party requestor would constitute a violation of the Act.

Licensing and permit records compared with confidential business data: Records related to Minneapolis Permits and Licensing are generally public, but financial data submitted as part of a license application — such as detailed revenue figures — may qualify for trade secret protection under Minn. Stat. § 13.37 if the submitting party has identified them as such and the city has determined that classification is warranted.

Meeting records vs. executive session records: Under the Open Meeting Law, the Minneapolis City Council must hold deliberations in public. The Act permits closed sessions for a narrow set of purposes — attorney-client privileged discussions under Minn. Stat. § 13D.05, subd. 3(b), labor negotiation strategy, and active litigation. Records from those sessions remain non-public until the specific statutory exception no longer applies.

When a requestor believes the city has improperly withheld data, the requestor may seek a written opinion from IPAD or file a complaint with the Office of Administrative Hearings. Courts may also award attorney fees and civil penalties against a government entity that knowingly violates the Act — reinforcing that these obligations carry enforceable consequences rather than operating as aspirational guidelines.