Are CO Detectors Required in Utah Rentals?

Utah's carbon monoxide detector requirements for rentals are embedded in Title 15A of the Utah Code, which contains the state's amendments to nationally adopted building and fire codes. The two primary sections are §15A-3-202, which amends IRC Section R315 for residential construction, and §15A-5-205.5, which amends IFC Chapter 11 §1103.9 for existing buildings. This two-track model means that CO alarm obligations depend on whether the rental is new construction, permit-triggered retrofit work, or an existing building that falls into a covered occupancy group.

For new residential construction and building-permit work, §15A-3-202 requires CO alarms on each level of the dwelling unit, following the IRC R315 framework as amended by Utah. For existing buildings, §15A-5-205.5 brings Group E, I, and R occupancies into the IFC §1103.9 retrofit pathway, which can require CO detection in occupied buildings that were not originally built to current alarm standards. The practical result is that many Utah rental properties, including apartments, leased single-family homes, and ADUs built or modified under permit, fall within one or both code tracks. Utah does not use a single standalone CO statute the way some states do; instead, the obligation flows through the state's adopted code amendment structure.

Utah's CO alarm requirements apply broadly to dwelling units covered by the state's adopted IRC and IFC amendments. In practice, that includes single-family rental homes, apartments, duplexes, and accessory dwelling units when the building is new construction, undergoes permit-triggered work, or falls within a Group R occupancy classification under the fire code pathway. ADU applicability is worth highlighting because Utah's building code amendments do not carve out accessory units from the level-based alarm requirement when a permit is pulled.

The IFC existing-building track also reaches Group E (educational) and Group I (institutional) occupancies, though most rental operators will encounter the Group R classification. Hotels and transient lodging generally fall under the same IFC pathway, but the operational details for those occupancies belong on the hotel/STR page. The coverage question for any specific Utah rental turns on the construction history, permit record, and occupancy classification, not solely on the lease type or property size.

Utah's code framework places the CO alarm compliance duty on covered owners and lessors. For rental properties, that means the landlord or property owner is responsible for ensuring that required CO devices are installed and maintained in compliance with the applicable code track, whether the obligation arises from the IRC residential path under §15A-3-202 or the IFC existing-building path under §15A-5-205.5.

The landlord's core duty is installation on each level of the dwelling unit in properties subject to the IRC R315 amendments. For existing Group R occupancies subject to the IFC retrofit pathway, the owner must bring the building into compliance with the applicable alarm provisions. In both cases, the responsibility does not shift to the tenant. The owner or lessor remains the party that local code officials and the State Fire Marshal Division will look to when evaluating compliance.

Practical compliance for Utah landlords means documenting installation during new construction or permit work, verifying alarm presence and operability during unit turns, and tracking device age for end-of-life replacement. Because Utah's code tracks are tied to construction and permitting events, a landlord who pulls a permit for renovation, addition, or ADU conversion should treat the CO alarm requirement as an automatic part of the scope of work rather than a separate compliance question to address later.

Utah's CO alarm code sections do not assign specific responsibilities to tenants. Neither §15A-3-202 nor §15A-5-205.5 includes tenant reporting duties, maintenance obligations, or a notification requirement comparable to what some states impose. The compliance obligation remains with the owner or lessor under the adopted code framework.

That statutory silence does not mean tenants have no practical role. If a CO alarm is missing, beeping, or visibly damaged, reporting the issue to the landlord or property manager is a reasonable safety step. Tenants should avoid removing or disabling CO devices, even if nuisance alarms occur, and should document any communication about alarm condition in writing. A written maintenance request creates a record that can matter if a dispute arises about whether the landlord was notified of a deficiency. While Utah law does not create a tenant enforcement pathway tied to CO alarms, tenant awareness and timely reporting remain important parts of the life-safety chain in any occupied rental.

Utah's IRC R315 amendments under §15A-3-202 require CO alarms on each level of the dwelling unit. That level-based placement rule is the primary installation standard for new residential construction and permit-triggered work. The alarm must be located where it can detect CO accumulation on each habitable level, consistent with the IRC framework as adopted by Utah.

Device standards follow the adopted IRC and IFC provisions within Title 15A. Alarms must comply with the listing and approval requirements referenced in the applicable code section. For Group E occupancies, §15A-5-205.5 also includes a provision requiring system testing before final approval by the fire marshal, a detail that matters for educational facilities but may also signal the level of rigor Utah applies to CO detection systems in covered buildings.

