Arcova Docs

Operations guide

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

Quick answer

Use this guide to understand operations, prepare the right records, and complete the workflow in 5 clear steps.

Start here

What this guide helps you do

  • 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.

Access

Before you start

What you can view or change depends on your Arcova role. If a button or page in this guide is missing, ask an account administrator to check your access.

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

Know the pieces

What Arcova keeps track of

These are the records you will see in this area. You do not need to memorize them—use this list when a field or status is unfamiliar.

Dispatch Case

Live operational event assigned to units or officers.

Information you will see
Priority, location, timeline updates, responders.
Statuses it can move through
Open, dispatched, acknowledged, closed.

Incident Report

Formal record tied to dispatch case or standalone event.

Information you will see
Narrative, severity, involved parties, evidence links.
Statuses it can move through
Draft, submitted, reviewed, locked.

Patrol Route

Template route with ordered checkpoints.

Information you will see
Checkpoint list, expected duration, task rules.
Statuses it can move through
Active or archived.

Patrol Run

Execution instance of a route by an officer.

Information you will see
Checkpoint timestamps, deviations, completion score.
Statuses it can move through
Started, paused, completed, aborted.

Step by step

Follow the workflow

  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.

Arcova in the background

What happens automatically

Arcova may update connected records, notify the right people, or check rules while you work.

Updates after a change

Other records that may change when you save or approve work.

  • 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.

Who gets notified

Messages Arcova may send during this workflow.

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

Checks Arcova performs

Rules and safeguards that may run before an action is completed.

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

See it in context

A practical example

Situation

Dispatch receives an unauthorized entry alert at Site 22.

  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.

Expected result

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

Avoid rework

Common problems to check

  • 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.

Could not find the answer?

Tell support what you were doing and where you got stuck.

Contact support