Missing Fire Alarm System Description? An Ontario Owner’s Checklist

A contractor asks for your building’s fire alarm system description, but the file you have contains only last year’s inspection report and a few service invoices. What should you do next?

For Ontario owners and property managers, the practical first step is to find out whether the description is missing, stored elsewhere or no longer matches the installed system. Tell your fire alarm provider about the gap before the next visit so the documentation work can be scoped properly.

What does Ontario require?

Ontario Fire Code Division B, Sentence 6.3.2.2.(3) requires the fire alarm system description specified by CAN/ULC-S536 to be kept current and maintained in the building at an approved location. Ontario’s referenced edition is CAN/ULC-S536-2019. The wording and reference are set out in O. Reg. 303/25; check the current Fire Code for the requirements that apply.

The standard determines the required description. A generic online checklist cannot establish that your document is complete. Ask a qualified fire alarm provider to assess the records against the installed system and applicable requirements.

Look for the existing document first

As a practical records check, ask the current and previous property managers, the installing contractor and the inspection provider whether they hold the system description. Check the building’s fire alarm documentation, project handover files and previous service packages.

Record the document’s date or revision and the property it covers. If several addresses share equipment, ask the provider to clarify the coverage. Finding a file is useful, but its title alone does not show that it reflects the current building.

Gather the information needed to check it

To help the provider assess the gap, gather what you already have:

• The building address, current use and panel make and model, if known.
• Existing system descriptions, drawings, device lists and verification documents.
• The latest inspection report and records of later repairs or alterations.
• Details of renovations, renamed rooms, added devices or changed equipment.
• A contact who can arrange access to the relevant areas.

This is a preparation list, not a substitute for the technical information required by the standard. Label missing or uncertain information clearly. Do not guess device details or copy another building’s description to fill the gaps.

Agree on the documentation work

Ask the provider what can be established from existing records and what needs a site assessment. Confirm whether the proposed service includes locating, checking, preparing or updating the description, and which other records may need attention.

Useful questions include: Which system and areas will the document cover? What information is still needed? Who will prepare the update? Where should the current version be kept? Does the proposed work also involve separate inspection, testing, repair or verification?

Keep those scopes clear in the quote. Updating a document does not demonstrate that equipment passed its required tests or that an unresolved fault has been repaired.

Keep it current through the next change

Include documentation in the handover whenever alarm equipment or relevant building information changes. Ask the responsible provider whether the description needs updating, identify the current version and make sure the building team knows its approved location.

If you also have an active trouble indication or impaired protection, report that promptly through the building’s authorized procedures. A records search should not delay attention to a safety problem. Do not open equipment, disconnect devices or change panel controls to gather information.

Discuss missing fire alarm records with FC Fire

Use our contact page to share the property address, panel details and which records you have. FC Fire Prevention can discuss the appropriate fire alarm service and documentation scope for your Toronto or GTA property.

Owner planning guidance. Technical work must follow the applicable requirements and system documentation.