PSARA License for Society Security Guards: What RWA Committees Should Verify

Why a security agency's license is a committee's problem too

Most societies outsource gate security to a third-party agency rather than hiring guards directly, and the working assumption is usually that whatever paperwork the agency needs is the agency's own concern. It isn't, entirely. Under the Private Security Agencies (Regulation) Act, 2005 (PSARA), any business that supplies security guards for payment is required to hold a license issued by the Controlling Authority of the state it operates in. A society that contracts an unlicensed agency isn't just exposed to poor service — it has effectively brought unregulated, unverified personnel onto its own premises, with no statutory oversight standing behind them.

Committees rarely check this at the time of hiring. A quote looks competitive, the agency sends a few guards for a trial, and the contract gets signed. The license question only tends to come up after something has already gone wrong — a theft, an assault, or a dispute over a guard's conduct — when the committee discovers there is no license on file and no real paper trail behind the people who were staffing its gate.

What PSARA actually requires

• Any agency supplying security guards, supervisors, or providing security guard training must hold a PSARA license from the Controlling Authority of the state where it operates
• Licenses are typically valid for a fixed multi-year term and must be renewed before expiry — an agency operating on an expired license is functionally unlicensed again
• The Act also expects guards to be verified and, in most states, trained under recognized guidelines before deployment, not simply hired and sent out the same week
• Requirements, exact renewal timelines, and enforcement vary by state, since PSARA is implemented through each state's own Controlling Authority rather than a single central office — a committee should always confirm current requirements with its state authority rather than assume a process used elsewhere applies as-is

Where societies get exposed

• Contracts are signed based on price and guard headcount, with no one on the committee asking to actually see the agency's PSARA license
• A license copy is collected once at onboarding and never checked again, even years after it may have lapsed
• The agency handles its own guard verification and training internally, and the society has no visibility into whether it was actually done
• Guard turnover at the agency is high, but the society has no record of which specific individuals were deployed on which dates
• If an incident occurs, the committee has no documentation to show what due diligence was done before the agency was engaged

What a committee should verify before signing

• A current, unexpired copy of the agency's PSARA license, checked against the name on the contract itself — not a group entity or a differently named affiliate
• The renewal date, tracked somewhere the committee will actually see it again before it lapses, not filed away and forgotten
• Confirmation that guards deployed to the society have completed police verification, in addition to whatever verification the agency itself performs
• A named point of contact at the agency for compliance questions, separate from the day-to-day site supervisor
• Basic training or certification records for guards being deployed, if the agency is willing to share them

What a defensible record looks like

• A copy of the license itself, tied to the vendor contract, with the renewal date visible to the committee rather than buried in an email from years ago
• A reminder before the license is due to expire, so a lapse gets caught before it becomes the society's problem
• Individual verification documents for the guards actually posted at the gate, not just a blanket assurance from the agency that "all guards are verified"
• A record of which guard was on duty at which gate and when, so an incident can be traced back to a specific, verifiable individual rather than "someone from the agency"

How MySocietyEntry helps

MySocietyEntry doesn't issue or verify PSARA licenses — that due diligence sits with the committee and the state Controlling Authority, and a society should always confirm an agency's license status directly with them rather than rely on the agency's word alone. Where the platform helps is in keeping the surrounding record straight: a security agency's vendor profile can hold the license copy and other compliance documents in one place instead of an inbox, and individual guards can carry their own verification documents on their staff profile, the same way domestic staff and tenant verification records are tracked. Because guard duty schedules and gate activity logs sit in the same system, a committee reviewing an incident can see exactly which guard was on duty at the time, rather than relying on the agency to confirm it after the fact.

Final takeaway

A security agency's PSARA license is not paperwork the committee can leave entirely to the vendor. It is the baseline check that confirms the people guarding a society's gate are operating under actual regulatory oversight, not just a uniform and a contract. Checking it once at signing isn't enough — a committee that tracks the license, its renewal date, and the verification status of the individual guards deployed is in a far stronger position if it ever needs to answer for who was watching the gate on a given day.