Lease Snapshot Report

Purpose

For organisations which have leased vehicles, the Lease Snapshot Report is a valuable tool to perform a 'lease health check'. The purpose of this report is to show you how each lease is performing in the context of

(a) current vehicle usage, and

(b) the lease term. 

The report performs calculations to produce a confidence number or score, which represents whether or not you are likely to exceed the lease term and thus incur penalties from the lessor, based on current usage patterns. By intervening before the lease terms have been exceeded, the report gives you a 'heads up' that certain vehicles may need to be moved to other departments where the usage is less.

The report is located at Sysadmin > Reports > Lease Snapshot Report

Lease Register

The data in the Lease Snapshot Report is taken from the Vehicle Register where a vehicle record has the 'Leased?' flag set to Yes.

Open

In the Lease Register (screen shots below), you can enter the lease details such as term, lessor, etc. The snapshot report simply extracts all vehicles that are leased.

Open

Reading the Report

Please refer to the below screen shot of a sample Lease Snapshot Report.

The column headings reading from left-to-right are self explanatory, the columns of note are below:

• Current ODO column - note this column is colour-coded with either a background of red, amber or green. This 'traffic-light' colour scheme shows how recent the current ODO reading is (ODO reading date). If the ODO reading date is 'fresh' then the color is Green; Red indicates the reading is stale, with a reading date more than 60 days old. 

• Budget KMs/Month - this column takes the lease term KMs and divides by the lease term months, arriving at how many KMs "should" be travelled per month. In other words, the monthly budget that can be travelled to stay on track with the leasing agreement.

• Actual KMs/Month - this column shows how many KMs a month the car is actually doing, based on supplied ODO readings and the age of the car.

• Estimated KMs End of Term - if the current usage continued as-is for the remainder of the term, what would the ODO be like at the end of the term? In other words, (months remaining on lease x actual KMs per month being travelled).

• Score - Again traffic-lighted into red, amber and green. If the estimated KMs at end of term exceeds the lease term then the color will be red (danger! vehicle will most likely exceed lease term). You want green here in this column, or better still, amber which means your lease term is slightly under the agreed terms. The percentage value shows how close/far you are likely to be at the end of lease term. 

Why Amber is Better than Green

If your vehicle scores are green, then one could reach the conclusion that the lease terms are too high meaning that you are probably not getting the most out of the leasing mechanism to maximize value for money. Amber would indicate that your negotiated lease terms closely reflect the reality of how the business is using their cars. To put it another way, green would mean you are playing too safe, whereas amber would mean you have negotiated relevant lease terms.

Things to Note

The score is an estimate based on current usage patterns. Where you are likely to exceed the lease terms, it would be a good idea to get the KMs down. You can use a variety of methods here - 

• Increase the 'discouragement factor' so that the vehicle receives less bookings

• Create 'maintenance' or dummy bookings for periods of time each month to get usage down

• Swap the vehicle out with that from another department, who would typically use the vehicle less

• Increase the lease terms or just wear the penalties (if any).

Most leases also have a 'buffer' so it could be that a red or amber score may land inside the lease term + buffer. 

To get the most out of the report, ensure your ODO readings are current.

A black score of zero indicates there is no data, meaning either no ODO readings or missing lease term details in the vehicle register.

• If you are unable to find an answer to your question in here please log a support request via the Smartrak Service Desk