> For the complete documentation index, see [llms.txt](https://docs.skyledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyledge.com/knowledge-base/articles/how-to-use-the-event-report.md).

# How to use the Event Report

The Event Report gives fleet and operations managers a central place to review events that have occurred across their fleet and understand the important information behind them.

Rather than simply showing that an event occurred, the new Event Report brings more of the relevant information directly into the report. Depending on the event, this could include information such as speed, duration, fuel volume, driver, tyre details, location or other event-specific information.

This helps you quickly answer three important questions: what happened, which assets were involved, and where did it happen?

When an event requires further investigation, you can open it directly from the report to explore the surrounding context in more detail.

### Opening the Event Report

Navigate to the Event Report within the Sky Ledge platform.

The new Event Report will open by default, providing an overall view of events across your fleet.

If you prefer to use the previous report, select the option to switch to the Classic Report. You can switch back to the new Event Report at any time.

### Step 1: Choose the period you want to review

Start by selecting the date or reporting period you want to investigate.

For example, you may want to review recent activity or look across the previous month to identify patterns that may not be obvious when looking at individual events.

Once your reporting period is selected, you can begin narrowing the results to the part of your operation you want to investigate.

<figure><img src="https://2860706610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwO7lqI7ldNl4mfD8FCC1%2Fuploads%2FodapZw1otDL29Js6aMxN%2Fimage.png?alt=media&amp;token=6f707c7e-8553-424f-aa00-2267f0204a4f" alt=""><figcaption></figcaption></figure>

### Step 2: Filter by asset type or asset

The Event Report allows you to look across your entire fleet or focus on particular parts of your operation.

You can filter by asset type, such as viewing events for all trucks, or drill down further and select an individual asset.

Once you have applied an asset filter, it remains in place as you move between different event types. This makes it easier to investigate the same group of assets without repeatedly setting up your report.

<figure><img src="https://2860706610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwO7lqI7ldNl4mfD8FCC1%2Fuploads%2FLC0FYwAJ6XqmzTS7coyz%2Fimage.png?alt=media&amp;token=c9fc163d-f9af-4ab6-830d-96d5fe7844f9" alt=""><figcaption></figcaption></figure>

### Step 3: Explore different event types

You can move between the different event types available within your organisation to focus on the operational issue you are investigating.

The report has been designed to show information relevant to the type of event rather than presenting every event in exactly the same way.

For example, a speeding event may include information such as maximum speed and speeding duration, while a fuel theft event may include the estimated litres lost, percentage change, confidence and nearby location.

Other event types can surface information such as driver details, fuel volumes, tyre numbers and pressures, service information, document expiry dates and other relevant information captured when the event occurred.

This allows you to understand much more about an event directly from the report without needing to open every event individually.

<figure><img src="https://2860706610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwO7lqI7ldNl4mfD8FCC1%2Fuploads%2Fn8w1TBrGndBClrG6qtEG%2Fimage.png?alt=media&amp;token=4b833982-5c7a-46ba-b932-247ac2fa43dc" alt=""><figcaption></figcaption></figure>

### Step 4: Use the heat map to understand where events are happening

Sometimes understanding where something is happening is just as important as understanding what happened.

Switch to the heat map view to visualise the location of events on the map.

This can help you move beyond individual events and start identifying geographical patterns across your operation.

For example, you may want to understand whether particular events are occurring repeatedly along the same route, around a particular location or within a specific area of your operation.

Your existing filters continue to help you focus the map on the assets and events you are investigating.

<figure><img src="https://2860706610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwO7lqI7ldNl4mfD8FCC1%2Fuploads%2FWF0XHGMLXQS5m5tfxPEM%2Fimage.png?alt=media&amp;token=c2a0e046-b458-4f7c-9c9c-8699e9515f07" alt=""><figcaption></figcaption></figure>

### Step 5: Open an event for further investigation

If you find an event that requires a closer look, select it directly from the Event Report.

You can then open the individual event to investigate the additional information available within Sky Ledge, including relevant metrics and other activity associated with the asset.

This is particularly useful when the Event Report identifies something unusual and you need to understand the wider circumstances surrounding the event.

The Event Report therefore becomes your starting point for finding and prioritising issues, while the detailed event experience is available when deeper investigation is required.

<figure><img src="https://2860706610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwO7lqI7ldNl4mfD8FCC1%2Fuploads%2FVUcjeVbMWbqntGJuaTq1%2Fimage.png?alt=media&amp;token=a766791f-6ef2-482a-8d09-e0abc6f5c651" alt=""><figcaption></figcaption></figure>

### Understanding the information shown for each event

Not every event tells the same story, so the information displayed can differ depending on the event type.

For example:

| **Event**                                | **Information that may be displayed**                             |
| ---------------------------------------- | ----------------------------------------------------------------- |
| Stationary                               | Stationary duration                                               |
| Speeding                                 | Maximum speed, speeding duration and driver                       |
| Harsh acceleration, braking or cornering | Duration and relevant rule information                            |
| Crash                                    | Collision severity or type                                        |
| Fuel theft                               | Fuel lost, percentage change, driver, confidence and nearby place |
| Fuel refill                              | Fuel added, percentage change, driver, confidence and location    |
| Fuel card transaction                    | Litres, amount, product, service station and card holder          |
| Onsite refill                            | Pump litres, refill litres, discrepancy, confidence and driver    |
| Private pump dispense                    | Volume dispensed, pump, product and location                      |
| Private tank dispense                    | Volume dispensed, tank, remaining volume and temperature          |
| Private tank refill                      | Refill volume, tank level and temperature                         |
| Document renewal                         | Document type and expiry date                                     |
| Service maintenance                      | Service name, next service due and service interval               |
| TPMS pressure                            | Tyre number, pressure and threshold information                   |
| Tyre blowout                             | Tyre number and recorded pressure                                 |
| TPMS battery                             | Battery status, where available                                   |

The information shown will depend on the event and the data available when it was created.

### Using the Event Report on mobile

The new Event Report has also been designed to work on smaller screens.

This means you can review events, change the reporting period, apply filters and investigate activity when you are away from your desk.

For fleet and operations managers who spend time in the field, this provides a convenient way to investigate an issue without needing to return to the control room.

### New Report or Classic Report

The new Event Report is the default experience, but the Classic Report remains available.

If you need to return to the previous report, select the option to switch to the Classic Report. You can return to the new experience whenever you are ready.

### Getting the most from the Event Report

A useful way to work with the report is to start broad and progressively narrow your investigation.

Begin with the reporting period you are interested in, then select an asset type or individual asset. From there, move between event types to identify anything requiring attention. If location is important, switch to the heat map to look for geographical patterns.

When something stands out, open the individual event for a deeper investigation.

This approach allows the Event Report to act as an operational overview of what has happened across your fleet, while still giving you access to the detailed information when you need it.

The result is less time piecing information together and more time understanding what happened and deciding what to do next.

{% embed url="<https://youtu.be/LaRGI40bl2w>" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.skyledge.com/knowledge-base/articles/how-to-use-the-event-report.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
