Onboarding a New Cleaning Contractor

A 90-day onboarding plan for a new cleaning contractor, built around gates, baselines and evidence, so the contract starts on a record instead of a promise.

Hands signing a cleaning services contract at a desk
Photo by Jakub Żerdzicki on Unsplash

Most contracts are lost in the first ninety days, long before anyone talks about renewal. Cleaning contractor onboarding is the short window where the standard, the evidence and the working relationship are either set properly or improvised — and an improvised start is very hard to correct later.

The failure pattern is predictable. The vendor starts, the building looks fine for three weeks, then the same washroom that was missed in the tender walk is missed on the schedule. Nobody has a baseline, so nobody can say whether the standard has slipped or was never met.

Key takeaways

  • Treat the first 90 days as a measured programme with three gates, not a handover.
  • Photograph and score the building before the first shift, not after.
  • Audit jointly at day 14, then independently from day 30.
  • The vendor's first monthly report is a deliverable, not a courtesy.
  • Hold a written day-90 review, and record the outcome even when everything is fine.

What does cleaning contractor onboarding have to produce in 90 days?

Three outputs: an agreed standard, a baseline condition record, and one complete scoring cycle you trust. If you have those by day 90, the rest of the contract runs on evidence. If you do not, you will spend the next year arguing about impressions. Onboarding is also the cheapest phase of cleaning contractor management to get right, because every correction made here lasts the whole term.

The standard is the area list, the target cleanliness level per area and the frequency — the content of the service level agreement you have already signed. Onboarding is where it gets translated into checklists a supervisor can actually score against.

Days −14 to 0: settle these before the first shift

The two weeks before mobilisation decide most of the outcome. Anything unresolved here becomes a dispute later.

  • Access. Keys, fobs, codes, alarm procedures, elevator bookings and after-hours contact for every area. Produce one list and make both parties sign it. Unresolved access is the most common quiet cause of missed areas.
  • Hours and shifts. Which hours are funded, when the building is occupied, and what happens on the night the loading dock is blocked.
  • Storage and services. Chemical store, equipment room, water and power points, waste route, and who supplies consumables.
  • Site rules and safety. Contractor orientation, sign-in, incident reporting, WHMIS requirements and any permit-to-work areas. The CCOHS contractor health and safety material sets out the owner's and contractor's responsibilities in language you can lift into a site pack.
  • Reporting obligations. What the vendor reports, in what format, by what date, and to whom.
  • Escalation contacts. Names, roles, phone numbers, and the response times attached to each level.

If the outgoing contractor is still in place, the overlap between the two is covered in cleaning transition and mobilisation. Do not let the incoming crew learn the building from the outgoing crew alone.

Week one: build the baseline, not the verdict

Walk the building with the new supervisor before the first shift and score what you find. That score is the baseline, and it does all the work for the rest of the contract.

Two reasons. First, it separates pre-existing condition from contractor performance: the scuffed corridor and the stained ceiling tile that predate the contract are documented on day one instead of blamed on the vendor in month three. Second, it gives both sides the same reference photographs.

Do this in daylight with the supervisor present, area by area, using the same checklist and the same five-point scale you will use all year. Photograph anything at Level 3 or worse. Mark genuine health and hygiene failures — blocked fire exits, unflushed toilets, mould in a washroom, standing water — critical so they cannot be averaged away later.

Store the baseline separately from routine inspections. It is a reference document, not a scorecard, and it should never be deleted.

Days 8 to 30: the joint walk and the first full audit

At about day 14, inspect together. You score, the supervisor scores, and you compare. The purpose is calibration, not catching anyone out.

  • Compare item by item, not area by area.
  • Where scores differ, revisit the area and agree what the target level looks like in that specific room.
  • Record the agreed interpretation in writing — a one-line note per disputed item is enough.
  • Confirm the area list is complete. Missing areas discovered now are cheap; discovered in month six they are a scope argument.

Then, between day 21 and day 30, run the first full audit alone. Unannounced or notified is a policy decision, but keep it consistent from the first cycle so the vendor is not learning a moving target. Publish the result with findings and closure dates, exactly as you will every month afterwards.

Days 31 to 60: the first scored cycle

