> ## Documentation Index
> Fetch the complete documentation index at: https://docs.harbinge.rs/llms.txt
> Use this file to discover all available pages before exploring further.

# EC Inspection Rounds Overview

> Joint Commission Environment-of-Care inspection rounds on Forager's attestation loop — item types, standards, and the layered evidence model

EC Inspection Rounds turns Forager's attestation loop — barcode scan, photo, RF snapshot, tamper-evident audit trail — into a Joint Commission Environment-of-Care inspection program. Fire extinguishers, emergency lights, eyewash stations, AEDs, fire doors, and med gas outlets become tracked, licensed items with their own inspection cadence, checklists, and compliance reporting.

Every inspection is an attestation underneath: who performed it, where, when, with photo evidence and a raw RF snapshot, recorded append-only.

## Supported item types

Each item type ships with a Harbingers-authored core checklist tied to the governing standard:

| Item type                   | Standard                         | Default cadence     |
| --------------------------- | -------------------------------- | ------------------- |
| Fire extinguisher           | NFPA 10 §7.2 · EC.02.03.05 EP 15 | Monthly             |
| Emergency light / exit sign | NFPA 101                         | Monthly             |
| Eyewash station             | ANSI Z358.1                      | Weekly              |
| AED                         | Manufacturer / facility policy   | Monthly             |
| Fire door                   | NFPA 80                          | Annual              |
| Med gas outlet              | NFPA 99                          | Per facility policy |

Core checklists are immutable and versioned — every inspection records exactly which template version it was performed against, so a surveyor can see the checklist as it existed on the inspection date. Facilities can append their own questions on top of the core; see [Admin Guide — Template add-ons](/ec-rounds/admin-guide#template-add-on-editor).

## The layered evidence model

Evidence is layered, strongest-available first. Nothing in the evidence stack ever blocks an inspector from completing an inspection.

<Steps>
  <Step title="Attestation core — always">
    Barcode scan match, photo, inspector identity, and dual timestamps (device capture time and server sync time), written append-only. This is the floor of every inspection, calibrated or not.
  </Step>

  <Step title="RF corroboration — where calibrated">
    The RF snapshot is always captured raw. In rooms with a surveyed fingerprint, it is scored and presented as corroboration ("RF environment consistent with Room 214") — never as a pass/fail gate. As you calibrate more rooms, historical raw snapshots become re-scorable, so evidence strengthens retroactively.
  </Step>

  <Step title="Sequence plausibility — always, no calibration needed">
    On sync, the server computes two co-signals per inspector session: the time gap from the previous inspection (physically impossible gaps between distant items) and the RF-environment similarity between consecutive snapshots (a static radio environment across many "different rooms" is the signature of pencil-whipping).
  </Step>

  <Step title="Flagged for review — surface, don't block">
    Implausible values flag the inspection for a supervisor review queue in the dashboard. Thresholds start loose and are tuned server-side — flags are informational and never stop a round.
  </Step>
</Steps>

<Note>
  RF corroboration is optional at rollout. You can run your first rounds with attestation-core evidence only and add RF calibration later — the raw snapshots captured in the meantime gain scoring once calibration exists.
</Note>

## How rounds are organized

The primary experience is the **due queue**: every EC item carries its own inspection cadence, and items surface automatically as due or overdue, grouped by building and floor. No round setup is required.

Optionally, admins can create **explicit rounds** — a named scope (a building, a floor, one or more item kinds) with a time window and an assigned inspector — for facilities that want dispatch and progress tracking. Both models use the same execution flow in the app.

## Licensing

EC items are licensed per item on the **EC Item** license tier, separate from device licenses. License limits are enforced at CSV import — see the [Admin Guide](/ec-rounds/admin-guide#csv-import).

## Where to go next

<Card title="Admin Guide" icon="gear" href="/ec-rounds/admin-guide">
  Import items, print labels, manage templates and rounds, run the compliance dashboard, and export surveyor reports.
</Card>

<Card title="Inspector Guide" icon="mobile" href="/ec-rounds/inspector-guide">
  Run rounds from the Forager Android app — due queue, floor-plan routing, checklists, and full offline operation.
</Card>

<Card title="Onboarding Runbook" icon="rocket" href="/ec-rounds/onboarding">
  From floor plans to your first completed round in one walk.
</Card>