TACPOINTS Request a Demo
Pilot program — now forming

Every patrol.
Every checkpoint.
Accounted for.

TacPoints helps security teams plan patrols, verify checkpoints, document incidents, and give supervisors a clearer view of field operations.

Request a Demo Explore the Platform

ADAPT • ENGAGE • PROTECT

PRODUCT PREVIEW — FICTIONAL SAMPLE DATA

Server-timestamped scans Role-based access Full audit trail GPS only at scan, with permission Isolated client data
Why TacPoints

Patrol work you can prove — not just claim

Paper logs and radio check-ins leave supervisors guessing. TacPoints turns every patrol into a reliable, time-stamped operational record.

01 / VERIFY

Verified checkpoints

Each checkpoint carries a unique QR code. A scan is recorded on the server with the officer, checkpoint, route, and time — plus location context at that moment, when permission is granted.

02 / REVIEW

Exceptions, surfaced early

Missed, late, duplicate, or out-of-sequence scans are flagged for supervisor review as they happen — so a gap in coverage gets a follow-up, not a shrug at the end of the month.

03 / REPORT

Reports that hold up

Shift summaries, patrol completion, checkpoint history, and incident logs export to PDF or CSV — backed by an audit trail of edits, status changes, exports, and permission changes.

The patrol loop

One loop, from assignment to review

Every patrol runs the same complete cycle: assign, perform, verify, report, review. Nothing falls between the cracks because the loop has no gaps.

STEP 1

Assign

Managers build sites, routes, and shifts. Officers see exactly what they are responsible for.

STEP 2

Perform

Officers work the route checkpoint by checkpoint, with site instructions in hand.

STEP 3

Verify

Each QR scan is time-stamped on the server and checked against the patrol plan.

STEP 4

Report

Incidents and exceptions are documented in structured reports, with photos where permitted.

STEP 5

Review

Supervisors clear exceptions, close follow-ups, and share clean reports with clients.

Built for every role

Each person sees what they need — and only that

Access is enforced by role on the server, not just hidden in the interface. A client never sees another client's sites, and an officer never sees internal staffing notes.

Security Officer Mobile app

Sees the assigned shift, patrol route, checkpoints, and site instructions — and submits clear checkpoint and incident records from the field.

Field Supervisor Dashboard

Watches officer activity across sites: missed or late checkpoints, exceptions, incidents, and follow-up tasks, all in one live view.

Operations Manager Dashboard

Configures sites, shifts, routes, and staff access, and keeps service-level oversight across every account.

Client Viewer Portal

Views authorized reports and a limited, site-level picture of service delivery for their own sites only.

Company Administrator Admin

Manages organization settings, users, permissions, billing configuration, data retention, and audit history.

Our standard

Evidence, not assumptions

“A QR scan or a GPS point is an evidence signal — not absolute proof. TacPoints is designed around that honesty.”

Flags are for review, not verdicts

A missed or unusual scan raises an exception for a supervisor to review. It is never presented as proof of misconduct.

Location with consent and purpose

Location is captured at the moment of a checkpoint scan, with permission — not continuous tracking. Officers see a plain explanation of what is collected and why.

Hard-to-guess checkpoint codes

Checkpoint QR codes use unique identifiers that can be rotated or replaced, and repeated suspicious scans are reported.

Human judgment stays in charge

TacPoints records and organizes. Supervisors decide. The platform never scores or disciplines people automatically.

See TacPoints on your sites

Tell us how your patrols run today. We'll walk you through the platform and talk honestly about whether a pilot fits your operation.

Request a Demo

ADAPT • ENGAGE • PROTECT

Platform

The patrol-management platform

Everything in the first release is built around one job: a complete, verifiable patrol cycle. Features below are labeled by release scope — nothing here is vaporware dressed up as a shipping product.

First release

Organization & site setup

Create a customer organization, its sites, buildings and areas, and site-specific instructions officers see in the field.

First release

Roles & permissions

Administrator, operations manager, supervisor, officer, and client viewer — each with access enforced on the server.

First release

Officer roster

Invite users, assign roles, record basic work contact details, and deactivate access the moment it is no longer appropriate.

First release

Shift scheduling

Create shifts and assign officers to a site and patrol plan. Deliberately simple — no payroll machinery in the first release.

First release

Patrol routes

Define ordered checkpoints for each site or route, with reusable route templates and scheduled patrol windows.

First release

QR checkpoints

A unique QR code at every checkpoint. The officer scans it in the app; the server records who, where, and when.

First release

GPS context at scan

When permission is granted, location and accuracy are captured at the moment of a scan — context for the record, not continuous tracking.

First release

Checkpoint exceptions

Missed, late, duplicate, out-of-sequence, or suspicious scans are flagged automatically for supervisor review.

First release

Incident reports

Structured category, narrative, time, site, people involved where appropriate, photos or attachments, urgency, and follow-up status.

First release

Supervisor dashboard

Live shift overview, patrol completion status, exceptions, incidents, and recent activity — the whole operation at a glance.

First release

Reports & exports

