> 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-journey-report.md). # How to Use Journey Report Journey Report helps you understand how your fleet performs between two important operational locations. You can create a report between two Places, select the assets and period you want to analyse, and then compare journey duration, distance and fuel usage. You can also drill into individual journeys to understand what happened along the way, including trips, Place visits, stationary periods and operational events. ### Before you start Journey Report is currently enabled for selected customers. If you cannot see Journey Report in the Sky Ledge navigation menu, contact your Sky Ledge representative. Before generating a report, you will need to know: * The two Places you want to analyse * Whether you want to analyse one-way or round-trip journeys * Which assets you want to include * The date range you want to analyse Journey Reports can currently be generated for a maximum period of 30 days at a time. Depending on the amount of data being analysed, larger reports may take longer to generate. ### 1. Open Journey Report From the main Sky Ledge navigation menu, select Journey Report. The Journey Report screen will open and allow you to define the journey you want to analyse. ### 2. Choose the journey direction Start by selecting whether you want to analyse a one-way or round-trip journey. **One-way**: Use this when you only want to analyse journeys travelling in one direction: Point A → Point B **Round trip**: Use this when you want to include journeys travelling in both directions: Point A → Point B\ Point B → Point A This is useful when vehicles regularly travel between the same two operational locations, and you want to analyse both directions. ### 3. Select Point A and Point B Select the two Sky Ledge Places from the lists that represent the journey you want to analyse. For example: (**Point A**: Head Office & **Point B**: Customer Depot) Journey Report will use these Places to identify journeys between the selected locations. ### 4. Select your assets Choose the assets you want to include in the report. You can select specific assets when investigating an individual vehicle or group of vehicles, or include all applicable assets when you want a broader view of fleet performance between the two Places. ### 5. Select the date range Choose the period you want the report to analyse. The selected date range should not exceed 30 days. (For larger fleets or locations with a high volume of journeys, consider using a shorter date range to reduce the amount of information being processed.) ### 6. Generate the report Once you have selected: * Journey direction * Point A * Point B * Assets * Date range **Select Generate**. Sky Ledge will analyse the journeys matching your selected parameters and generate the Journey Report. Generation time can vary depending on the customer environment, number of assets, selected period and volume of journey data. ### 7. Review the journey summary Once generated, the report provides an overview of journey performance between your selected Places. The summary includes metrics such as: * Average Distance * Average Duration * Average Fuel Used These metrics provide a quick way to understand typical journey performance and identify journeys that may be significantly different from the average. ### 8. Review individual journeys Below the overall summary, you can review the journeys completed by individual assets. Each journey provides key information including: * Asset * Journey direction * Distance travelled * Journey duration * Fuel used Use this information to identify journeys you want to investigate further. For example, you may notice that one vehicle took considerably longer than other vehicles travelling between the same locations. ### 9. Investigate an individual journey Opening a journey displays a side panel containing more information about what happened during that journey. At the top, you can see the overall journey information, including: * Direction travelled * Distance * Duration * Fuel used Below this, Sky Ledge provides a chronological breakdown of the activity associated with the journey. This can include: Trips: (The driving activity that occurred as the asset travelled between the selected Places.) Place visits: (Places visited by the asset during the journey.) Stationary periods: (Periods where the asset remained stationary with the engine off during the journey) *For example*, if a journey took significantly longer than expected, you may discover that the vehicle was stationary for an extended period along the route. Events: (Operational and Driver Performance events detected during the journey) Depending on the events configured for your organisation, this may include events such as: * Harsh driving * Fuel events * Other operational exceptions This allows you to move beyond knowing that a journey was unusual and begin understanding what happened during the journey. --- # 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-journey-report.md?ask=&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.