Data in Springboard Delivery are owned by organisations, which have one or more user accounts.  Data inside an organisation are private - other organisations have no visibility of them.

In an organisation, a user can belong to one of these levels:

  • Admin - Access to all functionality.
  • Planner - Access to most functionality except for user management and organisation settings.
  • User - Typically used for drivers, with no access to Springboard Delivery Hub.

The main purpose of Springboard Delivery is to manage orders, records of customer deliveries or collections.  When organised into routes, each order is assigned a stop number - the planned position of each order within the route.

There are a number of ways Springboard Delivery can be used.  The three examples below demonstrate increasing use of Springboard Delivery functionality.  How much functionality is utilised is up to each organisation and is not fixed:

Use CaseDetailsPre-Delivery Functionality UsedPost-Delivery Functionality Used
Passive POD collectionUsing the mobile app, drivers record deliveries as they happen, synchronising them to the Hub for later access by other users.  Orders do not have any prior existence and no planning takes place.
  • None
  • Access to POD's, for example to answer delivery queries
Passive POD collection with pre-defined ordersSimilar to passive POD collection, except that orders are created in advance.  As POD's are synchronised from the mobile app to the Hub, they can be matched against pre-existing orders.
  • Creation/import of orders
  • As above, with orders usually holding a larger amount of pre-defined data
Route planningOrders are organised into routes assigned to specific drivers, who receive them in the mobile app.  Drivers follow pre-defined routes and record POD's only against orders planned in the active route.

In addition to the above:

  • Planning of orders into routes
  • Review of route feasibility in terms of: drive time, vehicle weight and/or volume capacity
  • Optimising stop sequence within a route
  • Planning of vehicle/driver workload

In addition to the above:

  • Review of route taken

It is completely feasible to mix simple passive POD collection for some orders with full route planning for others.

Glossary

This is a glossary of terms and acronyms used in this documentation.

TermDefinition
ETAEstimated time of arrival
PODProof of delivery
  • No labels