You find out the same way you check any service you pay for: you look at the record. Here is how to know if your security guards are doing their job. Ask for the patrol log from last night, and see whether it shows scanned checkpoints with times, or a signature at the bottom of a page. One is evidence. The other is a promise. Texas rules already require your guard company to keep documentation showing the service was actually provided, so this is a request they should be able to fill the same day.
What is patrol verification?
Patrol verification is the record that proves an officer physically walked your property. An officer scans fixed checkpoints with a phone or handheld device, and each scan writes a time, a location, and an officer ID to a log the client can read. It turns a patrol from something you were told happened into something you can check.
That log is the whole argument. A guard company either produces one or it doesn’t.
How do you know if your security guards are doing their job overnight?
Overnight is where the gap shows, because nobody is on site to watch the watcher. Three things tell you: scanned checkpoint times with gaps you can see, incident entries filed the night they happened rather than typed up later, and a supervisor check-in you can point to on the log.
Look at the timestamps, not the total. A round showing 6 checkpoints scanned inside 90 seconds didn’t happen. Neither did a shift where every round lands at exactly the same minute each hour. Real rounds vary. Our officers run patrols on GPS guard tour systems, and a supervisor checks in every shift, which is what makes the pattern readable. We don’t run random drive-bys, because a drive-by leaves nothing to read.
The 6 fields a patrol log has to contain
A patrol log is worth reading only if it carries all 6 of these. Anything less and you’re looking at a timesheet with a nicer header.
| Field | What it proves | What its absence hides |
|---|---|---|
| Checkpoint ID and location | The officer was at a specific spot, not the parking lot | Which parts of the property were skipped |
| Scan timestamp | When the round actually happened | Rounds bunched at shift end to fill a log |
| Officer name and license number | A licensed person did the work | An unlicensed or unregistered fill-in |
| Condition noted at each point | Someone looked, instead of tapping and walking | Doors, gates, and gaps nobody checked |
| Exception entries with a reason | Which points were missed and why | A round that looks complete because failures aren’t recorded |
| Supervisor review and sign-off | A second person read it | A log nobody inside the company ever opened |
Keep the log separate from the incident report in your head. A log proves presence. It cannot tell you what someone intended. An incident report describes an event and cannot prove anyone was standing there. Ask for both, and read them together.
Ask for a sample before you sign, not after an incident. A company that hands one over in an hour keeps them. A company that needs a week is building one.
What each checkpoint method actually proves
Each method proves a different thing, and the differences matter more than vendors admit. A QR sticker proves someone scanned a sticker. An NFC tag proves someone stood within a couple of inches of a fixed tag. GPS proves a phone reached a coordinate.
| Method | What it actually proves | Where it fails | Best use |
|---|---|---|---|
| NFC tag | The device touched a tag mounted at that spot | Tag can be pried off and carried | Interior doors, stairwells, mechanical rooms |
| QR code | The device photographed that code | A photo of the code scans from anywhere | Low-risk interior points, quick rollouts |
| RFID button | The reader contacted a fixed metal button | Needs a dedicated reader, not a phone | Harsh outdoor spots, older installs |
| GPS geofence | The phone entered a mapped area | Accuracy drifts indoors and near steel | Perimeters, yards, large lots |
| Photo with timestamp | A specific condition at a specific time | Only as good as what the officer aims at | Gates, seals, damage, staged materials |
The strongest setups pair two: a fixed tag for the location, and a timestamped photo for the condition. One proves presence. The other proves attention. The technology officers carry on Houston sites goes further than this, but checkpoint scanning is the part that ends up in your log.
Where patrol logs get faked, and how to spot it
Logs get faked in 3 ways, and all 3 leave marks. First, a portable tag: someone unscrews the NFC tag and scans it from the guard shack. You catch it by checking whether a tag’s scans all share the same GPS coordinate. Second, a photographed QR code scanned off a phone screen. You catch it by requiring a live site photo at the same point. Third, backfilled entries, where a whole shift posts within a few minutes near the end.
None of this means guards are dishonest. It means the work is repetitive and the industry moves people constantly. The Bureau of Labor Statistics counted 1,304,000 security guard and gambling surveillance jobs in 2025 and projects 1 percent growth through 2035, noting that rising use of surveillance technology is expected to somewhat limit demand for these workers. A large, slow-growing, high-turnover workforce is exactly the setting where an easy shortcut gets taken. Design for that and you get honest data from ordinary people.
Texas already requires your guard company to keep the proof
This is the part most property managers never hear. Under Texas Department of Public Safety rules, a licensed security company has to keep its contracts. It also has to keep “related documentation reflecting the actual provision of the regulated service.” The rule runs 2 years, counted from the later of the service date or the contract end. Timesheets, invoices, and scheduling records showing when licensed employees worked fall under the same 2-year rule.
So when you ask for last month’s patrol records, you’re not asking for a courtesy. You’re asking a licensee to show you records it is already required to maintain under Texas rules. A company that can’t produce them has a licensing problem, not a filing problem. That line works on any provider in the state, including us.
The same rule set covers one more thing worth knowing. Under the state’s private security statute and its rules, an individual can’t contract directly with you to perform a regulated security service unless they’re licensed as a company. The “I know a guy who does security on the side” arrangement isn’t a bargain. It’s unlicensed.
What happens when a checkpoint gets missed?
A missed checkpoint should trigger an alert to a supervisor during the shift, not appear in a report 3 weeks later. That is the difference between a system that manages patrols and a system that only records them.
Here is the part almost nobody tells a client. A patrol log showing zero missed checkpoints across a full month is a warning sign, not a clean record. Real sites generate exceptions. A contractor chains a gate that was open last week. A delivery runs long and the officer holds the entrance. Something is going on in the yard and the round waits. A log with no exceptions in it usually means exceptions aren’t being written down, and a company that hides small failures will hide larger ones.
What good looks like: the alert fires, a supervisor calls the officer, and the round either gets re-run or the miss is logged with a reason you can read. Ask to see an exception entry from a live account with the client name removed. It tells you more than a month of perfect rounds. On our accounts the escalation path is written into the standing orders every officer works to, so the officer on post knows who to call before anything else.
How to verify a Texas security license in 2026
You can check any Texas guard company yourself in about 2 minutes. The Texas Department of Public Safety runs a public licensee search through its Texas Online Private Security portal, covering both companies and individual officers. Type in the number on the proposal and see whether it comes back active. If a provider won’t give you a number to type, that is your answer.
Ours is B07315701, active since 2018, and the team behind it has 20 years on Houston posts. We run about 150 licensed officers across more than 100 commercial sites, all of them licensed by Texas DPS. Officers work in English and Spanish, coverage runs 24 hours a day with no holiday closures, and there is no long-term contract, so a site can run weekly, month to month, or long term.
What to ask about patrol proof before you sign
Four questions, all about the record rather than the sales pitch, and every one has a same-day answer if the company is real.
- Show me a patrol log from a live account for a full shift, client name removed.
- What checkpoint method goes on my property, and where do the tags get mounted?
- Show me one exception entry and what happened after it.
- How long do you keep patrol records, and how do I request them?
That last one has a right answer, and you already know it. Ask it anyway and see whether they do.
We answer all 4 before a contract exists, because our patrol coverage in Houston is built on documented rounds rather than a promise of them. The same log covers every post we staff, including construction site security and warehouse and distribution accounts, where after-hours dock activity is the whole exposure.
So, how to know if your security guards are doing their job at your property: ask your current provider for last week’s log and read the timestamps. Then tell us about your site and we’ll show you what ours looks like, or start with what a Houston security guard company should be handing you in the first place.
FAQs
How do I know if my security guards are doing their job?
Read the patrol log, not the invoice. Scans should show varied times across the shift, a named officer with a license number, conditions noted at each point, and exception entries where a point was missed. Six checkpoints scanned inside 90 seconds, or rounds landing at the identical minute every hour, mean the log is being filled rather than earned.
What should a security patrol log contain?
A usable patrol log carries 6 fields: checkpoint ID and location, scan timestamp, officer name and license number, the condition noted at each point, exception entries with a reason, and a supervisor review. Anything missing those is a timesheet. Ask for a redacted sample before you sign, not after something goes wrong.
Can a security guard fake a patrol log?
Yes, in 3 common ways: removing an NFC tag and scanning it from one spot, scanning a photographed QR code off a phone screen, and backfilling a shift’s entries near the end. Each leaves a pattern. Repeated identical GPS coordinates, missing live site photos, and clustered timestamps are the tells.
How long does a security company have to keep patrol records in Texas?
Texas DPS rules require a licensed company to keep contracts and documentation showing the service was actually provided. The clock runs 2 years from the later of the service date or the contract end. Timesheets, invoices, and scheduling records for licensed employees fall under the same rule. So a records request for last month is well inside what a licensee must already hold.
What is the difference between a patrol log and a daily activity report?
A patrol log is the machine record of where an officer scanned and when. A daily activity report is the officer’s written account of the shift. The log proves presence and cannot describe intent. The report describes events and cannot prove anyone was there. Ask for both, because either one alone leaves a hole.
Should a patrol log ever show zero missed checkpoints?
Rarely, and a full month of them should make you suspicious rather than satisfied. Real properties generate exceptions: a gate chained by a contractor, a long delivery, an incident that holds the officer. A log with no exceptions usually means misses aren’t recorded at all, which is a bigger problem than the misses.
