Worker Camp Management: The Daily Discipline

The hard part of worker housing is not securing the building. That is a project with a start, an end and a signature; procurement takes it and closes the file. Running the building is different. The obligation repeats every day, and it stays open for as long as anyone sleeps there.

Take two buildings on the same specification at the same price. A year later, one is clean and orderly, its faults are closed before they become complaints, and its records could go in front of a client's auditor on any given day. The other has accumulated small failures, its complaints now reach the project manager directly, and nobody can say precisely who occupies which room. The difference was never the building. It was operating discipline.

So the useful questions are what daily management actually contains, and who each function belongs to. The answer is the same whether you run the accommodation with your own staff or hand the operation to a specialist. Either way you need to know what has to exist before you can judge what does.

What daily operation has to cover

A contract line does not describe operation. Operation is a set of independent functions running in parallel, each with its own way of failing. They rarely collapse together. The normal case is one function quietly left unowned, and the damage shows up in the others.

• Site supervision: a responsible person actually present in the accommodation, not an inspection visit now and then.
• Maintenance: handling reported faults, and a preventive programme that reduces how many there are to report.
• Cleaning, waste and pest control: regular cycles covering shared areas, rooms and facilities.
• Security and access control: who enters, who leaves, and who is genuinely sleeping in the building.
• Allocation and handover: receiving a new arrival, assigning bed and bedding, and taking the room back on departure.
• Safety: firefighting equipment and its condition, evacuation routes, and briefing occupants on them in a language they understand.
• Complaints and records: a channel occupants know about, and documentation proving that everything above actually happened.

A recurring mistake is to contract the rent explicitly and then leave every other function without a named owner. An unowned function does not disappear; it lands on whoever is nearest and available. A driver, a guard, a site foreman already busy with production, none of them trained for it and none of them measured on it. Write into the scope who performs each function, who bears its cost and who documents it, even where the answer to all three is your own team.

Who should perform these functions: your team or a specialist operator?→

The resident supervisor: the biggest variable, the vaguest line

If one factor explains why one camp works and another on the same specification does not, it is the resident supervisor. Yet in an offer the item often passes as a single phrase: "supervision included". Nothing in that is measurable, and what sits behind it varies widely from one provider to the next.

The role is neither guarding nor reception. A resident supervisor runs the site: they see a fault before it is reported, know which room has a recurring problem, defuse a dispute between occupants before it becomes an incident, and escalate what exceeds their authority instead of concealing it. Their manner also decides whether an occupant judges a problem worth reporting at all, which is the difference between having data about your accommodation and having silence.

• Presence: the hours they are on site, who covers the hours they are not, and who answers a call in the middle of the night.
• Language: do they speak a language the occupants genuinely understand, or does every report pass through an intermediary?
• Spending authority: can they authorise a small immediate repair without approval? A repair deferred for a sign-off is how a small fault turns into a large one.
• Reporting line: who they report to, what they decide alone, and what must be escalated immediately.
• Cover: who stands in during leave and sickness, named before they are needed rather than after.

Good supervision is measured by what does not happen: reports that never became complaints, complaints that never reached the project manager, audit findings that were never written. That makes it nearly impossible to price from a proposal and obvious a short way into operation, by which point the commitment is signed.

How to build a complaints channel occupants will actually use→

Maintenance: from response to prevention

A great deal of accommodation runs reactively: wait for the report, then respond. It looks cheaper because it consumes nothing until something breaks. It usually costs more, for a simple reason: a failure you wait for arrives at the worst possible moment.

Cooling units rarely fail in winter. They fail at the peak of the heat, when they have been running near capacity, when every technician is already committed elsewhere, when the part is scarce and the emergency call-out is at its most expensive. Then come the costs that never reach a maintenance invoice: nights without sleep, lower output the next day, complaints stacking up, and a reputation among the workforce that outlives the repair by a long way.

1. Build an asset register first: cooling units, water heaters, pumps, tanks, distribution boards, firefighting equipment. You cannot schedule maintenance for something you do not know you have.
2. Base the preventive schedule on real conditions (heat, humidity, occupancy density) rather than on a manufacturer's booklet written for light domestic use.
3. Classify faults by impact: loss of cooling, loss of water or an electrical defect is not in the same class as a door that sticks, and must have a different response path.
4. Document every report from receipt to closure, with confirmation from the occupant that the problem is actually resolved. A fault closed without confirmation has a way of coming back.
5. Review recurring faults regularly. What keeps failing in the same place is rarely a one-off; it is more likely a defect in the asset or the installation, and fixing it once properly is cheaper than fixing it repeatedly.

