Your people, their building: HR for a facility management workforce

A facility management business lost a large contract to a competitor. The competitor took over the site on a Monday, and by Wednesday most of the incumbent's staff on that site were working for the competitor, in the same uniforms with a different badge. The business was surprised and should not have been: its supervisor had visited the site once a quarter, its staff had been managed day to day by the client's facilities manager for three years, and when asked who they worked for, most of them had named the client. The employer had been absent so long that the contract, not the company, was what they belonged to.

Facility management HR has a defining problem that most sectors do not: the employee works at somebody else's premises, is managed in practice by somebody else's people, and may go weeks without contact from the organisation that pays them. Everything worth doing is about being present in that arrangement, deliberately, because the default is absence.

PERSON    -> SITE -> POST -> SHIFT

  the deployment, not the department, answers every
  question the business is actually asked:
  - who is on which site today, and is any post vacant
  - what was issued to whom by which client
  - what does this contract cost in people
  - who has this site's induction, and when does it lapse

A system that knows departments and not sites
cannot run this business.

The record design follows the work. Attendance is captured at site, offline-capable, because the site is where the person is. Client-issued credentials, keys and access cards are recorded against the person and the client, because they must be returned to the client at exit. Site-specific inductions are held per person with expiry, because the client's rules are the site's rules. And billing is reconciled from the same deployment record that runs payroll, because when the two come from one source the monthly dispute with the client largely disappears. That last point is where HR process automation in this sector earns its keep: the deployment record is simultaneously the HR system and the invoice.

The business in the opening was not absent by policy; it was absent by default, because nothing required a supervisor to be at the site more than quarterly. Presence has to be designed: a named supervisor who visits at a stated frequency, including night posts; employer identity reinforced through uniform, ID, briefings and recognition delivered by the company rather than the client; a grievance route that does not depend on the client's goodwill; and protection from client demands outside the contracted scope, which is where deployed staff most often feel abandoned. None of this is expensive. All of it is the difference between a workforce that follows the contract and one that stays with the company.

1. 1

   Supervisor visits at a stated frequency

   Weekly for large sites, fortnightly for small, and night posts included. Measured, because unmeasured visits become quarterly.

2. 2

   Employer identity, delivered by you

   Briefings, recognition, the annual event, the new uniform — from the company, at the site, so the staff know who they work for because that company keeps showing up.

3. 3

   A second door for grievances

   Independent of the client and of the site supervisor. Deployment changes must never be used as an informal response to a complaint; that leaves no record and is not a fair process.

4. 4

   Scope protection

   Staff need to know the business will back them when a client asks for something outside the contract. Where they believe it will not, they either comply and resent it or leave.

Two things decide retention in deployed workforces more than anything else, and both are entirely within the employer's control. The first is relief: a person at post who cannot take agreed leave because relief does not arrive will, sooner or later, leave permanently rather than argue. Relief planning against deployment — knowing, per site, who covers whom — is an operational process that HR has to own or be very close to. The second is payment on a fixed date regardless of when the client pays, which is a working-capital decision the business has to make deliberately, because a payroll that slips when a client is late teaches the workforce that the client is the real employer.

• Relief planned against deployment, per site, with a buffer pool for absence and sudden vacancy.
• Payment date fixed and honoured, decoupled from client receipts.
• Attrition tracked by site, contract and supervisor. Sites with persistently poor retention have a relief, visit or conditions problem, and it is visible only by site.
• Redeployment handled as career movement, with the person told why and what it means, not as reassignment by message.

The hazards belong to the client's building and the duty toward the employee remains yours — which means a site-specific risk assessment before deployment, client hazard information obtained and passed to staff, PPE appropriate to the actual site rather than a generic issue, working-at-height and electrical authorisations held per person, and an incident route that works from the site. The position that matters most, and is hardest to hold commercially, is that staff may stop unsafe work at a client site and will be supported when they do. Where staff do not believe that, they take the risk, and it becomes the company's incident at the client's premises.

Deployed staff often see the client site as the limit of their world, and a career route that crosses sites and contracts — site staff to supervisor to site in-charge to contract manager, with technical specialisms as parallel routes — is what converts a job into a reason to stay with the company rather than the site. Contract manager succession is the commercial version of this: those individuals hold the client relationship, and an unplanned exit is a contract retention issue before it is a staffing one. The succession and leadership development plan in facility management should name a successor for every contract manager, and build them before the vacancy.

Clients ask about the people on their premises, sometimes long after the deployment ended: who was there on a given date, were they verified, were they inducted to the site. The verification record — identity, address, background as the contract requires — is held per person, retained after exit, and retrievable by client and date. A business that can answer in minutes keeps clients; one that reconstructs the answer from old rosters and mailboxes is, in the client's eyes, unsure who it sent.

Start with the site whose staff would follow the contract tomorrow — every facility management business has one — and ask why. The answer will be some combination of visit frequency, relief failures, payment slips and an employer that has not been there. Fix those at that site, measure retention by site, and roll the design out. That work, and the deployment-centred record underneath it, is what HR for facility management involves. The business in the opening lost a workforce with a contract because it had never asked its people who they worked for; facility management HR work begins with that question, site by site, before a competitor answers it.