Module types
Arrow types
Markers
Follow One New Contract
SAMPLE: a 24-hour unarmed guard post at a distribution center, from web inquiry to renewal. Click a step to open its record.
A Shift Under Pressure
SAMPLE: a Friday night. A call-off, the coverage engine filling the post, a missed checkpoint, an incident with escalation, and the morning client summary.
Incident Escalation
Interactive flow by severity. Officers call emergency services first when life or safety is at risk; the system then escalates, collects the report, and keeps a record.
Who is notified
Supervisor → Client (by next report)
Channel
CRM + report
Within time
Next report cycle
Recorded as
IRP (routine)
The software does not direct tactical decisions. Emergency calls always go through phone and emergency services.
Executive Overview and Business Architecture
Four lanes feed an operations core and a revenue core. The CRM owns leads, accounts, contracts, communication and reporting; daily delivery runs in Mode A (CRM-native) or Mode B (an external guard-management tool).
Lead Generation and Capture
Every source feeds one company-and-contact upsert with attribution tags. Urgent requests route to the on-call manager immediately.
Account and Contact Management
Company = the client. Contact = a person. One account, many sites, many contacts. Smart lists surface risk and opportunity.
Records and Database
Custom objects with unique IDs and system-of-record badges. In Mode B, shift/patrol/report records are synced summaries from the operations tool.
Services, Pricing and Bidding
Service catalog and bid logic. A ballpark tool exists only from an owner-approved rate table, labeled 'not a bid.' Contract terms needing legal review are marked.
Scheduling, Coverage and Resources
Mode A: CRM calendars and recurring schedules. Mode B: the operations tool owns schedules, clock-ins, and patrol data.
Core Operations and Service Delivery
Swimlane from contract signed through daily service to monthly review. Each step shows actor, record changed, workflow fired, SAMPLE target time, and miss handling.
Communication
Email, SMS (with consent), phone, client portal, web chat, officer messaging, on-call alert tool. Quiet hours with exceptions for incidents and coverage. A2P 10DLC registration required.
Vendors, Partners and Referrals
Suppliers, training, background checks, insurance, subcontract partners, and referral partners. Subcontracted coverage requires matching licenses, insurance, and client approval; referral compensation needs owner review.
Payments and Financial Tracking
Accounting owns the books and receivables; payroll owns wages; the operations tool (Mode B) or CRM (Mode A) owns hours. The CRM stores contract values, invoice status, and links. Wage, prevailing wage, OT, and tax treatment vary — Legal Review Needed.
Team Management
Org chart, post and officer assignments, supervisor span of control, on-call rotation, training checklists, SOP library, license/training tracking, performance metrics. Employment classification, wage/hour, and license requirements need legal review.
External Integrations
Hub diagram with the CRM at the center. If an operations tool is the source of truth for shifts, patrols, and reports, the CRM does not overwrite them; any sync is Requires External Integration until confirmed. Emergency calls always go through phone and emergency services, never automated messaging alone.
CRM (Hub)
The CRM sits at the center. Every integration is labeled with data sent/received, method, and an Unavailable Mode fallback.
Reporting and Business Intelligence
Each report answers a question from named source records, with an owner and a SAMPLE visual. Plus a Bottleneck View and a Post Health Heatmap.
Data Architecture and Relationships
Interactive ER diagram with cardinality, a System-of-Record matrix for Modes A and B, a data lifecycle panel, and a Common Mistakes panel.
Common Mistakes
- One company record for every site (instead of one account, many sites).
- Storing each shift as an opportunity (an opportunity is one bid/event/renewal, never a single shift).
- Post orders or alarm codes left in notes visible to all.
- License dates tracked on paper, not in the system with expiry blocks.
- Incident reports emailed with no record in the CRM.
- Officer schedules shared with people who do not need them.
Data Lifecycle
Creation → updates → archive → retention of incident, report, and training records for required periods → deletion on request where permitted. Legal Review
AI Assistants and Automation
Ten assistants with can-do/cannot-do and hand-off rules. AI guardrails are displayed prominently. Emergencies always route to emergency services and the on-call manager.
Compliance, Security and Permissions
Every jurisdiction-dependent item carries a Legal Review Needed marker. The app never asserts the company is compliant. Interactive permissions matrix and audit trail.
Implementation Status and Validation
Filterable, sortable checklist with progress summary by category and a progress ring per section. 'Verified' requires a completed 'Tested' record. Go-Live Readiness gates listed.
Automation Workflows (W1–W24)
Each workflow is clickable. Trigger, conditions, actions, notifications, exceptions, and a status selector.
Workflow Dependency Map
If It Fails
No eligible backup for call-off
Owner: Dispatcher / Operations Manager · Fallback: Manager covers directly; client notice
Officer no-show / abandoned post
Owner: Dispatcher · Fallback: Relief officer + client notice plan
Missed patrol checkpoint
Owner: Supervisor · Fallback: Manual log; pattern in client summary
Incident report missing
Owner: Supervisor · Fallback: Officer & supervisor task; hold client report
Expired license at armed post
Owner: HR · Fallback: Block scheduling; reassign officer
Operations tool sync outage (Mode B)
Owner: Operations Manager · Fallback: Manual entry; CRM flags stale data
SMS opt-out
Owner: Account Manager · Fallback: Switch to email/phone; respect consent
Invoice hours dispute
Owner: Bookkeeper · Fallback: Pause reminders; owner service review
Sales and Revenue Pipelines
Seven Kanban pipelines with stage definitions, entry/exit criteria, automation hooks, and owners. An opportunity is one bid, event, or renewal — never a single shift.
New Business Bids
Hooks: W1 Speed-to-Response, W2 Survey & Proposal, W3 Follow-Up
Contract Onboarding
Hooks: W4 Post Setup, W5 Start-Up Transition
Renewals and Expansion
Hooks: W16 Renewal & Rate Review
Events and Special Coverage
Hooks: W11 Extra Coverage & Events
Account Retention
Hooks: W21 Early Warning, W13 Complaint
Officer Recruiting
Hooks: W17 Recruiting & Onboarding
Referral Partners & Electronic Security Projects
Hooks: Project: survey → quote → install → monitoring start (if offered)
External Integrations
Hub diagram with the CRM at the center. If an operations tool is the source of truth for shifts, patrols, and reports, the CRM does not overwrite them. Emergency calls always go through phone and emergency services.
CRM (Hub)
Team Management
Org chart, assignments, on-call rotation, SOP library, and performance metrics. Employment classification, wage/hour, and license requirements need legal review.
Org Chart
AI Assistants and Automation
Ten assistants with can-do/cannot-do and hand-off rules. AI guardrails are displayed prominently.
AI Guardrails
- Discloses it is automated when asked and offers a human at any time.
- Emergencies: if anyone reports danger, a crime in progress, fire, medical emergency, or a weapon, it tells them to call emergency services right now, alerts the on-call manager immediately, and takes no other action. It never dispatches officers or emergency services on its own and never gives tactical or safety instructions.
- Gives no binding price, bid, start date, or staffing commitment; ballpark ranges only from the approved rate table, labeled 'not a bid.'
- Never promises protection, deterrence, crime prevention, response times, or specific outcomes.
- Never gives advice on use of force, weapons, arrest or detention, search, surveillance, or what an officer may legally do; never decides whether a post needs armed coverage; never determines legal responsibility or fault in an incident.
- Never shares officer names, schedules, patrol routes, post orders, access codes, alarm codes, key locations, or site vulnerabilities in open chat or with unverified contacts; verification of the requester's authority is required; sensitive details live in restricted fields or an external vault.
- Never gives legal, labor, wage, immigration, tax, or insurance advice.
- Never approves credits, refunds, scope changes, rate changes, or contract exceptions.
- Does not request card numbers in chat; payments use approved links. Respects consent and opt-out. Applies written policies equally, without discrimination. Logs every conversation; flagged ones reviewed by a human.
Compliance, Security and Permissions
Every jurisdiction-dependent item carries a Legal Review Needed marker. The app never asserts the company is compliant.
Permissions Matrix
Roles × functions with View/Edit/Create/Delete/Export/Financial/Settings. Scope rules per role.
| Function | Owner | Ops Mgr | Dispatcher | Acct Mgr | Estimator | Supervisor | Officer | HR | Trainer | Bookkeeper |
|---|---|---|---|---|---|---|---|---|---|---|
| Accounts & Contacts | Full | Full | View | Own | View | View | — | — | — | — |
| Contracts & Pricing | Full | View | — | Own | Own | — | — | — | — | View |
| Schedules & Coverage | Full | Full | Full | View | — | Own posts | Own shifts | — | — | — |
| Patrols & Reports | Full | Full | View | Own | — | Own | Own | — | — | — |
| Incidents | Full | Full | Active | Own | — | Own | Own | — | — | — |
| Officer Records | Full | Full | View | — | — | Own | Own | Full | View | — |
| Financials | Full | View | — | Own | — | — | — | — | — | Full |
| Firearm/Key/Alarm Records | Full | View | — | — | — | — | — | — | — | — |
| Workflows & Integrations | Full | View | — | — | — | — | — | — | — | — |
| Exports | Full | — | — | — | — | — | — | — | — | — |
Reporting and Business Intelligence
Each report answers a question from named source records, with an owner and a SAMPLE visual. Plus a Bottleneck View and a Post Health Heatmap.
How fast do we respond to leads?
Source: Lead, Opportunity
Owner: Account Manager
SAMPLE DATA
Bid conversion by source and site type?
Source: Opportunity, Account
Owner: Account Manager
SAMPLE DATA
Bid-to-start time?
Source: Opportunity, Contract
Owner: Operations Manager
SAMPLE DATA
Pipeline value?
Source: Opportunity
Owner: Owner
SAMPLE DATA
Monthly recurring revenue?
Source: Contract, Invoice
Owner: Bookkeeper
SAMPLE DATA
Retention and churn by reason?
Source: Contract
Owner: Account Manager
SAMPLE DATA
Contracts expiring by month?
Source: Contract
Owner: Account Manager
SAMPLE DATA
Margin by post and account?
Source: Invoice, Shift
Owner: Owner
SAMPLE DATA
Scheduled vs. worked hours?
Source: Shift
Owner: Operations Manager
SAMPLE DATA
Overtime percentage?
Source: Shift, Timesheet
Owner: Operations Manager
SAMPLE DATA
Uncovered/late shift rate and time to fill?
Source: Shift, Coverage Request
Owner: Dispatcher
SAMPLE DATA
Patrol compliance rate?
Source: Patrol Tour
Owner: Supervisor
SAMPLE DATA
Supervisor audit scores?
Source: Audit
Owner: Supervisor
SAMPLE DATA
Incident counts by type/severity/post/time to escalate?
Source: Incident Report
Owner: Operations Manager
SAMPLE DATA
Report timeliness?
Source: DAR
Owner: Supervisor
SAMPLE DATA
Complaint rate and time to resolve?
Source: Complaint
Owner: Account Manager
SAMPLE DATA
Special coverage revenue?
Source: Client Request, Invoice
Owner: Bookkeeper
SAMPLE DATA
Receivables aging?
Source: Invoice
Owner: Bookkeeper
SAMPLE DATA
Rate adjustment acceptance?
Source: Rate Adjustment
Owner: Owner
SAMPLE DATA
Officer turnover and time to staff?
Source: Officer, Shift
Owner: HR
SAMPLE DATA
License/training/insurance expiry calendar?
Source: License, Training, COI
Owner: HR
SAMPLE DATA
Referral source performance?
Source: Lead, Referral
Owner: Account Manager
SAMPLE DATA
Bottleneck View
Post Health Heatmap (SAMPLE)
| Post | Cov | Audit | Inc | Margin | Pay |
|---|---|---|---|---|---|
| Distribution Center A (SAMPLE) | 98% | 4.6 | 1 | 37% | On time |
| Retail Plaza B (SAMPLE) | 94% | 4.2 | 2 | 33% | 7 days late |
| Construction Site C (SAMPLE) | 99% | 4.8 | 0 | 39% | On time |
| Office Tower D (SAMPLE) | 91% | 3.9 | 3 | 30% | 14 days late |
Data Architecture and Relationships
Interactive ER diagram with cardinality, a System-of-Record matrix, a data lifecycle panel, and a Common Mistakes panel.
Common Mistakes
- One company record for every site (instead of one account, many sites).
- Storing each shift as an opportunity (an opportunity is one bid/event/renewal, never a single shift).
- Post orders or alarm codes left in notes visible to all.
- License dates tracked on paper, not in the system with expiry blocks.
- Incident reports emailed with no record in the CRM.
- Officer schedules shared with people who do not need them.
Data Lifecycle
Creation → updates → archive → retention of incident, report, and training records for required periods → deletion on request where permitted. Legal Review
Implementation Status and Validation
Filterable checklist with progress summary by category and a progress ring per section. 'Verified' requires a completed 'Tested' record.
0 of 88 items Tested/Verified
All items default to Designed. Nothing is shown as live without a completed test record.
CSV export · Print view available
CRM Objects and Fields
0/5 · 0%- DesignedAccount & Site/Post objects
- DesignedContract object with rate fields
- DesignedShift & Coverage objects
- DesignedIncident Report object (restricted)
- DesignedEquipment & Asset custody
Tags and Smart Lists
0/3 · 0%- DesignedSource & site-type tags
- DesignedContracts expiring ≤120 days
- DesignedAt-risk accounts list
Pipelines and Stages (7)
0/7 · 0%- DesignedP1 New Business Bids stages
- DesignedP2 Contract Onboarding stages
- DesignedP3 Renewals stages
- DesignedP4 Events stages
- DesignedP5 Account Retention stages
- DesignedP6 Officer Recruiting stages
- DesignedP7 Referral Partners stages
Calendars and Booking Rules
0/2 · 0%- DesignedSite survey booking calendar
- DesignedShift schedule calendar (Mode A)
Forms
0/6 · 0%- DesignedRequest a Security Quote
- DesignedSite Risk Survey Booking
- DesignedEvent Staffing Request
- DesignedFire Watch Request (urgent)
- DesignedComplaint and Feedback
- DesignedOfficer Application
Workflows (W1–W24)
0/24 · 0%- DesignedW1
- DesignedW2
- DesignedW3
- DesignedW4
- DesignedW5
- DesignedW6
- DesignedW7
- DesignedW8
- DesignedW9
- DesignedW10
- DesignedW11
- DesignedW12
- DesignedW13
- DesignedW14
- DesignedW15
- DesignedW16
- DesignedW17
- DesignedW18
- DesignedW19
- DesignedW20
- DesignedW21
- DesignedW22
- DesignedW23
- DesignedW24
Message Templates and A2P registration
0/2 · 0%- DesignedApproved message templates
- Requires External IntegrationA2P 10DLC registration
AI Assistants & Knowledge Base
0/2 · 0%- DesignedServices, process, policies, FAQs knowledge base
- DesignedAI guardrails configured
Integrations
0/6 · 0%- Requires External IntegrationGuard management software (Mode B)
- Requires External IntegrationPayroll & HR
- Requires External IntegrationAccounting
- Requires External IntegrationCard processor & payment links
- Requires External IntegrationE-signature
- Requires External IntegrationInsurance certificate tracking
User Roles and Permissions
0/2 · 0%- DesignedPermissions matrix configured
- DesignedAudit trail enabled
Reports and Dashboards
0/4 · 0%- DesignedLead response time report
- DesignedMargin by post & account
- DesignedUncovered/late shift rate
- DesignedIncident counts by type/severity
Required Configuration
0/7 · 0%- DesignedBusiness hours & licensed areas
- DesignedRate tables, OT & holiday rules
- DesignedEscalation windows
- DesignedMargin targets
- DesignedContract & proposal templates
- DesignedTax settings
- DesignedBranding & policies
Testing Requirements
0/18 · 0%- DesignedQuote request to signed contract
- DesignedBid below margin target needing approval
- DesignedPost setup with unapproved post order
- DesignedCall-off with coverage engine fill
- DesignedCall-off with no eligible backup & escalation
- DesignedLate check-in & abandoned post alert
- DesignedMissed patrol checkpoint
- DesignedIncident at each severity level
- DesignedIncident report held for review before client delivery
- DesignedExpired license blocking armed post
- DesignedEquipment return with missing key
- DesignedTimesheet approval & payroll export
- DesignedInvoice with OT & holiday rates
- DesignedLate invoice & service review
- DesignedRenewal with competing bid
- DesignedOperations tool sync outage (Mode B)
- DesignedSMS opt-out
- DesignedPost order visible only to authorized roles
Go-Live Readiness Gates
Data model built; forms connected; A2P approved; bill/pay rate rules reviewed; contract/proposal templates reviewed by counsel; post order & access handling confirmed; incident escalation approved by owner & counsel; license/training blocks tested; operations tool sync tested (Mode B); invoicing tested; workflows tested; permissions reviewed; legal items cleared; backup & export confirmed.
Assumptions (Editable)
Every assumption shown here is editable and labeled SAMPLE DATA. Wage, prevailing wage, overtime, and tax treatment vary — Legal Review Needed.
Bill rate (unarmed post)
32 $/hr (SAMPLE)
Bill rate (armed post)
48 $/hr (SAMPLE)
Pay rate (unarmed)
20 $/hr (SAMPLE)
Pay rate (armed)
30 $/hr (SAMPLE)
Overtime multiplier
1.5 × (Legal Review Needed)
Holiday multiplier
2.0 × (Legal Review Needed)
Minimum shift hours
4 hrs (SAMPLE)
Alarm response time target
30 min (SAMPLE, not a guarantee)
Incident escalation window (elevated)
60 min (SAMPLE)
Patrol interval
60 min (SAMPLE)
Termination notice
30 days (Legal Review Needed)
Margin target
35 % (SAMPLE)
Version and Change Log
Version, date, what changed, and who changed it.
Add a Module (Template)
The fields a new module needs. Add an item to a data file and it appears in navigation, search, diagrams, and the checklist automatically — no layout code changes.
id
Stable unique id (kebab-case). Used in navigation, search, and links.
title
Display name shown on cards and the detail panel.
type
crm | external | human | ai | record | workflow | pipeline | role | report | integration | checklist.
status
Designed | Built | Configured | Connected | Tested | Verified | Requires External Integration | Requires Custom Development. Verified requires a completed Tested record.
sor
A | B | shared — which mode owns this data.
summary
One plain sentence of purpose.
whyItExists
Why this module exists (detail panel).
fields
Key fields with detail; mark restricted fields.
connected
Connected systems with arrow direction and data labels.
role
Responsible role.
steps
Workflow steps: label, actor, record, target time.
failureModes
Failure modes and fallbacks.
legalReview
True if jurisdiction-dependent (shows Legal Review marker).
safetyAlert
True if safety-critical (shows Safety Alert marker).