Tours - Drivers Portal

Use Sidebar LHS to navigate
For global help click here

Tours - Drivers Portal

Table of Contents

Overview



This document covers the Tour Drivers Portal and the activities done by the driver in the portal.



Driver logs in

Username and password gets you to the dashboard

NEW: Warning about license expiry to be added here and a driver is forced to acknowledge date of impending expiry - driver needs to press button - tickbox have read it, button to confirm have read (need 2 actions). Messaging acknowledgment already exists.

Drivers can view the roster of all drivers

Driver confirms they are driving next day

If the driver does not confirm the day before - they will not be able to view their manifest on the day of travel.

Driver does pre-start checks

NEW: Need a checklist of things to check off (list of items) - selection of possible items with scoring (-ve, zero or +ve), text, images. When problem identified - need to define actions. Need to show all checklists done by asset on the asset.

  1. cannot drive (need to change buses) - alert fleet manager and service manager and forced to change vehicles

  2. can drive fix tonight (alert to repairer to schedule work) - alert to fleet manager and service manager - mechanic to schedule work

  3. fix next repair - show on next repair - shows next time service required

Checklist to be linked to asset types

Need browser to confirm (1) Browser allows location (2) location at time of check - if not possible then checklist question result of not allowing location services is alerted to fleet manager



Driver reports Vehicle issues (anytime)

NEW: browser needs to record the driver app location on save

It will be shown against the Vehicle

Before the vehicle check is completed - you can change vehicles

Vehicle changes are not done by the drivers app - but is done by Fleet manager. Vehicle check will be done again.

If you do not have a run - you can replace an existing driver

Todays Run

Driver views the manifest

Manifest is not visible until the driver has done the prestart checks

Driver picks up passengers

  • Booking moves to on board

Driver takes payments - credit cards / cash for the booking or payment for lunches.

Note - the $ amount is now editable in case the system calculated value is not correct.  The number of lunches created is directly related to the booking number of passengers

When the Driver sells additional lunches the system finds the number of Adults and Children on the booking - takes payment.  The lunch count for the run is updated - so later it appears on the supplier reconciliation.  

Driver sends lunch order to venue

The email template is then sent to the restaurant

  • The email is sent to the list of contacts on the Company Card of type "Email address for lunch/meal orders"

The Return Manifest

Shows the passengers to be taken back and their destinations.  Mark them off as they alight.

The Roster View

Allows a view of other drivers on the same roster as you

Back to Vehicle Tours



For information about SaaSplications go to http://saasplications.com.au