The instinct behind always-on tracking is understandable. If visibility is good, more visibility is better. If a ping every 5 minutes tells you something, a ping every 30 seconds tells you more.
The problem with that logic is that it optimizes for data volume rather than operational value. And in battery-powered asset tracking — which covers the majority of deployed IoT devices in logistics — it creates a battery life crisis that undermines the entire deployment.
What always-on actually costs you
- Continuous cellular transmission
- Battery life measured in days or weeks
- High per-device data costs
- Thousands of pings — most unactionable
- Frequent battery swap or recharge cycles
- High field maintenance overhead at scale
- Transmits on trigger: motion, geofence, schedule
- Battery life measured in months
- Lower per-device data costs
- Signals fire when they mean something
- Minimal field maintenance at scale
- Higher fleet coverage from same device budget
The battery math that changes everything
The difference between a 2-week battery and a 12-month battery isn't just operational convenience. At scale, it's the difference between a fleet tracking program that's sustainable and one that requires constant field maintenance to stay alive.
A fleet manager running 500 battery-powered trackers on always-on mode is replacing batteries every two weeks across half a thousand devices. That's a part-time job just in battery logistics — before you account for the field access required to swap them.
"A tracker that's dead because the battery ran out isn't providing visibility. It's providing false confidence."
What wake-on-demand actually means
Wake-on-demand doesn't mean your assets go dark between pings. It means the device is in a low-power listening state — ready to transmit immediately when a trigger condition is met — rather than burning continuous power on a fixed transmission schedule.
The triggers that wake the device are the operationally meaningful events:
- Motion detection — device wakes when the asset starts moving after a dwell period
- Geofence crossing — device transmits when entering or exiting a defined zone
- Scheduled heartbeat — low-frequency check-in to confirm device health and position
- Shock event — impact above threshold triggers immediate transmission
- Temperature excursion — sensor crosses threshold, device reports immediately
- Remote wake — platform sends a wake command when you need a real-time location
Each of these triggers represents an event that might require operational response. The device wakes, transmits, and returns to low-power mode. Between triggers, it's conserving battery while remaining ready to respond in seconds.
When always-on is actually the right choice
There are scenarios where always-on or high-frequency reporting is genuinely warranted — and worth the battery trade-off:
Active high-value transit. A shipment of pharmaceutical product or high-value electronics in active transit on a known high-theft corridor warrants higher reporting frequency for the duration of the move. That's a time-bounded use case where you can justify the battery draw.
Hardwired assets. Trailers and vehicles with hardwired power sources have no battery constraint. Always-on makes sense when power isn't a limiting factor.
Post-exception escalation. When a device fires a geofence deviation alert, you can automatically switch it to high-frequency reporting mode until the exception is resolved — then drop back to wake-on-demand when the asset returns to normal behavior. You get high resolution when you need it, conservation when you don't.
The fleet coverage implication
There's a fleet coverage argument for wake-on-demand that rarely gets made explicitly. If your device budget covers 200 always-on trackers with 2-week battery life — requiring continuous replacement cycles — that same budget deployed on wake-on-demand devices with 6-month battery life covers 200 devices with dramatically lower maintenance overhead. In practice, that means more assets covered, more consistently, at the same cost.
Higher coverage matters more than higher frequency. A trailer that has a tracker — even one that reports on motion and geofence events — is infinitely more visible than a trailer with no tracker because the maintenance burden on always-on devices pushed it out of the rotation.
Always-on tracking sounds like the right answer. In most battery-powered asset deployment scenarios, it's the wrong architecture. The goal isn't maximum data — it's the right signals at the right moments, from devices that are still alive six months into the deployment.
Wake-on-demand is how you build a fleet tracking program that actually scales.
Design a tracking architecture that lasts
We'll help you configure wake triggers, reporting intervals, and fleet coverage for your specific asset mix — so your program is still running clean 12 months from now.
Book a fleet architecture session →