Dispatch prepares the service that the Departure Reviewer will consider. The review needs the current route, crew and seat capacity together with the booking context. The release action then retains an outcome that operations checks before relying on the decision for the intended service.
The Dispatcher creates the Draft departure under the correct booking and organization. Record the route, departure time, crew description and seat capacity. Compare the plan with the intended resource reservations and customer service window.
The Dispatcher checks the revision and moves the departure from Draft to Submitted. Make the relevant booking attachments available to the reviewer. Resolve changes made during preparation before presenting the plan as ready.
The Departure Reviewer independently checks crew and capacity against the current booking and departure. Record Approve, Reject or Return with a reason. An approved departure moves from Submitted to Approved; a rejection moves it to Rejected. A returned plan needs correction and fresh review under the agreed revision practice.
The Dispatcher and Operations Manager check the operation receipt for the release action. Match its expected revision and retained references to the intended plan. Investigate Failed or needs review outcomes before treating the handoff as ready for operation.
And how to keep it from happening.
Start free, then use Proto to change fields, steps and approvals before your team goes live.