Advertisement

What Minnesota Requires for CO Detectors in Homes, Rentals, Lodging

Last verified: February 16, 2026

"Minnesota carbon monoxide detector laws are anchored in Minn. Stat. section 299F.51 and apply broadly across covered dwelling contexts, including owner-occupied homes, rental units, and specified lodging scenarios. The statute establishes alarm obligations, replacement duties, and enforcement consequences, while Minnesota rules such as 1309.0315 and 7511.0915 provide additional code-layer implementation detail.

Minnesota's framework is operationally strict: owners and managers should treat placement, testing, and replacement records as routine compliance controls rather than one-time installation tasks. Enforcement can escalate from an initial warning to a petty-misdemeanor path with monetary penalties for repeated violations. The most reliable approach is section-linked documentation for occupancy turnover, maintenance tickets, and inspector communication in every covered property file.

Minnesota operators should log every warning, correction, and reinspection milestone in dated records."

In 60 Seconds

CO detector requirements for Minnesota
Applies to homes? Yes
Applies to rentals? Yes
Applies to hotels/STRs? Yes

When Are CO Alarms Required?

  • Minn. Stat. 299F.51 establishes broad statutory alarm requirements for covered dwellings.
  • Minnesota code rules 1309.0315 and 7511.0915 provide additional technical and scope detail in building-code contexts.

Where to Install CO Alarms

  • Within 10 feet of each room lawfully used for sleeping as stated in Minn. Stat. 299F.51.
  • Additional level and room conditions are addressed in statute and Minnesota code-rule context.

For detailed placement guidance beyond legal requirements, see where to place carbon monoxide detectors.

Device Requirements

  • Approved and operational carbon monoxide alarms as required by Minn. Stat. 299F.51.
  • Device and installation details are reinforced through Minnesota rules 1309.0315 and 7511.0915 where applicable.

Landlord and Tenant Responsibilities

Landlord: Landlords and multifamily owners must provide required alarms and maintain operability, including replacement obligations at turnover points.

Tenant: Occupants must maintain alarms in good repair during occupancy and avoid rendering devices inoperable.

Enforcement

Enforced by: Minnesota State Fire Marshal division and local authorities through statute and code-enforcement workflow.

Enforcement typically occurs:

  • During inspections and compliance checks where alarms are missing, disabled, or nonfunctional.
  • After notice, with escalation pathway for repeat violations under statutory penalty structure.

Penalties for Non-Compliance

First violation carries a warning-focused response; subsequent violations may be treated as petty misdemeanors with fines up to $300 under Minn. Stat. 299F.51.

Minn. Stat. 299F.51, subdivision 6.

Additional Notes

  • Minnesota statute and code layers should be read together for complete operational compliance.
  • Hotels and short-term rentals are treated as covered where statutory and guidance sources expressly identify lodging contexts.

Official Sources & References

Disclaimer: This information is provided for general guidance and is not legal advice. Requirements may vary by city, county, and building type. Always verify current rules with local authorities and official sources.

Frequently Asked Questions

For Minnesota compliance logs, which statute should be cited as the lead source?
Minn. Stat. section 299F.51 is the central statewide source for Minnesota carbon monoxide alarm duties, including installation obligations, occupancy coverage, and enforcement escalation language. Operators should treat this statute as the primary legal anchor and then apply supporting code rules for technical implementation. Reviewing only one summary page is not enough for defensible compliance. Minnesota teams should cite section 299F.51 directly in policy, training, and inspection documents. In Minnesota, cite section 299F.51 and Minnesota Rules 1309.0315 in each property compliance record.
What properties are covered by Minnesota CO alarm framework?
Minnesota's statutory framework reaches covered homes, rental contexts, and specified lodging scenarios, which means owner-occupants, landlords, and hospitality operators can each carry obligations. Applicability should be mapped by occupancy type and statutory language before turnover or inspection deadlines. Operators managing mixed portfolios should avoid assumptions based on one building class. Minnesota records should document why each property falls inside the section 299F.51 scope. In Minnesota, cite section 299F.51 and Minnesota Rules 1309.0315 in each property compliance record.
Under Minnesota section 299F.50, which sleeping-area locations require alarms?
Minnesota statute requires approved and operational alarms within 10 feet of rooms used for sleeping, with additional implementation detail supported by Minnesota rules 1309.0315 and 7511.0915 in code-applicability contexts. The practical method is room-by-room planning and as-built documentation before occupancy. Teams should capture device model details and exact locations in inspection files. Minnesota enforcement outcomes are generally better when placement decisions are documented with statute and rule references. In Minnesota, cite section 299F.51 and Minnesota Rules 1309.0315 in each property compliance record.
In Minnesota, which steps follow a missed detector correction deadline?
Under Minn. Stat. 299F.51, the first violation follows a warning-oriented path, and repeated violations may escalate to petty-misdemeanor treatment with fines up to $300. Even with this graduated structure, delayed correction can still increase inspection, legal, and liability risk after incidents. Owners should correct deficiencies quickly and keep dated proof of remediation. Minnesota compliance notices should explicitly reference subdivision-level enforcement language. In Minnesota, cite section 299F.51 and Minnesota Rules 1309.0315 in each property compliance record.
For Minnesota leases, which owner and tenant CO tasks should share one log?
Minnesota framework expects owners and landlords to provide required alarms and maintain operability at key occupancy points, while tenants must keep devices in working condition and avoid disabling them during tenancy. This split should be reflected in lease language, move-in checklists, and maintenance ticket procedures. Property managers should keep written records for notices, repairs, and replacements. Minnesota files with clear role documentation are easier to defend during disputes and inspections. In Minnesota, cite section 299F.51 and Minnesota Rules 1309.0315 in each property compliance record.
How do Minnesota rules compare with Wisconsin workflows?
Minnesota relies on a broad statutory baseline in section 299F.51 plus supporting code-rule pathways, while Wisconsin operators may face a different mix of statute and local implementation requirements. Regional teams should keep separate compliance matrices and avoid applying one default process across both states. For nearby benchmarking before finalizing Upper Midwest SOPs, review Wisconsin CO detector laws and compare triggers, penalties, and documentation controls. In Minnesota, cite section 299F.51 and Minnesota Rules 1309.0315 in each property compliance record.

Practical CO Detector Guides

Beyond legal requirements, these guides help you choose, install, and maintain CO alarms:

Advertisement