Update a Customers Travel Policies

Update Travel Policies

In this dashboard, you can edit the name of the policies, select if the policy is compliant and select to display the lost savings within Travel Analytics. 

The Non-Compliant Bookings percentage is based on Airfare data and the flag given to policy compliances.  Policies (such as Cheapest Fare Accepted) can be flagged as compliant or non-compliant via the Data Editing function to which Administrators have access.

Adminstrators is able to flag if they want to show the lost savings to the customer for this policy code.

This will allow you to nominate policy codes as being compliant (for example, Exception Authorised) and also show a lost saving to the customer. The lost savings is calculated as the difference between the supplier fare (excluding GST) and the best fare (excluding GST) so it is still reliant on the data received being correct.

Tip: The list of travel policies is determined by the data received by Travel Analytics.  We do not block certain policy codes to ensure quality of data however existing codes can be renamed.

If you have selected some policy codes as being non-compliant, then any non-compliant bookings will be shown as a percentage on the Summary dashboard.

Administrators can update policy settings and lost savings as follows:

Step 1: On the Summary dashboard, select the customer you wish to update

Step 2: Click on the Travel Policies link within the Data Editing menu

Step 3: In the table, click on the edit button for the policy you wish to update

Step 4: Select the correct compliant option for the policy and display as lost savings.

You can also update the Description by overwriting the information within the field.  This allows you to get consistency within your data or update the name to the customer requirements.

Step 5: Click OK to save

Step 6: Navigate back to the Summary Dashboard and refresh the browser (CTRL F5) to display data according to the updated settings.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.