Site Test Mode
When a technician is installing or servicing equipment at a site, they deliberately trigger alarms to confirm the system works. Those signals should be logged — but a response unit must never be sent to them. Test Mode is how a site is flagged so the control room does not act on those signals.
What Test Mode does
While a site is on test:
-
Dispatch is suppressed. If an operator (or an automatic action) tries to nominate or dispatch a unit to the site, the action is blocked and the operator sees a message such as:
Site is on test until 2026-06-16 14:35. Clear the site state before dispatching.
-
Signals are still recorded. Events continue to arrive and appear in history, so there is a full record of what was triggered during the test.
-
It expires on its own. Test Mode is always time-boxed (60 minutes by default). When the window ends, the site automatically returns to normal — there is nothing to remember to switch back.
Maintenance, suspended, and installation states behave the same way for dispatch (all suppress it).
Seeing it on the event queue
A site on test is flagged on every one of its events, so an operator knows before they act:
- Cards and kanban view — a violet, diagonally hatched banner at the very top of the card: 🧪 On test · dispatch suppressed · until HH:MM.
- Table view — a compact violet 🧪 On test chip in the row, with the full detail on hover.
- Event details — the same violet banner above the site notes.
Maintenance (🔧), suspended (⛔) and installation (🏗) states get the same flag with their own badge. The queue re-checks about once a minute, so a state started or cleared mid-shift appears (or clears) without a page refresh. See The event queue.
Putting a site on test
From the Sites page, search for and select the site. In the site's detail panel — just below the notes — is a Test mode control:
- When the site is live, it shows "Site is live — dispatch enabled" with a Put on test (60 min) button.
- Press it to place the site on test for 60 minutes. The control then shows an amber "On test until HH:MM — dispatch suppressed" badge and a Clear test mode button.
- Press Clear test mode to take the site off test immediately (for example, if a real emergency comes in during a test window).
The control is only shown to operators with site-management permission. If you don't have permission, the action is rejected with a clear message.
When the site's dispatch is suppressed by a state other than test — maintenance, suspended, or an installation window — the control shows that state read-only instead: an amber badge naming the state and its end time (e.g. "Installation mode until … — dispatch suppressed") with a note that it is managed from CleverOps. No test buttons are offered in that case, so an operator cannot accidentally clear a state that another surface owns. Installation windows are started, extended, and ended from the CleverOps site state card — see Installation Mode.
From the event queue, a site can also be quieted straight from its card: More actions → Quiet this site 1 h… (key q), or the 🔕 Quiet 1 h button that appears next to a red ×N today repeat chip. It asks for a reason and writes the same 60-minute test window; see Quiet a site for an hour.
An assigned technician can also place the site they are working on into Test Mode from the CleverTech app, for a site they have an active job at.
Clearing Test Mode early
If a genuine emergency occurs at a site while it is on test, the site state can be cleared so the alarm can be dispatched normally. Test Mode does not block anything other than dispatch, so the event is still visible the whole time — clearing it simply re-enables dispatch immediately rather than waiting for the window to expire.
Test Mode never changes a site's billing or monitoring status. It is a temporary, non-destructive flag layered on top of the site — when it expires or is cleared, the site is exactly as it was before.