Skip to Main Content
Vellox Group Ideas Portal
Status Gathering interest
Created by Kelsey Hoogendoorn
Created on Jun 21, 2026

Flag OCC with Manifest Changes

Problem

Once a manifest is approved, any change the pilot makes to it does not update the OCC. There is no flag and no notification, so the OCC has to manually open the manifest and notice the change on their own. Operationally significant pilot-side changes can sit unrecognized unless someone happens to look.

Context

The OCC is kept current today only when the comm center changes the route, whether through the CC dashboard or through the CAD. Those changes propagate to the OCC automatically and are already covered. There is no equivalent for pilot-initiated changes, which is the gap this idea targets.

Proposed solution

Flag the OCC whenever a pilot changes their manifest after approval, so a pilot-side change surfaces to the OCC instead of waiting to be discovered. Settings control which change types raise a flag (destination, passengers, fuel, and so on), so each operator decides what is worth flagging.

How it works

  • Detect changes a pilot makes to an approved manifest.

  • For the change types enabled in settings, raise a flag to the OCC.

  • The flag identifies what changed (old value vs new value), that it was a pilot change, and a timestamp, so the OCC gets context rather than a generic alert.

  • Give the OCC an acknowledge / clear action to mark the change as recognized once reviewed. This replaces today's manual step of going into the manifest and noticing the change on their own.

  • Scope to post-approval pilot changes. Comm center and CAD route changes continue to update the OCC as they do today and do not need a separate flag.

Configurable change types

  • Destination / arrival location change

  • Passenger updates (added, removed, or count change)

  • Fuel changes (fuel load or fuel plan)

  • Extensible to others as needed (weight, departure point, times, crew)

Value

  • The OCC learns about pilot-side changes without having to manually dig through manifests.

  • Supports operational control by making post-approval changes visible in something close to real time.

  • Configurable, so operators are flagged only on the changes that matter to them.

  • The acknowledge step leaves a clear record that the OCC saw and recognized the change.

  • Attach files