When an on-site workforce goes wrong, the failure is rarely the individual. It is almost always something decided earlier: the team was sized for an empty building, nobody defined who the staff report to, or the shift pattern assumed perfect attendance.
1. Start with the site, not the headcount
Before deciding how many people you need, map what the site actually is: total area and how much of it is cleaned daily versus weekly, number of entry points, occupancy at peak, visitor volume, pantry and cafeteria load, and operating hours including weekends.
A floor with heavy client traffic needs a different housekeeping rhythm than a back-office floor of the same size. Headcount derived from square footage alone is a guess.
2. Define the roles separately
- Housekeeping and facility staff — daily cleaning, restrooms, common areas, waste handling
- Security and surveillance — entry control, patrolling, visitor management, night cover
- Pantry and support staff — beverages, cafeteria assistance, stock handling
- Front office — reception, visitor handling, call and courier management
- Drivers — management movement, client pickups, shift transport
- On-site supervisor — rosters, escalation, quality checks, coordination with your admin team
3. Design the shift pattern deliberately
Decide whether the site is single-shift, double-shift, or 24x7, then work out the handover points. The weak spot in most rosters is not the middle of a shift but the transition between two — the fifteen minutes where nobody is clearly accountable.
For rotational patterns, also decide how rotation happens: weekly, fortnightly, or fixed teams per shift. Fixed teams are simpler to supervise; rotation is fairer to staff. Both work, but the decision should be explicit rather than accidental.
4. Set up supervision before staff arrive
Every deployment needs one named person on your side and one on the partner's side. Without that, small issues — a missing consumable, a late arrival — travel through informal channels and become complaints instead of corrections.
5. Plan for absence, not around it
People fall ill and take leave. A plan that only works at full attendance is not a plan. Agree upfront on how replacement cover is arranged, how quickly, and who authorises it. This is one of the main reasons companies use a manpower partner rather than hiring support staff directly.
6. Choose the deployment model that matches the timeline
- Short-term deployment — peak periods, events, seasonal load
- Long-term deployment — a fixed on-site team as standing capacity
- Project-based manpower — a defined scope with a start and end
- Bulk manpower supply — large sites needing scale at once
- On-demand workforce — fluctuating, hard-to-forecast volume
- Shift-based staffing — day, night and rotational cover
- Outsourced manpower management — the partner runs the whole function
7. Review after the first month
The first month always reveals something the plan missed: a floor that needs a second cleaning round, a gate that needs cover an hour earlier, a pantry that peaks at a different time. Build a review point into the engagement so those adjustments happen once, deliberately, rather than as a running argument.
Sizing the team without guessing
There is no universal ratio that converts square feet into housekeeping staff, and any provider who quotes one without seeing your site is describing an average rather than your building. What does work is breaking the site into tasks with a realistic time attached, then adding them up. Restrooms are the clearest example: servicing frequency, not floor area, decides the workload, and a floor with two restrooms serviced hourly is a different job from one with six serviced twice a day.
- List every task, its frequency and the area it covers — daily, alternate-day, weekly, monthly
- Attach a realistic time to each, measured on your site rather than assumed
- Add the fixed-position roles that are not task-based: reception, gate security, pantry service during peak hours
- Add transition and preparation time, which is real and routinely omitted
- Add cover for weekly offs and predictable leave — a team sized only for full attendance is understaffed by design
- Only then convert the total into people per shift
Occupancy is the number that changes everything
Hybrid working has made this harder and more important. A floor built for three hundred people that holds ninety on Monday and two hundred and forty on Wednesday does not need a flat daily team; it needs a base team plus a planned peak. If your access-control system can tell you daily occupancy by floor, that data is the single most useful input into a manpower plan. If it cannot, a two-week manual count is worth the effort before you commit to a headcount for a year.
Materials, equipment and storage
Plans usually specify people and forget everything the people need. Decide who supplies cleaning chemicals and consumables, who owns and maintains equipment such as vacuum cleaners, scrubbers and trolleys, where materials are stored, who tracks stock, and how reordering is triggered. A site that runs out of hand wash on a Friday evening has a planning failure, not a staffing failure — and it is the kind that visitors notice immediately.
Safety, access and induction
- Site induction covering emergency exits, assembly points and incident reporting, before the first shift rather than during it
- Access cards, biometric enrolment and any building or client ID formalities, with the lead time they realistically take
- Personal protective equipment appropriate to the task, including for wet work and waste handling
- Clear rules for working at height, electrical areas, server rooms and other restricted zones
- A named first-aid point and an escalation number that is answered outside office hours
What to measure once the team is running
Keep the measurement light or nobody will maintain it. Three or four indicators are enough: attendance against roster, complaints or escalations by category, consumable consumption against expectation, and completion of the periodic tasks that are easy to quietly skip — deep cleaning cycles, glass, terrace and parking areas. Reviewed monthly, those four will tell you whether the plan is holding long before anyone complains formally.
Frequently asked questions
How long does a plan take to stabilise? Usually a month or two, because the first weeks reveal the peaks and gaps no walkthrough shows. Should the supervisor be counted in the headcount? Yes — supervision is a role, not an overhead to be absorbed by someone already cleaning a floor. Can the team be reduced later? Yes, provided the engagement was written with a review point; retro-fitting flexibility into a fixed annual contract is much harder. Is it cheaper to hire support staff directly? Sometimes on paper, rarely once absence cover, statutory compliance, supervision and replacement are priced honestly.