Business & sites
Define the payer, operating owner, protected activity, sites, zones, and timing.
- Operating objective
- Sites and critical zones
- Hours and business constraints
Protection project intakeOwner: Customer or enterprise protection ownerNext:Open Managed Protection Operations and save the first governed project versionready
What this surface is for
Prepare the site, asset, threat, operating, authority, and commercial context required for a full protection engagement.
Connected so far
Risk design, guarding, monitoring, response, provider mobilization, assurance, and continuing operations.
Current owner
Customer or enterprise protection owner
Next controlled action
Open Managed Protection Operations and save the first governed project version
Governed project entry
Prepare the protection operations brief
Start with what the organization protects and how the operation must work. The governed Managed Protection Operations intake then creates one versioned brief for risk design, guarding, monitoring, response, providers, mobilization, and assurance.
This page prepares; the governed form saves
Nothing typed or reviewed on this reference page is stored. The next link opens the authenticated service intake where drafts, project versions, ownership, evidence, and submission are recorded.
Governed route: /projects/new/pro-ops-001
Before you begin
Evidence readiness
Unknowns are allowed. Mark them as unknown in the governed intake so an expert can request the right evidence rather than assume it exists.
Protected operation
Customer-owned facts
People, assets, sites, hours, critical services
Threat & incident context
Can begin incomplete
Unknowns remain evidence gaps
Existing controls
Inventory required
Guarding, CCTV, access, alarms, response
Decision authority
Named in project
Scope, commercial, operational, acceptance
Intake structure
What the project record will connect
These are business and operating sections, not a technical questionnaire disguised as a checkout form.
Risk & controls
Record known threats, incidents, assets, vulnerabilities, and existing controls.
- Protected assets
- Known incident patterns
- Current control inventory
People & response
Describe posts, patrols, monitoring, response partners, authority, and handoffs.
- Required posts and patrols
- Alarm/incident escalation
- Emergency and responder contacts
Evidence & commercial
Attach available records and set the budget, SLA, procurement, and acceptance boundary.
- Drawings and policies
- Budget and timing
- Acceptance and assurance needs
After the first save
No approval shortcut
Saving a draft creates a resumable customer record. Submission begins review; it does not approve design, price, provider, commissioning, or live operation.
- 1Draft briefCustomer
Evidence: Versioned project scope and known evidence gaps
- 2Readiness reviewPlatform + admin
Evidence: Completeness checks and explicit return reasons
- 3Protection designVerified expert
Evidence: Risk, coverage, guarding, systems, response, assumptions
- 4Customer correctionCustomer
Evidence: Missing facts, decisions, revised scope, acceptance criteria
- 5Commercial agreementCustomer + payer
Evidence: Price, SLA, responsibilities, provider process
- 6Mobilization gateProvider + reviewer
Evidence: People, systems, training, tests, unresolved warnings
Consequential decisions remain separateThe intake cannot award a guarding provider, publish a roster, activate monitoring, dispatch a response, accept commissioning, or assert that a site is safe. Those actions require their own reviewed evidence and named authority.
Ready to create the real project?
You can save a draft and return. Missing evidence stays visible and is resolved through customer–expert corrections.