Paper logbook
- Very small sites with one or two checkpoints.
- Owner or manager is on site every day to read it.
- No need for proof beyond a signature.
Many properties still record patrols in a paper logbook or with a guard tour wand that is downloaded to a PC. Here is how those methods compare with an NFC patrol app on an Android phone, including where the traditional options still make sense.
| What matters | K Guard | Paper logbook | Guard tour wand |
|---|---|---|---|
| Proof the guard was there | NFC tap records checkpoint, guard and time. Optional GPS check and random live camera photo. | Handwritten time and signature. Entries can be filled in later or copied. | The wand records the tag and time when touched. |
| When owners see it | Check-in alerts through Telegram as soon as the phone is online. | When someone reads the book on site. | After the wand is docked and the data is downloaded to a PC. |
| Missed checkpoints | Daily and monthly reports list checkpoints that were not patrolled. Patrol reminder alarm each round. | Found only by reading the pages. | Visible after download, in the PC software. |
| Incident evidence | Category, location, photo, video or voice note in one report, sent to selected owners. | Written description. Photos taken separately, if at all. | Usually limited to preset event tags or codes. |
| Cheating checks | Mock location can be flagged or blocked. Check-ins stop if the phone clock is set back. | None. | Tap times come from the wand clock. |
| Reports | Daily summary and monthly report with PDF and CSV, delivered through Telegram. | Typed up by hand. | Exported from the PC software. |
| Hardware needed | Android phone with NFC and NFC tags (NTAG213/215/216). | Book and pen. | Patrol wand, download cradle or cable, PC with software, checkpoint tags. |
| Works without internet | Yes. Records stay on the phone; Telegram messages retry when back online. | Yes. | Yes, until the data is downloaded. |
Guard tour wands vary by brand and model. This table describes a typical setup. Telegram delivery needs an internet connection and a configured bot.
Each method has a place. A short, honest summary:
You keep the same patrol route. Only the recording method changes.
Most wand buttons cannot be read by a phone, so stick an NFC tag next to each point.
Register each tag by name, add your guards, and set GPS checks or a fixed route order if you need them.
Choose who receives check-in alerts, incident reports, proof photos, and daily or monthly reports.
Send the device code shown in the app to KTech Solution and enter the yearly or lifetime licence code you receive.
For most condominium, gated community, factory and warehouse patrols, yes. Guards tap NFC checkpoint tags with an Android phone instead of a patrol wand, and owners receive check-in alerts and reports through Telegram instead of waiting for the wand data to be downloaded to a PC. A wand may still suit sites where guards cannot carry a phone.
You can keep the same patrol route and checkpoint locations. Many patrol wands use touch buttons or tags that a phone cannot read, so most sites place a new NFC sticker or tag (such as NTAG213, NTAG215 or NTAG216) at each existing checkpoint.
No. Check-ins are saved on the phone without internet. Telegram alerts and reports are queued and sent when the phone reconnects.
K Guard replaces the patrol round record, the part of the logbook that shows which checkpoints were visited and when. Some properties still keep a separate visitor or occurrence book for other purposes.
Tell us how your property patrols today and how many checkpoints you have. We will explain what the switch involves.


Website, ERP, software and AI development, from idea to launch.