PaxRelay Flow

Make the decision path after an operational change explicit.

Flow evaluates the event, passenger impact and operating rules to decide what should happen, what needs approval and where an exception belongs.

Map a workflow Platform overview

Rule evaluation

01Delay ≥ 30 min · YES
02Affected passengers > 0 · YES
03High-risk route · NO
04→ APPROVAL REQUIRED

From judgement to repeatable process

Your best disruption playbook should not live only in someone’s memory.

Flow makes thresholds, decisions and handoffs visible. Teams can define where automation is appropriate and where operational judgement must stay in the loop.

Conditions: Evaluate service, timing, location, passenger and operational context.
Approvals: Route selected actions to the right role before release.
Escalation: Raise exceptions when required data, timing or delivery conditions are not met.
Decision history: Record which rule ran and the outcome it produced.

Deterministic by design

The same inputs follow the same approved rule path.

Operational execution should be explainable. Flow is centered on configured rules and human control, not opaque decision-making.

1Match the event to a workflow
2Evaluate conditions in order
3Pause for approval where configured
4Record the action or exception

Automation remains bounded.

A workflow can be automatic, approval-based or manual. The mode is configured for that workflow and can change as an operation gains confidence.

Bring the checklist your team uses today.

We will turn one real disruption path into clear conditions, approvals, exceptions and outcomes.

Book a demo Contact us