Why Generic Attendance Software Fails Security Agencies
Most attendance products were designed for an office or a factory: one location, one gate, staff who arrive between 09:00 and 10:00 and leave in the evening. A security agency is the opposite. Guards are posted at dozens or hundreds of client sites the agency does not own, on 8 and 12-hour shifts that run through the night, often with no supervisor present, using low-cost Android phones with patchy connectivity, and every attendance record has to become both a wage line and a client invoice line.
When a generic tool is forced into this shape, the failures are predictable. A single company-wide geofence cannot cover 60 sites. Face verification tuned for a lit office fails at a 02:00 gate post. Rosters live in WhatsApp so the software has no idea who was supposed to be where, and cannot flag the guard who checked in at the wrong site. Month-end billing still means someone typing man-days into Excel.
So the buying question is not 'which attendance app is best' but 'which product understands that a guard's day is a post, a shift, a client and a rate, all at once'. The checklist below is organised around the guard's day. Use it alongside the general buyer's guide to attendance software in India for the broader questions about payroll and rollout.
- Guards work at client premises: the software must handle many sites, each with its own geofence and rules
- Night posts, lone workers and low-end phones are the normal case, not the edge case
- Attendance must connect to a roster (to validate) and to billing (to invoice), not sit alone
Field Capture: Geofences, Selfie and Liveness, Offline Check-in
Start with how the guard marks attendance. You need a geofence per site, not per company, with a radius you can set individually: a gated township may need 300 metres, a small ATM post 50 metres. The product should allow a guard to be assigned to a specific site so a check-in from a different site is flagged rather than accepted. Ask whether the system flags mock-location apps on Android, because fake GPS is the commonest way guards mark attendance from home.
Identity verification at a night post is harder than in an office. A selfie with liveness detection (the app checks for a live face, not a printed photo or a phone screen) is the practical standard; fingerprint devices cannot be installed on every client's gate. Test it in the dark, with a torch, with a cap and a mask, because that is how your guards actually look at 22:00 in December. Face recognition that stores encrypted descriptors rather than photos also keeps you safer on data protection.
Connectivity inside basements, factory compounds and rural highways is unreliable. The app must accept a check-in offline, store it with the device timestamp and GPS fix, and sync when network returns, with the record clearly marked as synced-later so a supervisor can spot patterns of abuse. Attend Mitra's guard attendance combines per-site geofences, selfie with liveness, mock-location flagging and offline attendance that syncs automatically, which is the minimum set an agency should insist on.
- Per-site geofence with individually configurable radius; guard assigned to a site, not just a company
- Selfie with liveness check that works in low light; test it at night during the trial
- Mock-location detection on Android
- Offline check-in with delayed sync, visibly marked as such in reports
Roster-to-Attendance Validation and Reliever Handling
Attendance without a roster is just a list of timestamps. The product should hold the duty roster (who is posted to which site, which shift, which dates) and compare every check-in against it. That comparison is what tells you a post was uncovered at 20:15, a guard doubled two consecutive 12-hour shifts, or someone checked in at Site B while rostered at Site A. If the software cannot do this, your supervisors will still be doing it by phone.
Ask specifically about shifts crossing midnight. A 20:00 to 08:00 shift must count as one duty on the date it started, not split across two days that break wage and billing counts. Ask about roster presets, because most agencies run the same weekly pattern per site for months, and about draft-then-publish so that a half-built roster is not pushed to 200 guards' phones.
Relievers are the daily reality of guarding: someone does not show, a reliever is sent, and now two guards have partial attendance at the same post. The system must let a supervisor assign the reliever to the post from their phone, record the actual hours each guard covered, and produce a single billable duty for the client. Watch for products that treat this as an exception you have to fix in Excel. Attend Mitra's guard scheduling handles rosters, roster presets, open shifts and shift swaps with approval, with reliever hours recorded against the post.
- Roster stored in the system and every check-in validated against it (site, shift, date)
- Night shifts crossing midnight counted as one duty
- Roster presets and draft-then-publish for weekly rosters
- Reliever assignment from a supervisor's phone, producing one billable duty per post
- Warning when a guard is rostered on an approved leave day
Supervision, Patrols and Incidents
Clients pay for a guarded site, not for a check-in record. The software should give you proof of supervision and activity between check-in and check-out. Three features matter. First, supervisor site-visit check-in: when your field officer visits a site, they mark presence there with GPS, creating a record you can show the client that the site was inspected on the dates promised.
Second, guard tour or patrol monitoring: NFC tags or QR codes at checkpoints that the guard scans on a defined route and frequency, with missed checkpoints flagged to the control room. This is what converts a 'guard present' record into a 'site patrolled' record and is increasingly demanded by industrial and residential clients. Ask vendors how missed checkpoints are escalated and whether the patrol log can be shared with the client.
Third, incident reporting and SOS from the guard's app: a structured incident form with photos, a timestamp and location, and a one-tap SOS that alerts supervisors. Attend Mitra's patrol monitoring covers NFC and QR checkpoints, incident reports, SOS alerts and supervisor site-visit check-in, with duty reports per site that can be shared with the client.
- Supervisor site-visit check-in with GPS, reportable per client
- Patrol checkpoints via NFC or QR with missed-checkpoint alerts
- Incident reports with photo, time and location from the guard's phone
- SOS alert routed to the supervisor and control room
- Duty reports per site that can be shared with clients
Billing, Payroll and PSARA Outputs
The output side is where agencies lose the most money. Insist on a site-wise man-hour or man-day export that matches how your contracts bill: per 8-hour or 12-hour duty, with overtime and national-holiday duties shown separately, per client and per site, for a date range you choose. If the product cannot produce this, month-end billing stays manual, and the invoice and wage register will keep disagreeing.
On the payroll side, guards are minimum-wage employees in most states, classified as semi-skilled (unarmed) or skilled (armed or supervisor), with rates revised typically twice a year. The software needs a wage master by state and category that you can update when the notification changes, an overtime calculation at double rate derived from attendance, and EPF and ESIC computation with the current ceilings (EPF wage ceiling ₹25,000 from 17 September 2026; ESIC gross ceiling ₹21,000). It should generate payslips, a bank NEFT file and the salary register. Be clear that attendance-linked payroll tools like Attend Mitra's guard payroll prepare the data and payslips; they do not file EPF or ESIC returns for you.
PSARA requires the agency to maintain a register of guards and supervisors with names, addresses, photographs and salaries, plus management and client details, open to inspection by the Controlling Authority. Ask whether the employee database, deployment records and salary registers can be exported in a form that satisfies this without re-keying, and ask to see that export during the demo rather than taking it on trust.
- Site-wise man-hour export per client, per duty type, for any date range
- Wage master by state and skill category, editable when minimum wages revise
- Overtime at double rate, EPF and ESIC computed from attendance with current ceilings
- Payslips, NEFT bank file and salary register
- Employee, deployment and salary data exportable for the PSARA register
Device Realities and Pricing Questions
Your guards carry entry-level Android phones, often several years old, with limited storage and cracked cameras. Some do not have smartphones at all. Test the app on the cheapest phone in your fleet, not on the vendor's demo device. Check the installed size, whether it works on older Android versions, and how much data it consumes per check-in. Where guards share a phone or have none, kiosk mode on one tablet at the post lets multiple guards mark attendance with face verification on a shared device.
On pricing, most products charge per guard per month. The key question is whether you pay for active guards (those who actually marked attendance or were rostered in the month) or for total headcount in the database, because agencies carry large pools of inactive or seasonal guards. Ask what happens to pricing when you add a client with 80 guards for a three-month event contract. Ask whether the mobile app, client reports and supervisor app are included or priced separately.
Also ask about data: who owns the attendance history, can you export everything if you leave, and how long records are retained. Attend Mitra prices per active employee per month, includes the Android and iOS apps, and offers a 14-day free trial without a card, which is long enough to run the demo script below at two or three real sites.
- Test on your worst phone, at night, at a real post, before signing
- Kiosk mode on a shared tablet for guards without smartphones
- Per active guard vs per headcount pricing; clarify seasonal surges
- Confirm apps, supervisor features and client reports are included
- Confirm data export on exit and retention policy
A 10-Scenario Demo Script and the Red Flags
Do not let the vendor drive the demo. Take these ten scenarios, ask to see each one end to end, and have your operations manager watch rather than your IT person. The trial period should reproduce them at two live sites, with a night post included.
Red flags to watch during the process: a single geofence for the whole company; face verification demonstrated only in a bright room; 'offline mode' that turns out to mean the app opens but the check-in fails; rosters that exist only as a printout feature; billing exports that are just the attendance log; pricing on total headcount; and any statement that the software 'handles PSARA compliance' without being able to show you the register output. A vendor that cannot answer how mock GPS is detected has not worked with security agencies. For a wider comparison of products in this category see our best attendance software for security agencies roundup and the security guard attendance software page.
- 1. Guard checks in at 20:00 at Site A with selfie; show the record with geofence result and liveness result
- 2. Same guard tries to check in from 2 km away; show how it is blocked or flagged
- 3. Guard checks in with a fake-GPS app installed; show the mock-location flag
- 4. Guard checks in with no network in a basement; show the record after sync, marked as synced later
- 5. Night shift 20:00 to 08:00 crossing midnight; show it counted as one duty on the correct date
- 6. Rostered guard does not show by 20:15; show the alert and assign a reliever from a supervisor's phone; show the billable duty
- 7. Guard completes a patrol scanning four NFC or QR checkpoints, misses one; show the alert
- 8. Supervisor visits Site B; show the site-visit record on the client report
- 9. Export man-days for Client X for 1 to 30 September split by 8-hour and 12-hour duties and national holidays
- 10. Run payroll for one guard with 26 duties, 3 duties of overtime and ESIC eligibility; show payslip, NEFT line and PF/ESIC amounts