Planning & AssessmentAction checklist

30-Day Security Contract Launch Checklist

A 30-day security contract launch checklist helps the client and provider convert a signed scope into a functioning site operation. It covers decision owners, site assessment, post orders, emergency coordination, staffing, orientation, equipment, reporting, go-live verification and early performance review. The checklist does not replace the contract, a professional risk assessment, required guard training or the employer's emergency action plan. Complete it jointly, keep sensitive operating details in controlled records, and document every unresolved dependency. Dates are a planning framework: higher-risk sites may require more preparation, supervision or testing before independent service begins.

20 checks5 sectionsSources checked July 19, 2026
Why it matters

Use a system view, not a single-control view

Many launch failures are coordination failures: a contact list is outdated, a report route is unclear or a relief guard has not seen the current orders. A written readiness record makes dependencies visible before the first shift.

CISA's SAFE model uses a structured review of current security measures and identifies practices to sustain, vulnerabilities and options. A contract launch should likewise connect staffing and procedures to the site's actual conditions rather than copy a generic post.

Before you begin

How to use this checklist

  1. Name one accountable client lead and one provider lead, then set the planned service start and review dates.
  2. Complete the pre-launch sections in a controlled working session; never enter alarm codes, access credentials or sensitive layouts in this public tool.
  3. Do not mark a critical dependency complete until the responsible owner has verified it.
  4. At days 7 and 30, compare actual records with the agreed scope and close or reassign every open action.
Interactive checklist

Mark each task from current evidence

Use Not applicable only when the item genuinely does not apply, and follow the site’s approved escalation process for any urgent condition.

Section 1 of 5

Scope and governance

Establish what the service must achieve and who can make decisions.

01The executed agreement, statement of work and approved service schedule are available to authorized launch leaders. Priority review item

Evidence to look for: Confirm the controlling versions, effective date, covered locations, posts and approved change process.

02Client and provider launch leads, backups and decision authority are documented. Priority review item

Evidence to look for: Record roles for routine requests, urgent operational decisions, invoicing, safety and contract changes in a controlled contact list.

03Service objectives and measurable acceptance criteria are agreed.

Evidence to look for: Each measure should trace to a requirement and define evidence, calculation, exclusions and review cadence.

04Known exclusions, client-retained responsibilities and provider dependencies are explicit.

Evidence to look for: Examples can include access-system administration, facility repairs, emergency-plan ownership or information supplied by the client.

Section 2 of 5

Site and procedure readiness

Translate site conditions and the client's plan into controlled operating instructions.

05A documented site walk identified relevant operations, access points, hazards and existing protective measures. Priority review item

Evidence to look for: Use qualified client and provider representatives; store detailed layouts and vulnerabilities only in access-controlled records.

06Current post orders define duties, limits, reporting and escalation without conflicting with the contract. Priority review item

Evidence to look for: Orders should be site-specific, version-controlled, approved and understandable to a qualified guard.

07The client's emergency action plan and the guard's supporting role have been reviewed. Priority review item

Evidence to look for: Confirm alarm recognition, evacuation or shelter instructions, accountability support, emergency contacts and the boundaries of the guard role.

08Access credentials, keys and site information have a secure issuance, return and loss process. Priority review item

Evidence to look for: Use a controlled inventory; this checklist should record readiness only, never the credentials themselves.

Section 3 of 5

People and equipment

Confirm that the assigned team can perform the approved scope safely.

09Staffing and relief coverage are assigned for the launch schedule. Priority review item

Evidence to look for: Verify primary and contingency coverage without publishing names or schedules on the public page.

10Required Arizona registrations and assignment qualifications are current and verified. Priority review item

Evidence to look for: Use employer records and the Arizona DPS status process as applicable; verify before duties begin.

11Every assigned guard completed documented site orientation and demonstrated understanding. Priority review item

Evidence to look for: Cover orders, hazards, emergency role, communications, reports, equipment, prohibited disclosures and whom to call for help.

