Okla. Admin. Code § 265:10 § 265:10-5-4

Equipment

In Force
Verified 10/17/2026 · Next check 10/24/2026
effective 9/12/2014OklahomaCO & Smoke Alarms

Operative Text

Okla. Admin. Code § 265:10 § 265:10-5-4
(a) All devices, combination of devices and equipment to be installed in conformity with the edition of National Fire Protection Association (N.F.P.A) Standard #72 as referenced by the building codes most recently adopted by the Oklahoma Uniform Building Code Commission and shall be approved or listed and installed for the purpose for which they are intended.
(b) A device or system of devices having materials or forms different from those detailed in N.F.P.A. Standard #72 may be examined and tested according to the intent of these standards and, if found equivalent, may be approved.
Source: Legislative text reproduced verbatim
Plain English

Oklahoma Administrative Code § 265:10-5-4 establishes that fire alarm and detection equipment must conform to the edition of NFPA Standard #72 referenced by the building codes most recently adopted by the Oklahoma Uniform Building Code Commission, and all devices must be approved, listed, and installed for their intended purpose. The rule also provides a pathway for alternative devices or systems that differ in materials or form from NFPA #72 specifications: such equipment may be examined and tested against the intent of the standard and, if found equivalent, may be approved. This provision governs both standard and non-standard equipment, ensuring a consistent baseline for fire protection technology used in covered buildings.

Written by anthropic/claude-sonnet-4.6 · Reviewed on October 17, 2026

Plain English — not legal advice.

For Property Managers

Property owners and managers operating under Oklahoma Administrative Code § 265:10-5-4 generally ensure that all fire alarm devices and systems they install carry proper approval or listing and are installed specifically for their intended use, in accordance with the applicable edition of NFPA Standard #72. When considering equipment that differs in materials or design from NFPA #72 specifications, compliant operators typically pursue the equivalency review and testing process before installation rather than assuming the equipment qualifies. Maintaining documentation of device listings, approvals, and installation records is a common practice that supports demonstrating compliance during inspections.

General guidance for property managers — not legal advice for your specific situation. Consult an attorney for advice on your case.

For Tenants

Under Oklahoma Administrative Code § 265:10-5-4, tenants have an interest in knowing that fire alarm and detection equipment in their building is required to meet NFPA Standard #72 as adopted by the Oklahoma Uniform Building Code Commission, and must be properly approved and installed for its intended purpose. If a tenant has concerns that fire alarm equipment in their unit or building does not appear to meet these standards, general enforcement paths include contacting the local fire marshal's office or the relevant building code authority, or reaching out to a tenant-rights organization for guidance. Tenants may also raise equipment compliance under § 265:10-5-4 as a relevant issue when reporting habitability or safety concerns to the appropriate local or state authority.

General guidance for tenants — not legal advice for your specific situation. Consult a tenant-rights organization or attorney for advice on your case.

Generated October 17, 2026 — auto-generated, not yet human-reviewed. See /transparency for methodology.

Effective Timeline

Current
Sep 12, 2014
Click on timeline segments to view historical versions.

References Out

No outbound references recorded yet for this provision.

References In

Rules and statutes that cite this regulation

Okla. Admin. Code § 265:10-3-4

Related Rules

§ 26C
Certain public accommodations; automatic smoke or heat detectors
§ 26D
Definitions applicable to Secs. 26D to 26F
§ 26E
Residential buildings or structures; installation of smoke detectors

Source Information

Snapshot SHA:
Fetched:Oct 17, 2026, 09:23 PM UTC