# Introduction

The timeline component displays the user's driving score history to help them understand if they are making progress.

The data represents weekly or monthly averages that are calculated periodically by services that run on the DriveQuant platform and automatically synchronised with the DriveKit SDK.

The design is designed to be technical but ergonomic in order to highlight the qualities and weaknesses of the user's driving behaviour.

The user can easily navigate to consult :

* the evolution of his driving scores by theme. The safety score out of 10 for example.
* the evolution of sub-scores or secondary driving indicators that were used to build the main driving scores. The number of hard braking for example.

## Main screen

The main screen highlights the scores for each theme. The driver can choose between two types of display: 

1. weekly average history
2. monthly average history

<figure><img src="/files/6iQHOCNLnofio1hG1o6u" alt=""><figcaption><p>Timeline UI - main screen</p></figcaption></figure>

## Score detail screen

The secondary screens are accessible from the main screen by tapping on "See more details about my score".

They contain the sub-scores of the selected theme. As for the main screens, data is available by week and month.

🛡Safety sub-scores :&#x20;

* Number of accelerations per 100 km
* number of brakings per 100 km
* Adherence limits per 100 km

🌿 Eco-driving sub-scores:&#x20;

* Acceleration score
* Deceleration score
* Speed maintain score
* Fuel consumption (in l)
* Achievable fuel savings (in l)
* CO2 mass (in kg)

📱Distraction sub-scores:&#x20;

* Number of phone unlocks per 100 km
* Duration of forbidden calls per 100 km
* Percentage of trips with forbidden calls

🏎 Speeding sub-scores:

* Overspeeding relative duration
* Overspeeding relative distance

<figure><img src="/files/nvhuxegcMqoxChHKN9sW" alt=""><figcaption><p>Timeline UI - Score detail screen</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.drivequant.com/driver-data-timeline-ui/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.