Minnesota Government Data Practices Act Requirements
Managing the Minnesota Government Data Practices Act requires a modern approach to public visibility; under the Act, almost all government data is public by default. For public sector compliance, legal, and IT teams, the operational challenge isn't necessarily deciding what to release, but determining what the law allows them to protect.
A single public records request can trigger a massive search across legacy email systems, employee mobile devices, and shared collaborative drives. Moving from reactive searching to proactive communication data intelligence dramatically transforms workflow efficiency for public agencies — as well as their ability to respond quickly and stay compliant.
Key takeaways
-
The Minnesota Government Data Practices Act assumes all data a government entity holds is public unless a specific classification says otherwise.
-
Data falls into five distinct categories, and the classification of a piece of data determines who has the right to see it.
-
A prompt and reasonable deadline applies to the public, but a strict 10-business-day limit applies to data subjects.
-
If access is wrongfully denied, a requester has a range of options available, including free advisory, administrative hearings, and lawsuits.
-
An agency's ability to capture and store its communications data impacts its ability to respond within a reasonable amount of time and limit risk of errors or wrongful disclosures.
What is the Minnesota Government Data Practices Act?
The Minnesota Government Data Practices Act (MGDPA), outlined in Minnesota Statutes Chapter 13, has governed how state and local entities handle government data since 1974. Its core premise is a presumption of openness. Unless a state statute, a federal law, or a temporary classification says a piece of data is private or otherwise protected, it is public.
The five primary data classifications
To maintain regulatory readiness and respect individual privacy, the MGDPA organizes all information into distinct categories. These classifications dictate exactly who can legally access, review, or distribute the records:
- Data on individuals applies to any record where a human being can be identified as the subject. This information is classified as public (accessible to anyone), private (accessible only to the subject and authorized staff), or confidential (withheld from both the public and the subject).
- Data not on individuals encompasses all other corporate or operational government records. These files are categorized as public, nonpublic (withheld from the public but open to the data subject), or protected nonpublic (completely restricted from the public and the subject).
- Summary data involves statistical reports derived by removing personal identifiers from private or confidential datasets. This material remains public unless a specific statute limits exposure.
- Data on decedents addresses records created prior to an individual's death. These records inherit private or confidential status and generally become fully public 10 years after death and 30 years after the file's initial creation.
- Statutory exemptions remove specific data sets from standard public access rules altogether. This includes active criminal investigations, medical files, specific personnel background records, and most judicial branch communications.
How to file a Minnesota Government Data Practices Act request
The process to request a record is meant to be easy and accessible to the public. For agencies, appropriately managing a response requires a thorough understanding of who is allowed to see what category of data and how digital records are treated under the Act.
Who can submit records requests?
The MGDPA allows any person to inspect or copy public data, and an entity cannot require a requester to give their name, state a reason for the request, or say what they intend to do with the information. Requesters are also not required to be Minnesota residents.
While individuals do not have to use a specific, state-mandated form to submit an inquiry, encouraging written requests helps staff accurately track, scope, and locate records across distributed messaging systems.
Response timelines and obligations
Unlike states that enforce rigid statutory deadlines counted in days, the MGDPA requires state and local entities to respond to public inquiries in a prompt, appropriate, and reasonable manner. What qualifies as a reasonable timeframe under Chapter 13 depends entirely on the size, complexity, and operational scope of the request.
For public sector records managers, this open-ended framework means simple questions might be answered within the same business week, while massive discovery demands requiring deep data redaction can take months. To see how this flexible approach contrasts with the fixed calendars used by other jurisdictions, you can evaluate state-by-state statutory timelines using our interactive FOIA laws map.
Data inspection
Compliant delivery formats require agencies to either arrange an immediate on-site data inspection or deliver copies as soon as reasonably practical. If data is legally classified as nonpublic, the agency must issue a timely denial that identifies the specific statutory section authorizing the restriction.
Costs and fees
Cost-free inspection rights protect the public's right to view records without paying administrative fees, allowing requesters to audit files before committing to duplication expenses. Standard copy limits state that for 100 or fewer standard black-and-white, letter-sized, or legal-sized pages, agencies cannot charge more than 25 cents per page.
Actual cost recovery models apply to complex or specialized media requests, permitting entities to bill for the true operational expense of gathering data, including manual staff review time. Public bodies are not permitted to bill requesters for the labor hours spent separating public information from data that they are legally required to withhold.
Electronic and digital records
Because the Act is concerned with the content of records and not their form, digital communication is always included. Emails, texts, chat messages, and recordings are all government data when they touch public business. The commissioner of administration has advised that a text or email can count as government data even when it sits on an official’s personal phone or in a personal account, as long as it was sent or received in an official capacity.
The increasing business that happens over text and chat on personal devices has increased the risk of public data getting lost. That’s why, for public agencies, implementing government text message archiving is no longer optional.
Tip
The open-ended response timeline often causes unintentional problems for Minnesota agencies. Because nothing forces a hard deadline, large requests are easily forgotten, and a requester who feels ignored can take the matter to an administrative judge. A quick acknowledgment, an honest estimate, and occasional status updates are usually sufficient to keep a routine request from turning into a complaint.
What are the penalties for non-compliance?
No agency enforces the Data Practices Act on its own. The Minnesota Department of Administration and its Data Practices Office cannot order anyone to comply, but the commissioner of administration can issue advisory opinions interpreting the law for a specific dispute. Even though those opinions are not binding, they are often used to settle the matter in court.
Disputes can follow two paths. The first is the district court, where an entity can be ordered to comply with the Act and made to cover the requester’s damages, costs, and attorney fees, plus a civil penalty of up to $1,000. If the non-compliance is deemed willful, the exemplary damages run from $1,000 to $15,000 for each violation. The other route for disputes is through the Office of Administrative Hearings, where an administrative law judge can order compliance and award attorney fees up to $5,000.
A willful violation is a misdemeanor that a prosecutor can charge, and it can cost the responsible employee their job. Moreover, the public fallout from disputes often costs agencies far more than financial penalties — disputes can have real long-term consequences to both an agency's operations and overall reputation.
Challenges of managing Minnesota open records compliance
For public sector IT and compliance leaders, state statutes are rarely the primary obstacle. The true complexity lies in locating requested data across modern communication channels and proving the subsequent search was defensible.
Minnesota’s data-centric oversight environment places immense weight on daily operational practices. This modern regulatory landscape creates distinct pressure points for records teams.
Defining a reasonable response time
Minnesota’s flexible timing standards give government entities the necessary room to process large or complex requests, but they also introduce challenging judgment calls. A request can easily stall without a centralized system to track search status, pending reviews, or requester updates. Maintaining a prompt and appropriate response becomes increasingly difficult the longer an agency remains unresponsive. Teams can protect their audit trail by establishing continuous visibility over the request lifecycle.
Managing data outside the usual records workflow
Shadow IT and expanding communication stacks quickly shift from a policy inconvenience to a major public records liability. Daily workflow tools often bypass legacy archiving systems entirely, leaving records teams to discover fragmented data midway through a request. This visibility gap poses a critical challenge because the Minnesota Government Data Practices Act regulates the data itself, regardless of where that data lives. Organizations can solve this by capturing data comprehensively at the source.
Proving the search was complete
Most public sector tech failures occur in the gap between official records policies and actual employee communication habits. An inadvertently omitted text or chat message can raise immediate compliance questions even when data deletion was entirely unintentional. Defending a slow or incomplete search is exceptionally difficult without a unified digital footprint of the verification process. Compliance teams win back time when they can instantly verify which systems were reviewed, where the search occurred, and how data was preserved before a request ever arrived.
A summary of the Minnesota Government Data Practices Act
The Minnesota Government Data Practices Act gives the public access to government data unless the law classifies that data as private, confidential, nonpublic, or otherwise protected. Classification is at the center of the request process. Agencies need to know what data they have, what category it falls into, and how quickly they can provide access without losing track of the Act’s reasonable-time standard.
For Minnesota entities, compliance depends on more than knowing the bounds of the statute. When data is scattered across email, mobile messages, shared systems, social platforms, and meeting files, robust recordkeeping technology makes data far easier to search and retrieve.
| Regulatory Element | Details |
|---|---|
| Law Name | Minnesota Government Data Practices Act |
| Statute Citation | Minn. Stat. ch. 13 |
| Governing Body | Commissioner of admin. (advisory) |
| Response Deadline | Prompt and reasonable, no set days |
| Fee Structure | Inspection-free, 25¢/page copies |
| Covered Entities | State and local government entities |
| Key Exemptions | Investigations, personnel, and medical |
| Penalty Provisions | Damages, fees, up to $15,000 if willful |
| Electronic Records | Covered as government data |
| Appeal Process | District court or admin. hearing |
Managing these statutory variables requires an infrastructure that eliminates guesswork. Modern oversight demands a proactive approach to information governance — one that transforms unstructured communication data into a reliable source of truth. By consolidating your email, mobile messages, and collaboration tools into a unified platform, your team gains the precise intelligence needed to reduce review times, satisfy complex search parameters, and consistently build FOIA-proof archives that protect organizational integrity.
Frequently asked questions
Government entities can charge for the actual labor cost of searching, retrieving, and copying data only when a request exceeds 100 physical pages. For smaller electronic distributions or inspections, agencies generally cannot assess search and retrieval fees. Additionally, the MGDPA strictly prohibits organizations from charging requesters for the staff time required to redact nonpublic data from public data. Public sector teams can reduce these operational overhead costs by using centralized platforms that drastically reduce search and retrieval times.
Requesters can pursue administrative complaints, seek formal advisory opinions, or file lawsuits in district court if an agency fails to respond within a reasonable timeframe. Because Minnesota statute does not define a fixed number of calendar days for standard requests, an unmonitored tracking workflow can easily lead to compliance exposure. If a court finds that an entity willfully ignored or delayed a request, the organization faces up to $15,000 in civil penalties, plus actual damages and mandatory attorney fees. Maintaining a continuous, immutable audit trail of the entire search process protects agencies against these costly non-compliance claims.
The MGDPA regulates all government data based entirely on its content and public purpose, regardless of its format or whether it lives on a personal mobile device. Text messages, Slack communications, and Zoom logs generated during official public business are legally binding public records. If an employee uses a personal phone or an unapproved chat application to discuss agency matters, those conversations remain subject to disclosure and retention rules. Public sector IT leaders mitigate this shadow IT risk by implementing automated, multi-channel capture tools that capture communication data directly at the source.
Share this post!
- Nevada Public Records Act Requirements - June 22, 2026
- Minnesota Government Data Practices Act Requirements - June 16, 2026
- Alaska Public Records Act Compliance Guide for Agencies - June 15, 2026
Smarsh Blog
Our internal subject matter experts and our network of external industry experts are featured with insights into the technology and industry trends that affect your electronic communications compliance initiatives. Sign up to benefit from their deep understanding, tips and best practices regarding how your company can manage compliance risk while unlocking the business value of your communications data.
Ready to enable compliant productivity?
Join the 6,500+ customers using Smarsh to drive their business forward.
More Resources
Subscribe to the Smarsh Blog Digest
Subscribe to receive a monthly digest of articles exploring regulatory updates, news, trends and best practices in electronic communications capture and archiving.
Smarsh handles information you submit to Smarsh in accordance with its Privacy Policy. By clicking "submit", you consent to Smarsh processing your information and storing it in accordance with the Privacy Policy and agree to receive communications from Smarsh and its third-party partners regarding products and services that may be of interest to you. You may withdraw your consent at any time by emailing [email protected].
FOLLOW US