What should alarm response records capture?

An alarm response is hard to explain later if the only record is that someone went to site. Managers need a clear view of which site was called, what the officer was sent to do, what they found, which keys moved, when they arrived against the contracted time, and what the client can see afterwards. NightWarden can hold the site record, raise an alarm response dispatch, generate the run sheet, store on-site checks with photos and timestamps, log key issue and return, and show the closed job to the client. People and procedures still decide how to respond, whether the premises are safe, and what happens next.

The detail of how NightWarden does this is on the keyholding management software page. Use the points below as operational guidance for what an alarm response record should contain, not as a replacement for your written response procedure or legal advice.

Keep the site record current before the call-out

The response record starts before the alarm. In NightWarden, each client site can hold access notes, alarm panel notes, contact lists, key inventory and response protocols. Access notes and panel notes are stored on the site, and field staff access is controlled by shift assignment. Contact hierarchies are on the same site record.

If those notes are out of date, the officer and the control room are working from the wrong instructions. Someone still has to confirm that the site record matches the current keyholding contract, including who should be called and what the response protocol says.

Record the dispatch and the run sheet

In NightWarden, alarm response dispatch is a one-tap dispatch. The run sheet for that job is generated from the site record when the dispatch is raised. Control room staff can see progress on the job.

That run sheet is the record of what the officer was sent to do, and which site the dispatch pointed at. A job with no run sheet, or a run sheet for the wrong site, leaves a gap that a later note cannot honestly fill. Someone still has to raise the dispatch against the right site record.

Record the checks, photos and times on site

On the job, the officer completes each step in NightWarden. Those steps are the external check, the internal check and re-securing the premises, with photo evidence and GPS-stamped timestamps. A structured incident report can carry photo attachments. It is timestamped and signed off by the attending officer on the mobile app.

Completed task records keep the date and time, the staff member who completed the work, and the evidence attached to it, such as a form, photos or checkpoint scans.

For an alarm response form, the date and time on the completed report should be the operational arrival, not only the moment the form was submitted. On a partner-owned form, set the arrival date field billing role to Arrival Date and the arrival time field billing role to Arrival Time. Those roles take priority when NightWarden fills Date of Task and Time of Task. If the call-out crosses midnight and you record duration, also set Departure Date and Departure Time on the matching departure fields. NightWarden system templates are read-only for partners, so change a partner-owned copy. Do not put Arrival Date or Arrival Time on fields you do not want shown as the task time. Those form fields are not the same thing as the GPS-stamped timestamps on the steps.

A form is not added to the incident count on its own. In Form Builder, the switch to count submissions from that form as incidents controls only the Operations Pulse incidents count. Leave it off for forms that should not be counted as incidents.

Record keys issued and returned

Alarm response often depends on which key set left the office and whether it came back. NightWarden tracks key sets by site, records each issue and return, and can produce a chain of custody log. Keys marked overdue raise an alert. A lost key incident can be logged with evidence attached.

In Key Checks, the register for a site shows the key reference, who currently holds it, and when it was last checked. When a key is issued, the staff member is asked to acknowledge receipt in the Field app. That acknowledgement is stored for audit. Returning a key is recorded on the same register. Monthly checks and quarterly audits reconcile the keys held. They do not replace the issue and return line for a single call-out.

Record arrival against the contracted SLA

NightWarden calculates arrival time against the contracted SLA for the site, raises a breach alert, and can produce a monthly SLA summary. The site record can also hold the keyholding contract dates, the SLA terms and the billing schedule, so the comparison uses the SLA term you have stored.

The portfolio view can show activation frequency, SLA performance and upcoming contract renewals, including which sites had activations and which SLAs were met. That is a management view of what was recorded. It does not decide that the response was adequate, and it does not choose the contracted time for you.

Do not type a target into the record if the contract does not state one. The record should show the arrival that was captured and the SLA term you stored. It is not a police response time, and it is not a promise that an officer will attend.

Pass a completed report to the client

On the keyholding management software page, the completed report is available to the client on their portal within minutes of the job closing. Through that portal, clients can open completed response reports, key register summaries and SLA performance.

Partners can also open the submission under Completed Reports, download a PDF, or create a share link that can be set to expire. Those are actions a partner takes on a stored report. They are a different route from the client portal. Check that the job was closed and that the site and officer on the report are the ones who attended.

Service Reports can include alarm response for a period you choose, with shift, report or checkpoint information where that output is available, and can generate a PDF from the selected data. Use the same dates and service filters if you compare that export with other operational records. The export is not a staff pay calculation.

Honest limits

NightWarden can store site instructions, dispatch a run sheet, keep photos and timestamps, log keys and compare arrival with an SLA you have recorded. It does not replace human judgement, risk assessment or the procedures managers follow when an alarm comes in, when a building does not look secure, or when a key is missing.

A form draft held on the officer's phone during a loss of signal is not a completed report. Pending submissions sync when the phone is online and the officer is still signed in. Until that submitted item is visible in history, do not treat the draft as progress the control room or the client can already see.

The software does not attend the site and does not decide whether to enter. It does not guarantee that an insurer, a client or an auditor will accept the record. What you can show is what was captured and saved.

NightWarden is software for field operations. It does not supply officers or attend sites for you.

Next step

Write down what your alarm response procedure already expects a record to contain: site instructions, dispatch, on-site checks, times, photos, keys, SLA arrival and the client report. Then compare that list with the site record, alarm response dispatch, key register and client portal in NightWarden. See how it works on the keyholding management software page, or start from the NightWarden homepage if you want a demonstration against your response procedure.