Skip to main content
← Back to blog
Engineer WorkflowFire Alarm EngineerService HistoryReportsFault Diagnosis16 July 20262 min read

What a useful fire alarm site file vault should contain

What a useful fire alarm site file vault should contain: practical guidance for fire alarm engineers on evidence, reports, service history and safer diagno

By Incognito Fire & Security

What a useful fire alarm site file vault should contain

A site file vault should answer engineering questions, not just store documents.

Use this article as engineering support only. It does not replace competent inspection, current manufacturer documentation, site procedures, risk assessment or the applicable standards.

The engineering problem

Fire alarm work is rarely blocked by a complete lack of information. The bigger problem is that useful information is scattered across worksheets, photos, old reports, panel event logs, WhatsApp messages, office memory and the experience of whoever attended last time.

When that context is missing, every visit starts from zero. The engineer has to reconstruct the site, repeat checks that may already have been done, and write a report with limited evidence.

What engineers should capture

  • Exact panel message, time, date and whether the condition is current or historic.
  • Zone, loop, address, device label and physical location.
  • Recent works, environmental conditions and customer observations.
  • Measurements taken, assumptions used and test results.
  • What was isolated, reinstated, replaced or left outstanding.
  • Any limitation that affects the confidence of the diagnosis.

Practical workflow

  1. Preserve the symptom before resetting, replacing or isolating anything.
  2. Check the panel history and compare it against previous service notes.
  3. Confirm whether the issue is device, circuit, configuration, power, environment or user-process related.
  4. Record evidence in a way that the next engineer can search and understand.
  5. Convert the findings into a clear customer-facing report with limitations and next actions.

Where Incognito Fire & Security fits

Incognito Fire & Security is being built to keep diagnosis, calculations, reports, site files and service history connected. The goal is not to replace judgement. The goal is to make competent judgement easier to apply when the engineer is under time pressure on site.

Use the platform to structure fault notes, keep assumptions with calculations, save site context and turn engineering evidence into a usable report.

Related workflows

  • AI-assisted fault diagnosis for structuring checks and evidence.
  • Fault database for common causes and investigation prompts.
  • Battery and voltage-drop calculators for preserving assumptions.
  • Report writer for turning site notes into customer-ready wording.
  • Site file vault for keeping drawings, cause-and-effect notes and history together.

Bottom line

The vault is useful when it connects drawings, reports, faults, calculations and limitations.

Create a free Incognito Fire & Security account to save notes, run calculations and generate better fire alarm reports.

Frequently asked questions

Can what a useful fire alarm site file vault should contain replace competent engineer judgement?

No. Incognito Fire & Security is designed as a support tool. The competent engineer must verify the site, system, manufacturer guidance and applicable standards.

How does Incognito Fire & Security help with this workflow?

It helps structure evidence, save site history, run calculations where relevant and generate clearer reports from engineering notes.

Put this into practice on site

The Incognito F&S fault database and AI assistant give you structured diagnostic guidance for any fault — from any of 24 manufacturers — live at the panel.

5 free AI questions/day — no card required