> For the complete documentation index, see [llms.txt](https://docs.dataloy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/operations/voyage-analysis-dashboard.md). # Voyage Analysis Dashboard The Voyage Analysis Dashboard was established to give Senior Operator’s (primarily operations and chartering managers) visibility over day to day voyage operations and their possible deviations. This to enable faster reaction from staff to problems and deviations in voyages. Ship owners can get an early warning for a number of selected voyages operated by different operators and be able to identify and react quickly to problems and deviations. Daily snapshots are automatically taken for every voyage in progress. The main dashboard window displays voyage figures with deviations on voyages waiting to be operationally closed. {% hint style="info" %} **Red** = deviation has negative impact on voyage result\ **Blue** = deviation has positive impact on voyage result\ **Black** = no impact on voyage result {% endhint %} --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/operations/voyage-analysis-dashboard.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 `build a script that syncs our docs to a CMS` 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.