What a Guard Tour System Does on a Construction Site
Construction is an awkward place for any system that assumes a building. The site is temporary, the site fence moves every few weeks, the gate often has no mains power, and half the workforce changes each month. Anything that depends on cabling or site internet is a hard sell to a site manager.
What Actually Disappears From a Construction Site
Ask a site manager what went missing last month and the answer is rarely the finished work. It is the things that are easy to carry and easy to sell.
- Machinery and small equipment — mini-excavators, generators, plate compactors, breakers.
- Cable and metal — drum cable, earthing conductor, scaffolding couplers, lead flashing.
- Fuel — a full diesel bowser sitting in an unlit compound is the easiest target on site.
- Tools and fixings — taken from containers and cabins, usually in ones and twos so nobody notices.
- Finished materials — tiles, sanitaryware, doors and cladding panels waiting to be installed.
Almost all of it leaves at night or over a weekend, through a gate or a gap in the site fence. That is exactly the window a documented patrol covers — and exactly the window where a paper log proves nothing, because nobody was awake to write in it.
Where Checkpoints Go on a Site That Keeps Moving
A construction site is a moving target: compounds relocate, gates close, the site fence follows the build. The checkpoint plan has to be easy to change. Six positions cover most sites.
- Main vehicle gate and pedestrian gate — mounted on the inside face, high enough that nobody can reach over the site fence.
- Machinery compound or secure store — on most sites this is the highest-value point on the whole route.
- Fuel bowser and its bund — a single diesel theft is a week of losses in one night.
- Material laydown area and the cable drum store.
- Site office and cabin cluster — laptops, drawings, keys and the safe all live here.
- The far perimeter corner — the point a patrol is most likely to skip, and the easiest place for someone to cut through.
Safety Walks and Subcontractor Checks
On most sites the same walk checks far more than theft. Scaffolding, edge protection, temporary electrics, housekeeping and fire points are all on the route. The difference a tour system makes is that the walk leaves a timestamp instead of a tick on a clipboard.
| What the site must be able to prove | Paper checklist | Guard tour record |
|---|---|---|
| A safety walk took place at the agreed time | A tick and a hand-written time | A timestamped read at each inspection point |
| The walk reached the far corner, not just the gate | Nothing | Point-by-point coverage, with gaps flagged |
| Who carried out the walk | A signature that may not be theirs | Personal ID tag read at the start of the walk |
| The record still exists at handover | Filed somewhere, or lost | An exportable, dated file kept with the project |
Subcontractor checks work the same way. Where a principal contractor has to show that each trade was inspected before an area was closed up, one personal ID tag per supervisor turns "we checked it" into a dated list of who checked what, and when.
Running a Patrol Route With No Power and No Network
A site cabin may have a generator and a 4G dongle. The far corner of the site has neither, and that is where the risk sits. Systems that assume connectivity fail exactly where they are needed most.
- Checkpoints are passive: no battery, no wiring, no data line. A checkpoint is a small metal button fixed to a wall or a post.
- The reader carries the data. Every scan is written to the reader with the point ID and the time from its internal clock, and the log is uploaded at the office by USB.
- The reader is built to be dropped. It lives in a van, a cabin drawer or a coat pocket, gets knocked off a scaffold, and still has to work in a January frost.
- If head office must see incidents the same day, an online reader sends reads over a mobile network. That is a choice about response time — both types record every scan.
From Weekly Walks to Handover Records
Snagging and handover arguments are almost never about quality. They are about time: did that defect exist when we signed, or did it appear afterwards? A dated walk record answers that with a document instead of a memory.
- Weekly walk reports exported as PDF and attached to the progress report.
- Exception lists showing which areas were not walked, and why.
- Event codes recorded at the checkpoint — a defect, a hazard, an access problem — so the walk carries findings, not just presence.
- Archive everything with the project file, not only inside the software.
