Skip to main content

Workflows

The Traveler Management Module ships a catalog of configurable operational workflows that drive how officers act on traveler records. Workflows run on top of Traveler Identity Service data, so any channel that triggers the same workflow gets consistent semantics, audit trail, and downstream effects on the traveler record.

This page is the integrator-facing capability catalog — what is supported, not how it is implemented. See the data model pages for entity and field details.

Capabilities​

  • Configurable lifecycle stages for traveler records, with server-enforced transitions
  • Adjudication workspace for identity conflicts surfaced by Traveler Identity Service
  • Border Post Review with four resolution actions (merge, split, keep separate, mark with reason)
  • Officer-raised flags with reason codes and a shared resolve queue
  • Full audit trail on every workflow decision

Traveler lifecycle​

Every traveler record moves through a lifecycle: it is created, becomes operationally active, may need to be resolved when evidence conflicts, and can be retired when no longer in use. Transitions are enforced server-side, and the officer UI only exposes actions valid for the current stage.

The lifecycle stages are referenced via the identityStatus field on the Traveler entity. The full set of stages and allowed transitions is part of the platform configuration delivered with your deployment.

Adjudication​

Adjudication is the operator triage workspace for identity conflicts that Traveler Identity Service cannot resolve automatically — likely duplicates, ambiguous biometric matches, or conflicting evidence on the same traveler. Conflicts are staged into a review queue; an authorized operator (the adjudicator) opens each entry, reviews the supporting context, and commits an audit-logged resolution that is reflected back into the matching backend.

Border Post Review​

Border Post Review is the resolution mechanism for identity incidents raised at a border post — suspected duplicate travelers, conflicting evidence on a single record, document-holder mismatches, or evidence flagged as suspicious during enrollment, journey processing, or field identification. Each case is staged for an authorized operator, who applies one of four resolution actions:

  • Merge travelers — consolidate records that represent the same real person.
  • Split travelers — separate evidence that belongs to more than one real person.
  • Keep separate — confirm that flagged records actually belong to different people; close the case so the conflict does not re-surface.
  • Mark traveler with a reason — tag the record with a documented business outcome when none of the above fits. The reason vocabulary is part of platform configuration.

Every resolution is audit-logged against the affected records.

Flag traveler​

Officers can raise flags on a traveler record outside of an automatically generated review case — for example, suspicious behavior, data inconsistencies, or a note for a colleague. Flags carry a reason code and an optional free-text note, surface in the shared resolve queue, and can be cleared as part of a review resolution or independently. The action is audit-logged.

See also​