Intruder Alarm Fault Before Site Closure: What Should Facilities and Security Agree?

Short answer: if an intruder-alarm fault is discovered before a commercial site closes, the facilities lead and security contact should confirm exactly what has failed, which areas or functions are affected, whether the monitoring provider is receiving signals, what temporary controls are authorised, who will respond to further alerts and who can declare the normal arrangement restored. A vague instruction to “watch the building” is not a workable temporary security plan.

The fault may be limited to one detector, communication path or door contact, or it may affect a larger part of the system. Security staff should not diagnose, reprogramme, bypass or repair equipment unless that technical work is specifically within their competence and authority. Their role may instead be to apply an agreed temporary guarding, patrol, access-control or reporting instruction while the responsible alarm company and site management deal with the fault.

This article provides general operational guidance for commercial premises. It is not an alarm-engineering instruction, insurer requirement, police-response guarantee, fire-risk assessment or site-specific security plan.

Confirm the fault rather than relying on a verbal description

Start with the information shown by the system and the responsible provider, not an assumption based on one warning light or message.

Record:

• when and by whom the fault was discovered;
• the alarm panel, area or function identified by the approved site description;
• whether the system can still be set normally;
• whether alarm, tamper and fault signals are reaching the monitoring provider;
• whether any separate transmission path is affected;
• the engineer or maintenance reference and expected next update; and
• who has authority to approve a temporary operating arrangement.

Do not publish zone descriptions, detector positions, codes or the practical limits of the remaining coverage. The working record should be controlled and shared only with people who need it.

The National Protective Security Authority’s guidance for security managers recommends checking intrusion-detection systems for mechanical damage, interference and unexplained fault messages, and notifying the alarm company when damage or a fault is identified. The same guidance explains that documentation, records, maintenance and system handover form part of reliable operation. See the NPSA intrusion-detection guidance.

Separate four different conditions

“The alarm is down” can hide important differences. The temporary plan should distinguish between:

1. A local device fault. One identified component is reporting a fault while other agreed functions remain available.
2. A setting or arming problem. The system will not enter its normal secured state, even if some devices appear to operate.
3. A transmission or monitoring problem. The on-site system may detect an event, but the monitoring centre may not receive or act on it as expected.
4. A wider power, communications or control failure. Several security measures may be affected together, including CCTV, access control, lighting or intercoms.

Each condition creates a different operational question. An audible device that works locally does not prove that a remote monitoring service received the signal. A panel that can be set does not prove that every agreed area is protected. A monitoring-centre acknowledgement does not by itself confirm the physical condition of the premises.

Ask the competent provider to state the known limitation in plain operational language. Security personnel then need an instruction based on that confirmed limitation, not an invitation to make a technical diagnosis.

Decide whether the site can close under the normal plan

The site manager, facilities lead or other authorised decision-maker should determine whether normal closing can proceed. That decision may depend on the affected area, assets, occupancy, insurer conditions, existing guarding, monitoring status and the duration of the fault.

Questions to resolve before the last routine staff leave include:

• Which protective function is unavailable or uncertain?
• Which unaffected controls remain in service?
• Can the site be secured without overriding an unexplained warning?
• Has the monitoring or alarm provider confirmed the current signal status?
• Do any insurer, landlord, contract or internal-security conditions require notification?
• Is an authorised manager accepting the temporary plan and its review time?

Do not ask an officer at the gate or a lone keyholder to carry an undeclared business decision. The assignment instruction should record who accepted the temporary arrangement and what would make it unacceptable.

Define temporary security measures precisely

Temporary measures should respond to the confirmed limitation without exposing sensitive details. Depending on the site assessment, an authorised plan might change guarding hours, add a static post, revise patrol checks, restrict access, arrange a controlled lock-up, maintain management presence or introduce another approved technical measure.

A useful temporary instruction states:

• the start time and review deadline;
• the named decision owner and escalation contacts;
• the officer’s permitted duties;
• the areas or functions described by safe operational identifiers;
• how normal and abnormal conditions are reported;
• what requires immediate escalation;
• how welfare, breaks and lone-working controls are maintained; and
• who can end or extend the temporary arrangement.

“Increase patrols” is incomplete. It does not say what must be observed, how often the arrangement is reviewed, what happens if access is unsafe, or which normal duty is reduced to create capacity. Avoid publishing or casually circulating patrol routes and times.

