How to Manage Voyages

1. All Voyages

Purpose:

• To view and manage all voyages, across all statuses, in a single place. 

What’s displayed:

• Shows every voyage — whether it's Scheduled, Ongoing, or Completed. 

Common Actions:

• Edit voyage (if not started)
  
  

• View voyage details

Notes:

• Often used for bulk reviews, search, and tracking all scheduled operations.
  
  

2. Scheduled Voyages 

Purpose:

• To manage voyages that are planned but not yet started. 

Common Actions:

• Add or remove trip/delivery requests
  
  

• Assign a different vehicle or driver
  
  

• Cancel voyage before start
  
  

• View routes and coverage

Notes:

• This is the primary tab for preparing and finalizing voyage plans. 

3. Ongoing Voyages 

Purpose:

• To monitor voyages that are currently in progress. 

Key Features:

• Automatically updated when the driver starts the voyage via the mobile app. 

• Real-time visibility into: 

  1. Request status (picked/dropped)
     
     

  2. Driver actions (e.g., reporting breakdowns)
     
     

  3. Passenger presence
     
     

  4. Package verification

Common  Actions:

• View live status 

• Check on package and passenger progress 

Notes:

• Ideal for active monitoring and response during execution. 

4. Completed Voyages 

Purpose:

• To view voyages that have been finished and marked as complete by the driver. 

Key Features:

• Archived record of:  

  1. Route summary
     
     

  2. Packages delivered
     
     

  3. Passengers dropped
     
     

  4. Proof of delivery (image or signature)

Common  Actions:

• Review completed voyage data
  
  

• Verify uploaded proofs
  
  

• Audit trip performance or discrepancies

Notes:

• This tab is essential for reporting, compliance checks, and dispute resolution. 

5. Abandoned Voyages 

Purpose:

• To display voyages abandoned by the driver.

When is a voyage marked as abandoned? 

• A voyage is marked Abandoned only after it has been started by the driver via the mobile app.
  
  

• If the driver encounters a situation where the voyage cannot be completed (e.g., vehicle breakdown), they can submit an abandonment request from the app.
  
  

• The Transport Coordinator receives a notification and must review and either approve or decline the abandonment.
  
  

• If approved, the voyage is officially marked as Abandoned and shown under this tab.

Common  Actions:

• Review abandonment requests (pending review may appear under a prompt or alert)
  
  

• If already approved, view abandoned voyage details
  
  

• Reassign affected passenger or delivery requests to new voyages

Notes:

• Once abandoned, the voyage cannot be resumed.
  
  

• All passenger and package requests from that voyage return to an unallocated state.
  
  

• Employees and request owners are notified that their transport/delivery will be rescheduled.

6. Deleted Voyages 

Purpose:

• To display voyages abandoned by the driver.

Notes:

• Requests from a deleted voyage are automatically moved back to the unallocated pool.

• Notifications are sent to employees whose requests were affected.

  1. For example: “Your request was removed from Voyage ID: X and will be reassigned shortly.”

• This tab is useful for auditing and understanding which voyages were removed before execution.