Shift summaries, patrol completion, checkpoint history, and incident logs — downloadable as PDF or CSV where authorized.

First release

Audit trail

A retained record of important actions — edits, status changes, exports, and permission changes — protected from unauthorized alteration.

Officer workflow

A shift, step by step

Designed for the field: large tap targets, high contrast, minimal typing, clear scan feedback, and readable in daylight.

01

Sign in

The officer signs in securely and sees today's assigned shift.RECORDS — User identity and sign-in event

02

Start shift

The officer confirms the site and shift, and reviews the site instructions.RECORDS — Shift start acknowledgement and timestamp

03

Start patrol

The officer opens the assigned route and sees the checkpoint sequence.RECORDS — Patrol instance and start time

04

Scan checkpoint

The officer scans the site's QR code; the app confirms the checkpoint.RECORDS — Checkpoint, officer, server timestamp, route, permitted location context

05

Report exception

The officer files an incident or explains an inaccessible checkpoint.RECORDS — Incident / exception record with status and attachments

06

End shift

The officer completes the handoff notes and shift summary.RECORDS — Shift completion and submitted report

07

Supervisor review

The supervisor reviews exceptions and closes follow-up items.RECORDS — Review decision, notes, and audit history

The supervisor's home screen answers

  • Which sites and shifts are active right now?
  • Which officers are assigned — and have they acknowledged their shifts?
  • Which patrols are complete, in progress, late, or not started?
  • Which checkpoints were missed, late, duplicated, or out of order?
  • Which incidents need immediate attention or follow-up?
  • What changed since the last review of this site?

Deliberately not in the first release

  • NFC, camera, alarm, or access-control integrations
  • Automatic dispatch or emergency-response promises
  • Facial recognition, biometrics, or covert monitoring
  • AI scoring of employee discipline, credibility, or threat
  • Payroll, HR, or a public officer-tracking map

Each may be considered later — only with a validated customer need, a budget, and legal and technical review.

Roadmap

Built in stages, validated at each one

TacPoints grows in small, reviewable steps. A stage only starts when the previous one has proven itself with real users.

Phase 0Current focus

Validate

Interview security operators and site managers, map how patrols actually run today, and identify a specific painful workflow and a pilot customer.

Phase 1Current focus

Prototype

Test the officer scan flow and supervisor dashboard with real users until the main workflow works without coaching.

Phase 2

MVP

Sites, roles, shifts, QR checkpoints, patrol events, incident reporting, supervisor dashboard, and basic reports — the full patrol cycle, end to end.

Phase 3

Pilot

Run with one or two sites. Measure scan completion, reporting quality, reliability, and supervisor time saved.

Phase 4

Commercial

Billing, onboarding, support, documentation, service terms, and a security review — repeatable and sustainable.

Phase 5

Expand

Only where customers pull for it: integrations, advanced scheduling, multi-site analytics, and facility inspection workflows.

Talk to us about a pilot See who it's for
Solutions

For the teams who answer for patrols

Different organizations run patrols for different reasons. The record they need is the same: what was planned, what happened, and what still needs attention.

Contract security providers

You sell verified service. Clients renew contracts with providers who can show — not just say — that patrols happened as agreed.

How TacPoints helps

  • Supervisors oversee many client sites from one dashboard, with exceptions ranked by what needs attention.
  • Each client sees only their own sites and approved reports — organizations are fully isolated from each other.
  • Patrol completion and incident reports are export-ready for contract reviews and renewals.

In-house security teams

Your own officers, your own buildings. Rounds need to be consistent across shifts and provable when an incident is questioned later.

How TacPoints helps

  • Standard routes and patrol windows keep every shift covering the same ground the same way.
  • Structured incident reports replace scattered notebooks, texts, and radio logs.
  • A full audit trail shows who changed what, and when — useful for internal review and insurance questions.

Property & facility operators

You buy patrol services for your sites. You need a clear picture of the service you're paying for — without access to anyone's internal operations.

How TacPoints helps

  • A limited client view shows patrol completion and approved reports for your sites only.
  • Incident logs give you a factual record for tenant questions, vendors, and insurers.
  • No internal staffing notes, no other clients' data, no security-sensitive configuration — by design.
Request a Demo Explore the Platform
About

One company. One brand.
One trustworthy record.

TacPoints is a security operations company building patrol-verification technology. Our promise is simple: tactical advantage through clear, verified operational information.

Mission

Why TacPoints exists

Patrol work is only as credible as its record. When rounds live on paper logs and radio calls, supervisors can't see problems while they're still small, officers' good work goes unproven, and clients are asked to trust what they cannot check. TacPoints closes that gap: every route, checkpoint, and incident produces reliable, time-stamped information that the right people can review.

How we work

Narrow first, then earned growth

We start with one problem — patrol verification — and solve it exceptionally well before expanding into broader facility operations. Features are added when real customers need them, not to lengthen a feature list. And we never claim a capability, certification, or customer we don't have.

PRINCIPLE 01

Clarity over flash

Interfaces an officer can use at 3 a.m. in the rain, and a supervisor can read at a glance. If it needs explaining, it isn't finished.

