Define the parked period before changing settings
A van waiting for its next contract and a vehicle in a workshop may both stand unused for days. Their reporting requirements can differ. Before the parked period begins, agree what the fleet team needs to know, when it expects a check-in and who will investigate a missed observation. Do not assume that normal driving updates continue at the same frequency after ignition is off.
Write down the expected duration, approved parking location, responsible team and planned return to service. Keep vehicle identifiers and actual parking locations in controlled fleet records. The worksheet below is blank; it is a planning aid, not a record of a SafarTrak customer or a promise of uninterrupted tracking.
Ask what the actual sleep mode changes
A power-saving label does not tell the buyer which functions remain available. Teltonika documents several sleep modes for its FMC920, with different GNSS and mobile-modem behaviour and wake conditions. Its documentation also describes conditions that must be met before a configured mode starts. These examples show why the device model, firmware and configuration matter; they are not SafarTrak feature descriptions.
Ask your provider to describe the proposed parked configuration in plain language: which measurements continue, which records are sent, which commands can reach the device and which event wakes it. A setting that changes communications can change what dispatch sees. Confirm the consequences before the responsible installer or provider makes any change.
Keep vehicle power and internal backup separate
Do not treat the phrase backup battery as a duration guarantee for a parked vehicle. Ask which power source supplies the proposed tracker, what the internal battery is intended to do and which conditions limit its operation. Teltonika’s FMC920 status reference lists power voltage and internal battery voltage separately, illustrating that the two observations answer different questions. It does not establish which readings your SafarTrak setup supplies.
Give the provider the exact vehicle and device details, the planned parked duration and any required reporting duty. Ask for a demonstration and written limitations for that combination. This article supplies no safe parking duration, current-draw figure, battery-health diagnosis or universal voltage threshold. Vehicle battery care and any installation, charging or removal work belong to the relevant manufacturer instructions and qualified responsible team.
Agree an exception rule instead of guessing from the map
An old position is a reason to review the agreed parked behaviour, not immediate proof that a tracker has failed or a vehicle has moved. Geotab’s device-status guidance uses device-type-dependent offline periods. That manufacturer example supports asking how a provider defines an exception; it does not supply a SafarTrak timeout.
Record the expected observation, its source and the time at which a reviewer should escalate. Distinguish a scheduled stationary check-in from a newly measured position, and ask how those appear in the actual report. Use the existing timestamp article to review measurement and receipt times, and the mobile-network article for the separate question of recovering records after a communications gap. Do not copy a threshold from another device’s manual.
Test the departure as well as the quiet period
Before accepting the setup, arrange a representative parked-and-return observation with the provider and fleet team. Record the last normal report, the agreed parked observations and the first required report after the approved wake event. Keep the evidence references and actual configuration together. Do not disconnect wiring or interfere with safety equipment to manufacture a test.
Example: a dispatch team plans to return a parked delivery van to duty on an agreed morning. The reviewer checks whether the expected departure information becomes available and notes any missing evidence before relying on the report for that duty. This is a hypothetical review process, not a customer result or a guaranteed wake-up time. If the required behaviour is not demonstrated, keep that acceptance question open and assign an owner.
Bring a parked-operation brief to SafarTrak
Use the blank review sheet to collect the planned duration, required observations, proposed power-saving behaviour, wake event, evidence and escalation owner. Ask the SafarTrak team which parts can be demonstrated for your exact vehicle, tracker and configuration. Supported behaviour must be confirmed for the proposed setup.
Keep the hardware Guide as the wider device-and-software selection reference. This article focuses on a vehicle standing unused and returning to duty. It does not claim that SafarTrak offers every sleep mode, remote wake-up, automatic low-battery warning or continuous parked monitoring, and it provides no security, compliance or battery-runtime assurance.
Sources and further reading
Manufacturer documentation illustrates vehicle-specific coverage. It does not establish compatibility for a SafarTrak deployment.
- Download the blank parked-fleet power and reporting review sheet (CSV)
- Teltonika FMC920: model-specific sleep modes and wake conditions
- Teltonika FMC920: status information and separate power/battery fields
- Geotab: device-status definitions and device-specific offline periods
- Check the measurement time behind a position
- Test mobile-network gaps as a separate condition
BRING IT TO YOUR FLEET
Start with your vehicles.
Ask the right questions.
Share your vehicle mix, existing devices and required signals with the SafarTrak team.
Discuss your vehicle, device and parked reporting needsDiscuss your deployment
