The service outcome affects the customer conversation and the work finance must reconcile. Use the booking and departure together when confirming that the journey began and ended. Retain the supporting evidence so someone joining the case later can understand what happened.
The Dispatcher identifies the approved departure and relevant release receipt. Confirm the intended service with the Booking Coordinator. Resolve an uncertain release result before relying on it for the operating plan.
The Booking Coordinator moves the booking from confirmed to in progress when the service actually begins. A scheduled time is useful planning context; the team still records the observed operating state.
After the service, the Dispatcher marks the departure Completed and the Operations Manager confirms the booking's completion time and Completed state. For a cancellation or no-show, retain the actual booking outcome and its supporting explanation instead of completing an unoperated service.
The responsible team member attaches the service information with a clear title, evidence type and visibility. The Operations Manager checks unresolved operation receipts, identifies the action and expected revision, and follows the references before arranging another attempt or closing the investigation.
And how to keep it from happening.
Start free, then use Proto to change fields, steps and approvals before your team goes live.