Transitioning Healthcare Security Vendors: A Risk-Managed Approach

The reason facilities tolerate a failing provider far too long is fear of the switch — the worry that changing hands means a gap in coverage, chaos on the floor, and blame if something goes wrong. It doesn’t have to. You can change your healthcare security vendor without a single unguarded shift if you treat the transition as a managed project rather than a light switch. This guide lays out a risk-managed approach: what to plan, what the law expects, and how to hand over so patients and staff never feel the seam. For the broader context, see our healthcare security services.

Start with your exit terms, not your new provider

Before you talk to anyone new, read your current contract. Your notice period, termination clause, and any transition-assistance obligations dictate your entire timeline. Facilities that skip this step either trigger penalties or box themselves into a rushed handover.

If your current service is failing, document why — dated records of the problems you’ve seen protect you if the exit is contested. Then confirm exactly what notice you owe and what the outgoing provider is contractually required to do on the way out. Some agreements oblige the outgoing provider to cooperate in the handover; if yours does, that cooperation is an asset you’ve already paid for, so use it.

Understand the building-services rule before you switch

Here’s a point many hospitals miss. In Ontario, security is classified as a “building service” under the Employment Standards Act, 2000. That matters because when a building services provider is replaced, specific rules apply: the new provider may choose not to hire the previous provider’s on-site employees, but if it doesn’t, it must in most cases meet the ESA’s termination and severance obligations toward them as if it had terminated them. If it does hire them, their length of service carries over.

This isn’t a reason to avoid switching — it’s a reason to plan it properly and get advice. It affects your timeline, your provider’s obligations, and sometimes which officers stay on site. Importantly, the rule doesn’t force the new provider to hire anyone, and it doesn’t trap you with your current one; it simply sets out what’s owed to the on-site employees who are left behind. This is general information, not legal advice, so confirm the specifics with an employment lawyer or advisor before you act.

The transition, phase by phase

A clean handover runs in overlapping stages, never a hard cutover.

• Plan. Agree a transition date, a communication plan for staff and clinical teams, and who owns each task on both sides. A named lead on each side prevents the “I thought you had that” gaps that derail handovers.
• Transfer knowledge. Post orders, site-specific risks, hospital codes, escalation contacts, and access details all move to the incoming provider before day one — not on it. Capture it in writing so it doesn’t live only in the heads of officers who are leaving.
• Confirm compliance. Verify licensing, insurance, and healthcare-specific training for every incoming officer, so nothing lapses at the seam. This is the check that protects you if an incident happens in week one.
• Overlap on site. Where possible, incoming and outgoing officers work together briefly, so the new team learns the building from the people leaving it. Even a few shared shifts transfer more site knowledge than any document.
• Cut over, then review. After go-live, review performance against your agreed standards in the first weeks, while the transition is still fresh enough to fix.

Knowledge transfer is where most of the risk lives. An officer who doesn’t know your codes or your patient-watch protocols on their first shift is a gap even if the post is technically staffed.

Planning a change and want it done without a coverage gap? Book a consultation and we’ll map the transition with you.

Communicate so no one is blindsided

A transition touches more people than the security team. Nurses, clinical leaders, reception, and facilities all interact with security daily, and a quiet switch breeds rumours and resistance. Tell them what’s changing, when, and who to contact — and reassure them that coverage continues throughout. The goal is that a nurse arriving for a night shift after go-live notices a new face and a smooth introduction, not a scramble to figure out who’s responding to the next Code White.

Bring the incoming provider into that conversation early. The best transitions feel collaborative, not disruptive, because the new team introduces itself before it takes over. When you choose that provider, a disciplined healthcare security RFP and a carefully read service agreement set the standard the transition then delivers on.

Frequently Asked Questions

1. Will changing security vendors leave a gap in coverage?
Not if it’s planned. A phased transition with knowledge transfer and on-site overlap keeps every post staffed, so patients and staff never experience a lapse.

2. What should I check before giving notice?
Your contract’s notice period, termination clause, and any transition-assistance obligations. These determine your timeline and whether early exit carries any penalty.

3. What is the building-services rule and why does it matter?
In Ontario, security is a “building service” under the ESA, so when providers change, specific successor obligations around termination and severance can apply. It affects your timeline and your provider’s duties.

4. Do we have to keep the outgoing provider’s officers?
No. The incoming provider isn’t required to hire them — but if it doesn’t, ESA obligations toward those employees may apply. Confirm the specifics with a legal advisor.

5. How long does a security vendor transition take?
It depends on your notice period and site complexity, but allow enough time for knowledge transfer, compliance checks, and overlap. Rushing the handover is where gaps appear.

6. What’s the most important part of the handover?
Knowledge transfer — post orders, codes, site risks, and escalation paths. A staffed post with an uninformed officer is still a gap.

7. Should we tell clinical staff about the change?
Yes. Communicate the change, timing, and contacts to everyone who works with security, so the switch feels managed rather than disruptive.

8. Can we run both providers at once during the switch?
A brief on-site overlap is often the safest approach, letting the incoming team learn the building from the outgoing one before taking full responsibility.

9. Is this legal information the same as legal advice?
No. This is general guidance; the building-services and employment rules have specifics that depend on your situation, so consult an employment lawyer or advisor before acting.

10. How do we make sure the new vendor is actually better?
Choose them through a rigorous RFP, hold them to written KPIs from day one, and review performance early and often so any slippage is caught while it’s still easy to fix. The transition is also the moment to reset expectations, so start the new relationship the way you intend it to continue.

Changing your healthcare security vendor is a project, not a leap. Read your exit terms, respect the building-services rules, transfer knowledge deliberately, and communicate widely — and the switch becomes a quiet upgrade rather than a risky disruption.

Ready to transition without the risk? Request a consultation with our healthcare team.