The short answer
Switching security guard companies goes wrong in one of two ways: you give notice before you have a replacement and end up with an uncovered post, or you wait too long to read the contract and get auto-renewed into another twelve months.
The sequence that avoids both is boring and it works. Read the contract first and find your notice window. Source and vet the replacement while you are still under contract and still covered. Sign the incoming agency for a start date, then give written notice to the outgoing one. Overlap the two for a few shifts so the handover happens on-site rather than over email. Only then let the old vendor off the property.
Nothing here is legal advice. Contract terms vary enormously between vendors and states, so treat this as a list of things to check in your actual agreement, and have counsel look at anything you cannot read cleanly.
Benchmark what you should be paying first →
Why coverage gaps happen
Almost every gap traces back to doing the steps in the wrong order.
The most common version: a site manager gets fed up after a third no-show, sends a termination email that afternoon, and only then starts calling agencies. The outgoing vendor is now a lame duck with thirty days left, no incentive to fill callouts, and every reason to move its best officers to accounts it is keeping. Service quality on a terminated contract almost always drops, and it drops fastest on overnight and weekend posts.
The second version is quieter. The buyer decides in March to switch when the term ends in June, forgets that cancellation notice is due between 45 and 60 days before expiration, sends notice on May 1, and discovers the contract renewed on April 12. Now they are paying for a vendor they already decided to leave.
The third is a handover failure rather than a scheduling one. Coverage technically never lapsed, but the incoming guards arrive with no post orders, no alarm codes, no escalation contacts, and no idea which door the delivery drivers use. The post is staffed and functionally uncovered at the same time, which is arguably worse because it looks fine on the invoice.
What to check in your current contract
Pull the signed agreement, not the proposal. Work through these in order and write the dates down.
The term and the expiration date
Find the effective date, the initial term length, and whether you are in the initial term or a renewal term. Contract security commonly runs on annual terms, though month-to-month and multi-year agreements both exist. If you are already in a renewal term, check whether the renewal period matches the original term. Some agreements renew in twelve-month blocks; others roll month to month after the first year, which is a much easier exit.
The auto-renewal clause and its notice window
This is the clause that causes the most damage. Auto-renewal is standard in the industry. What varies is how narrow and how early the cancellation window is. A clause requiring written non-renewal notice "not less than sixty days nor more than ninety days prior to the expiration of the then-current term" gives you a thirty-day window that opens and closes months before you would naturally think about it.
Three things to extract: the number of days of notice required, whether the window has an outer bound as well as an inner one, and the exact calendar date by which notice must be received. Then put that date in a calendar with a reminder two weeks earlier.
Termination for convenience
This is your right to end the agreement without alleging any wrongdoing, usually on a stated number of days of written notice. Thirty days is common and reasonable. Sixty to ninety days is heavy. Check whether the notice periods are symmetric: some agreements require ninety days from you and permit thirty from the vendor, which tells you something about how the document was drafted.
Also check whether termination for convenience is available during the initial term at all. Some agreements only permit non-renewal, meaning you cannot exit mid-term for convenience at any price.
Termination for cause
Termination for cause typically permits a faster exit, sometimes immediate, when the vendor breaches material terms. Read what actually counts as cause in your document. Deploying an unlicensed guard, letting insurance lapse, failing to provide required incident reports, and repeated failure to staff a post are the usual candidates. Many agreements also require you to give written notice of the breach and a cure period, often ten to thirty days, before you can terminate on that basis.
If you intend to terminate for cause, the documentation matters more than the frustration does. Dated no-show records, unanswered escalation emails, missing incident reports, and any licensing or COI lapse you can evidence are what turn a dispute into a clean exit. Start keeping that file before you send anything.
Early termination fees and minimums
Look for liquidated damages, remaining-term buyouts, unamortized equipment or uniform costs, and any minimum hour or minimum revenue commitment you have not yet met. A fee capped at actual documented damages is defensible; a clause demanding the full remaining contract value is aggressive and worth having counsel look at before you accept it as final.
Property, credentials, and records
Decide in advance what has to come back and what has to be produced. Site keys, access badges, fobs, alarm codes, radios, gate remotes, patrol scanners or checkpoint tags, uniforms bearing your branding, and any vehicle decals. Separately, request the records you are entitled to: incident reports, daily activity logs, patrol tour data, visitor logs, and any video the vendor holds. Records are far harder to obtain after the final invoice is paid.
Non-solicitation and guard hiring
Many security agreements bar you from hiring the vendor's officers directly for some period after termination. If there is a specific officer your site depends on, read this clause carefully before you make anyone a promise. Note also that on private commercial contracts there is generally no requirement that an incoming agency hire the outgoing agency's guards; retaining familiar officers is something you negotiate, not something you are owed. Federal service contracts have their own rules on this, and those rules have changed more than once in recent years, so confirm current requirements with counsel if your site is federally contracted.
Our companion guide on what belongs in a security guard contract covers these clauses from the drafting side, which is useful context for the agreement you sign next.
Evaluate the replacement before you give notice
The single most important rule of switching is that you do not give notice until the replacement is signed with a confirmed start date. Everything else is negotiable; this is not.
That means the sourcing and vetting work happens while you are still under contract. You are paying for coverage anyway, so use the runway. Confirm the incoming agency's state license is active with the regulator, verify individual guard registrations, and get a certificate of insurance naming your business as an additional insured before you commit to a start date, not after. The full sequence is in our guide on how to vet a security guard company.
Be specific about what you are actually buying this time. Write down the failure that made you switch and turn it into a term in the new agreement. If the problem was callout coverage, ask for a stated fill-time commitment and an escalation path with a named person. If it was guard churn, ask about retention rates and whether the same officers are assigned to the post. If it was cost, get itemized rates by shift and guard type rather than a blended number.
One practical warning: do not tell your incumbent you are shopping until you are ready. A vendor that knows you are leaving in ninety days behaves differently than one that thinks it is keeping the account.
The transition timeline
This assumes a thirty-day notice requirement and a routine, non-emergency switch. Shift every row earlier if your notice period is sixty or ninety days.
| Timing | What happens | Who owns it |
|---|---|---|
| Day -60 to -45 | Pull the contract, confirm the notice date and any fees, start an issue log if terminating for cause | You |
| Day -45 to -30 | Source and compare replacement agencies, verify licenses and COI, collect itemized rates | You |
| Day -32 | Sign the incoming agency with a confirmed start date and a written transition plan | You and incoming |
| Day -30 | Send written termination or non-renewal notice by the method the contract requires, and keep proof of delivery | You |
| Day -25 | Walk the site with the incoming agency; hand over post orders, site maps, access points, and escalation contacts | Incoming |
| Day -20 | Incoming agency names the assigned officers and supervisor; you confirm credentials and any site-specific training | Incoming |
| Day -14 | Notify internal stakeholders, tenants, and anyone whose badge or gate access the change touches | You |
| Day -7 | Confirm the outgoing vendor's last shift in writing; schedule the overlap shifts | Both |
| Day -3 to 0 | Overlap: incoming officers work alongside outgoing officers on each distinct shift | Both |
| Day 0 | New agency assumes full responsibility; keys, badges, codes, and equipment returned and rotated | Both |
| Day +1 to +7 | Daily check-ins, verify patrol logs and reports are arriving in the agreed format | You |
| Day +30 | Formal review against the specific failure that caused the switch | You |
The two rows people skip are the overlap and the day-zero credential rotation. Both are cheap. Both are the ones you regret.
Running the overlap and handover
An overlap is not a formality and it should not be a single shift. Cover each distinct shift pattern you run. A site with day, swing, and overnight posts plus weekend coverage needs the incoming team to ride along on all of them, because the overnight job at a warehouse has almost nothing in common with the daytime one.
What actually needs to move, in writing, before day one:
Post orders. The written instructions for the post: duties by hour, patrol routes and frequency, checkpoint locations, access control rules, who is authorized where, and the scripted response for specific scenarios such as an unauthorized person, a medical emergency, a fire alarm, or a lockout. If your post orders live with the outgoing vendor rather than with you, get a copy now. Ideally the next contract attaches them as an exhibit you own.
Site knowledge that is not written down anywhere. Which gate sticks. Which tenant works late on Thursdays. The two or three repeat trespassers officers recognize on sight. Which neighbors call in noise complaints. This is the material that only transfers if humans stand next to each other, which is the whole argument for the overlap.
Systems and access. Alarm panel codes, badge and fob issuance, camera system logins, visitor management software, guard tour or checkpoint scanning systems, and the reporting portal your incident reports arrive through. Decide who holds the administrator account. If the outgoing vendor owns the tour system, your historical patrol data may not be portable, so export it before the last shift.
Escalation contacts, both directions. Who the officer calls at 2am, and who the agency calls if the officer does not show. Names and mobile numbers, not a dispatch line.
Reporting format and cadence. Daily activity reports, incident report timelines, and where they get delivered. Agree the format before day one or you will spend the first month re-explaining it.
Then, at the moment of changeover: collect every key, badge, fob, and remote from the outgoing agency and rotate the codes anyway. Assume nothing was returned. Disable the old vendor's logins to your camera and access systems the same day. This is basic hygiene and it is not an accusation of bad faith.
Compare vetted local agencies for your post →
Stay or switch
Switching costs real effort, and not every problem justifies it. Some are cheaper to fix in place.
| Situation | Usually fix in place | Usually switch |
|---|---|---|
| One bad officer | Yes: request replacement by name under the supervision clause | Only if the vendor refuses or repeats it |
| Rate increase within the escalation cap | Yes: negotiate, benchmark against local rates | If the increase exceeds the contract cap |
| Repeated unfilled shifts | Escalate in writing once with a deadline | Yes, and document each instance for cause |
| Incident reports missing or late | Yes: put the timeline in writing and hold payment on disputed items | If it persists after written notice |
| Licensing or COI lapse | No | Yes, and check whether it qualifies as cause |
| Guards unlicensed for the post type | No | Yes, immediately, and confirm your own exposure |
| You need to scale coverage up and down | Depends on the contract's flexibility | Yes, if the term cannot bend to the actual need |
| Account manager unresponsive | Yes: request a named contact change first | If nothing changes after escalation |
The honest read on this table: single-incident problems are usually contract-management problems, and a well-drafted supervision clause solves them faster than a transition does. Structural problems, meaning licensing, insurance, chronic staffing failure, or a term length that does not match your actual need, do not get better with another conversation.
When you do not have thirty days
Sometimes the trigger is not a renewal date. A vendor's license lapses, insurance expires, a serious incident goes unreported, or the agency simply stops showing up. In that case, the order of operations changes but the principle does not: get coverage first, resolve the contract second.
Source interim coverage immediately for the shifts at risk. Short-notice and same-day staffing is a specific capability and not every agency has bench depth for it; our guide on same-day and emergency security coverage covers what is realistic on a short clock. Then document the breach carefully, send written notice of the breach and any required cure period, and let the termination-for-cause process run on its own timeline while your post stays staffed.
Paying for a few days of overlapping coverage is almost always cheaper than the alternative. An uncovered post is not just a service problem; depending on your lease, your insurance policy, or a client contract that specifies staffed security, it can be a compliance problem too.
What to fix in the next agreement
The best outcome of a switch is that you never have to run one under pressure again. When you sign the replacement, use what you just learned:
Cap the notice period for termination for convenience at thirty days, and make it symmetric. Require the vendor to send you a written renewal reminder ninety days before the renewal date, so the auto-renewal window cannot close quietly. Attach post orders as an exhibit you own, so the next transition starts with a document rather than an archaeology project. Put a fill-time commitment and a named escalation contact in writing. Cap rate escalation at a specific number with written notice and a right to terminate if you decline it. And confirm that all patrol logs, incident reports, and tour data are your records, exportable on request.
If your coverage need is genuinely variable, seasonal, or project-based, the deeper question is whether an annual term is the right instrument at all. Calvis is a marketplace that connects businesses with independently licensed local security agencies. You compare vetted agencies on published flat hourly rates, book the coverage window you actually need, and there is no annual minimum or notice period to exit. Calvis is not a security agency and does not employ the guards; each agency holds its own state license, and those licenses and individual guard registrations are verified before an officer is assigned.
That model removes most of what makes switching painful, because there is no renewal window to miss and no termination clause to negotiate around. For sites that do want a single ongoing agency relationship, the guidance above still applies: read the exit terms before you sign the entry terms.
Post your coverage and compare licensed local agencies →