VehoCheck is a very lightweight app. The initial installation uses around 20Mb of data. Once installed the app does not perform any background data transfer. Data is only transferred when initiated by the user, either through updating the app checklists, vehicle and driver data (syncing), or when a check report is submitted.

Check reports vary in size depending on the number of photos contained in the report. The majority of reports submitted by drivers are “nil defect” so will contain no photos. This type of report would typically use around 200kB of data allowance to upload.

Where checks include records of defects, a driver on average will submit 2 photographs with the report (many defects are often recorded without the need for a photograph). The data allowance used for uploading this type of report is typically around 900KB.

We can see from analysing VehoCheck data that defects are recorded on average on 12% of checks that are submitted.

During the submission process a PDF copy of the report is also returned to the app from our servers for storage on the driver’s device. This report file size also varies depending on whether the report contains photos. A PDF report without photos has an average size of 40KB and a PDF report with 2 photos has an average size of 185KB.

So, given the above figures, the process of submitting a report that contained no photos would use 240KB (0.024MB) of data allowance, and a report that contained photos would use 1085KB (1.085MB).

A driver will typically submit a maximum of 24 vehicle check reports in one calendar month. 12% or 3 of those checks will contain photos, the remaining 21 will contain no photos.

3 x 1,085KB = 3,255KB
21 x 240KB = 5,040KB
TOTAL = 8,295KB = 8.295MB = 0.0083GB per month

If we use an example of a driver with a phone contract that allows for 5GB of data allowance per month and using the data usage figures we have demonstrated above, we can calculate that the VehoCheck app would only use 0.17% of the driver’s monthly data allowance.