Running five washroom vendors across twenty buildings isn't procurement, it's hobby collecting. Consolidation is the obvious move. The leverage is in what you demand for it.
Key takeaways
- Consolidation changes four things: one standard, one data set, one escalation path, one invoice, price follows route density.
- Convert by the supplier's route geography, not your org chart; the long tail of small sites is where programs leak.
- A site is converted when its first visits are logged. Not when it is scheduled to convert.
- Key clauses: per-site frequency, schedule-amendment additions at standing rates, bilingual documentation.
What consolidation buys you: one agreement, one invoice, one standard across buildings, and per-site records that reconcile centrally. It also buys route density on the supplier's side. Which is your negotiating room on rate.
Demand per-site granularity. A consolidated contract with blended reporting is worse than five contracts. You lose the per-building signal. Records must break out by site, washroom and (where relevant) tenant, or the chargeback machinery seizes.
Demand mid-term elasticity. Portfolios change: acquisitions, dispositions, fit-outs. The agreement should add and remove sites at the standing rate without renegotiation, growth shouldn't reopen the contract.
Demand bilingual as standard if any site touches Quebec, New Brunswick or federal tenancy. Retrofitting French documentation later costs more than specifying it on day one.
What consolidation actually changes
Moving five or fifty sites onto one washroom-services contract changes four things structurally, and only one of them is the price:
- One standard — every site gets the same unit spec, product mix and service definition; the quality of your worst washroom rises to the contract's floor.
- One data set — per-site service logs in one format make sites comparable for the first time; the outlier site becomes visible in a way fifty local arrangements never show.
- One escalation path — a missed visit anywhere goes to the same account contact with the same response commitment, instead of whichever local number still answers.
- One invoice — the administrative saving that facilities teams cite most: one reconciliation instead of a monthly folder of local bills at inconsistent rates.
Route pricing is the economic engine underneath: a supplier serving all your sites builds them into route density, and density is what moves rates. The saving is real but it arrives as structure, not as a discount line.
Getting the rollout sequence right
National and regional rollouts fail at the middle, not the ends, headquarters and the flagship sites convert cleanly, and the long tail of small sites drifts. The sequence that holds: convert by region along the supplier's route geography (not by your org chart), give every site a named cutover date with the old arrangement's end tied to the new service's first logged visit, and run the whole program from the per-site logs from week one. A site whose first three visits are logged is converted; a site \"scheduled to convert eventually\" is where the program leaks.
Convert along route geography, not the org chart. The supplier's density is your price, and their route map is the real rollout plan.
The contract terms that matter at scale
Three clauses earn attention in multi-site agreements: per-site frequency flexibility (a national rate card with per-site cadence set from each site's traffic, never one frequency portfolio-wide), additions and disposals handled by schedule amendment at the standing rate (portfolios change; re-quoting every acquisition burns the consolidation gains), and bilingual documentation as standard for any portfolio touching Québec or federal jurisdiction. None of these are exotic; all of them separate suppliers who run true multi-site operations from suppliers who run one big route with extra invoices.
When consolidation is the wrong answer
Honesty about the edges makes the case for the middle. Consolidation underperforms in three situations: portfolios whose sites sit far off any shared route geography (the density discount cannot form, and a strong local arrangement at an isolated site may beat the national rate); organisations mid-acquisition whose site list will change materially within the term (consolidate after the dust settles, or negotiate unusually flexible amendment terms); and portfolios where one site has genuinely specialised requirements. A hospital in an office portfolio. That a generalist national supplier would serve as an afterthought. The hybrid answer is normal and unembarrassing: consolidate the eighty per cent that fits, keep the specialist arrangements that earn their exception, and revisit the split at renewal.
The test for any exception is the same one that runs through this whole series: can it produce a service log? A local arrangement that documents its visits is an exception with a case; one that cannot is just an unmanaged corner of the portfolio wearing a loyalty story.
Frequently asked
The visible saving is route pricing, sites folded into density price better than isolated stops. The larger saving is usually administrative: one reconciliation replacing dozens of local invoices, plus the first real per-site comparability, which surfaces over-visited sites no one had itemised. Portfolios commonly find structural savings in the five-to-fifteen per cent range in the first annual review.
Yes, with bilingual documentation as a standard term, service records, invoices and site communications in both languages. For portfolios with federal-jurisdiction sites the same clause covers the Labour Code's documentation expectations. Ask for it at signature; retrofitting bilingual records later is the expensive version.