Passing a Client Audit of Worker Housing

When a client or main contractor gives notice they are coming to look at the accommodation, the reaction is nearly always the same: a deep clean, a fast repaint, new bedding where it has worn out, a tidied yard. Then the auditor arrives, sits in the supervisor's office and asks for the maintenance records for the preceding months.

The problem starts here. You prepared for one thing and the auditor came to ask about another. A client audit measures documentation discipline across the preceding months, and that is precisely what the last week cannot arrange.

The document your housing is measured against

A regulatory inspection measures your building against published requirements issued by the competent authorities, which apply to everyone. A client audit measures it against something private: your contract, the scope of work attached to it, and whatever housing standard the client annexed. The same building can pass for one client and be written up by another without anything about it changing.

The consequence is commercial. There is no fine, but your position moves: a score in a supplier evaluation, a status in prequalification, a remediation notice with a date on it, payment withheld until findings close, and at worst scope removed or a contract not renewed. Those decisions get made in a meeting you do not attend, on the strength of a report by someone who spent a few hours on your site.

Many of these visits come at short notice or none, and they arrive because something happened: a complaint that reached the client, an incident, a video circulating, a question the client's own client put to the supply chain. The auditor may not be a safety specialist either. Procurement, sustainability and third parties acting for the client each read the same building from a different angle.

The regulatory baseline the contract builds on: worker housing requirements in Saudi Arabia→

The auditor writes the report out of your records

An auditor can only assess what you are able to evidence. That is the limit of the job. They were not here across the preceding months, and have no way to vouch for cleaning regularity, maintenance response or water safety except through what is written, dated and signed.

Hence a scene that repeats: a well-run site, a supervisor who knows every room and every open fault, and a report that comes back full of findings. The operation held up; the proof of it did not. A weaker site with tidier files scores better. Unfair by the measure of effort, and exactly fair by the measure of what an outsider can verify.

The worse mistake is trying to make that up once the notice arrives. Retrospectively completed records carry signs any auditor knows: one hand, one pen, an unbroken run of dates, signatures from people who were not on shift, a complaints log where everything is closed and nothing is open. Once the auditor sees it, the finding stops being a documentation gap and becomes an integrity question, which is the category that travels above the project manager.

The records that have to exist continuously

There is no single folder called the audit file. There are records that run daily, and you pull out of them whatever gets asked for. This is the minimum that comes up in nearly every audit:

• Maintenance requests logged with when the fault was reported, when it closed, what was done and by whom, rather than a list of visits.
• Cleaning schedules signed off at the frequency you claim to run, naming who did the work and who checked it.
• Tank cleaning and disinfection records, and water quality test reports from an accredited laboratory, kept with their certificates.
• Where there is a kitchen or catering on site: temperature logs, health certificates for food handlers, pest control reports and treatments.
• A current occupancy record showing who sleeps in which room. It is what ties the others together, and in practice the one most often stale.
• A complaints log: what was raised, when the resident was told, what was done, when it closed. Including the entries you would rather not show.
• Incident and near-miss reports, with the investigation and the action taken.
• Current permits and certificates for the premises, inspection certificates for systems subject to periodic checks, and renewals tracked before they lapse.

All of this is daily operating routine. It gets written as things happen, reviewed by the supervisor each week, and summarised upward to whoever owns the contract. A log nobody inside the company reads will not convince anybody outside it, and it is usually incomplete as well.

What daily camp management actually has to cover→

Assess yourself before anyone else does

A self-assessment is the only way to find the gap while you still own both the time and the decision. What makes it work is that it reads against the contract wording rather than against your impression of the accommodation.

1. Actually assemble the reference documents: the contract, the scope of work, any annexed housing standard, and later variations. It is common for the site team never to have read the housing clauses, because a commercial team negotiated them and then filed them.
2. Turn each clause into an evidence question: what proves we comply, where does that proof live, who owns it, how often is it produced. A clause with no answer is a finding waiting to be written.
3. Walk the site with an outsider's eye. Give the job to someone who does not run it, from another project or from a quality function, because anyone who passes a defect daily stops seeing it.
4. Write your own findings in the form the auditor will use: description, evidence, owner, closure date. Do not soften the wording, because softening it defeats the exercise.
5. Start remediating immediately. The gap between "you missed this" and "we know, here is the plan already running and here is what it has done so far" is the gap between a finding written against you and a position that earns you credit.

On the day: how to conduct yourself

Open with a short meeting that settles scope, sample and timing, and put one person in charge of producing documents. A frantic search for a file in front of the auditor leaves a worse impression than the file itself would, because it says the record is not in use.

Escort the auditor without crowding them. They will speak to residents, which is a legitimate part of the job. Do not coach anybody. Coached answers tend to be obvious, and they cost more than the defect they were meant to cover. What helps is residents already knowing how a complaint is raised and to whom, because that question always gets asked, and the answer shows whether the process is real.

If a record is asked for and does not exist, say so. Do not promise to send it later in the hope the finding evaporates; it gets written either way, with a second one about the reliability of your answers. At the closing meeting, read every finding back and correct factual errors, the wrong building or the wrong date, but leave the judgement alone. Ask instead what evidence would close each finding. That answer saves weeks of work in the wrong direction.

The complaints system, in detail: handling worker housing complaints→

Closing findings at the cause

Most of the effort wasted after an audit goes into shallow closures. An air-conditioning unit left broken past the agreed response window is not closed by fixing the unit. The repair deals with the instance. The finding was written about the process behind it. Why was the fault not tracked, who should have reviewed the log, why did the delay not escalate on its own?

An acceptable closure needs evidence that the cause was treated: the procedure as amended, the person now accountable by name, the review frequency that was set, the first cycles of the new record, and a later check showing it held once attention moved elsewhere. A before-and-after photograph will not carry that. It closes the instance and stops there.

And meet the remediation dates. Missing a closure date weighs more than the original finding, because it moves the conversation from a defect in the accommodation to a doubt about reliability, and reliability is what gets read at prequalification. The next audit starts there as well: the first thing pulled into the sample is last time's findings and the evidence that closed them.

What you build for the audit alone falls apart within weeks of it. What you build because it is how the accommodation is run turns the audit into an administrative event: the auditor asks, and the supervisor hands over what was asked for. No week of preparation comes before it, because there is nothing left to prepare.