Rochester, Minn., Code of Ordinances § 7 § 7-4-37
Basement hatchways (Rochester Housing Code)
Operative Text
Every basement hatchway shall be maintained to prevent the entrance of rodents, rain and surface drainage water.
Rochester, Minn., Code of Ordinances § 7 § 7-4-37 requires that every basement hatchway in a residential property be kept in a condition that blocks rodents, rain, and surface drainage water from entering. The rule applies continuously—it is a maintenance standard, not a one-time installation requirement. Any hatchway that allows these intrusions is considered out of compliance with the ordinance.
Plain English — not legal advice.
Under Rochester, Minn., Code of Ordinances § 7 § 7-4-37, compliant property operators routinely inspect basement hatchways for gaps, deteriorated seals, and drainage deficiencies that could allow rodent entry or water infiltration. Operators generally document inspections and repair or replace hatchway components—such as weatherstripping, frames, and covers—before deficiencies become violations. Keeping maintenance records tied to this provision can help demonstrate ongoing compliance during city inspections.
General guidance for property managers — not legal advice for your specific situation. Consult an attorney for advice on your case.
Rochester, Minn., Code of Ordinances § 7 § 7-4-37 gives tenants a basis to expect that basement hatchways are maintained against rodent entry and water intrusion. If a hatchway appears to be failing—allowing pests or water into the building—tenants may document the condition with photographs and dates, then report the issue to Rochester's code enforcement office. Tenant-rights organizations familiar with local housing codes can also help residents understand available options, including whether a violation can be raised in other housing proceedings.
General guidance for tenants — not legal advice for your specific situation. Consult a tenant-rights organization or attorney for advice on your case.
Generated September 15, 2026 — auto-generated, not yet human-reviewed. See /transparency for methodology.
Effective Timeline
References Out
No outbound references recorded yet for this provision.
References In
No inbound references recorded yet for this provision.