12Required communications and non-weapon equipment are inventoried, functional and supported by a defect process. Priority review item

Evidence to look for: Test normal and backup communications in representative authorized areas and record known limitations privately.

Section 4 of 5

Go-live and first week

Use close supervision to detect assumptions that planning did not reveal.

13The first shift received an on-site or otherwise effective supervisory startup check. Priority review item

Evidence to look for: Confirm arrival, handoff, orders, equipment, client contact and immediate site conditions.

14The client verified that expected coverage and primary duties were visible on go-live day.

Evidence to look for: Use the scope and approved records rather than assessing guards against unstated preferences.

15Daily activity and incident reporting reached the intended recipients in a usable format. Priority review item

Evidence to look for: Test submission, access permissions, timestamps and review responsibility with non-sensitive sample or actual approved records.

16A first-week review captured guard, supervisor and client feedback and assigned actions.

Evidence to look for: Ask what was unclear, unavailable or different from the orders; separate urgent corrections from future enhancements.

Section 5 of 5

Days 8 through 30

Stabilize the operation and establish the normal quality-management rhythm.

17Supervisor samples show required duties and reports are consistently completed.

Evidence to look for: Review multiple shifts and dates; protect patrol patterns and personal information.

18Post orders and contact lists were updated for validated launch lessons and reapproved. Priority review item

Evidence to look for: Changes should show revision date, owner, approval and acknowledgment by affected personnel.

19Open safety, access, equipment and staffing dependencies have owners and target dates. Priority review item

Evidence to look for: High-priority items should also state an interim control or service limitation.

20The 30-day review compares evidence with agreed objectives and sets the ongoing meeting cadence.

Evidence to look for: Record strengths, exceptions, trend baselines, corrective actions and any approved scope changes.

Current result

Complete the checklist to see a summary

Results are informational and do not certify compliance or eliminate risk.

Common mistakes

What can weaken the review

  • Treating the signed contract as if it were a complete set of site instructions.
  • Copying post orders from another property without validating local conditions.
  • Starting service before responsibilities, emergency contacts and report routing are confirmed.
  • Giving verbal changes to one shift without version control and acknowledgment.
  • Closing the launch at day 30 while critical corrective actions remain unowned.
Practical questions

Frequently asked questions

When should planning for a new security contract begin?

Begin as soon as the scope and decision owners are sufficiently clear. The time required depends on site complexity, risk, staffing, access provisioning, training and equipment; 30 days is a framework, not a universal promise.

Who should approve security guard post orders?

At minimum, authorized representatives of the licensed provider and client should approve them. Safety, HR, legal, facilities or emergency-management reviewers may also be needed depending on the duties and site.

Can guards start while some launch items remain open?

Only the accountable client and provider leaders can decide that after evaluating the risk, contract and applicable requirements. Critical gaps may require delaying or limiting service and documenting an interim control.

What should happen at the 30-day security review?

Compare actual coverage, duty and report evidence with the agreed scope; record effective practices, exceptions and feedback; close or reassign actions; approve needed order changes; and set the ongoing review cadence.

Sources and evidence baseline

These references support the general planning baseline. Site-specific decisions still require the responsible organization and appropriate qualified professionals.

  1. Security Assessment at First EntryCybersecurity and Infrastructure Security Agency

    Structured site review, good practices, vulnerabilities and mitigation options.

  2. Steps to Performance-Based AcquisitionU.S. General Services Administration

    Connecting objectives and measurable requirements to performance management.

  3. Emergency Action Plan ChecklistOccupational Safety and Health Administration

    Emergency roles, contacts, communications and plan readiness.

  4. Security Guard and Private Investigator LicensingArizona Department of Public Safety

    Current Arizona registration, training and verification context.

Source links checked: July 19, 2026

Related services and checklists

Continue with the service context or a neighboring planning tool that helps you act on what you found.