Security FAQs

They can, but the required fields and evidence practices should be agreed before service begins. A strong incident report records the date, time, precise location, people involved or notified, objective observations, actions taken, emergency response, and any case or report number. Patrol or GPS information can establish where the officer was and when relevant activity occurred.

Yes—post orders should be updated when the property, risk, systems, schedule, or client requirements change. Effective orders are controlled operational documents, not a one-time attachment that remains unchanged for years. Changes may follow an incident, construction phase, new tenant, gate or alarm replacement, staffing change, revised emergency plan, or a recurring issue identified in reports.

Security officers should receive training matched to their duties, but clients should verify each assigned officer’s records rather than assume every guard has the same credentials. Arizona guard registration sets state requirements; it does not automatically establish current First Aid, CPR, AED, or advanced de-escalation certification.

Arrow’s construction-security page specifically describes uniformed officers, and a visible uniform is common for assignments where deterrence, recognition, and public assistance are priorities. Arizona law requires security uniforms and insignia to be approved under DPS rules, not deceive or confuse the public, and not be identical to law-enforcement uniforms. It also requires agency-name shoulder patches on uniform jackets, coats, and shirts. The presentation should fit the environment, weather, mobility, protective-equipment needs, and client dress standards.

Measure security against defined objectives and leading indicators, not only whether crime occurred. A month with no reported incidents could reflect effective controls, low exposure, or poor detection. Start by documenting the problems the program is meant to address and the current baseline.