Advertisement

CO Detectors in Virginia: Landlord and Tenant Duties Explained

Last verified: February 17, 2026

Virginia carbon monoxide detector laws are implemented through a combination of landlord-tenant statute and statewide construction code pathways. Virginia Code section 55.1-1229 requires a landlord to install a carbon monoxide alarm within 90 days after a written tenant request if one is not already installed, while section 55.1-1227 prohibits tenant tampering or removal of required alarms.

Technical trigger and placement duties are reinforced through Virginia Construction Code and related residential-code provisions for covered Group I and Group R or dwelling contexts. This creates broad applicability across homes, rentals, and lodging scenarios where code conditions are met.

Virginia operators should maintain written request records, installation documentation, and section-linked inspection notes to reduce dispute and enforcement risk. Tracking local code-edition effective dates in each jurisdiction file further supports compliance readiness.

Quick Safety Summary

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

When Are CO Alarms Required?

  • Buildings with fuel-burning appliances
  • Buildings with attached garages
  • New construction
  • Virginia Code section 55.1-1229 creates a written-tenant-request trigger for landlord installation if an alarm is not already present.
  • Virginia code and construction-code pathways apply by occupancy type and locally enforced edition.

Where to Install CO Alarms

  • Outside each separate sleeping area in the immediate vicinity of bedrooms under residential-code pathways.
  • On each story of covered dwelling units, including basement contexts where required by adopted code language.
  • Additional Group I and Group R placement requirements apply through Virginia Construction Code occupancy provisions.

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

Device Requirements

  • Carbon monoxide alarms listed to applicable recognized standards such as UL 2034 in cited Virginia code pathways.
  • Installation follows code text and manufacturer instructions in the locally enforced edition.
  • Power and interconnection configuration can vary by occupancy and code section, so local edition confirmation is required.

Landlord and Tenant Responsibilities

Landlord: Must install an alarm within 90 days of written tenant request if no alarm is already installed and maintain compliance with applicable code obligations.

Tenant: Must not remove tamper with or disable required alarms under Virginia Code section 55.1-1227.

  • Virginia enforcement is local, so operators should verify the active code edition used by each jurisdiction.

Enforcement

Enforced by: Local building and fire officials administering statewide code in their jurisdictions, with landlord-tenant remedies available under Virginia Code.

Enforcement typically occurs:

  • During permit and inspection workflow for construction-code scenarios.
  • During rental compliance disputes when written request and installation obligations under section 55.1-1229 are at issue.

Penalties for Non-Compliance

Virginia carbon monoxide alarm enforcement is generally handled through local code remedies and landlord-tenant legal remedies, not one statewide stand-alone fine table in the cited sections.

Virginia Code sections 55.1-1227 and 55.1-1229 plus locally enforced construction-code pathways.

Additional Notes

  • Virginia compliance should combine statute and code references because duties arise from both tracks.
  • Owners should preserve written request dates and response dates for section 55.1-1229 compliance.

Official Sources & References

  • Virginia Code section 55.1-1229 — 55.1-1229 (state code, accessed 2026-02-17)
    Landlord installation duty after written tenant request when alarm is not already installed.
  • Virginia Code section 55.1-1227 — 55.1-1227 (state code, accessed 2026-02-17)
    Tenant duties including prohibition on tampering or removal of alarms.
  • 2018 Virginia Construction Code — Group I and Group R carbon monoxide detection provisions including IBC Section 915 pathways (building code, accessed 2026-02-17)
    Statewide technical code source used by local jurisdictions for covered occupancies.
  • 2018 Virginia Residential Code — Residential carbon monoxide alarm location framework including Section R315 pathways (building code, accessed 2026-02-17)
    Residential placement and trigger framework in Virginia local code enforcement context.

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

What Virginia statute creates the landlord installation trigger?
Virginia Code section 55.1-1229 is the key statute for landlord installation timing because it requires installation within 90 days after a written tenant request if no alarm is already installed. This is a concrete legal trigger, not only a best-practice recommendation. Property managers should log request receipt date, installation completion date, and any follow-up communication in the same record. Virginia files with clear timeline evidence are easier to defend during disputes and inspection-related reviews.
What does Virginia code say about tenant tampering?
Virginia Code section 55.1-1227 prohibits tenant removal tampering or disabling of required alarms. This means compliance controls should include tenant communication and documented move-in condition checks, not only owner installation activity. Landlords should keep lease language aligned with the statute and create a clear reporting path for device failures. Virginia operators who document notices and repairs consistently reduce downstream legal and operational risk. Written tenant acknowledgments should be stored with move-in documentation.
Which Virginia occupancies are covered by code-based CO detection?
Virginia Construction Code pathways include coverage for specified Group I and Group R occupancies, while residential code sections apply placement rules in covered dwelling contexts. Because local enforcement applies the statewide code edition by jurisdiction, operators should confirm occupancy classification and active edition before finalizing scope decisions. One generic policy is rarely enough across mixed portfolios. Virginia compliance packets should include occupancy mapping and section citations for each property. This should include dated review notes for any mixed-use occupancy determination.
In Virginia, which enforcement sequence should teams map before assigning penalty risk?
In the cited Virginia sections, enforcement is generally through local code remedies and landlord-tenant legal remedies rather than one stand-alone statewide fine table dedicated only to carbon monoxide alarms. That still creates meaningful exposure when requests are ignored, alarms are missing, or tampering issues remain unresolved. Teams should treat corrective action timelines as high priority and preserve dated proof of completion. Virginia notices should cite sections 55.1-1229 and 55.1-1227 where relevant.
For Virginia all-electric homes, which trigger analysis is required before exemption?
Not always. Virginia applicability depends on occupancy and code-trigger analysis, including attached-garage and other risk conditions in locally enforced code sections. Owners should avoid automatic exemptions based only on utility type and request clarification when scope is unclear. Documenting exemption reasoning with the local authority and governing section text is the safer approach. Virginia records should store that reasoning with turnover and maintenance documents. Keep the approving authority and date in the same record.
Which Virginia policy control differs most from Maryland in mixed-state portfolios?
Virginia in this dataset combines landlord-request statute triggers with code-based occupancy enforcement, while Maryland portfolios can follow a different statutory and implementation mix. Regional teams should use separate Mid-Atlantic matrices rather than one shared template. For side-by-side planning, review Maryland CO detector laws and compare trigger timing, role allocation, and documentation controls. Virginia teams should keep request-trigger logs distinct from Maryland workflow records. Include jurisdiction-specific enforcement contacts in each state packet.

Practical CO Detector Guides

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

Advertisement