AIGIS
AIGIS Command · Incident accountability

Keep responder accountability connected to the incident.

Run immediate or scheduled PAR checks, review unit-reported personnel counts, maintain incident personnel and recorded shifts, and track ICS 214 expected-day completion from the browser-based AIGIS Command platform.

AIGIS Command · PAR checks and unit responses
Sanitized AIGIS Command PAR workspace showing an in-progress check with one responding unit, one pending unit, and a reported personnel count
Working AIGIS Command interface using deterministic fixture data. Names, callsigns, incident details, and response values are fictitious; no production responder records are pictured.

AIGIS Field

iOS and Android

Respond from the field

Receive and submit a PAR response for the active unit. Authorized responders can also request a check from the map.

AIGIS OPS

macOS and Windows

Maintain live operational context

Keep unit and PAR state beside the live map, missions, and other command-post work.

AIGIS Command

Browser

Run and review accountability

Start checks, review incident personnel and recorded shifts, and keep expected ICS 214 reporting visible.

PAR checks

See every PAR response and every missing one.

Send an immediate or scheduled PAR check to selected units. Command shows each reported personnel count and keeps unanswered requests visible.

  1. 01

    Select

    Choose the units in scope.

    Build the check around selected units in the active incident rather than a disconnected contact list.

  2. 02

    Run

    Send now or use a schedule.

    Start an immediate check or configure one-time or recurring daily timing for the selected units.

  3. 03

    Report

    The unit submits its count.

    A responder in Field enters the current personnel count associated with the active assigned unit.

  4. 04

    Review

    See reported and pending state.

    Inspect run progress and the integer personnel count reported by each responding callsign.

  5. 05

    Follow up

    Reissue a pending check.

    When authorized, create a new request for a unit that has not yet responded and keep the gap visible.

Representative roster using fictitious responder and unit data. The implemented workspace keeps role, assignment, shift, worked-time, and deployment state together.
Incident personnel and shifts

Keep the roster tied to the operational period.

Review who is recorded on the incident, the unit and response role assigned to them, and the shift periods that form their operational history.

Responder and incident assignment

Assigned unit or callsign

Recorded response role

On-shift or off-shift state

Last shift start and end

Recorded worked-time total

Preloaded, activated, demobilizing, or demob-complete state

Shift history with authorized start, end, manual, and edit actions

Shift durations reflect recorded operational intervals. They are designed for incident accountability and service history, not payroll or independent proof of physical presence.

ICS 214 status

See what is expected, submitted, and missing.

Keep daily ICS 214 record completeness in view for the selected incident without reconstructing the gap from separate spreadsheets and messages.

Expected report days

AIGIS derives expected dates from recorded operational periods and supported mission participation.

Completion and missing dates

Compare expected dates with submitted report dates to see completed versus expected counts, percentage, and remaining dates.

Submitted 214s

Review submitted ICS 214 documents linked to the selected incident and open the responder record for detail.

Human follow-through

Open an email reminder when a responder address is available; content review and approval remain with the organization.

Representative daily-status view using fictitious data. AIGIS calculates completion and missing dates from expected and submitted report dates; it does not certify report content or agency compliance.
Incident record

Accountability remains connected to the response.

PAR activity, incident participation, response roles, unit or callsign context, recorded shifts, and supported operational events remain part of the authorized incident record. Command service history is limited to recorded operational facts; evaluations and private personnel notes are not included.

Explore the service-history story
Record scope

What the accountability record shows.

AIGIS displays configured PAR, staffing, shift, and ICS 214 status. Your agency remains responsible for policy, report quality, approvals, and recordkeeping.

A reported count is not automatic verification

A PAR response records the integer personnel count submitted for the responder’s current assigned unit.

Request status does not confirm device receipt

A saved PAR request does not certify notification receipt; request-creation warnings are separate from confirmed device delivery.

Operational time is not payroll time

Worked duration is derived from recorded shift intervals, including an open shift that continues to accrue.

Record completeness does not establish compliance

ICS 214 status compares expected dates with submitted dates. It does not certify report quality, agency approval, or regulatory compliance.

See accountability with your incident structure.

Request access for PAR, incident personnel, shifts, and ICS 214 using your organization’s unit structure, reporting cadence, and authorized roles.