Informational
Panic Button Testing and Maintenance
Maintenance
Testing schedule
| When | What to test | Who should know |
|---|---|---|
| At installation | Every button, every zone name, every alert recipient and every reset process. | Installer, owner, family, manager or monitoring provider. |
| Monthly or quarterly | Button activation, notification delivery, batteries and response notes. | Responsible person and backup responder. |
| After furniture or fit-out changes | Reachability, wireless range and visibility. | Resident, staff or site manager. |
| After a real event | What worked, what was slow and what confused people. | All relevant responders. |
Test method
- Tell responders or monitoring that a test is about to happen.
- Press the button from the real position, not from a comfortable standing position.
- Confirm which alert appeared and how long it took.
- Confirm who received the alert and whether backups were notified.
- Reset the system and document the result.
- Fix any weak point before relying on the system again.
Maintenance checklist
- Button batteries are checked and replaced on schedule.
- Panel backup battery and communications path are understood.
- Internet, SIM and monitoring accounts are paid and owned by the right person.
- App users are current and old staff or family members are removed.
- Zone names still match the physical site.
- Buttons are not blocked by furniture, stock, blankets, equipment or mobility aids.
- Written response plan is current.
The system worked last year, but the room changed
A bedside table moved, a counter was replaced, or a staff desk changed position. That is enough to make a once-good panic button hard to reach or visible to the wrong person. Retesting after layout changes is one of the simplest ways to avoid failure.
FAQ
How often should panic buttons be tested?
At installation, after any changes and on a regular schedule. Monthly is sensible for higher-risk sites; quarterly may suit lower-risk homes or offices.
Should I test with monitoring connected?
Yes, but notify the monitoring provider first and follow their test process so emergency escalation is not triggered by mistake.
What should be recorded?
Date, button location, alert recipient, result, battery status, faults found and actions taken.
Test records worth keeping
Good records turn maintenance from memory into evidence. Keep a simple log that can be understood by family, staff, installers or a monitoring provider. For a vulnerable person or higher-risk business, recordkeeping can also show that the system was not installed and forgotten.
| Record | Example detail |
|---|---|
| Date and tester | 9 June 2026, manager or family member name. |
| Button tested | Reception under-desk, bedside, wearable, safe room or portable remote. |
| Alert result | Who received it, how quickly, and what zone name appeared. |
| Fault found | Battery low, blocked button, old app user, wrong contact or range issue. |
| Action taken | Battery replaced, contact updated, button moved or installer booked. |
After staff or family changes
- Remove old app users and add new authorised responders.
- Update monitoring contacts and after-hours contacts.
- Retest every button with the new responder list.
- Reissue the response plan to staff, family or carers.
- Check whether keys, intercom access or site notes have changed.
When to call an installer back
- Repeated missed alerts, range faults or low-battery warnings.
- Button locations no longer match furniture, counter layout or user mobility.
- The site adds monitoring, CCTV or extra buildings.
- A real incident shows the response path was too slow or unclear.
- The system has not been tested for a long period and nobody is sure how it behaves.