Fire Alarm Report Template: What Engineers Should Include

Short answer: a fire alarm service or fault report needs to accurately reflect what you did, what you found, and what you recommend — nothing more, nothing less. Overclaiming and underdocumenting are both liabilities.

This guide covers the sections a competent engineer's report should contain, what to write in each, and what to avoid.

Who This Is For

Fire alarm engineers writing reactive fault reports, planned maintenance reports, or commissioning notes. The goal is documentation that protects you professionally, informs the client clearly, and stands up to review under BS 5839-1.

Why Good Reports Matter

A poorly written report creates problems in both directions. An overclaiming report ("system is fully compliant") asserts something you may not be able to verify in a single visit. An underdocumenting report ("attended and cleared fault") creates no evidence trail if something goes wrong later.

BS 5839-1 requires that all service visits, fault investigations, and remedial works are documented in the system log book. Your report is the written evidence of your professional work.

Report Sections

1. Site Details

Every report needs unambiguous identification of the site and system:

• Site name and address
• Client or responsible person name
• Panel manufacturer and model
• Panel location (for multi-panel sites: which panel)
• System reference or contract number if applicable
• Date and time of attendance
• Engineer name and company

Do not assume the office knows which panel you attended on a multi-site estate. Be explicit.

2. Reason for Attendance

One sentence stating why you were on site:

• "Reactive attendance to fault condition: Loop 1 Earth Fault."
• "Planned six-monthly service visit."
• "Commissioning of new first-floor zone extension."

This establishes the scope of the visit. Everything in the report flows from this.

3. Observations

What you found on arrival, before any work was carried out:

• Panel condition (normal, faulted, in alarm, partially disabled)
• Any existing faults displayed
• Any visual damage, evidence of recent works by others, or environmental concerns
• Log book condition — was it present and up to date?

Write what you observed, not what you assumed. "Panel displayed Loop 2 Earth Fault on arrival" is correct. "Panel had been in fault for several days" is an assumption unless you checked the log.

4. Tests Carried Out and Results

The core of the report — what you actually did:

• List each test or investigation action
• Record the result of each
• Include device addresses, zone numbers, or circuit references where relevant
• For fault investigations: the diagnostic steps taken and what each revealed

Example format:

• "Insulation resistance test carried out on Loop 1: 450 MΩ phase-to-earth with all devices disconnected. Fault persisting on reconnection of devices 1–35."
• "Isolated Loop 1 at Address 24 isolator module — fault cleared in section 25–64."
• "Fault located to junction box at second floor, west corridor: loose termination on A conductor."

Do not write vague entries like "tested system" or "carried out investigation". Record specifically what you tested and what the result was.

5. Work Carried Out

What remedial or service work was done:

• Describe the repair or action taken
• Note any materials used (replacement device model, cable joint type, etc.)
• State whether the system was restored to full operation at the end of the visit

If the work was a planned maintenance visit, list the elements covered — devices tested, outputs verified, battery checked, logbook updated.

6. Outstanding Items and Limitations

Anything you could not test, access, or complete on this visit:

• Areas that were inaccessible (locked room, occupied space)
• Devices that could not be tested (patient areas in hospitals, production areas in factories)
• Work that requires parts on order or a follow-up visit
• Any items noted that fall outside your contracted scope

Phrasing example: "Devices in Server Room B (Addresses 67–72) could not be tested — room locked. Recommend client arranges access for follow-up testing."

This section protects you. If a fault occurs in an area you documented as inaccessible, the report shows you flagged it.

7. Recommendations

Professional observations and recommended actions:

• Devices approaching end of service life
• Environmental conditions affecting system performance
• System design concerns identified
• Suggested works outside the current contract scope

Phrase recommendations as recommendations, not requirements, unless you are citing a specific mandatory standard clause. "It is recommended that..." is accurate. "The system is non-compliant because..." requires specific evidence and a standards clause reference.

8. System Status on Departure

One line stating the condition of the system when you left:

• "System restored to full operation. No active faults on departure."
• "System partially restored. Loop 2 disabled pending replacement device. Client notified and fire watch procedure confirmed."

Do not leave a site without recording the system state at handover.

What Not to Write

• "System is compliant" — unless you have completed a full compliance assessment against the applicable standard. A reactive fault call does not constitute a compliance assessment.
• Vague time entries — "attended and cleared fault" tells the client nothing and protects you even less.
• Copied boilerplate — A report that doesn't match what actually happened on site is worse than a brief report. Copy the structure, not the content.

How Incognito Fire & Security Helps

The report writer generates structured draft reports based on your site and fault inputs. You edit to reflect actual work, then export.

Open the report writer →

Disclaimer

This article is a workflow support resource. Reports must accurately reflect actual work completed and applicable contractual, professional, and legal duties. This guide does not constitute legal or professional advice. Consult your employer, professional body, or legal adviser for specific requirements.

Next Step

Try the report writer → or start a free trial to access report drafting on site.