Arcova Docs

Operations

Operations

Operations helps you coordinate dispatch, document incidents, and run patrol routes — preserving a complete edit history of dispatch and incident activity. Locked records and edit logs are audit-ready, not legal advice on admissibility or chain-of-custody.

Last updated February 2026

Overview

When to Use This

  • You coordinate live events and officer response in real time.
  • You need incident reports with evidence and review states.
  • You need checkpoint-based patrol workflows with accountability.

Model

Core Concepts

Operations uses the following objects and relationships as its operating model.

Dispatch Case

Live operational event assigned to units or officers.

Persisted Data
Priority, location, timeline updates, responders.
State Changes
Open, dispatched, acknowledged, closed.

Incident Report

Formal record tied to dispatch case or standalone event.

Persisted Data
Narrative, severity, involved parties, evidence links.
State Changes
Draft, submitted, reviewed, locked.

Patrol Route

Template route with ordered checkpoints.

Persisted Data
Checkpoint list, expected duration, task rules.
State Changes
Active or archived.

Patrol Run

Execution instance of a route by an officer.

Persisted Data
Checkpoint timestamps, deviations, completion score.
State Changes
Started, paused, completed, aborted.

Role Requirements

  • Dispatch roles can open and route active cases.
  • Supervisors review and lock incident reports.
  • Officers execute patrol runs and submit field updates.

Side Effects

  • Critical incidents can escalate to compliance or legal hold workflows.
  • Dispatch closure updates response metrics and SLA dashboards.
  • Locked reports prevent further edits except approved amendments.

Notifications

  • Dispatch assignments notify responders immediately.
  • Incident review queues notify assigned supervisors.
  • Missed checkpoint alerts notify patrol supervisors.

Automation Hooks

  • Priority rules can auto-escalate unacknowledged dispatches.
  • Patrol deviations trigger exception flags.
  • Severe incidents can create follow-up tasks automatically.

Flow

How It Works

  1. 1

    Create dispatch case or patrol assignment from the operations board.

  2. 2

    Assign responders and track timeline updates in real time.

  3. 3

    Capture incident data and evidence during or after response.

  4. 4

    Run supervisor review and lock final report state.

  5. 5

    Expose approved records to client and audit consumers.

Walkthrough

Example

Scenario

Dispatch receives an unauthorized entry alert at Site 22.

Walkthrough

  1. 1

    Dispatcher opens high-priority case with geotagged location.

  2. 2

    Nearest patrol unit is assigned and acknowledges in mobile app.

  3. 3

    Officer resolves scene and submits incident report with photos.

  4. 4

    Supervisor reviews narrative, adds legal hold flag, and locks report.

  5. 5

    Client receives finalized summary through portal.

Outcome

Response, reporting, and retention are tied into one traceable record.

Watch Out

Edge Cases / Gotchas

  • Editing locked reports requires explicit amendment permission.
  • Timezone mismatches can distort SLA dashboards if site timezone is wrong.
  • Patrol runs with skipped checkpoints still close unless strict mode is enabled.
  • Evidence redaction policy applies before external portal visibility.