Load Lifecycle
Every load moves through a series of statuses that reflect its real-world progress. Understanding this lifecycle is key to managing the loading board effectively.
Status Flow
Building → Ready → In Flight → Landed → Finalized
Building
The load has been created and is accepting passengers. This is the default status for new loads. Passengers can be freely added, removed, or moved between loads, and removing a passenger never incurs a cancellation fee.
Ready
The roster is locked: removing a passenger now incurs a cancellation fee (unless waived), and passengers can no longer be returned to the jump queue. A load is marked ready once staff consider it settled, whether or not a departure time has been set yet. A load can be moved back to Building at any time.
In Flight
The aircraft has taken off. The departure time is confirmed when marking a load as departed. While in flight, the load is visible on the board as airborne.
Landed
The aircraft has returned. A flight time (in minutes) is recorded when marking a load as landed. This records how long the aircraft was in the air.
Finalized
The load is complete. Finalization is a critical step that:
- Locks the load — No further changes can be made to passengers, crew, or details.
- Processes payments — Charges are applied to passenger accounts based on their jump tickets and line items.
- Records revenue — Financial transactions are created in the ledger.
- Consumes credits — Any credits used to pay for jumps are consumed.
Finalization cannot be undone. Make sure all passenger details, pricing, and line items are correct before finalizing.
A load cannot be finalized if:
- Flight time has not been recorded (the load must have landed first).
- A passenger does not have enough funds in their account.
- A credit used for payment has expired or already been consumed.
Departure Time and On Hold
A load's departure time is independent of its status — it can be set, changed, or cleared while the load is either Building or Ready. There's no separate "on hold" status: a load is simply considered on hold whenever it has no departure time set, regardless of whether its roster is still open (Building) or already locked (Ready).
Putting a load on hold (clearing its departure time) is useful when waiting for weather, maintenance, or other delays — it doesn't change whether the roster is locked, and a load can be given a new departure time at any point to bring it off hold.