The post that was left empty while paperwork happened: HR for security services

A security guard resigned from a services firm with the notice his contract required. HR processed the exit correctly: uniform returned, badge recovered, settlement scheduled. The operations team was informed on his last day. On Monday morning the client's gate was unmanned for four hours, because the exit process had been written around the leaver and nobody's task had been to have a replacement briefed and at the post before his last shift. The client's facilities manager, who had not been told, found out at the gate.

In security services the post is the unit of everything — the exit, the roster, the billing, the client relationship — and an HR process organised around the employee rather than the post will leave a gate empty while the paperwork is completed correctly. The design has to start from coverage.

NOTICE RECEIVED   the post is flagged; a replacement is identified
                  and their verification and site briefing
                  scheduled to complete before the leaver's
                  last shift
CLIENT INFORMED   through the contracted route, by the firm,
                  before the change - not at the gate
HANDOVER AT POST  post orders, incident history, site-specific
                  instructions passed to the replacement, at the
                  post, on an overlapping shift
LAST SHIFT        client-issued cards and keys returned to the
                  client; uniform, badge, equipment recovered;
                  attendance reconciled for billing
RETAINED          verification and deployment record kept per
                  client requirement, retrievable by date

Coverage is continuous, or the exit failed
whatever the checklist says.

The reordering is the whole fix: the first task on a security exit is the replacement, and the leaver's checklist is completed only once coverage is confirmed. That requires the exit to be visible to operations the day the notice arrives, not on the last day, and a relief and replacement process that HR either owns or sits inside. The exit and offboarding process in this sector is an operations process with an HR record attached, and treating it the other way round is how the gate ends up unmanned.

Security onboarding is gated by verification — identity, address, background as the role and the client contract require — and a guard deployed before checks are complete is a contractual and reputational exposure at a client's premises. The process has to be a sequence: application, verification completed and recorded, training and certification per role and client requirement, client-specific site briefing, deployment. Under contract pressure the temptation is to deploy on the assumption the checks will clear; the rule has to prevent it. The second half is the record: clients ask who was deployed on their premises on a given date, whether they were verified and to what, sometimes years after the deployment ended. The verification record is held per person, retained after exit, retrievable by client and date — and a firm that can answer in minutes keeps clients that a firm reconstructing from old rosters loses.

A guard who cannot take agreed leave because relief does not arrive will, sooner or later, leave permanently rather than argue — and relief failure is the most common avoidable cause of exits in the sector. Relief planning against deployment, with a buffer pool for absence and sudden vacancy, is an operational process that decides retention, and it has to be sized honestly: a post requiring round-the-clock coverage needs materially more than three people, and plans built on three run permanently short and burn out the three. The HR strategy and workforce planning question in security services is mostly this arithmetic — post and shift requirements per contract, a realistic relief factor, verification lead times, and an attrition assumption that reflects the sector rather than the hope.

1. 1

   Size the relief factor honestly

   Per post, per coverage pattern. The number is higher than the contract's headcount and it is the real cost.

2. 2

   Plan relief against deployment

   Who covers whom, per site, with a buffer pool. Relief that depends on finding someone on the day is relief that fails.

3. 3

   Track leave requests that were refused for want of relief

   It is the earliest warning of the exits that follow.

4. 4

   Pay on the same date, every month, regardless of client payment

   A slipping salary date teaches deployed staff who the real employer is, and it is the second most common cause of exits.

A guard works alone at somebody else's premises, often at night, and the employer is experienced as a supervisor who visits and a salary that arrives. Supervisor visit frequency — measured, including night posts — is the engagement variable in the sector, and unmeasured visits become monthly and then quarterly. Basic facilities at post (shelter, water, washroom access), uniform and equipment issued and replaced properly, a grievance route independent of the client, and recognition for incidents handled well, communicated to the client, are the rest of the list. None is expensive. All of them are visible only by site, which is why attrition, supervisor visits and post conditions have to be tracked by site and client rather than for the firm as a whole.

• Visit frequency per post, including nights, measured and reviewed.
• Attrition by site, supervisor and client. Sites with persistently poor retention trace to relief, visits or conditions.
• Post conditions checked on the visit, not assumed from the contract.
• A second door for grievances, independent of the client and the site supervisor — deployment changes must never be an informal response to a complaint.

Security staff are frequently managed as deployable units rather than as individuals with futures, and that is a substantial part of the sector's attrition. The ladder — guard to senior guard to supervisor to site in-charge to operations manager — exists and is rarely stated, and the most effective retention routes are the specialist ones: control room and electronic surveillance roles offer a materially different working life to guards who have served well at post, and they retain experience that would otherwise leave. Supervisor capability built before deployment to the role, criteria stated and applied consistently, and long service recognised as a route rather than a badge are what make the ladder real.

Rewrite the exit so its first line is the replacement, and make notice visible to operations on the day it is received. Then measure supervisor visits per post, including nights. Then size the relief factor honestly and track refused leave. That sequence is where HR for security services work begins, because it addresses the two things — coverage and relief — that the sector's exits and its client losses both come from. The gate in the opening was unmanned by a process that was correct about the leaver and silent about the post; security services HR work exists to make the post the first thing the process thinks about.