Prove the guard was actually on post.
A code tapped into a phone does not prove identity or presence. A security agency needs to show that a specific, verified officer was physically at a specific post at a specific time, and that the hours billed to the client match hours a punch can actually prove.
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: the location it was taken at, a live photo of the person taking it, a confidence score on whether that photo matches the officer assigned to the post, and a record of how that punch location relates to the post's actual address.
gates
in every punch, on post
question sets
punch-in and punch-out differ
platform uptime
SLA commitment
Every punch at a post is a five-gate sequence, not a code and a timestamp.
Punch in and punch out both follow the same mandatory order, and each gate blocks the next until it clears. 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.
Gate 1
Geofence check
An admin draws a boundary around the post address and sets the radius. The officer's app checks live distance from center before the punch can proceed, so a punch cannot be entered from off site.
Gate 2
Job confirmation
The officer confirms the specific post being covered, or selects the right one if more than one assignment sits at that address that shift.
Gate 3
Photo capture
A live photo is required to continue. On an overnight, single-officer post with nobody else present, this is the only visual confirmation of who is actually there.
Gate 4
Face confidence
The photo returns a numeric confidence score, not a pass or fail. A low-confidence match, the kind buddy punching produces, is caught and the officer is prompted to retake it before the punch clears.
Gate 5
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.
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.
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.
A guard on post,
proven, not assumed.
We will map Hirebase to your compliance framework,
your ERP and your region.
© 2026 Hirebase. All rights reserved.