Guard deployment to sites and shifts
Assign guards to client sites and shifts, keeping the coverage picture live.
Guards on the right sites, shifts covered, incidents on the record.
Security services ERP that runs guard deployment across client sites and shifts, proves attendance with located punches, records incidents against the post, and turns those hours into payroll and client billing.
A security company's whole product is presence: the right guard, on the right site, for the right shift — and being able to prove it. When that runs on a whiteboard and a WhatsApp group, cover gaps go unnoticed, incident reports live on someone's phone, and the hours that pay guards and bill clients are two different guesses. Farexa makes deployment a live record: guards assigned to client sites and shifts, replacements logged when someone can't cover, and attendance that proves who actually stood the post.
Because attendance punches carry their time and location, a guard's presence on site is evidence, not a claim — which matters when a client asks whether the post was manned. Incidents get logged against the assignment rather than lost in a call, so there's a record of what happened and where. And since payroll and client billing both run off those same proven hours, the gap between what you pay the guard and what you bill the client is a visible margin instead of a monthly reconciliation.
It's the operating system for a guarding business: shifts planned and covered, presence proven, incidents recorded, and the money — pay and billing — coming from the same hours the operation actually worked.
Key features
How Farexa maps to security services.
Located attendance
Time-stamped, located punches prove a guard stood the post, not just that they were rostered.
Replacements for cover
When a guard can't cover, a replacement is a recorded action, so gaps are handled on the record.
Incident logging
Log incidents against the assignment and post, so what happened is recorded, not recalled.
Shifts and schedules
Rotating shifts are read correctly, so hours and overtime reflect the roster.
Payroll on proven hours
Payroll runs on the same attendance, so guards are paid for hours actually worked.
Client billing from the same hours
Bill clients from the hours guards were present, tying charge to proven cover.
Support requests from clients
Client requests and issues are tracked as conversations rather than lost calls.
How it works
From roster to proven, billed cover.
01
Set up sites and guards. Register client sites, guards, shifts, and the contracts they're covered under.
02
Deploy to shifts. Assign guards to sites and shifts, recording replacements when cover changes.
03
Prove presence. Located punches confirm who stood which post, and incidents are logged against it.
04
Pay and bill from proven hours. Payroll runs on those hours, and client billing is built from the same presence.
05
Answer the client. Coverage, incidents, and hours are on the record when a client asks.
Who it's for
Who guards with it.
- Security and guarding companies — Deployment, proven presence, and billing on one system.
- Manpower suppliers with guarding — Guards run as part of a wider labour-supply operation.
- Facilities with security teams — Guard coverage alongside the rest of site services.
- Operations managers and owners — Managers cover the roster; owners read presence, incidents, and margin.
Works with
The app cluster for security.
- Workforce — Guard deployment to sites and shifts, with replacements and incidents.
- Attendance — Located punches that prove a guard stood the post.
- Payroll — Runs on the same proven hours that bill the client.
- Manpower — The labour-supply business side — contracts and client billing.
- Support Tickets — Client requests tracked as conversations.
FAQ
What security companies ask.
Can I prove a guard was actually on site?
Yes. Attendance punches carry their time and location, so a guard's presence on the post is evidence rather than a claim — which is exactly what you need when a client asks whether a shift was manned.
How are shift gaps and replacements handled?
Guards are deployed to sites and shifts as a live record, and when someone can't cover, the replacement is a recorded action — so gaps are handled and visible rather than discovered later.
Are incidents recorded?
Yes. Incidents are logged against the assignment and post, so what happened and where is on the record instead of living in a phone call or a message thread.
Does it connect guard pay to client billing?
Yes. Payroll and client billing both run off the same proven attendance hours, so the gap between what you pay a guard and what you bill the client is a visible margin, not a monthly reconciliation of two different numbers.
Which apps does a security company start with?
Usually Workforce and Attendance to get deployment and proven presence in place, then Payroll and Manpower so pay and client billing run off the same hours.
Prove the post was manned.
Book a walkthrough with your own sites and shifts, and see located attendance turn presence into payroll and billing.