Combination smoke/CO alarms are generally acceptable when they meet the listing standards referenced in the adopted code. Landlords should follow manufacturer instructions for mounting height and distance from appliances in addition to the code-level placement baseline.

Utah's code sections do not prescribe a specific move-in verification checklist, a recurring testing schedule, or a landlord entry provision tied to CO alarm service. These operational details are left to general landlord-tenant law and local code enforcement practices rather than being embedded in the CO-specific code amendments.

For landlords managing Utah rentals, the absence of a statutory testing cadence does not eliminate the need for operational maintenance. CO alarms have a finite lifespan, typically seven to ten years, and devices installed during original construction or a previous permit cycle may need replacement. Documenting alarm condition during unit turns, replacing expired devices, and keeping records of battery changes or hardwired system checks are prudent practices that demonstrate ongoing code compliance.

Landlord entry for CO alarm work in Utah follows general landlord-tenant access principles. Reasonable notice and documented maintenance visits help establish that the owner is maintaining the building in compliance with the applicable code track, even though the CO alarm provisions themselves do not include a specific entry mechanism.

Enforcement of Utah's CO alarm requirements falls to local code officials and the Utah State Fire Marshal Division. Compliance is most commonly verified during the building permit and inspection process, meaning new construction, additions, renovations, and ADU conversions are the primary enforcement touchpoints. The IFC existing-building pathway may also trigger enforcement when a local fire official inspects a Group R occupancy and identifies a missing or deficient alarm.

No provision names carbon monoxide as a tenant remedy, and the Fit Premises Act nonetheless reaches an alarm by a route worth following, because where it lands decides how long the owner gets.

Utah Code 57-22-3(1) makes the owner maintain the unit in accordance with local ordinances and the rules of the board of health. Utah's statewide code adoption under Title 15A amends IFC Section 1103.9 to require carbon monoxide detection in specified existing Group R occupancies, so a code-required alarm arrives inside that duty rather than beside it. Then 57-22-6(1)(g) defines a standard of habitability by listing which duties count: 57-22-3(1) and 57-22-4(1)(a) and (b)(i) to (iii), and it leaves out (b)(iv), the paragraph covering other appliances and facilities specifically contracted for in the rental agreement.

The consequence is a fork most tenants never see. An alarm the code requires is a standard of habitability and the owner gets three calendar days to take substantial action. An alarm promised only by the lease is not, and the owner gets ten. Calendar days rather than business days, so a Friday notice can spend most of its life on a weekend.

The remedies themselves are in 57-22-6(4)(a), and the renter elects one in the notice rather than afterwards. Subparagraph (ii) is a repair-and-deduct with a ceiling of two months' rent, which is perhaps fifty times what an alarm costs, so the cap is not the constraint; the conditions are procedural, meaning elect it in the notice, keep every receipt, and give the owner copies. Subparagraph (i) is called rent abatement and is not what the name suggests: rent abates from the date of the notice and the rental agreement terminates with it, the owner must return the whole security deposit immediately and prorate any prepaid rent. There is no free-standing right to terminate for a defect, which is why termination and abatement cite the same subsection.

The notice is where this succeeds or fails. It has to describe each deficient condition, state the corrective period in terms of the applicable number of days, name the remedy the renter has chosen, and give the owner permission to enter to correct it. Local building or fire code enforcement and the State Fire Marshal Division remain the other route, and they work on the building rather than on the tenancy.

One caution on vintage. 57-22-6 was read as amended in 2023 and was amended again by chapter 445 of the 2026 session; the corrective periods and the two-months ceiling above are unchanged in the currently published text, and anyone relying on a figure here should confirm it against the current chapter.

The cited sections of Utah Title 15A, §15A-3-202 and §15A-5-205.5, do not include a standalone CO-specific fine schedule or penalty provision. This distinguishes Utah from states that impose per-offense monetary fines for missing detectors. Enforcement is handled through the general building and fire code compliance framework, which operates through the permit, inspection, and correction process administered by local officials and the State Fire Marshal Division.

The absence of a dedicated penalty does not eliminate landlord risk. If a CO incident occurs in a rental that should have had alarms under the applicable code track, the missing devices could become evidence in a negligence or liability claim. Landlords should treat the requirement as binding regardless of the penalty structure.