Why it matters
Without this, gaps in coverage, expired licences, incomplete threat data, and missing duty logs can lead to security lapses, non-compliance, and unsafe client experiences across residences, events, and travel.
From design to safety
Design
AI-enabled service design for protection
Design defines data governance with the SIA Licence Registry, CP roster schemas, and threat feeds; it selects risk models, SLA flows, and assignment brief templates; it maps data ownership across CP, compliance, and client services.
- Close Protection Officer Roster
- SIA Licence Registry
- Assignment Brief Template
Build
Integration and onboarding of protection data
Build imports licences, risk profiles, and client constraints; it sets secure data channels, creates onboarding playbooks for CPs, and aligns duty log templates with governance controls.
- Threat Assessment Matrix
- Duty Log Ledger
Operation
Ongoing protection coordination and logging
Operation continuously matches CP deployment with real-time licence status, threat signals, and assignment briefs; it records actions and distributes actionable intelligence to teams; it preserves a complete audit trail across incidents.
- Close Protection Officer Roster
- SIA Licence Registry
- Threat Assessment Matrix
Maintenance
Data integrity and compliance checks
Maintenance performs licence verifications, updates CP rosters, refreshes threat models, audits duty logs, and archives incident reports and corrective actions for governance and training.
- SIA Licence Registry
- Threat Assessment Matrix
- Duty Log Ledger
Safety
Duty of care and regulatory protection
Safety ensures client privacy, licence compliance, and incident transparency; it signs off on risk assessments and ensures duty of care records meet regulatory standards and client expectations.
- Assignment Brief Template
- Secure Incident Report File
Part by part
- 1
Close Protection Officer Roster
- Watch for
- Officer gaps, unverified CPOs, shifts overlapping or missing sign-offs.
- AI action
- Flag coverage gaps and alert head of security for reallocation.
- 2
SIA Licence Registry
- Watch for
- Licence expiry near, status mismatch, or unapproved licensing.
- AI action
- Trigger licence renewal workflow and validate CP status in real time.
- 3
Assignment Brief Template
- Watch for
- Incomplete risk profile, missing client constraints, or absent security requirements.
- AI action
- Prompt completion and route to risk lead for approval.
- 4
Threat Assessment Matrix
- Watch for
- New indicators or outdated risk levels.
- AI action
- Auto-adjust risk level and notify CP team and client service director.
- 5
Duty Log Ledger
- Watch for
- Missing entries, inconsistent timestamps, or unverified actions.
- AI action
- Flag gaps and initiate compliance review with duty of care owner.
- 6
Secure Incident Report File
- Watch for
- Unsecured or incomplete incident records.
- AI action
- Encrypt and file incident data; notify governance for audit trail.
Worked example
Catching a threat signal before a charter
Illustrative scenario with sample data.
A sudden threat indicator appears during a high‑profile trip; the system correlates CP roster status, licence validity, and threat feed to trigger a proactive response.
Signal in
CP_export: client_id=987; trip_id=TX-204; date=2026-11-04; location=London; CPs=[A, B]; licences=[L1=valid, L2=expiring 2026-12-12]; threat sources=[T1=unverified intel]; assignment_brief={risk=high, client_prefs=private, weapons=no}; duty_logs=[log_2026-11-04_08:00:00, log_2026-11-04_08:15:00]
System out
Alert raised to Security Lead; CP roster adjusted; licence L2 flagged for immediate renewal; threat assessment upgraded to high; new assignment brief issued to CPs with updated controls; duty log entries appended.
Human sign-off: Head of Security reviews the alert, validates threat source credibility, confirms licence renewal actions, and approves revised assignment brief for the trip.
How to roll it out
Phase 1
Weeks 1 to 2
Baseline data integration; establish CP roster, licence registry, and threat feed connections.
Phase 2
Weeks 3 to 6
Automate risk scoring, implement duty log templates, and test incident reporting workflow.
Phase 3
Weeks 7 to 10
Audit, governance sign-offs, and operator training across all devices and modules.
Where people stay in charge
- Decisions on licence renewals and threat risk level must be signed off by the Chief Security Officer or delegate.
- Duty of care and privacy decisions stay with the client service director or principal; audits ensure accountability.
- Data handling and access controls must be enforced by the Data Protection Officer and comply with GDPR and PCI DSS.
Questions owners and crews ask
What data sources feed the SIA licence checks for CP teams?
The system ingests licence registry databases, regulatory status feeds, CP assignment databases, and identity verification records to validate ongoing eligibility.
How does the system handle conflicts between licence status and CP deployment?
It flags the conflict and routes to the Security Lead for immediate review and assignment renegotiation with client teams.
What happens when a threat alert is generated during an assignment?
The threat assessment matrix updates risk levels, and the assignment brief is revised; operations coordinate CPs and communicate with the client service director.
How are duty logs protected and audited?
Duty logs are encrypted, timestamped, and stored in a secure incident report file with access limited to governance and compliance roles.