The question everyone asks — and the complaint nobody makes
When evaluating a guard tour system, one of the first specs buyers check is record capacity: how many patrol reads can the reader store before it must be downloaded. It feels like a natural number to compare. Yet in two decades of selling these systems, capacity has almost never been the reason a customer was dissatisfied.
We ship large numbers of readers that store only 3,600 or 7,200 records. None of those customers complained that the device could not hold enough. The capacity question is asked; it is rarely the deciding factor.
Why bigger storage can backfire
A guard tour reader accumulates reads in its internal memory and later downloads them to management software via a cradle or USB. The problem appears at the download step, not during use.
Once a single reader holds more than roughly 10,000 records, exporting that data to software becomes very slow — often ten minutes to half an hour. The customer sees a progress bar that will not move and concludes the system has frozen.
How guards actually use it
In real deployments, data is uploaded the same day, every day or two, or at worst once a week. Patrols are frequent but each read is tiny.
| Upload frequency | What the reader holds | Download time |
|---|---|---|
| Most common: same day or every 1–2 days | A few hundred to ~2,000 records | Seconds to tens of seconds |
| Slowest: about once a week | Still only up to ~2,000 records | Seconds to tens of seconds |
At those volumes, the upload finishes in seconds. The reader never gets close to the point where export slows down.
What to weigh instead
If capacity is not the lever, what is? Two things dominate real buying decisions for a patrol device that guards will carry every shift and may try to abuse:
- Durability — can it survive being dropped, crushed, soaked, or deliberately damaged?
- Battery life — how long does a cell last, is it easy to buy and replace, and for rechargeable units, how long per charge?