> For the complete documentation index, see [llms.txt](https://aus2018gp.f1datajunkie.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aus2018gp.f1datajunkie.com/qualifying/quali-report.md).

# Quali report

Drivers progressed through the qualifying session as follows: 

![](/files/-L9C-CnjWVV4zMovaGbg)

Going from Q1 to Q2:

* ALO failed to improve his time, recording 83.692 compared to 83.597 (0.095s slower)
* OCO failed to improve his time, recording 84.786 compared to 84.503 (0.283s slower)

Going from Q2 to Q3:

* SAI failed to improve his time, recording 83.577 compared to 83.061

  (0.516s slower)

Order change going from Q2 to Q3, along with laptime improvement (-ve is a better time in Q3)

```
##   driverName   imp1 driverName   imp2
## 1        HAM -0.887        VET -0.106
## 2        RAI -0.679        VET -0.106
## 3        RAI -0.679        VER -0.537
## 4        MAG -0.113        SAI  0.516
## 5        GRO -0.129        SAI  0.516
## 6        HUL -0.012        SAI  0.516
```

![](/files/-L9C-CqJfbw5x8GUciiN)

The official session results were recorded as follows:

| POS | DRIVER | Q1            | Q2            | Q3           |
| --- | ------ | ------------- | ------------- | ------------ |
| 1   | HAM    | 1:22.824 (1)  | 1:22.051 (2)  | 1:21.164 (1) |
| 2   | RAI    | 1:23.096 (2)  | 1:22.507 (5)  | 1:21.828 (2) |
| 3   | VET    | 1:23.348 (3)  | 1:21.944 (1)  | 1:21.838 (3) |
| 4   | VER    | 1:23.483 (4)  | 1:22.416 (4)  | 1:21.879 (4) |
| 5   | RIC    | 1:23.494 (5)  | 1:22.897 (6)  | 1:22.152 (5) |
| 6   | MAG    | 1:23.909 (11) | 1:23.300 (8)  | 1:23.187 (6) |
| 7   | GRO    | 1:23.671 (8)  | 1:23.468 (9)  | 1:23.339 (7) |
| 8   | HUL    | 1:23.782 (10) | 1:23.544 (10) | 1:23.532 (8) |
| 9   | SAI    | 1:23.529 (6)  | 1:23.061 (7)  | 1:23.577 (9) |
| 10  | BOT    | 1:23.686 (9)  | 1:22.089 (3)  |              |
| 11  | ALO    | 1:23.597 (7)  | 1:23.692 (11) |              |
| 12  | VAN    | 1:24.073 (12) | 1:23.853 (12) |              |
| 13  | PER    | 1:24.344 (13) | 1:24.005 (13) |              |
| 14  | STR    | 1:24.464 (14) | 1:24.230 (14) |              |
| 15  | OCO    | 1:24.503 (15) | 1:24.786 (15) |              |
| 16  | HAR    | 1:24.532 (16) |               |              |
| 17  | ERI    | 1:24.556 (17) |               |              |
| 18  | LEC    | 1:24.636 (18) |               |              |
| 19  | SIR    | 1:24.922 (19) |               |              |
| 20  | GAS    | 1:25.295 (20) |               |              |

### Session Utilisation

Activity throughout the three qualification sessions took place as follows:

![](/files/-L9C-CyveHVKNePg3ehA)

### Q1

![](/files/-L9C-Cz8SDnysY8WdiGZ)

#### Cut-off Time Evolution

The cut-off time in Q1 evolved as follows:

![](/files/-L9C-CzNjxKZGCV_1FVy)

### Q2

![](/files/-L9C-CzawVsNEdwZXY9N)

#### Cut-off Time Evolution

The cut-off time in Q2 evolved as follows:

![](/files/-L9C-CzlN98q2o3D190n)

### Q3

![](/files/-L9C-D--tnhkdvuZn3XY)

#### Front Row Cut-off Time Evolution

The cut-off time in Q3 evolved as follows:

![](/files/-L9C-D-8ou5xThSbnzV5)

## Intra-Team Qualifying Comparison

![](/files/-L9C-D-Odz-6poWCNa0w)

To learn how to wrangle F1 results and timing data to create charts like these, see [f1datajunkie.com](https://f1datajunkie.com) or [buy the *Wrangling F1 Data With R* book](https://leanpub.com/wranglingf1datawithr).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://aus2018gp.f1datajunkie.com/qualifying/quali-report.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.