One short question tests all of this. What is held in the store? An operation that keeps fast-moving spares (pumps, cooling components, valves) knows what fails in its own buildings. An operation that buys every part at the moment of failure is not running a maintenance programme; it is running a sequence of surprises.

Cleaning, waste and pest control

Cleaning looks like the cosmetic line on a scope of work. In practice it is often among the first things a competent authority inspection or a client audit looks at, and among the first to slip when supervision weakens. In heat, in humidity, or at high occupancy density, the consequences accelerate: food waste left in an enclosed space at the height of summer becomes a health problem far faster than it would anywhere cooler.

The right cycle is not a fixed figure copied from a previous contract; it is derived from density, climate and the type of space. Kitchens and shared washrooms run on a completely different rhythm from rooms, and rooms on a different rhythm from corridors and yards. Set the cycle per type of space, then document that it was performed.

• Shared areas: washrooms, kitchens, laundries. The highest frequency, and what the eye falls on first on any visit.
• Waste: defined collection points, closed containers, and an off-site removal schedule that anticipates capacity rather than trailing it.
• Pest control: a contracted preventive programme on a known cycle, not a call-out after an infestation appears. Treatment after spread is harder, slower and more expensive.
• Water tanks: cleaning on a documented cycle with certificates from whoever performed it, and a named responsibility in the contract.
• Bedding and laundry: who owns the replacement and washing cycle, and who bears the cost of replacements when items are damaged.

A common gap is the boundary of responsibility inside the room. Room cleanliness is left to the occupants in the contract, becomes nobody's responsibility in practice, and then appears in the audit report. As a working rule, what belongs to the occupant is explained in their own language at allocation and what belongs to the operator runs on a known cycle. What sits between them, periodic room inspection for instance, gets written down rather than assumed.

Security and access: who is actually sleeping here?

Security in worker accommodation answers two entirely different questions: who is permitted to enter, and who is actually sleeping in the building tonight. A guard at the gate settles the first. The second needs a live allocation record, updated on every arrival, departure and room transfer.

The distinction is not academic. When the allocation record is not accurate, occupancy you never recorded becomes possible: relatives, colleagues from another employer, beds informally re-let between the occupants themselves. Actual density can then exceed what the building was configured for and what the safety arrangements assume, and anyone who asks later, your main contractor or an inspecting body, will find your answer does not match the building. The operational cost is worse than the audit one. You cannot evacuate people you do not know are there.

Access control runs the other way round. It is not about tightening the screws on occupants or supervising their lives outside working hours. Accommodation is a place of residence, not an extension of the site, and restrictions that look like discipline on paper, hard curfews or blanket bans on visitors, produce resistance and workarounds that corrode the accuracy of the very record you were trying to protect. The practical balance is a written, published visitor policy, a disciplined entry log, and respect for privacy inside the living space. Anything touching worker entitlements, the holding of personal documents or freedom of movement is governed by regulation and the relevant labour bodies, and should be checked with them rather than with a service provider.

Records: the only evidence any of this happened

At audit there is no difference between work that was not done and work that was done and not recorded. An auditor cannot see the past months; they see what you put in front of them today. This is where disciplined operation separates from operation that merely looks disciplined: the first opens its files, the second starts assembling them.

• Allocation register: who occupies which bed in which room, updated at the moment of every arrival, departure or transfer.
• Maintenance log: the report and its time, the action, who performed it, the closure time, and the occupant's confirmation.
• Cleaning, pest control and tank cleaning records, with certificates from whoever carried out the work.
• Safety log: inspection and validity of firefighting equipment, condition of evacuation routes, and drills carried out.
• Complaints register: what was raised, when, what was done, and when it was closed, including what was declined and why.
• Entry and visitor log, plus a periodic report reaching the employer in a consistent format.

The decisive condition is that a record is created at the moment of the event, not on the eve of an audit. A record assembled afterwards often reads like one: a single handwriting, repeating patterns, dates too regular to be true. It does more damage than a missing record, because it turns an operational finding into a question of credibility. Ask for records routinely while nothing is wrong, rather than for the first time under pressure.

What an auditor is actually looking for in worker accommodation→