A periodic patrol is also not the same as continuous guarding, and neither is automatically equivalent to a functioning detection and monitoring system. State what each temporary control can and cannot do.

Keep access control and closing responsibilities aligned

An alarm fault can create pressure to leave doors unlocked for an engineer, share codes more widely or improvise a later entry route. These shortcuts may create a second control problem.

Agree:

• who admits the alarm engineer or other authorised contractor;
• how identity and attendance are verified;
• which person holds responsibility for keys, fobs and temporary credentials;
• whether the contractor is escorted;
• who confirms doors, gates and windows are secured after the visit; and
• how any changed access arrangement is withdrawn at handback.

If locks, codes, fobs or alarm-access details change during the repair, complete a controlled handover rather than relying on a message sent to one person. The separate guide on keyholding after locks or access codes change explains the points to reconcile.

Give the responder an evidence-based escalation route

An activation, tamper warning, new fault or loss of communication during the temporary period should lead to an agreed decision process. The responder needs to know who receives each type of notification, who may authorise attendance and what conditions require withdrawal or emergency assistance.

NPSA control-room guidance emphasises verification, defined escalation conditions, clear response criteria, fallback arrangements and knowing who reports to whom during an incident. These principles remain useful even where a site has no dedicated control room. See the NPSA control-room guidance.

The instruction should not encourage an officer to enter an unassessed area alone simply because an alarm device is unavailable. If the temporary arrangement involves lone working, the employer must manage the associated risks, including training, supervision, monitoring, communication and incident response. The HSE’s lone-working guidance expressly includes security staff among workers who may work without close or direct supervision.

Record decisions without revealing vulnerabilities

The temporary record should be detailed enough for accountability and handover, but not a convenient map of the site’s weakness.

Record:

• the time and source of each fault update;
• the provider or internal reference number;
• the authorised temporary instruction and its owner;
• attendance, calls and significant observations;
• alerts, faults or access exceptions during the period;
• missed or incomplete temporary checks and the reason;
• changes approved during the shift;
• the next review time; and
• the final technical and operational handback.

Use safe identifiers in routine logs. Keep codes, detailed detector information, access arrangements and private contact data in the approved controlled system.

Do not confuse engineer attendance with restoration

The arrival or departure of an engineer does not prove that the normal security arrangement has been restored. Before removing temporary measures, obtain an authorised handback that states what was tested and whether any limitation remains.

Confirm, as applicable:

• the original fault status;
• whether the system sets and unsets through the approved process;
• whether agreed alarm, tamper and fault signals reach the intended recipient;
• whether any temporary bypass or access permission has been removed;
• whether monitoring and response records have been updated;
• who accepts the result on behalf of the site; and
• whether a further repair, test or review remains open.

If a limitation remains, issue a revised temporary instruction with a new decision owner and review time. Do not close the incident because the first work visit ended.

Alarm-fault closing checklist

• Confirm the fault through the responsible provider or competent site contact.
• State which function is affected without circulating sensitive system details.
• Verify whether setting, detection, signalling and monitoring are separately available.
• Identify the authorised person deciding whether normal closure can proceed.
• Check relevant landlord, contract, insurer and monitoring notifications.
• Write the temporary security duties, boundaries and review time.
• Preserve access control for contractors and out-of-hours attendance.
• Maintain welfare, breaks, communication and lone-working safeguards.
• Define verification and escalation for further alerts or faults.
• Record activity using safe identifiers.
• Obtain technical and operational handback before withdrawing temporary measures.
• Keep unresolved items open with an owner and next review date.

Discuss a suitable temporary guarding arrangement

K9 Security Services can consider static guarding, mobile patrol, keyholding and agreed reporting duties for suitable commercial, industrial, construction and vacant sites. The current services overview explains how guarding and technical requirements can be discussed as separate responsibilities within an agreed package.

For an enquiry, use the security quotation form and provide the site postcode, proposed hours, required duties, current access arrangements, the confirmed operational effect of the alarm fault and the people responsible for the alarm system and site decision. Do not send alarm codes, detailed detector locations, hidden access routes or other sensitive vulnerability information in the initial enquiry.

Requirements and availability must be assessed for the individual site, duties, timing and feasibility. This article does not promise a response time, continuous coverage, fault repair or prevention of an incident.

Featured image: illustrative intruder-alarm control panel.