How to Hire a Security Guard Company in Arizona: A 15-Point Buyer Checklist

Before contacting providers: define the assignment

Start with the problem, not a predetermined headcount. A provider cannot responsibly design coverage from “we need one guard” alone.

Prepare a one-page assignment profile:

• Property or event type, address, layout, and operating hours
• People and assets to protect, including any vulnerable population
• Public, employee, resident, vendor, delivery, vehicle, and after-hours access
• Recent incidents, recurring concerns, known threats, alarms, and near misses
• Existing fencing, lighting, locks, cameras, alarms, gates, and access-control systems
• Required dates, days, hours, post locations, and desired start date
• Duties you believe are needed and duties that must not be performed
• Emergency procedures and police, fire, EMS, venue, or management contacts
• Required reports, communication methods, technology, uniforms, PPE, vehicles, or credentials
• Insurance, contract, procurement, and budget requirements

Describe desired outcomes in observable terms. “Improve safety” is important but difficult to evaluate alone. More useful objectives include controlling a named entrance, documenting after-hours patrols, reducing recurring open-gate findings, escalating disturbances under an approved procedure, or ensuring a trained officer is present during specified hours.

The 15-point buyer checklist

1. Verify the Arizona security agency license

The Arizona Department of Public Safety regulates security guard agencies and individual guard registrations. Use the current DPS licensing page and public status portal to verify the provider—not a search-engine directory or a document supplied years ago.

Confirm:

• Exact licensed agency name and any approved business name
• Current status and identifying license information
• That the entity submitting the contract matches or clearly explains its relationship to the licensed entity
• The contact and escalation information that will appear in the agreement

DPS explicitly states that a registration card or photocopy is not proof that it remains valid. Build a current-status verification into procurement and periodic vendor review.

2. Distinguish the agency license from individual guard registration

An agency license authorizes the business to provide regulated security services. Individual guards must have the registration appropriate to their assignment. Armed status requires additional DPS-approved firearms training.

Ask how the company verifies a guard’s status before assignment and monitors expirations or restrictions. Do not request confidential criminal-history details the company cannot lawfully share. Ask for the provider’s process and auditable confirmation instead.

Arizona law also states that security guards and armed security guards do not have the authority of commissioned police or peace officers. A proposal should not depend on exaggerated claims of police power.

3. Confirm insurance and risk-transfer requirements

Arizona currently requires a security guard agency to submit proof of general liability and workers’ compensation insurance as part of agency licensing. DPS currently identifies minimum general-liability limits of $100,000 per occurrence and at least $300,000 aggregate. Those licensing minimums may be lower than the limits your organization, venue, lender, landlord, or risk profile requires.

Ask your insurance adviser or counsel what coverage and endorsements are appropriate. Request current certificates and confirm:

• Insured legal entity and policy dates
• General liability limits
• Workers’ compensation coverage
• Automobile coverage if vehicles will be used
• Any other coverage required by the contract or exposure
• Notice and certificate-holder requirements
• Whether subcontracting changes coverage or responsibility

A certificate is evidence at a moment in time, not a complete interpretation of the policy. Direct coverage questions to qualified advisers.

4. Evaluate the provider’s site-assessment process

A serious proposal should connect identifiable risks to duties and controls. Ask who assesses the site, what information is reviewed, whether the property is visited after dark when relevant, and what deliverable you receive.

Clarify whether an advertised “consultation” is a sales walkthrough, a staffing recommendation, or a formal written risk assessment. Those are not automatically the same service. A credible assessor should be willing to explain assumptions, exclusions, and why a guard, patrol, camera, access control, or layered plan fits the objective.

5. Review officer selection and assignment fit

Ask how the company matches people to the environment. A calm commercial lobby, construction gate, hospital, apartment community, school, and alcohol-serving event demand different communication, mobility, judgment, and site knowledge.

Useful questions include:

• What minimum qualifications apply to this assignment?
• Who approves the officer before placement?
• How are required licenses and certifications verified?
• Which physical, communication, driving, technology, or PPE requirements are job-related and documented?
• How are conflicts, conduct concerns, or client requests handled?
• When is a relief officer used, and how is that person prepared?

