Login
Installation · Excel and Word script

Yard-safe alert functional test script

A free script to test every alert of a tracking device in a closed yard: how to trigger it safely, what should reach the platform, how long it took, and whether each test setting is back to normal.

Get the Excel script (.xlsx)Get the printable script (.docx)
Arabic Excel versionArabic Word version
Free: enter your name and e-mail and we email you the files. Works in Excel, Google Sheets, LibreOffice and Word.
  • 15 alerts, 21 spare rows
  • Delay worked out in seconds
  • Restore check per setting
What the script records

Five example rows from the test script

Each alert gets a result from three facts: did it arrive, how long did it take, and is the setting back. One fail makes the vehicle Not ready.

  • Pass
  • Late or restore
  • Fail
  • N/A
AlertSetting: original, test, nowDelayResult
Ignition on and offNone21 sMax 60Pass
Overspeed120 → 15 → 120km/h75 sMax 60Late
Idling10 → 2 → ?min42 sMax 60Restore
Harsh acceleration4.0 → 3.0 → 4.0m/s²NoneNot receivedFail
GNSS antenna unpluggedInternal antenna-N/A

Test values are examples. Replace them with your own, and with your device datasheet values where they apply.

What's inside

What's in the alert test script?

An Excel workbook for the results and a Word script for the clipboard. Same alerts, same order.

  1. 01

    Test record

    Vehicle, IMEI, firmware, configuration profile, yard, yard speed limit and the control-room call, then a summary and a Ready, Check or Not ready result.

  2. 02

    Test script

    15 alerts from ignition to the driver camera, each with a safe set-up, a yard trigger, the expected result and a maximum delay.

  3. 03

    Restore check

    Original value, test value and the value now. A test that passed but left a setting changed shows Restore.

  4. 04

    Word script

    Safety rules, the 15 alerts with tick boxes, a change-and-restore table and three signatures. Landscape, for printing.

How it runs

From the yard briefing to the sign-off

  1. Prepare the yard

    Closed area, spotter, yard speed limit, and a call to the control room.

  2. Write, then change

    Write the original value of each setting before you lower it for the test.

  3. Trigger one alert at a time

    Note the trigger time, then the time it shows on the platform.

  4. Restore and sign

    Put every setting back. The vehicle leaves only with no Restore left.

Why test alerts in the yard?

A device can report its position and still miss an alert. The ignition wire sits on the wrong source, a threshold is too high, a geofence is drawn on the wrong account, or the panic button goes to nobody. You find out on the day it matters. A short yard test finds it on the day of installation.

Some alerts need a real event: speed, harsh braking or a long idle. In a yard you do not create the danger. You lower the threshold for the test device, trigger it at walking pace, and put the threshold back.

Safety comes before the test

Closed yard only, never a public road. Keep a spotter outside the vehicle and stay under the yard speed limit. Test the immobilizer only with the vehicle stationary and the engine off.

How the result is worked out

Delay (s) = (time received − time triggered) × 86,400 Result = Fail if it did not arrive or arrived with wrong data Result = Late if the delay is above your maximum Result = Restore if the setting now differs from the original value Otherwise PassExcel stores a time as a fraction of a day, so the difference is multiplied by 86,400 seconds. Example: 09:12:05 to 09:13:20 is 75 s, above a maximum of 60, so the overspeed test shows Late.

The vehicle result is Ready when every alert that applies passed, Check when something is late, pending or not restored, and Not ready when at least one alert failed. In the example: 9 pass, 2 late, 1 fail, 1 to restore, so the vehicle is Not ready.

Test values and maximum delays

The file ships with example test values: a 15 km/h speed limit, a 2-minute idle limit and a 3.0 m/s² level for harsh braking and acceleration. The 3.0 m/s² level is a typical starting value. Adjust it after the pilot. None of them is a device specification. Pick values your yard allows, and keep the original values on record.

The maximum delay is yours too. It depends on the reporting interval, the network in the yard and how the platform shows events. A power-cut alarm on a device without a backup battery may only arrive after the power is back, so its example maximum is longer.

Typical value. Replace with your device datasheet value.

When to run it

  • After every new installation, before the vehicle goes back to work.
  • After a configuration change or a firmware update.
  • After a repair that touched the wiring or the device.
  • When a driver or the control room says an alert never came.

Limits

The script records what you observed in one test. It does not certify the device, the installation or the platform, and it does not describe the alerts of any particular Tracom model. Which alerts a device sends depends on its model, firmware, configuration and accessories.

Related Tracom solution

Test the alerts the day you install

Tracom designs its trackers to record ignition, movement, power and input events on the device. Which alerts your model sends, and which settings you can change for a test, depends on the model and the configuration file. Ask us before a large rollout.

  • Ignition finder to choose the ignition source before the first test.
  • Harsh-event translator to read a threshold in g, m/s² or km/h per second.
  • Geofence planner to size a test zone for your reporting interval.
  • As-built dossier to file the signed script with the rest of the project.
Questions

Alert test questions, answered

Testing a new fleet? Talk to Tracom.

Can I test overspeed without driving fast?

Yes. Lower the speed limit for the test device only, for example to 15 km/h, drive a little above it inside the yard, then restore the original limit. The script records both values.

What maximum delay should I use?

Your own. It depends on the reporting interval, the network and the platform. The file uses 30 s to 300 s as examples. A longer delay than usual is worth a look even when the alert arrived.

Is it safe to test the immobilizer?

Only with the vehicle stationary, the engine off and the keys with the tester. Never send a cut command to a moving vehicle. Follow your site rules and the wiring plan of your installer.

Why does the power-cut test have a longer delay?

Without a backup battery the device may only send the alarm when power comes back. With a battery it can send it at once. Check which case applies to your device.

Does a full Pass mean the installation is approved?

No. It means the alerts you tested reached the platform in time on that day. Acceptance of the installation follows your contract and your own checks.

What does Tracom do beyond the script?

Tracom makes the devices and can tell you which alerts and settings your model supports. The script works with any tracker. It does not certify a device, an installer or a platform.

Next step

Installing a new fleet?

Tell us the vehicles and the accessories. We will help you plan the alert tests.

Contact Us Get the script
Related tools and templates

More for installation and testing

Get the report

Enter your details and we will email you the file.

Use your real name so the file arrives addressed to you. Don't worry, we won't flood you with emails or calls.

Tracom uses your details to send what you requested and may contact you about it. See our privacy notice for your rights and how to delete your data.

Tracom is an advanced GPS tracking device designed to enhance fleet visibility, safety, and efficiency through real-time data, intelligent alerts, and remote monitoring.

Device

Help

Facebook Youtube Linkedin Instagram X-twitter

Copyright © 2026 SAFEE

Scroll to Top