Start here
Separate contract exit obligations from operational readiness. Name a client transition lead, confirm assignment-appropriate credentials and staffing, approve current post orders, test access and communications, account for equipment and authorized records, and document who accepts responsibility at the handover. Agree on a lawful fallback if the incoming team is not ready. No provider change can guarantee uninterrupted service in every circumstance.
Key takeaways
- Define the service problems to correct and the effective procedures to preserve.
- Review notice, records, equipment, recruiting, and final-charge terms with the appropriate advisers.
- Verify current agency and officer eligibility; armed registration must cover each sponsoring licensee.
- Use readiness evidence for staffing, post orders, access, reporting, and relief rather than a universal lead time.
- Keep credentials and incident information restricted to authorized recipients.
- Record the acceptance time, unresolved exceptions, fallback decision, and early service corrections.
A replacement security company can have a signed contract and still arrive unprepared for the property. The officer may not have a working access credential. Dispatch may have the wrong entrance. The overnight supervisor may be expecting instructions from a manager who left months ago.
Those are handover problems. They deserve their own plan, separate from the decision to replace the incumbent provider.
For an Arizona business or property manager, switching security guard companies means coordinating two employers, your own operating team, access-system administrators, and sometimes tenants or residents. A written transition plan should identify who owns each task, what must be verified before the change, and what happens if the incoming provider is not ready. No plan can promise uninterrupted service under every circumstance, but specific acceptance checks make an avoidable gap easier to catch.
Start with the service failure you need to correct
Put the reasons for the change into factual terms. “Poor communication” might mean incident reports arrived late, urgent calls went unanswered, or nobody owned maintenance follow-up. “Inconsistent officers” might mean relief staff lacked site orientation. Each problem calls for a different operating requirement.
Use attendance records, redacted reports, documented complaints, and unresolved action items. Avoid repeating allegations you cannot substantiate or circulating personnel information that the incoming company does not need.
Then decide what should remain. An effective visitor procedure, reliable report format, or well-understood emergency contact chain should not disappear merely because the uniform changes. Keep a short list of procedures to preserve alongside the changes you expect.
If you are still comparing providers, use Arrow’s Arizona security company hiring checklist. The discussion here starts when a replacement is being planned.
Review the exit terms before announcing a start date
Have the person responsible for the agreement confirm termination notice, delivery requirements, the final service period, outstanding charges, equipment ownership, and records access. Ask counsel about disputed terms, hiring restrictions, confidentiality, and any obligation that could affect the transition. There is no single notice period that should be assumed for every Arizona security contract.
The incoming proposal also needs a precise starting point: property, posts, days, hours, duties, equipment, and the person authorized to accept service. “Start Monday” leaves room for confusion when the outgoing shift runs overnight.
Document the ending and beginning times in local site time. For an overnight change, include both calendar dates. Make clear which provider is responsible during any agreed overlap and who is paying for it. Overlap can support orientation or joint inventory, but it should have defined tasks and supervision rather than two teams assuming the other is in charge.
Use readiness checks instead of a universal transition timeline
A small daytime lobby and a multi-site overnight assignment will not need identical preparation. The practical question is whether the required work is complete, not whether an arbitrary number of days has passed.
| Checkpoint | What management should be able to verify |
|---|---|
| Scope agreed | The schedule, duties, exclusions, pricing assumptions, and responsible managers are documented. |
| People ready | The provider has confirmed qualified staffing, relief arrangements, supervision, and completed site orientation. |
| Systems ready | Authorized access, communications, reports, and necessary equipment work for the incoming team. |
| Handover accepted | The client records who accepted responsibility, when, and which exceptions remain open. |
| Service checked | Early shifts and reports are reviewed against the agreed assignment, with corrective actions assigned. |
Assign a client transition lead with a backup. The lead should keep one action register showing the owner, due date, evidence of completion, and unresolved issue for each item. Changes approved in a phone call should reach the people working the actual shifts.
Verify Arizona credentials for the incoming assignment
Confirm the incoming agency’s current status using the Arizona DPS licensing page and its license-status link. Match the licensed entity to the company providing the service. Ask the provider to confirm the registrations and qualifications applicable to every regular and relief officer it proposes to assign.
For regulated agency work, A.R.S. 32-2608 establishes the registration and licensed-agency employment framework, with an exception for regularly commissioned peace officers. Do not assume that a familiar officer, a training certificate, or an old photocopy settles current assignment eligibility.
Armed assignments require particular care during an employer change. Under A.R.S. 32-2624, an employee must obtain an armed security guard registration certificate and identification card for each sponsoring licensee. On-duty firearm carry also requires current armed registration and employer authorization. An armed credential associated with the outgoing company should not be treated as automatic authorization to work armed for the replacement.
At this guide’s November 5, 2026 source check, DPS displayed a notice that electronic applications and fingerprint submissions were suspended beginning October 30 during a processing-system transition, while paper submissions remained accepted. Check the current notice and ask the incoming provider about any effect on staffing readiness. Do not base the handover on an assumed approval date.
Rewrite post orders around the property as it operates now
Collect the current instructions, then walk the assignment with the incoming supervisor and the client representative who knows the site. Old post orders can contain obsolete contacts, entrances that no longer operate, or duties added verbally over time.
Resolve disagreements before the first independent shift. Who authorizes an after-hours visitor? Who can approve a delivery exception? Where does a patrol officer’s responsibility end? Who receives a time-sensitive report when the property manager is unavailable?
Emergency instructions need the same review. Security should know how to call for help, provide the correct location, communicate with management, and support responder access under the site plan. For workplaces subject to OSHA’s emergency-action-plan requirement, 29 CFR 1910.38 includes employee review when responsibilities or the plan change. Coordinate the provider’s instructions with the employer’s applicable plan rather than treating a guard-company change as a substitute for it.
Keep detailed access information, sensitive layouts, and emergency operating instructions in controlled documents. A tenant announcement does not need the patrol schedule or system credentials.
Account for keys, credentials, equipment, and records
Create an inventory before the change. For each item, record the owner, current custodian, approved recipient, return or activation requirement, and verification method. Include physical keys and badges as well as radios, phones, vehicles, chargers, reporting accounts, and any client-owned devices.
Have the authorized system administrator create appropriate individual access for incoming staff and end outgoing access at the agreed time. Test the replacement access before withdrawing something the active team still needs. Compromised credentials may need immediate revocation under the site’s incident procedure. Shared credentials require a deliberate change plan; simply passing along the old password preserves uncertainty about who can still use it.
The FTC’s business security guidance supports limiting access to people with a legitimate need and controlling service-provider access. Apply those principles to the handover without emailing passwords, resident lists, or incident files to a broad distribution group.
Separate client records from the outgoing company’s proprietary material and personnel records. Confirm what the agreement allows you to obtain, who may receive it, and how an export will be checked. Preserve records subject to an applicable retention obligation or legal hold. A transition is not permission to delete evidence or take information belonging to another party.
Record unresolved incidents and pending maintenance separately. The new company needs enough authorized context to continue the assignment, not an indiscriminate download of everyone’s personal information.
Orient regular and relief officers before they work alone
Ask the incoming supervisor to demonstrate how orientation will be completed and documented. A walkthrough should cover the officer’s duties, approved exceptions, communication methods, reporting, equipment, site hazards, and escalation limits. Staff should be able to explain the instructions back in their own words.
Include relief staff in the preparation. A strong opening shift does little for continuity if the next call-out brings someone who cannot enter the site or locate the approved instructions. Identify who checks attendance, who arranges replacement coverage, and when the client will be told about a problem.
Make training expectations assignment-specific. Arizona’s guard-training statute establishes preassignment and firearms-training requirements, but a state curriculum does not teach a particular building’s visitor rules or reporting system. Obtain confirmation of the proposed officers’ applicable credentials and completed site orientation without requesting confidential background files.
If management hopes to retain familiar officers, discuss that through the companies and appropriate advisers. Employment decisions, eligibility, contractual restrictions, and acceptance by the new employer need their own review. Do not promise employees a transfer or make continuing coverage depend on an unconfirmed arrangement.
Plan the handover and the fallback together
At the changeover, the client lead and designated supervisors should confirm the incoming coverage, communication checks, equipment inventory, open incidents, and acceptance time. Record exceptions with an owner and a decision. “Someone will sort out the badge tomorrow” is not an acceptance check.
Agree beforehand on what happens if a required item is missing. Options might include a contractually agreed extension, a revised start, or separately arranged temporary coverage. Each option requires actual availability, qualified personnel, and approval. Do not assume the outgoing company will stay late or that mobile patrol provides the same service as a continuously staffed post.
For an urgent replacement, concentrate on the immediate lawful coverage requirement, responsible contacts, access, emergency instructions, and essential reporting. Document any temporary limitations and the decision-maker who accepted them. Do not quietly expand the assignment into tasks the incoming team is not prepared or authorized to perform.
Tell site users what changes, then review the early service
Employees, tenants, residents, reception teams, and regular vendors may need a brief notice explaining the change date, how to identify the new provider, and the approved contact route. Make clear that emergencies still go to 911. An urgent call should not wait for a new reporting portal or a manager’s approval.
Review the first shift, the first full schedule cycle, and an agreed first-month checkpoint. These are suggested management reviews, not Arizona statutory deadlines. Look at actual attendance, report delivery, access problems, supervisor involvement, and whether the service failures that prompted the switch are being corrected.
Use a small issue log rather than relying on impressions. For each problem, record what happened, its effect, the responsible person, the correction, and how completion was verified. Arrow’s guide to security reports and patrol verification explains how to evaluate the evidence without confusing a timestamp with completion of every duty.
Finally, reconcile returned property, authorized records exports, outgoing access removal, and the final invoice under the agreement. Keep the transition record with the account documentation so the next manager can understand what was accepted.
Questions about switching security guard companies
How much lead time should we allow?
Ask the incoming company for a written readiness plan tied to your scope, staffing, credentials, orientation, equipment, and current processing conditions. Review the outgoing contract separately. There is no reliable universal lead time for every Arizona assignment.
Can we keep our existing officers?
Possibly, but do not assume it. The companies, employees, and relevant advisers must resolve hiring, contractual, and credential requirements. Confirm the new employer’s approval and any armed-registration sponsorship requirements before relying on those officers for the start date.
Should the two companies overlap?
Where feasible and agreed, a limited overlap can support orientation, inventory, and transfer of responsibility. Specify duties, command, access, timing, and charges. Overlap alone does not prove readiness or guarantee continuous coverage.
What should we bring to a transition discussion with Arrow?
Bring the property type, desired schedule, service concerns, proposed change date, and a non-sensitive summary of the assignment. Ask about available staffing, supervision, orientation, reporting, and contingency arrangements for your site. Share contracts, access details, and incident records only through an agreed channel with authorized recipients. Discuss contract security with Arrow to establish a property-specific scope and realistic next steps.
