Onboarding a new site without the first month going wrong

Winning a new cleaning contract is, in some ways, the easier part. The first few weeks of actually running it tend to be where a client forms a lasting impression of the contractor — and most of the problems that surface in that window aren't about cleaning quality at all. They're logistics: access arrangements not properly set up, staff unfamiliar with the site layout, a specification that reads clearly on paper but is ambiguous once someone's actually standing in the building.

Why the first month is disproportionately risky

A new site is, by definition, the one place where staff have the least accumulated familiarity — with the layout, the client's specific preferences, where equipment and consumables are actually kept, and who to contact when something's unclear. Problems that would be quickly and quietly resolved on an established site, because everyone already knows the answer, become visible delays or errors on a new one.

What a solid onboarding checklist actually covers

Beyond the cleaning specification itself, a genuinely useful onboarding process covers access and security arrangements, key holder and out-of-hours contacts, where consumables and equipment are stored, and — critically — getting the site properly entered into the contract register with its specific requirements, so it's not relying on the memory of whoever won the contract.

• –Confirm access, security and out-of-hours arrangements before the first shift, not during it
• –Walk the site with the assigned team before day one, rather than sending staff in cold on the first shift
• –Set up the site's specific task checklist in advance, rather than relying on a generic template for the first few weeks
• –Enter the site fully into the contract register immediately, including any non-standard requirements the client specified
• –Schedule an early supervisor visit — inside the first two weeks — specifically to catch onboarding issues before they become a pattern

Getting the checklist right from day one

Rolling out with a generic checklist and refining it after a few weeks of feedback is a common shortcut, and it does mean the first weeks generate less accurate task records than they should. Where practical, building the site-specific checklist before the first shift, based on the actual walk-through rather than the paper specification alone, avoids that gap and gives the client a more consistent experience from the start.

Why an early supervisor visit matters more than usual

A supervisor site visit in the first fortnight of a new contract is worth more than the same visit later in the relationship — it's the best chance to catch a misunderstanding about the specification, a logistics gap, or a task that's being done differently than intended, before the client has formed a settled view of how the contract is going to run.

Why month one is where contracts are lost

A new site is the only point where the client has no baseline of trust to draw on. Every problem in the first month is evidence about the contractor; the same problem in month fourteen is an exception against a known record. That asymmetry is why the first four weeks deserve resourcing that looks disproportionate — the same incident simply costs more.

Practically, that tends to mean a supervisor on site far more often than the contract assumes, a checklist reviewed against reality after the first week rather than at the first quarterly review, and a deliberate check-in with the client before they have a reason to make one.

Common mistakes

• –Resourcing month one at the same level as month twelve
• –Building the checklist from the specification without walking the building
• –Waiting for the first scheduled review to ask the client how it is going
• –Starting with cover staff who have never seen the site
• –Not confirming access, alarms and key-holding before the first shift
• –Treating snags raised in week one as complaints rather than calibration