Avoid relying on claims such as “all officers are former law enforcement” unless the provider can substantiate them and the background is relevant to the actual duties.

6. Separate state-required training from site-specific preparation

Arizona DPS currently identifies an eight-hour required general curriculum covering orientation, criminal law, uniform, communications, use of force, general procedures, crime scene, ethics, and first response. Armed guards must additionally complete the DPS-approved 16-hour initial firearms course, with other current requirements described by DPS.

That baseline is not a substitute for assignment-specific orientation. Before an officer works alone, the provider should cover the site boundary, post orders, people and assets, access rules, client contacts, emergency procedures, report system, equipment, hazards, and prohibited actions. Ask how competence is checked and how changes reach every regular and relief officer.

Do not assume every officer holds the same assignment-specific credentials. Ask the provider to document which First Aid, CPR, de-escalation, healthcare, school, construction, or other qualifications apply to the officers proposed for your post.

7. Require clear written post orders

Post orders are the operating instructions for the assignment. They should be specific enough for an officer, supervisor, client contact, and auditor to understand what must happen.

They should identify:

• Address, boundaries, schedule, posts, patrol areas, and checkpoints
• Entry, visitor, vendor, delivery, key, badge, and alarm procedures
• Routine duties, frequency expectations, and documentation
• Incident, emergency, and 911 thresholds
• Client and security notification paths
• Equipment and technology use
• Privacy, photography, evidence, and records rules
• Restricted areas and prohibited duties
• Who can change instructions and how changes are documented

Ask to review and approve the site-specific version before launch. Generic handbook language does not replace it.

8. Examine supervision and field support

Supervision should be a defined process, not simply the existence of a manager’s phone number. Ask:

• Who supervises the account and who is the after-hours escalation contact?
• How are attendance, punctuality, uniform, post knowledge, patrol completion, and report quality checked?
• Are site inspections announced, unannounced, remote, or a combination?
• How are performance problems documented and corrected?
• How quickly are material client concerns acknowledged and assigned?
• Who reviews recurring incidents and recommends changes?

If the proposal refers to GPS, geofencing, checkpoints, or a client portal, request a demonstration or redacted sample. Confirm what the data proves; a timestamp alone does not prove that every required duty was performed.

9. Test the relief and missed-shift plan

Ask the provider to walk through a realistic call-out:

1. When must the officer notify the company?
2. Who receives the alert?
3. How is a qualified replacement identified?
4. How is the relief officer oriented to this assignment?
5. When and how is the client informed?
6. What happens if immediate replacement is not available?
7. How is the service failure documented and addressed contractually?

Do not accept an unsupported guaranteed replacement or response time. Put any material commitment and remedy in the agreement.

10. Review daily and incident reporting

Request redacted examples of a daily activity report and an incident report. Look for factual writing, specific times and locations, actions, notifications, attachments where appropriate, and unresolved follow-up.

Confirm:

• Required report types and fields
• Delivery timing and recipients
• Urgent notification versus end-of-shift reporting
• Photograph and video policy
• GPS or checkpoint detail
• Supervisor review and correction
• Client access, export, retention, privacy, and breach procedures

Reports should distinguish what the officer directly observed from what another person reported.

11. Define communication and emergency coordination

The plan should name the person who can change instructions, the after-hours client contacts, provider dispatch or management contacts, and backup methods if a phone or network fails.

Ask how officers coordinate with police, fire, and EMS without implying law-enforcement authority. Supply correct addresses, gate codes or access procedures, hazardous-area restrictions, muster points, and responder routes. Security can support communication and site access under the plan; public responders retain their legal authority and responsibilities.

12. Confirm technology, equipment, vehicle, and uniform details

List what is included and who owns, maintains, charges, replaces, and trains users on each item. This may include radios, phones, panic devices, patrol vehicles, body-worn equipment, access-control terminals, cameras, portable camera towers, reporting software, and PPE.

