Organize incoming client accounts, prepare site operating settings, and plan eligible guard-bank coverage.
Restricted management workspace
Setup workflow — not live dispatch: These forms store non-operational setup requests. A client and its sites are not active until signed contracts, security requirements, and authorized back-office approvals are verified. Do not enter gate codes, post orders, sensitive emergency contacts, or confidential security instructions. Only manager/owner-authorized backend publishing may make those available.
CLIENT SETUP REQUESTS—Restricted to your account
SITE SETUP REQUESTS—Not operational locations
GUARD-BANK PLANS—No officer access granted
OFFICIAL SITE SNAPSHOTS—Authorized records, if synced
CLIENT ONBOARDING
Client Setup
Capture basic client details for management and contract review.
1 / Intake
Client Requests
0
No requests loaded.
Selected client
Choose a client to review its summary or prepare a proposed site.
New Client Setup Request
Not active
The request will be saved to your private setup queue. It will not create an approved operational client.
LOCATION CONFIGURATION
Security Site Setup
Define a proposed site and its basic, non-confidential operating parameters.
2 / Location prep
Proposed Locations
0
No site requests loaded.
Selected site
Select a proposed site to review configuration and prepare guard-bank coverage.
New Site Setup Request
Not active
COVERAGE PLANNING
Guard Bank Planning
Propose officers for a draft site. Actual membership remains locked until management verifies qualifications and the site is activated.
3 / Eligibility prep
New Guard-Bank Plan
Proposal only
Recorded Planning Requests
0
No guard-bank plans submitted.
Authorization requirements
Confirm the client's signed agreement and activate the location.
Verify the officer’s Florida credentials and approved armed/unarmed qualifications.
Check the officer's active eligibility, coverage schedule and management approval.
Create the official guard-bank membership through an authorized backend service.
Site instructions and emergency contacts will be versioned and published exclusively by manager/owner-authorized backend actions. Officers will acknowledge the current version before every shift; access to confidential information ends after their final assignment unless separately authorized.