Arcova Docs

Compliance

Compliance

Compliance helps you keep officer credentials current, prevent unqualified assignments, and document any exceptions you authorize. Arcova helps you track credentials and document exceptions; recording an exception does not make non-compliant work legally compliant. Consult counsel before authorizing exceptions.

Last updated February 2026

Overview

When to Use This

  • You need to prevent unqualified officers from working regulated posts.
  • You need expiration alerts and renewal workflows.
  • You need documented waivers for temporary exceptions.

Model

Core Concepts

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

Credential Type

Template used by employee credentials and post requirements.

Persisted Data
Name, renewal interval, grace rules, verification requirement.
State Changes
Active or retired.

Employee Credential

Belongs to an officer and references a credential type.

Persisted Data
Issue date, expiry date, document references, verifier.
State Changes
Valid, expiring, expired, revoked.

Requirement Rule

Applied to post, site, or contract context.

Persisted Data
Required credential list and enforcement mode.
State Changes
Draft or active.

Exception

Temporary override tied to an officer and requirement.

Persisted Data
Reason, approver, validity window.
State Changes
Requested, approved, expired, revoked.

Role Requirements

  • Compliance managers define credential types and requirements.
  • Supervisors can submit or approve exceptions based on permission scope.
  • Schedulers see enforcement output but cannot override blocked assignments without exception rights.

Side Effects

  • Requirement updates immediately affect future assignment eligibility.
  • Credential status changes update compliance dashboards.
  • Exception actions generate immutable audit events.

Notifications

  • Officers receive renewal reminders before expiration.
  • Supervisors receive pending exception approvals.
  • Managers receive daily summaries of expired credentials.

Automation Hooks

  • Assignment checks query current credential status in real time.
  • Expiration jobs recalculate risk buckets and alert windows.
  • Revoked credentials invalidate dependent assignment eligibility.

Flow

How It Works

  1. 1

    Define credential types and attach required evidence rules.

  2. 2

    Assign requirement sets to posts, contracts, or sites.

  3. 3

    Upload or verify employee credentials with dates and documents.

  4. 4

    Run assignment checks during scheduling and claim workflows.

  5. 5

    Process exceptions when temporary overrides are approved.

Walkthrough

Example

Scenario

A courthouse post requires active armed guard license and CPR certification.

Walkthrough

  1. 1

    Compliance manager creates both requirement rules in block mode.

  2. 2

    Scheduler attempts to assign an officer with expired CPR.

  3. 3

    Assignment is held back and a renewal task is created.

  4. 4

    Supervisor grants a 24-hour exception with justification during active renewal.

  5. 5

    System auto-expires the exception and re-enforces standard rules.

Outcome

Coverage stays compliant with a clear record of temporary risk acceptance.

Watch Out

Edge Cases / Gotchas

  • Warn mode still permits scheduling and can hide policy drift if overused.
  • Backdated credential edits can reopen prior compliance findings.
  • Expired exceptions do not retroactively invalidate completed shifts.
  • Multi-tenant boundaries prevent sharing credential records across companies.