GPS patrol verification in TeamMap: setup and limits

"The guard said they walked it" is not evidence. A client who has just had a break-in wants to know where your officer was at 0247. GPS patrol verification answers that, with one limit: it puts a guard near a place, not at it.

What does GPS verification actually prove?

Less than people assume, and more than paper ever did. Paper sign-offs, key-turn boxes and supervisor spot checks share one flaw: they can be produced without the patrol happening. A position trail cannot. What you get from it:

• Where a guard is right now, rather than where they said they were an hour ago
• A shift you can replay on the map, on the plans that keep location history
• A position stamped at check-in, captured by the app rather than typed by the guard
• Response times, measured from the incident timestamps rather than estimated afterwards
• A route completion report built from the record, with nothing retyped

What it does not give you is certainty that a guard stood at a particular door. That is the difference between a defensible record and one a lawyer takes apart.

How do you set it up?

Getting the device permissions right

Background location is where most rollouts quietly fail. A phone that only reports while the app is open reports nothing during a patrol.

Platform	Setting	Value
iOS	Location Access	Always, for background tracking
iOS	Precise Location	On
Android	Location Permission	Allow all the time
Android	Battery Optimization	Off for TeamMap
Both	High accuracy mode	On

Check these on the device during onboarding, not by asking. "Allow once" is what a distracted person taps, and it looks identical to a working install until the first night nobody can find anyone.

Choosing the reporting cadence

Two settings decide how much data you get and how much battery it costs.

Interval. How often a guard's device reports position while sharing is on. The choices run from every 5 seconds to every 30 minutes, with 5 minutes as the default, and they cost battery in direct proportion. The fast end is gated by plan: Pro reports at best every 30 minutes, Business and Enterprise go down to every minute, and Enterprise can reach every 5 seconds on a custom contract. Free has no GPS tracking at all.

Distance filter. How far the guard has to move before a new position is written, defaulting to 25 meters and adjustable from 10 up to 500. Raise it for a stationary lobby post where a phone on a desk writes drift all night. Lower it for foot patrol.

One exception overrides both. When a guard has an active SOS, the distance filter drops to zero and every fix is reported. That is the one moment where battery life is not the priority.

Building the route

1. Open the TeamMap web dashboard and go to Routes.
2. Choose New Route.
3. Drop a pin for each checkpoint.
4. Choose what proves each checkpoint: GPS, an NFC tag, a QR code, a photo or a report.
5. Set the order to sequential or flexible.
6. Set the schedule: one-time, or repeating hourly, daily, weekly or per shift.
7. Choose what a missed checkpoint does: log it, raise an alert, or block the route from closing.
8. Assign it to guards or groups.

Where the checkpoints go matters as much as how they are proven. Placing checkpoints where an intruder would go covers the reasoning, and routes that repeat on schedule covers turning a set of pins into a patrol somebody can actually walk.

Why is a GPS fix not proof of presence?

Because the number has a margin, and the margin is bigger than a building.

GPS.gov states it directly: GPS-enabled smartphones are typically accurate to within a 4.9 meter radius under open sky, and accuracy worsens near buildings, bridges and trees. Guard work is conducted almost entirely near buildings, and often inside them.

So a fix at a loading dock is consistent with a guard standing at the dock. It is also consistent with a guard sitting in a vehicle 15 meters away. The record does not distinguish, and a defense attorney knows it.

How the app draws the line

• Only a matching NFC or QR scan marks a checkpoint verified. A plain tap records the visit as unverified.
• Checkpoints carry an order, so the report shows the sequence actually walked rather than the sequence you designed.
• A checkpoint still unvisited when the route is due raises a missed-checkpoint alert without anyone watching for it.

Verified and unverified side by side in one report is the useful part. You claim no more than you can prove, and the client sees which is which.

How do you measure response time?

1. An incident is created with a location.
2. A guard is assigned or dispatched from the console.
3. The live map shows them moving toward it.
4. The dispatcher confirms arrival against the guard's position.
5. The incident timestamps give the elapsed time without anyone doing arithmetic.

Measured response time is the number worth putting in front of a client, and most companies cannot produce it. What to do with it is in metrics that prove the work.

How do you introduce tracking without a mutiny?

Get five things in writing before the first device is enrolled.

• A written policy stating when, why and how location is collected
• Shift-only tracking, so nobody is followed home
• Disclosure that the guard can read, not a line buried in an onboarding packet
• A retention limit, stated in days
• Access controls, so location is visible to the people who dispatch and nobody else

Retention is set by the plan. Free and Pro keep no location history, so there is nothing to replay on those plans. Business keeps 180 days, Enterprise 365, and older points are removed for you. Tell guards the number. A specific figure reads as a policy; "we keep it for a while" reads as a threat.

Then say why it exists, in their terms. If you are hurt and cannot call, we can find you. When someone says you were not there, this is what clears you. The fuller playbook is in rolling out GPS without losing trust.

How do you read the data?

On the map

• Current positions, refreshed on the tracking interval
• Location history trails
• Checkpoint completion status
• Active incidents and who is responding

A guard's sharing state reads as live, stale or off. Stale is the one to watch: no position for longer than the interval allows, usually a sleeping phone, occasionally a guard who needs someone to go and look.

In the patrol report

• Every checkpoint on the route, verified or not
• How each verified checkpoint was proven: GPS, NFC, QR or photo
• The timestamp on each verification
• Route completion, and how many of those checkpoints were verified rather than merely visited
• A map of the route, your company name, and the route ID

That report is what a renewal conversation is built on. Client reports that win renewals covers presenting it.

When the trail looks wrong

Anomaly	Likely cause	What to do
Position jumps	Drift, reflected signal off a facade	Check for indoor sections and tall buildings on that leg
Stationary for hours	Phone left on a desk	Ask the guard before you conclude anything
Impossible speed	A single bad fix	Compare against the points either side of it
No data at all	Phone off, battery dead, no signal, permission revoked	Contact the guard, then check the device permissions

Treat the first and third rows as instrument error until proven otherwise. Disciplining a guard over a GPS glitch makes the whole system something people work around.

What breaks, and how do you fix it?

Poor accuracy. Confirm high accuracy mode is on, look for underground or steel-framed sections on the route, restart location services, and update the OS. If a specific checkpoint is always bad, the answer is a tag, not a setting.

Battery drain. Lengthen the interval on stationary posts and raise the distance filter. Check that battery optimization has not re-enabled itself after an OS update, which it does. Put chargers in the vehicles: a 12-hour shift on a 5-second interval will not make it.

Missed checkpoints. Open the checkpoint and look at its recorded fix to see where the guard stood. Sometimes they missed it. More often the checkpoint sits in a dead zone, or somewhere the patrol has no reason to walk, and it needs moving or tagging.