One operational memory from the Guard’s first observation to management review.
The connected incident, awareness, notes and case layer inside PatrolFlow.
Does this match your operation?
Every PatrolFlow organization that needs incident reporting and site awareness, with deeper entity, case and multi-site Intelligence capability available only to authorized roles. Nexus is included as a connected platform layer where the assigned plan enables it rather than sold as an unrelated standalone portal.
The important capabilities.
One canonical incident/event record
Guard and Dispatch submissions flow into Nexus automatically. Nexus does not create a second copy of the incident simply to make it visible elsewhere.
Controlled Awareness Feed
Managers can publish a curated awareness version to a site, organization or named users without exposing confidential source fields or private case notes.
Structured entity profiles
Create factual person, vehicle, location, organization and asset profiles linked back to the incidents or events where the information originated.
Case workspace
Bring source incidents, dispatch events, evidence references, notes, tasks and disclosure activity into one case file.
Append-only review notes
Authorized users can comment on records they are allowed to see without editing the original submission. Note visibility is itself permission-controlled.
Guard visibility policy
Organizations can keep Guards at own-submissions-only, assigned-site awareness, site-history or organization-awareness levels, with narrower site/user overrides.
Acknowledgement tracking
Important awareness items can require acknowledgement so management can see who reviewed the information before or during an assignment.
Submission certification
New Guard incident reports and dispatcher-created operational events record an accuracy-to-best-of-knowledge attestation.
Cross-site link analysis
Where the customer permits it, profiles can connect recurring activity across multiple sites within the same organization.
Opt-in Trust Network
Network correlation is off by default and separately governed. Source records stay in their originating tenant; authorized analysts review only permitted correlation candidates.
No facial recognition by default
The current correlation layer uses human-entered descriptors and identifiers, not automated biometric face matching.
Controlled disclosure
Voluntary law-enforcement disclosure follows the source customer’s policy and approval workflow. Lawful-authority/emergency requests are documented separately and do not rely on a customer setting to create or defeat legal authority.
White-label client copies
Eligible security-company customers can brand client-facing generated copies while PatrolFlow retains canonical IDs, provenance and audit history internally.
From first action to completed record.
Incident/event is submitted with attestation
Authorized team links relevant profiles and evidence
Potential patterns are surfaced for human review
Related records are organized into a case
Follow-up and any permitted disclosure remain audited
Same customer, sites and records as the rest of PatrolFlow.
Built as an extension of the operational record rather than a separate notebook or spreadsheet.
Tenant boundaries and client policy controls are part of the workflow.
Pattern suggestions remain reviewable hypotheses—not automatic accusations.
The same intelligence layer supports customer-run Command and PatrolFlow Managed Command & Dispatch.
What customers usually want to know before a demo.
Can PatrolFlow work with our existing Guards and sites?
Yes. PatrolFlow is designed around the customer’s organization, approved team, sites and operating procedures rather than requiring a new Guard workforce.
Do we have to buy every PatrolFlow capability at once?
No. An organization can start with the workflow it needs most and add connected capabilities later without recreating the same customer, site and shift records.
Will Guards or dispatch staff need administrator access to the website?
No. Guards, Dispatch staff, Operations users and Managed Dispatch centre staff use role-specific PatrolFlow workspaces. Website administration stays with PatrolFlow's platform administrators.
Can this connect with PatrolFlow Managed Dispatch?
Where the workflow is applicable, Managed Dispatch can operate the connected Command and coordination layer while the customer keeps control of its own Guards, contracts and procedures.
Want to see PatrolFlow Nexus with your real workflow?
Bring one real example of how you run security today. We’ll show you the simplest package or Managed Dispatch scope around it.