How to Put an Alarm Account on Test and Take It Off

Why this matters

Every service visit on a monitored system can send a signal: a tamper when a cover comes off, a burglary alarm when a contact is tested, a fire alarm when a detector is smoked, a trouble when the battery is pulled. If the account is not on test, the central station treats each of those as real, calls the customer, and may dispatch police or the fire department. That is a false alarm on the customer's record, often a fine from the city, and a crew of responders pulled off real calls. The opposite failure is worse: an account left on test after the tech drives away means a real break-in or a real fire at that house goes unanswered until someone notices. Both are prevented by one call at the start and one at the end, done the same way every time.

This card owns the procedure. Every other card in this shelf that says "put the account on test" means this.

What on test actually does

At the central station, putting an account on test tells the automation software to log incoming signals from that account without sending them to an operator for action, for a set window. When the window expires, the account restores on its own and the next signal is handled as real. Some stations let you test only certain signal categories (burglary but not fire, for example); some put the whole account on test. The signals still arrive and still appear on the account's history, which is what lets you prove each device reported. On test does not stop the local siren and does not change anything at the panel.

Before you call

Have these in hand, because the operator will ask and a fumbled answer costs minutes on every job:

• The account number the panel actually reports on. On a takeover or an older system, read it from the panel's programming or the last history, not from the paperwork; a panel still reporting on a previous dealer's account means your test call protects the wrong account.
• Your dealer or technician passcode. Stations issue these per dealer or per tech. Never use the customer's passcode; it is theirs for cancelling alarms, and using it blurs who did what on the record.
• The scope. Which signal categories you will generate (burglary, fire, CO, panic, troubles) and roughly which zones.
• A duration long enough for the work plus margin, but not the maximum the station allows. An hour or two covers most service calls; an install day may need the whole day, set in blocks.

The life-safety point. If the system monitors smoke, heat or CO, putting the account on test means a real fire or CO alarm at that house will not be dispatched during the window. Tell the occupants, in person, that fire monitoring is offline until you call back, and keep the window short. Where the fire side falls under NFPA 72 in the edition adopted, and on any commercial fire system, the AHJ may also require notifying the fire department or building owner of the impairment; that is fire-side work, often separately licensed. See related: The Fire-Side Work and License Routing SOP.

The call, both halves

ON TEST, 09:02
TECH:     Dealer code 4471, tech ID 22. Account 3125-0884,
          the Patel residence. I need it on test.
OPERATOR: Passcode for tech 22?
TECH:     (gives passcode)
OPERATOR: Verified. What are you sending and for how long?
TECH:     Burg on zones 1 to 6, fire on zone 9, AC loss
          and low battery. Ninety minutes.
OPERATOR: All categories on test until 10:32. Fire is
          offline. I'm Dana, operator 31.
TECH:     Dana, 31, until 10:32. Thanks.

OFF TEST, 10:14
TECH:     Tech 22, account 3125-0884, ready to come off.
          Can you read me what came in since 09:02?
OPERATOR: Zone 1 to 6 alarm and restore, zone 9 fire alarm
          and restore, AC trouble and restore, low battery
          and restore. And a 601 manual test at 10:12.
TECH:     That's all of it. Take it off test please.
OPERATOR: Account is live as of 10:15. Dana, 31.

The steps

1. Call before you touch anything that can send a signal. That includes removing the panel cover (tamper on many panels), unplugging the transformer (AC loss after a delay), opening a detector, or even entering installer programming on some panels. Call in the driveway, not after the cover is off. A signal sent two minutes before the call is handled as real, and you will be on the phone with the station explaining it while the customer's phone is already ringing.

2. Identify yourself with the dealer code, tech ID and tech passcode, and name the account by number and by customer name. The name catches a transposed digit. If the operator reads back a different name, stop and resolve it before anything else.

3. State the scope and duration, and get the operator's name or ID and the exact end time. Write all three on the work order with the time you called. If anything goes wrong later (a dispatch during your window, a dispute over a fine), that line is the record that shows the account was on test and who put it there.

