Eliminate Ghost Posts & Billing Disputes.
Verified Guard Attendance on Every Shift.
Proven across US security deployments and expanding globally. Hirebase eliminates abandoned posts, buddy punching, and client SLA penalty deductions with 10-metre GPS geofencing, mobile AI facial liveness checks, and post hazard sign-offs—ensuring every billed hour is backed by tamper-proof attendance evidence.
An agency bills per guard-hour at a post. Without proof, that hour is a dispute waiting to happen.
A post covered on paper is not the same as a post covered in fact. If a punch can be entered by anyone with the code, an agency cannot tell a client, an insurer or a court who was actually there. Buddy punching and phantom posts are not just an internal integrity problem, they show up directly on the invoice: a client questioning whether a post was really staffed for the hours billed has, without independent proof, only the agency's word to go on. Every punch needs to carry its own proof: a 10-metre GPS geofence validation, a 1.5-second live facial liveness check with numeric anti-spoofing confidence, and a tamper-proof timestamp tied directly to the post contract. Hirebase gives security guard agencies defensible operational records that stop SLA penalty deductions and prove contract compliance without dispute.
checks
in every punch, on post
question sets
punch-in and punch-out differ
photo required
the punch button stays disabled without it
Every punch at a post carries a geofence check, a photo, and a safety check, not a code and a timestamp.
Punch in and punch out both run the same checks, in the same order. That matters most on posts nobody else is watching: an overnight, single-officer assignment with no supervisor or colleague on site to confirm the officer showed up. Full step-by-step verification detail lives on Verification & Enforcement.
Check 1
Geofence check
An admin draws a boundary around the post address and sets the radius. Every punch is checked against live distance from that boundary, and out-of-geofence punches are flagged for review.
Check 2
Photo capture
A live photo is required to continue — the punch button stays disabled until it's done. On an overnight, single-officer post with nobody else present, this is the only visual confirmation of who is actually there.
Check 3
Face confidence
The photo returns a numeric confidence score, not a simple pass or fail, giving an agency a real signal to review instead of a checkbox that only shows the punch happened.
Check 4
Safety Q&A
A short set of hazard questions is reviewed and confirmed before the shift starts. Punch-in and punch-out use different question sets, not the same quiz repeated at the end of the post.
One shift, several posts on the tour, not one fixed spot.
Coverage isn't always a single door. A patrol assignment moves an officer between several checkpoints across a property or a contract during one shift, and each stop needs its own proof, not one punch standing in for the whole tour. A single shift can nest up to five job-site check-in and check-out stops, each independently timestamped and photo-documented, so a multi-checkpoint patrol produces a separate, verified record per stop.
Each checkpoint on the tour gets its own timestamped, photo-documented check-in and check-out, not a single punch covering every stop on the property.
The path between checkpoints, on a map.
Distance and travel time between waypoints are computed from real GPS readings and laid over a map for every leg of the tour, so the route an officer actually walked between checkpoints is reviewable after the fact, not just the total hours they reported for the shift.
Per-leg distance and travel time sit next to each checkpoint's photo and timestamp, on the same record.
A guard's punch is tied to the post's actual address, not a raw GPS point.
The Enhanced Punch report uses real routing data to show Distance From Job, Travel Time and Traffic Time for every punch, reconciled against the job the officer was assigned to. This is raw distance and elapsed time only, not a mileage reimbursement or dollar calculation, but it is exactly what a billing dispute needs: whether a punch actually traces back to the billed post.
When a client questions an invoice, the agency has more than a timesheet to answer with: the geofence distance at the post, computed per punch, sitting next to the hours billed.
A selfie and a map pin, in and out.
Every punch carries an in and out selfie photo alongside a map pin, so the reconciled distance and travel-time data sits next to visual and location confirmation for the same event. For a post covered overnight with no one else present, that pairing is the record: who, where, and how far from where they were supposed to be.
In/out selfies and map pins are attached to the same punch record the distance and travel-time figures are computed from, all readable from the Enhanced Punch report.
An incident record built for OSHA and workers' compensation, not a text message to a supervisor.
An incident at a post, a trespasser, an injury, a break-in, needs to hold up when a client, an insurer or a court reviews it later. An incident record is organized into the categories that review will actually ask for: employee details, incident details, medical and investigation notes, workers' compensation status, and injury information, with up to five photos attached directly to the record.
Incident and comp details capture the job, weather, supervisor, date and time and who investigated it, plus the DWC first-report-of-injury form and its dates on the same record.
Evidence attaches up to five photos directly to the incident, not a separate file to track down later.
Every call and message to a guard, logged against that person.
A dispatcher checking in on an officer at a post, or an officer calling in an issue, builds a full timestamped history against that specific person, not a note in a shared inbox. Admins log a call with an explicit direction choice and notes; a separate per-officer message thread carries the written conversation. Both directions, dispatcher-initiated and officer-initiated, are attributed and timestamped. This is the same calling and messaging framework covered on Sales & Client Growth.
Call Out / Call In logs every dispatcher- or officer-initiated call into that person's history.
A dedicated message thread keeps the written conversation with that officer in one place, separate from the call log.
Security agency operational & dispute defense decision criteria.
Compare Hirebase against legacy guard tour wands and standalone time-tracking apps across mission-critical post verification, patrol telemetry, and billing defense.
| Operational Requirement | Hirebase Platform | Legacy Guard Wands (Guard1, Silvertrac) | Point Time Tracking Apps (Deputy, When I Work) |
|---|---|---|---|
| Post Physical Presence & Buddy-Punching Defense | 10m GPS geofencing, 1.5s live camera selfie with numeric face confidence score, out-of-geofence punches flagged for review. | ~Magnetic baton or NFC tag swipe proves a wand touched a sensor, with zero biometric proof of which guard held it. | Basic smartphone app with easily spoofed GPS coordinates, no facial anti-spoofing, and zero post-specific hazard sign-offs. |
| Multi-Checkpoint Patrol Route Telemetry | Up to 5 nested checkpoint stops per shift with independent timestamps, photo proof, and Enhanced Punch routing distance and travel time. | ~Requires guards to dock physical wands at end of shift into hardware download docks before patrol data can be inspected. | Single blanket punch at shift start/finish; completely incapable of tracking discrete checkpoints on a multi-building tour. |
| Abandoned Post & Dispatch Alerting | Master Project View with real-time no-show detection, automated dispatcher Call Out / Call In history logs, and dedicated officer message threads. | ~Post-incident discovery only; dispatchers learn a guard abandoned their post hours later when the property manager complains next morning. | Basic push notification to guard's phone with no automated dispatch escalation protocol or centralized muster roll visibility. |
| Incident Reporting & OSHA / Workers' Comp Defense | Structured 5-category incident records (employee, incident, medical/investigation, workers' comp DWC, injury) with 5 photo attachments. | ~Separate incident reporting software or paper log binders; photos and incident notes disconnected from timesheet and GPS data. | Unstructured plain-text notes field or external supervisor text messages with zero OSHA or workers' comp audit defensibility. |
| Enterprise Guard Licensing Economics | Predictable flat enterprise licensing with zero per-guard monthly seat tax; add seasonal or reserve officers with zero cost penalty. | ~Expensive proprietary wand hardware purchases ($300-$800/wand) plus annual software maintenance fees and battery replacements. | Punitive per-user monthly seat tax ($4-$8/guard/mo) that escalates costs when rotating high-turnover security rosters. |
Stop Ghost Posts & SLA Chargebacks
10m geofence boundaries, numeric face confidence scoring, and punch-in hazard Q&A ensure every billed guard hour is backed by verifiable physical evidence.
Zero Per-Guard Headcount Tax
Maintain reserve rosters of hundreds of licensed security officers without incurring escalating monthly per-user software seat penalties.
Frequently asked questions about security workforce software.
Operational answers on how Hirebase stops buddy punching, tracks multi-checkpoint patrols, supports OSHA incident compliance, and delivers flat licensing.
How does Hirebase eliminate ghost posts and buddy punching for security guard agencies?
Hirebase enforces a three-point verification sequence on every post punch: an admin-defined 10-metre GPS geofence boundary, an instantaneous 1.5-second camera selfie with numeric facial confidence scoring, and customized post safety questions. The punch button remains physically disabled until the selfie is captured, preventing guards from having peers punch in remotely or logging shifts from off-site vehicles.
Can Hirebase track mobile patrol routes with multiple checkpoint stops during a single shift?
Yes. Hirebase allows up to five nested job-site check-in and check-out stops within a single scheduled shift. Each checkpoint stop captures an independent timestamp, photo record, and geographic coordinates. Furthermore, the Enhanced Punch report calculates the physical routing distance and travel time between waypoints, providing clients and dispatchers with full visibility into the officer's patrol tour.
How does Hirebase support OSHA compliance and incident reporting for on-duty security guards?
When an incident, trespass, or workplace injury occurs on post, guards and supervisors log the event directly into Hirebase across five structured categories: employee details, incident circumstances, medical and investigation notes, workers' compensation status (including DWC first-report-of-injury form tracking), and injury specifics. Up to five high-resolution evidentiary photos can be attached directly to the permanent record.
Does Hirebase charge per-guard monthly seat fees for seasonal or high-turnover guard staffing?
No. Hirebase operates under a flat enterprise licensing model with zero per-guard per-month seat taxes. Security agencies can onboard, dispatch, and manage hundreds of full-time, part-time, or seasonal reserve officers without worrying about software bills escalating with roster turnover or fluctuating client contracts.
Go deeper
Practical answers for your evaluation
A guard on post,
proven, not assumed.
We will map Hirebase to your compliance framework,
your ERP and your region.