These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Bus / Coach Management
- Features
- Departure review
Departure review
Record an independent release decision and inspect the outcome of the attempted action.
OverviewDeparture review×
Bus / Coach Management · Departure review
New
Departure review
Approval conditions
| Parent | Route | Departs at | Seat capacity | Crew | Organization | |
|---|---|---|---|---|---|---|
| BKN-31889 | RTE-364 | 25 Oct | 340 | CRW-160 | ORG-7231 | |
| BKN-28185 | RTE-726 | 05 Oct | 270 | CRW-875 | ORG-5235 | |
| BKN-19304 | RTE-148 | 07 Oct | 650 | CRW-751 | ORG-8034 | |
| BKN-65869 | RTE-103 | 27 Oct | 450 | CRW-276 | ORG-6430 | |
| BKN-44774 | RTE-535 | 20 Oct | 330 | CRW-619 | ORG-1081 |
6 of 6 records
RTE-364Route departures · RD-39650
SubmittedParentBKN-31889
Departs at25 Oct
Seat capacity340
CrewCRW-160
OrganizationORG-7231
What you can do
Decide on the departure that is actually prepared
The Departure Reviewer considers the submitted departure alongside its booking context. Crew and seat capacity are central to the release review. The reviewer also needs to know which current plan is being considered, especially after a change to the booking window or reserved resource.
The decision records the reviewer, reason and source revision against the booking. The release action has an operation receipt that retains its expected revision and outcome. These records let the team distinguish the human decision from the result of attempting to carry out the action.
How the work is organized
- Independent review. The reviewer checks the submitted plan prepared by dispatch. Confirm the booking, carrier organization, route and intended crew before deciding. Keep the reason understandable to the Dispatcher who must act on it.
- Recorded decision. Approve, Reject and Return describe the reviewer’s decision. The departure’s own status records whether it is Submitted, Approved or Rejected. A returned plan needs correction and another review through the agreed revision practice.
- Execution evidence. The operation receipt records the action, expected revision and result. Completed, Failed and needs review outcomes require different follow-up. Read the failure reason and effect references before deciding whether an action needs investigation or another attempt.
What to agree during setup
Name the people who may act as Departure Reviewer and establish their independence from the person preparing the booking and departure. Agree what crew information and capacity evidence they need. Define what should happen when the reviewer finds an unclear plan or a change made after submission.
Rehearse how the booking revision, departure revision and action receipt are checked together. Decide who investigates a Failed or needs review outcome and who can authorize a fresh operating attempt. Keep the decision and its execution result available to the Dispatcher before the service begins.
Check the handoff on an actual case
The Dispatcher submits a staffed departure with its booking and resource arrangement ready. The Departure Reviewer checks the crew description and seat capacity, then records the decision and reason. Inspect the resulting operation receipt and identify the action and revision it concerns.
Next, use a departure with an unresolved crew assignment. The reviewer should reject or return the plan with an explanation the Dispatcher can act on. Correct the plan through the agreed revision practice and present the updated information for a fresh review. An earlier reason remains part of the booking’s decision history.
Finally, rehearse an action that reports Failed or needs review. Have the Operations Manager follow the receipt to the booking and read the recorded failure reason. Check any effect references before repeating the action so the team understands what already happened. The handoff is ready only when dispatch can identify the reviewed plan and the outcome relevant to the intended service.
What your team sees
- Departure review — Submitted plans with crew, capacity and revision ready for the reviewer’s decision.
- Approved departures — Plans whose approved state and decision time can be checked before operation.
- Operations needing review — Release actions with a failed or unresolved result that needs investigation.
Follow the work through
Rehearse departure review and release and the evidence checks in service completion.
What it keeps track of
Data model- Route departures
- Staffed coach departure extensions requiring review and release
- Review decisions
- Independent review decisions recorded against a booking revision
- Operation receipts
- Durable receipts for executed operations and their results
- Bookings
- Charter and scheduled booking records with reserved resources
- Team members
- Authenticated platform identities attached to an organization
- Booking resources
- Reserved capacity lines attached to a booking
Who uses it
Permissions- Departure Reviewer
- , Dispatcher, Operations Manager.
- The reviewer owns the decision, dispatch prepares the plan and the manager coordinates unresolved operating outcomes.
Set up Bus / Coach Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.