Smoke and Carbon Monoxide Alarm Compliance Log (Public Housing)

It records whether smoke alarms and carbon monoxide alarms are present where required, properly located, powered correctly, and able to activate during testing. It also captures visible condition, device identification, maintenance status, and any corrective actions. Use it as the inspection record for a unit, common area, or other inspected area under a housing authority’s compliance process.

Use it during scheduled unit inspections, move-in or move-out checks, annual compliance reviews, and follow-up visits after a deficiency is found. It is also useful after alarm replacement work to confirm the new device is installed, labeled, and functional. If the property has a recurring issue with missing or inoperative alarms, this log helps standardize the recheck.

It is typically completed by housing authority staff, property management personnel, maintenance supervisors, or a designated inspector who is responsible for compliance verification. The person completing it should be able to identify required alarm locations, confirm device type, and document deficiencies clearly. If local policy requires it, a qualified maintenance technician can complete the corrective-action portion.

This template is designed to support NSPIRE-style inspection documentation for life-safety devices in public housing. It also aligns with the broader expectation that smoke alarms and carbon monoxide alarms be present, functional, and maintained in accordance with applicable housing rules and local code requirements. If local fire code or landlord-tenant rules are stricter, the stricter requirement should govern.

Common mistakes include recording only that an alarm exists without noting its exact location, failing to identify whether the device is hardwired or sealed 10-year battery, and skipping the manufacture or replacement date. Another frequent issue is documenting a failed test without assigning a due date or responsible party. The log works best when every deficiency is tied to a specific device and room.

Yes. You can adapt it for family units, senior housing, scattered-site properties, or mixed portfolios by changing the inspection area labels and adding property-specific fields. Some housing authorities also add fields for local code references, contractor work order numbers, or photo attachments. Keep the core fields for location, power source, test result, and corrective action so the record stays consistent.

Yes, it pairs well with work order systems because failed alarms usually require a repair or replacement task. Many teams use the log as the field record and then create a work order from the deficiency entry. If your software supports attachments, add photos of the device, the location, and any end-of-life indicator to strengthen the audit trail.

The inspection cadence should follow your housing authority policy, lease requirements, and any applicable local or state rules. Many programs check alarms during scheduled unit inspections and again after maintenance work that could affect the device. If a device is replaced or a deficiency is found, it should be retested before the unit is closed out.