Most facility intrusion detection systems should be inspected at least monthly, with certain components requiring weekly or even more frequent checks. The exact schedule depends on the type of sensors, the environment they operate in, and any regulatory or insurance requirements your facility must meet. There is no single universal mandate, but industry standards and equipment manufacturers converge on a layered inspection schedule where different components get checked at different intervals.
The Weekly, Monthly, and Annual Framework
Intrusion detection system inspections aren’t a single task you do on one calendar date. They break down into tiers based on how quickly each component can fail or drift out of alignment. A practical schedule looks like this:
- Weekly: Walk-test motion sensors. Johnson Controls, one of the largest security equipment manufacturers, instructs users to walk-test PIR (passive infrared) detectors at least once a week to verify proper function. This means physically walking across the far end of each sensor’s coverage area and confirming it registers the movement.
- Monthly: Test all alarm points (door contacts, window sensors, glass break detectors), verify the control panel displays correctly, check that the keypad and arming/disarming functions work, and confirm backup power is charged.
- Quarterly or semi-annually: Perform a full system audit including communication link tests, battery load tests, and a review of all system logs for anomalies.
- Annually: Have a qualified technician conduct a comprehensive inspection of all wiring, sensor alignment, panel firmware, and communication equipment. This is also when batteries are typically replaced regardless of test results.
Communication Link Testing
Your intrusion detection system is only useful if its alarm signals actually reach the monitoring center. The communication link between your facility’s alarm panel and the central station needs regular verification. The National Fire Protection Association notes that depending on the transmission method, a test signal should be sent every 6 hours. Most modern systems handle this automatically, sending a supervisory “heartbeat” signal to the monitoring station at set intervals. If the station stops receiving that signal, it flags a trouble condition.
Your role in inspecting this is to confirm the process is working. During monthly checks, verify that the monitoring company has been receiving those automated signals without gaps. If your system uses a phone line, cellular communicator, or internet connection, check that the primary and backup communication paths are both active. A system that silently lost its cellular backup three weeks ago will still appear to work perfectly until the primary path fails.
Backup Power Checks
Standby batteries keep your intrusion detection system running during a power outage. Most systems are designed to operate on battery alone for at least 4 to 24 hours depending on the installation standard, but batteries degrade over time. A monthly visual inspection should confirm the battery isn’t swollen, leaking, or corroded at the terminals. Beyond visual checks, periodic load testing verifies the battery can actually deliver the power it claims. This means disconnecting AC power and confirming the system stays fully operational on battery alone for the required duration.
Most sealed lead-acid batteries used in alarm panels have a usable life of 3 to 5 years. Replacing them on a fixed schedule, rather than waiting for a failure, prevents the scenario where a power outage and a dead battery combine to leave your facility completely unprotected.
Sensor-Level Walk Tests
Motion detectors, glass break sensors, and beam detectors can lose effectiveness without triggering any trouble alert on the panel. A PIR motion sensor might have its lens partially blocked by dust, a shifted mounting bracket, or a new piece of furniture in its field of view. The sensor still “works” in the technical sense but no longer covers the area it was designed to protect.
Walk testing is the only reliable way to catch these problems. Put the system into test mode, then physically move through every detection zone and verify the panel registers each activation. For glass break detectors, use a handheld simulator that produces the specific sound frequency the detector is calibrated to recognize. Document which zones you tested and whether any required adjustment. Weekly testing is the manufacturer recommendation for motion sensors in active facilities, though lower-risk environments with stable layouts can sometimes extend this to biweekly or monthly.
Outdoor Systems Need More Attention
Sensors installed outdoors face dust, rain, temperature swings, spider webs, and vegetation growth, all of which degrade performance faster than indoor conditions. Outdoor infrared beams can be blocked by a single cobweb. Fence-mounted vibration sensors lose calibration as temperatures shift between seasons. Camera-based detection systems accumulate grime that reduces image clarity.
If your facility uses outdoor perimeter detection, increase your inspection frequency beyond the indoor baseline. Cleaning sensor lenses and housings may need to happen weekly or even more often depending on the local environment. A facility in a dusty industrial area or one surrounded by trees will need more frequent attention than one in a clean urban setting. Seasonal recalibration is also important: a sensor tuned for winter conditions may produce excessive false alarms in summer as heat changes how infrared detection behaves.
Keeping Inspection Records
Documenting every inspection protects you in two ways. First, it creates a maintenance history that helps technicians identify recurring problems or gradual degradation trends. Second, it provides evidence of due diligence if your system fails and you need to demonstrate to an insurer or auditor that you maintained it properly.
Each inspection record should include the date, the name of the person performing the inspection, which components were tested, the results of each test, and any corrective actions taken. Note specific details: which zones were walk-tested, battery voltage readings, whether the communication test succeeded on all paths. Keep these records for a minimum of one year, though many organizations retain them for three to five years to satisfy insurance requirements or internal security policies.
What Drives Your Specific Schedule
The baseline frequencies above apply broadly, but your actual inspection schedule may be tighter depending on several factors. Insurance policies for high-value facilities often specify minimum testing intervals as a condition of coverage. Government facilities and defense contractors typically follow more rigorous standards that mandate documented inspections at fixed intervals. If your facility holds certain certifications or operates under industry-specific regulations (financial institutions, healthcare, critical infrastructure), those requirements override general guidelines.
The age of your system also matters. Newer systems with built-in self-diagnostics can alert you to many faults automatically, which supplements but does not replace physical inspections. Older systems with fewer diagnostic capabilities need more hands-on attention. If your system is more than 10 years old, consider increasing inspection frequency across all components, as failure rates climb significantly past that age.