4. Tell the occupants what is offline and until when. Especially fire and CO. If they leave during the work, they need to know the system will not call for help until you finish.

5. Do the work, and send test signals deliberately. Trip each device you touched, and every device if this is a full test, one at a time, so each event lands separately on the history. Let each restore before the next. For how to work through zones in order, see related: How to Walk Test Every Zone with the Central Station.

6. Watch the clock against the end time. If the work will run past it, call and extend before it expires. When a window expires mid-test, the next device you trip is a real alarm. Setting a phone timer for ten minutes before the end time is a habit worth building.

7. Verify every expected signal on the history before you take it off test. Either ask the operator to read the history since your on-test time, as in the call above, or read it yourself on the dealer portal. Check three things per signal: the event (alarm, trouble, restore), the zone or user number, and that it arrived at all. A zone that tripped at the keypad but never appeared on the history is a programming or reporting fault you have to fix now, while the account is still protected by the test window. For decoding what comes back, see related: Reading Event Codes on a Signal History.

8. Send one final non-alarm signal. A manual communicator test (Contact ID event 601, the manual test report, on panels that report in that format, or the panel's equivalent test report) proves the path still works after your last change, without generating an alarm. Confirm it arrived.

9. Call to take it off test, and do not leave until the operator confirms the account is live. Write the off-test time and operator on the work order. If the call drops, call back; a voicemail or a portal request that you did not see confirmed does not count.

10. Arm and disarm once with the customer, if they are home. It proves the keypad, the codes and the system state are back to normal, and it gives them a chance to ask about anything you changed.

The record on the work order

The minimum line, filled in on every visit:

Notice the times close on themselves: on at 09:02 with a 10:32 end, signals verified by 10:14, off at 10:15, seventeen minutes inside the window.

How it goes wrong, and what each failure looks like later

The account is still on test the next morning. The tech asked to be taken off test, the call dropped, and they assumed. Nothing shows at the house. The only defense is step 9's confirmation, and an office habit: anyone reviewing the day's work orders looks for an off-test time on every monitored visit and calls the station about any that lack one.

The window expired and a test became a dispatch. Usually during a long install where a delay pushed the work past the end time. The station's record shows the alarm arrived after the window. Step 6.

The right signals went to the wrong account. On a takeover, the panel still reported on the old dealer's account at another station. The tech put their own new account on test and generated a fire alarm that the old station dispatched. Read the account number from the panel, step 1 of "before you call", and see related: How to Take Over an Existing Alarm System.

Everything tested at the keypad, nothing arrived. The communicator was dead or the panel was not programmed to report those zones. The tech who skips step 7 leaves a system that sounds fine and calls nobody. This is the commonest serious finding on an annual inspection.

A zone reported as a different zone. The station's zone list says zone 4 is "back door" and the panel's zone 4 is now a motion detector. The signal arrived, but a responding officer would be sent to the wrong door. Step 7's check of the zone number against the station's description catches it; update the station's zone list before you leave.

Restores but no alarms. Some panels report only certain events by default. If the history shows restores without the alarms they restore, the reporting codes need programming.

When the procedure changes

Commercial fire systems. The fire alarm contractor puts the fire account on test with their own station and handles impairment notification; a burglary dealer does not put someone else's fire account on test.

Video-verified and app-driven accounts. Some services also send video clips or app notifications to the customer during testing even with the station on test. Tell the customer to expect them.

A station that allows category-only testing. Use it: put only burglary on test when the fire side is untouched, so fire monitoring never goes offline.

References

• See related: How to Walk Test Every Zone with the Central Station
• See related: Reading Event Codes on a Signal History
• See related: How a Central Station Handles a Signal, from Panel to Dispatch
• NFPA 72, National Fire Alarm and Signaling Code, impairment and notification provisions, in the edition adopted by your jurisdiction
• Your central station's dealer procedures for test windows, passcodes and category testing