Ask what happens during an outage or equipment failure. Do not assume that “camera monitoring,” “GPS tracking,” or “integration” has the same meaning across providers.

13. Compare the full contract and pricing assumptions

Require a written scope and price assumptions. Review:

• Base schedule and total expected hours
• Armed or unarmed classification
• Included supervision, reporting, equipment, and vehicle use
• Overtime, holiday, short-notice, travel, setup, or event charges
• Minimum shift or contract duration
• Deposits, invoice timing, taxes, and payment terms
• Schedule-change, extension, cancellation, and termination procedures
• Indemnity, insurance, confidentiality, records, and dispute terms
• Duties and conditions specifically excluded

Have counsel review material legal terms. A low hourly rate may omit functions another proposal includes.

14. Check relevant references and evidence

Ask for references from comparable assignments—with the other client’s permission. “Comparable” means a similar environment, schedule, risk, and service model, not merely a satisfied customer.

Ask references about startup, officer consistency, supervision, reports, call-outs, communication, invoicing, and adaptation when the assignment changed. Respect confidentiality; a provider should not disclose another client’s sensitive security plan.

Public reviews can reveal patterns, but they do not replace current licensing, insurance, a relevant reference, or examination of the operating plan.

15. Approve implementation and performance review

Before launch, establish:

• Named account owner and client decision-maker
• Approved post orders and contact tree
• Officer orientation and readiness confirmation
• Equipment, keys, credentials, access, and report testing
• Start-of-service briefing and first-shift support
• Early check-in after launch
• Regular review frequency and performance measures
• Change-control process for schedule, duties, post orders, and price

Measure leading indicators such as shift coverage, patrol completion, report accuracy, access exceptions, hazards found, supervisor reviews, and corrective-action closure. Incident counts alone can mislead: increased reporting may reflect better detection rather than a worsening environment.

Weighted security company scorecard

Score each category from 0 to the maximum points. Require notes and evidence rather than scoring from presentation quality alone.

A scorecard supports disciplined comparison; it does not eliminate judgment. A serious licensing, insurance, integrity, safety, or scope defect can be disqualifying regardless of total points.

Red flags during procurement

• The agency cannot be found in the current Arizona DPS status system or the contracting entity is unclear.
• The provider treats a photocopy or website license number as sufficient proof of current status.
• The proposal promises prevention, guaranteed outcomes, police powers, or universally rapid response.
• The company recommends armed coverage without a risk-based explanation.
• Duties, exclusions, supervision, reporting, or call-out coverage remain vague.
• The provider will not supply redacted report examples or explain how performance is checked.
• The rate is presented without schedule, minimums, overtime, holiday, equipment, or cancellation assumptions.
• Generic post orders will be used without site-specific approval.
• Subcontracting, insurance, monitoring, or data handling is concealed or unexplained.
• References or client details appear to be shared without permission.

Vendor information worksheet

Use the same worksheet for every bidder:

Frequently asked questions

How do I verify a security company in Arizona?

Use the Arizona DPS licensing page and linked Public Services Portal status search. Confirm the exact agency and current status. DPS says the card itself or a photocopy is not proof of validity.

Should I hire the lowest-priced security company?

Not without confirming that the scope matches. Compare schedule, officer type, duties, supervision, relief coverage, reporting, equipment, fees, and contract terms. A lower number can represent a narrower service.

Should a security company visit the property before quoting?

A visit is valuable when layout, access, hazards, patrol travel, lighting, technology, or operating conditions affect the plan. Some simple assignments may initially be scoped from complete documentation, but assumptions should be verified before launch.

Can I require the same officers every shift?

Ask for a regular-team strategy, but account for lawful leave, illness, turnover, training, and emergencies. The more important control is that every regular and relief officer meets the assignment requirements and receives current site orientation.

What should be ready before the first shift?

Approved post orders, contacts, access, keys or credentials, equipment, reporting access, emergency procedures, officer orientation, escalation paths, and a process for resolving first-shift issues.