What Is a Guard Tour Reader?
Definition: A Guard Tour Reader is a handheld, battery-powered data collector that a security guard carries on patrol to read fixed Checkpoint Buttons and record the time of each visit.
It is the most expensive single item in a patrol kit and the one that takes the physical abuse, so its build quality matters more than any other component. In English it is also called a patrol reader, data collector, or tour stick.
What Is Inside
- Microcontroller and real-time clock, every read is stamped with date and time; an inaccurate clock makes the reports meaningless.
- Read head, touches an iButton (contact) or induces an RFID tag (contactless) to capture the ID.
- Non-volatile memory, stores reads even if the battery dies, so no record is lost between downloads.
- Feedback, LED, beep or vibration confirms a successful read, important in noise or darkness.
- Battery, typically a 3V cell; efficient designs reach hundreds of thousands of reads per charge.
Specifications That Matter
| Specification | Why it matters | What to look for |
|---|---|---|
| Housing | Survives drops and weather | Alloy or stainless steel with a rubber shell |
| Storage | Sets how often you download | 3,600 reads (contact) up to 60,000 (RFID) |
| Temperature | Outdoor or extreme sites | At least -20 C to +60 C; industrial to -45 C to +85 C |
| Feedback | Confirms reads in noise or dark | LED plus beep plus vibration |
| Battery | Downtime between charges | Months of normal shift work per cell |
Accessories matter too: a Holster keeps the reader on the belt and off the floor, and a spare Data Transmit Cable or cradle avoids a patrol gap at shift change.
FAQ
Field life is typically 3 to 5 years of daily use. The battery and the contact pad wear first; both are inexpensive to service. Choose a sealed, rubber-shelled model for longer life in rough conditions.
It follows the Checkpoint Button technology you choose, see our contact vs. contactless comparison. The reader and the button must match.
Physically yes, but each guard should read his own GuardID Key at shift start so reads are attributed correctly. For concurrent shifts, provision one reader per guard on duty plus a spare.