PRINCIPLE 02

Reliability is the product

A patrol record that goes missing is worse than no record at all. Backups, monitoring, and a tested recovery process are part of the platform, not an afterthought.

PRINCIPLE 03

Privacy by design

Collect only what the service needs. Location is gathered at defined moments for a defined purpose, explained plainly to the people it concerns.

PRINCIPLE 04

Honest about limits

QR codes and GPS are evidence signals, not absolute proof. TacPoints supports human judgment — it never replaces it, and it never pretends otherwise.

Talk to TacPoints

Questions, pilot interest, or a demo — start with the request form.

tacpoints.com Contact TacPoints
Contact

Request a demo

Tell us how your patrols run today and what isn't working. We'll reply with next steps and an honest view of whether TacPoints fits.

What happens next

A short conversation about your current patrol process — routes, checkpoints, reporting, and where the record breaks down. No pressure and no inflated claims: if a pilot makes sense, we'll scope it together with clear dates, scope, and data handling.

Website
tacpoints.com
Who should ask
Security providers, in-house teams & property operators
Pilot status
Pilot program now forming
Your data
Used only to respond to your request
Please enter your name.
Please enter a valid work email.
Please enter your organization.
Tell us a little about the problem — a sentence is enough.
Your request is ready to send 

                  

                    Open in email app
                    
                    Copied ✓
                  

                

              

            

          

        

      


      
      

        

          Legal
          
Privacy Policy

          Draft — pending professional legal review
          
How TacPoints handles operational data. This policy is written for the patrol platform described on this site and will be finalized with legal review before launch.


          
What we collect

          
    
            
  • Account data — names, work email addresses, roles, and organization details needed to provide the service.
    • 
            
  • Patrol records — checkpoint scan events with checkpoint, officer, route, and server-recorded timestamps.
    • 
            
  • Location at scan — when permission is granted, the location and accuracy captured at the moment of a checkpoint scan. TacPoints does not perform continuous location tracking.
    • 
            
  • Incident reports — narratives, categories, and photos or attachments an officer chooses to submit.
    • 
            
  • Audit events — records of significant actions such as edits, status changes, exports, and permission changes.
    • 
          


          
Why we collect it

          
Data is collected only to operate the patrol-verification service: planning patrols, verifying checkpoints, documenting incidents, producing reports, and maintaining an audit trail. We practice data minimization — if the service does not need it, we do not collect it.


          
Separation between organizations

          
Each customer organization's data is isolated. A user cannot access another organization's records without explicit authorization, and client viewers see only their own sites and approved reports.


          
Security

          
Data is encrypted in transit and at rest. Access is controlled by role-based permissions enforced on the server, and audit logs are protected from unauthorized alteration.


          
Retention and deletion

          
Retention periods for location data, incident media, and employee records are defined per organization and documented in customer agreements. Data is deleted or anonymized when its retention period ends or when a valid deletion request is fulfilled.


          
Your choices and requests

          
Officers are told plainly what is collected, when, and why, including how location permission works. To ask a question about your data, or to request access, correction, or deletion, contact TacPoints through the demo/contact form on this site, identifying your organization.


          
Cookies

          
This website uses no advertising or cross-site tracking cookies. The product uses only the cookies and local storage strictly needed for sign-in and session security.


          
Changes

          
If this policy changes materially, we will update this page and note the effective date before the change applies.

        

        

      


      
      

        

          Legal
          
Terms of Service

          Draft — pending professional legal review
          
The terms governing use of the TacPoints website and patrol platform. Final terms will be published with customer agreements before commercial launch.


          
The service

          
TacPoints provides software for planning, verifying, documenting, and supervising security patrol activity, including QR checkpoint verification, incident reporting, supervisor dashboards, and reports.


          
Evidence signals

          
QR scans, timestamps, and location context are evidence signals that support supervisor review. They are not, by themselves, absolute proof that a person physically completed every task, and TacPoints does not present them as such. Exception flags indicate items for human review; they are not findings of misconduct.


          
No guaranteed outcomes

          
TacPoints does not guarantee security outcomes, patrol completion, or incident prevention. The platform records and organizes operational information; security decisions and outcomes remain the responsibility of the organizations using it.


          
Accounts and acceptable use

          
    
            
  • Each user is responsible for activity under their own account and for keeping credentials secure.
    • 
            
  • Access must stay within the roles and permissions granted by your organization.
    • 
            
  • You must not attempt to access another organization's data, forge or replay checkpoint codes, or interfere with the service's audit records.
    • 
            
  • Location features may be used only as disclosed to the people being recorded and as permitted by applicable law.
    • 
          


          
Out of scope

          
The service does not provide emergency response, dispatch, alarm or camera monitoring, access control, facial recognition, or automated decisions about employee discipline.


          
Availability and changes

          
We work to keep the service reliable, with backups and a tested recovery process, but we do not promise uninterrupted availability. Features in development may change before release; only capabilities described as part of your customer agreement are committed.


          
Contact

          
Questions about these terms can be sent through the contact form on this site.