By the second month the vendor should be producing their own inspection data, and you should be producing yours. Two streams, compared monthly, is the model that keeps a contract honest for years.

  • Send the first vendor scorecard at day 45, covering quality, reporting timeliness, responsiveness and compliance. Score it even though the sample is small — the point is that a scorecard exists from the start.
  • Require the first monthly report by the fifth working day. If it is late or thin, say so in writing now. Standards set in month two are still negotiable; standards set in month nine are a fight.
  • Check that deficiency closures are being recorded with dates and photographs, not just marked done.
  • Look for early patterns rather than early disasters. A single bad washroom is noise. Three bad washrooms with the same supervisor is a training issue. The same two items failing every week is a schedule or access issue.

Days 61 to 90: the gate review

The day-90 review is where onboarding ends and normal management begins. Hold it as a meeting with an agenda, and write a one-page record of it.

GateDateDecisionEvidence required
MobilisationDay 0Contract may startSigned access list, site induction complete, insurance and clearance on file
CalibrationDay 14–21Area list and targets confirmedJoint inspection sheet with agreed interpretations
Cycle oneDay 30Reporting format acceptedFirst full audit published with closures
Gate threeDay 90Continue, continue with conditions, or escalateTwo complete cycles, scorecard, closure times, open deficiencies

Outcomes at gate three are not binary. "Continue with conditions" is a legitimate result: name two or three specific fixes, attach dates and re-check them at day 120. What you should not do is record nothing because the building looks acceptable. Silence at day 90 becomes ambiguity at renewal.

What the manager has to fix on the manager's side

Half of a poor start is the client's fault, and it is worth saying so out loud in the review.

  • Access that actually works. Every area reachable on the shift it is scheduled for, with a named person to call when a lock fails.
  • A named contact. One person the vendor escalates to, with a deputy. Shared inboxes are where escalations go to die.
  • Consumables and equipment. If the building supplies paper, soap or liners, own that obligation properly. A crew that runs out of liners at 2am is a client failure, not a contractor one.
  • Decisions inside a week. Scope questions left open for a month become resentments and then become recurring findings.
  • Consistent inspection. Turning up twice in the first month and then not again until an owner complaint is the single most common onboarding failure on the client side.

When the first 90 days go badly

Escalate on evidence, not atmosphere.

  1. Name the finding, the area and the date. "Washroom 3, floors and partitions, below target on 4 of 6 inspections" is a position. "Quality is poor" is an opinion.
  2. Ask for a written response within five working days, including the cause and the fix.
  3. Check the cause yourself. Short-funded hours, broken equipment, blocked access and staff turnover are all things you can verify.
  4. Put a short improvement plan in place with dates and a re-inspection schedule if the response is weak or the cause is structural. The mechanics are set out in vendor improvement plans.
  5. Do not wait for renewal to act. A contract that starts badly and is never challenged is a contract that will end badly.

Frequently asked questions

How long should cleaning contractor onboarding take?

Plan for 90 days with three checkpoints: mobilisation at day 0, calibration around day 14, and the first independent audit by day 30. The formal review at day 90 closes onboarding. Smaller buildings can compress this to 60 days, but do not drop the baseline walk.

Should the contractor attend my inspections during onboarding?

Yes, for the first joint walk — it calibrates both sides. After that, run your own inspections independently so your data is not shaped by the vendor's presence, and compare results with theirs monthly.

What documents should be collected before the first shift?

At minimum: certificate of insurance naming the building or owner, workers' compensation clearance, WHMIS training records, site-specific orientation sign-off, a supervision contact list, and the vendor's own inspection and reporting procedure. Get expiry dates, and set a reminder 30 days before each one lapses.

What if the previous contractor left the building in poor condition?

Score it, photograph it and share the baseline with the new vendor in writing. Where the condition is beyond routine cleaning, agree in writing whether it is a one-time deep clean, a billable extra, or excluded. Do not let it sit inside the recurring price.

Can onboarding be shortened if the vendor already cleans another building in the portfolio?

Partly. Access, site rules and baseline still apply — buildings differ more than vendors expect. What you can skip is the general induction, and you can carry over the reporting format and scorecard cadence already in use elsewhere.

An onboarding you can audit later

The value of a 90-day programme is not the schedule. It is the file it leaves behind: a baseline, two cycles, a scorecard and a written review, all dated.

NeatScore lets you run the baseline walk and every later inspection on the same scored checklist, attach photos per item, track deficiencies to closure, and pull a branded report for each gate review. Try it free for 14 days, or see pricing.

Share: LinkedIn X Facebook Email