1. Bus / Coach Management
  2. Features
  3. Departure planning
Feature · Departure planning

Departure planning

Prepare the route, departure time, crew description and seat capacity for an independent decision.

OverviewDepartures to prepare
Bus / Coach Management · Departure planning

Departures to prepare

Approval conditions

New
ParentRouteDeparts atSeat capacityCrewOrganization
BKN-93088RTE-16706 Oct630CRW-989ORG-9662
BKN-41602RTE-35206 Oct850CRW-178ORG-1518
BKN-82660RTE-41321 Oct190CRW-896ORG-6837
BKN-83096RTE-66113 Oct650CRW-806ORG-8309
BKN-68545RTE-99011 Oct430CRW-120ORG-6379
6 of 6 records
RTE-167Route departures · RD-73871
Draft
ParentBKN-93088
Departs at06 Oct
Seat capacity630
CrewCRW-989
OrganizationORG-9662
Example screen with sample data

What you can do

Put the intended departure in front of the reviewer

The Dispatcher prepares a departure under the booking it serves. The route describes the planned service, and the departure time establishes when it is intended to begin. Crew information and seat capacity give the reviewer the operating details needed to consider release.

The departure begins as Draft while dispatch prepares the plan. Submission places the current revision in the review queue. The booking remains the shared context for the customer request, resource reservations and supporting files, so the reviewer can examine the departure as part of the actual service arrangement.

How the work is organized

  • Booking context. Link the departure to the correct booking and carrier organization before preparing the route. Check the customer subject and service window so an apparently similar departure is not attached to the wrong request.
  • Operating details. Record the route, departure time, crew description and seat capacity in a form the reviewer can understand. Compare these details with the intended resource arrangements and resolve discrepancies with the Dispatcher responsible for them.
  • Submission state. Keep the departure Draft while essential planning details are being settled. Submit the intended revision for review once the operating plan is ready. Later changes need a clear review path so an earlier decision is not mistaken for approval of a different plan.

What to agree during setup

Agree how routes and crew descriptions are written. Use wording that distinguishes services with similar names or departure times. Confirm the organization and team time zones and decide how the team records departures that cross a date boundary. Identify who checks the crew description and seat capacity before submission.

Define the handoff between the Booking Coordinator and Dispatcher when the customer changes the service window. Decide who revisits the resource reservations and what supporting information the reviewer should read. Explain how a rejected or returned plan is corrected and submitted for a fresh decision under the agreed revision practice.

Check the handoff on an actual case

A scheduled service has a confirmed booking and intended resource arrangements. The Dispatcher prepares the route description, departure time, crew and seat capacity. Compare the departure with the booking window and the resource lines, then submit it for review.

The Departure Reviewer should be able to open the submitted plan, identify the booking and understand who is intended to operate the service. If the crew description is unclear, resolve it with dispatch before recording the release decision. The team should know which revision is being considered throughout that conversation.

Repeat the case after a coach substitution. Update the capacity and crew description where the substitution affects them, and check the booking’s resource lines. Preserve the connection between the revised plan and the information presented for review. Finally, rehearse an evening departure where the organization and a team member use different time zones, confirming that both people understand the intended operating time.

What your team sees

  • Departures to prepare — Draft departures with the route, crew, capacity and revision still being prepared.
  • Departure review — Submitted departures awaiting an independent readiness decision.
  • Approved departures — Approved plans that dispatch checks before beginning the service.

What it keeps track of

Data model
Route departures
Staffed coach departure extensions requiring review and release
Bookings
Charter and scheduled booking records with reserved resources
Booking resources
Reserved capacity lines attached to a booking
Resources
Coaches, drivers and partner operators allocated to bookings
Organizations
Carrier organizations operating the coach network
Team members
Authenticated platform identities attached to an organization

Who uses it

Permissions
Dispatcher
, Booking Coordinator, Departure Reviewer.
Dispatch owns the plan, the coordinator supplies the customer context and the reviewer decides on the submitted departure.

Set up Bus / Coach Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started