# Odometer Readings

The **Odometer Readings** section helps you keep vehicle mileage accurate and up to date.\
Loopit automatically estimates odometer values based on telematics trip data, while allowing you to manually record actual readings whenever needed.

***

#### Adding an Odometer Reading

You can add an actual odometer reading at any time to improve accuracy.

1. Navigate to the **Fleet** module and select the relevant vehicle record.
2. From the vehicle record, select the **Odometer** tab.
3. Click **Add Odometer Reading** in the bottom right corner.
4. Enter the **Exact Odometer Value** as shown on the vehicle dashboard.
5. Click **Save**.

Once saved, this will appear as an **Actual** reading and become the new baseline for future estimates.

{% hint style="success" %}
Odometer readings also also captured and recorded against a vehicle record when submitting an inspection report that includes the odometer field type.
{% endhint %}

{% hint style="warning" %}
When adding a manual odometer reading, it is important that is accurately represents the exact current odometer in the vehicle's dashboard. Estimates or rounded readings can cause issues with vehicle odometer tracking and accuracy.
{% endhint %}

***

#### Actual vs Estimated Readings

Loopit distinguishes between two types of odometer readings:

<table><thead><tr><th width="136.5">Type</th><th width="250.8331298828125">Source</th><th>Description</th></tr></thead><tbody><tr><td><strong>Actual</strong></td><td>Manual entry or linked inspection template</td><td>A verified odometer reading taken directly from the vehicle.</td></tr><tr><td><strong>Estimated</strong></td><td>Telematics device</td><td>A calculated odometer value based on trip distance since the last actual reading.</td></tr></tbody></table>

After each actual reading, Loopit continues to **estimate odometer values** by accumulating telematics trip data until the next actual reading is recorded.

***

#### How Loopit Handles Telematics Data

Loopit does **not** use the odometer value reported directly by a telematics device. Instead, Loopit calculates an estimated odometer reading based on **trip usage data** collected every 30 minutes.

Each trip record is validated for feasibility:

* Trip data that represents **unrealistic distance travelled within a 30-minute period** is automatically ignored.
* This prevents errors caused by device misreporting, poor GPS signal, or when telematics devices are moved between vehicles.

This ensures that estimated odometer values remain consistent and realistic over time, even when telematics data is imperfect.

***

#### Odometer Validation Rules

To maintain accuracy, Loopit enforces a few key validation rules when you enter or update odometer readings:

* An **actual odometer reading cannot be less than a previous actual reading**.
* An **actual odometer reading can be less than an estimated reading** to correct for small inaccuracies that naturally occur over time.

{% hint style="info" %}
If your telematics data overestimates the distance travelled, entering a new actual reading will automatically correct future estimates.
{% endhint %}

***

#### Handling Odometer Readings in Contracts

The **current odometer reading** shown at the top of the vehicle record—whether **actual** or **estimated**—is automatically used to populate odometer-related fields in contracts, agreements, and booking documents.

Because odometer readings can be estimated between actual updates, Loopit recommends that operators include a clause in their standard agreements clarifying that:

> **“Odometer readings may be estimated based on telematics data and may not reflect the precise vehicle odometer at the time of contract.”**

{% hint style="info" %}
This disclaimer helps set clear expectations with customers and protects against disputes arising from normal differences between dashboard and system readings.
{% endhint %}

<details>

<summary>Why doesn’t Loopit use the odometer value from my telematics device?</summary>

Loopit avoids using the raw odometer value from telematics devices because devices can be moved between vehicles or experience GPS irregularities. Instead, Loopit calculates odometer estimates based on trip data for improved consistency and accuracy.

</details>

<details>

<summary>How often does Loopit update estimated odometer readings?</summary>

Loopit fetches telematics trip data every **30 minutes**. Each trip is validated to ensure the distance travelled is realistic before being applied to the estimated odometer total.

</details>

<details>

<summary>Can I correct an estimated odometer reading if it’s too high?</summary>

Yes. Simply click **Add Odometer Reading** and enter the verified value from the vehicle dashboard. Loopit will reset the baseline and continue estimating from the corrected value.

</details>

<details>

<summary>How do I know whether a reading is estimated or actual?</summary>

Each entry is clearly labeled in the **Meter Type** column.

* **Actual** readings appear in green and are sourced from manual entry or inspections.
* **Estimated** readings appear in purple and are calculated from telematics trip data.

</details>

<details>

<summary>How do I know what the current odometer of the vehicle is?</summary>

The **most up-to-date odometer reading** is displayed at the **top of the Odometer Readings page** for each vehicle.

This value may be either:

* **Actual**, if the most recent update came from a manual entry or inspection template, or
* **Estimated**, if the most recent update was calculated using telematics trip data.

The displayed value always represents the latest known odometer reading for that vehicle and is automatically used to populate any **contract or agreement fields** that reference odometer data.

</details>