Proof of Service

The Proof of Service report displays sensor activity for monitoring and reporting of vehicles to deliver a comprehensive record of activity to the customers, who are monitoring contractual obligations or service level agreements (SLAs).

Proof of Service is a subscription service. Contact your EROAD account manager for more details.

Screenshot 2025 09 01 at 11.28.41AM 

To win, retain and get paid for civil contracting or construction contracts, it is critical to be able to monitor and deliver proof of activity execution for service level agreement (SLA) obligations. Proof of Service provides gold standard reporting with a map visualization of vehicle or fleet activity for the contracted period and area, as well as an auditable drill-down of every auxiliary equipment activation.

The Proof of Service report confirms that a comprehensive description of civil contracting activity is active, which includes gritter, sweeper, excavator, grader, or other vehicles with auxiliary equipment.

It shows a map visualisation for quick proof of activity by day-week-month, and a CSV export detailing requisite activity is available for download or scheduling — either to Project Managers for monitoring of the fleet’s activity or to the contract holder.

Generating the Proof of Service Report

Perform the following steps to run a Proof of Service report.

  1. Click Reports in the red menu bar.
  2. Click the Proof of Service icon on the Reports screen. The Proof of Service dialog box appears.
  3. Click the Select Group drop-down arrow and select a group.
  4. Click the Select Period drop-down arrow and select the time period for the report. The report defaults to the last 30 days.
  5. (optional) Click the From drop-down arrow and select the beginning date of the reporting period.
  6. (optional) Click the To drop-down arrow and select the ending date of the reporting period.
  7. Click Search.  

The report displays the sensor activity of vehicles selected within the date range and includes vehicle name, distance, and duration.

Screenshot 2025 09 01 at 11.27.42AM

 

  • Click the Sensor Type drop-down arrow on the upper right corner of the map view to select display options. 
  • To Export the report as a CSV file, use the filter panel’s 3-dot menu.

The Proof of Service report includes the following data to prove that service has been completed in line with SLAs or contractual requirements.  

Column Name Sample Value Definition 
Activity  Sweeper  Name of I/O
Plate  CME123  Plate of vehicle
Asset Code  DO123  Asset code of vehicle 
I/O Start   7/18/2014 9:20 AM  Start date and time the auxiliary equipment was engaged 
Start Location 

 419 Kyber Pass Rd
 Newmarket
 Auckland  

 Address location where the auxiliary equipment was engaged 
Start Lat Long 

 -36.718735
 174.712093

 Latitude / longitude where the auxiliary equipment was engaged  
I/O End  7/18/2014 9:41 AM  End date and time of the auxiliary equipment disengagement
End Location   599 Kyber Pass Rd
 Newmarket
 Auckland
 Address location where the auxiliary equipment was disengaged
End Lat Long   -36.712613
 174.722121
 Latitude / longitude where the auxiliary equipment was disengaged  
Distance  1230  Distance (metres) in which the auxiliary equipment was engaged
Duration  21  Duration (minutes) in which the auxiliary equipment was engaged
Average Speed  34  Average speed that the vehicle travelled whilst the auxiliary equipment was engaged 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

The Proof of Service report shows activity of vehicles with sensors, from sensor ON to sensor OFF, from one day to one month’s time. Activity is visible from the date that the report was enabled for the organisation. 

You can search for a vehicle within a group that is selected. Once your search is configured to view certain groups, you can go inside the group of vehicles to search for a particular vehicle. 

Sensor names and management

Administration > Vehicles > Input Outputs.

Click Edit to label the I/O sensors for the vehicle. Ensure that the physically connected sensor is labelled to the correct Input, such as 1, 2 or 3. The installer should provide these details when the I/O is physically installed.  

Users may request a sensor to be connected to an Ehubo 2 that is already installed in your vehicle, or request that the sensor be connected when an Ehubo 2 is newly installed.

Note: There is an additional charge for this service.