Why deployment and billing drift apart
Sanctioned strength known only from the contract file
The client agreed to 18 guards, but the ops team works from a WhatsApp list that has drifted to 16 names and one duplicate, so the vacancy is invisible until the client counts.
Transfers recorded nowhere
A guard moved from a mall to a warehouse on the 12th is billed to the mall for the whole month and paid on the warehouse rate, or the reverse.
Licence and armed requirements unchecked
An armed post is filled with whoever is available; the arms licence expiry is in a file cabinet, not in the deployment record.
PSARA register rebuilt before inspection
The section 15 register of guards, supervisors, sites and clients is assembled in a hurry when the Controlling Authority asks, from records that do not match each other.
How Attend Mitra manages guard deployment
Client → site → post → shift hierarchy
Model each contract as sites, posts and shifts with sanctioned headcount and attributes, so 'deployed' and 'vacant' have a precise meaning per post.
Deployment board every morning
Sanctioned, deployed and vacant strength per site and shift on one screen, with vacant posts sorted by how long they have been open.
Posting orders and transfers with dates
Generate a posting order when a guard is assigned, record transfers with effective dates, and let attendance, payroll and billing follow the deployment history automatically.
Register and invoice from the same record
Export the PSARA register extract, the client's man-day statement and the site-wise cost from one deployment and attendance dataset that always agrees with itself.
Deployment management features
Client & Contract Master
Client details, contract period, sanctioned posts per site and shift, rate card and approving contact stored together.
Post Attributes & Eligibility
Armed, supervisor, lady guard, gunman licence and training flags on posts and guards, with expiry dates that surface before posting.
Posting Order Generation
A deployment letter with guard name, photo, site, post, shift and reporting officer generated from the record and shared with the client.
Transfer History
Every move between sites with effective date and reason; the guard's app shows the current site and the history stays for audit.
PSARA Section 15 Register Extract
Guard and supervisor names, addresses, photographs, salaries, management details and client list exported in a register-ready format.
Deployment-to-Invoice Reconciliation
Deployed days per post compared with attendance-verified days and the invoice, with differences listed for the ops head to resolve.
From Check-In to Payroll-Ready Reports
Client & Site Created
Client contract, sites, posts and shifts entered with sanctioned strength and armed or licence requirements.
Guards Posted
Guards assigned to posts; posting order generated and the guard sees the site and shift in the app.
Vacancy Monitored
Sanctioned versus deployed versus vacant strength visible per site every morning on the deployment board.
Transfers Recorded
Guard moved between sites with effective dates; attendance and billing follow the deployment history.
Register & Invoice Reconciled
PSARA register extract, verified man-days and client invoice drawn from the same deployment record.
What the agency gains
Vacancies visible before the client counts
A post open since Tuesday shows on the board on Wednesday morning, not in the client's month-end complaint.
Bill for what was deployed and present
The invoice is built from deployed posts and verified attendance, which removes the 'you billed 18, we saw 15' dispute.
Licence compliance by design
An armed post cannot be filled by a guard whose licence has expired without an explicit override that is logged.
PSARA inspection without a scramble
The section 15 register extract is produced from live data, with photographs and salaries, whenever the Controlling Authority asks.
Transfers stop leaking money
Effective-dated moves mean the guard is billed to the right client and paid at the right site rate for each part of the month.
Operations scale beyond one person
Deployment knowledge is in the system, so a branch manager can run 40 sites without the founder on every call.
Deployment scenarios
Bank branch contract across a district
A bank sanctions one day guard and one night guard at 22 branches, with armed guards at four cash-handling branches.
e.g. the deployment board shows 44 posts, 42 deployed and 2 vacant; the armed post at one branch is flagged because the assigned guard's licence expires in ten days.
Guard transferred mid-month
A guard moves from a residential society to a corporate office on the 16th at a different post rate.
e.g. the transfer is recorded with effective date 16th; the society is billed 15 days, the office 15 days, and the guard's slip shows both site rates on the correct days.
New client mobilisation
A logistics park contract starting on the 1st with 30 posts across three shifts to be filled in ten days.
e.g. posts are created from the contract, guards are assigned as they clear police verification, posting orders go to the client, and unfilled posts stay red on the board until day one.
Frequently Asked Questions
Related Pages
Ready to Simplify Guard Deployment Attendance?
Book a free demo and see how Attend Mitra helps Indian businesses track attendance, manage shifts, and export payroll-ready reports.
