> 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-5.37/fleet-allocation-and-scheduling/getting-started/fleet-plans/cargo-management-board.md). # Cargo Management Board The **Cargo Management Board** displays all allocated and unallocated voyages, as well as each of their cargoes in the voyages. The unallocated cargoes are placed under the **Commitments** column. For details on the vessel open positions, voyage cards and board settings, see [Open Positions Board](/release-5.37/fleet-allocation-and-scheduling/getting-started/fleet-plans/open-positions-board.md). ## Board structure The cargo management board displays all cargoes belonging to the selected scenario. In the left-most column, we display the unallocated cargoes, that is all cargoes that have not been allocated to a voyage. The other columns display voyage cards with the cargoes allocated to them. ### Unallocated Cargoes The most lefthand column, **Commitments**, contains all the unallocated cargoes. This column displays all cargoes with status Unallocated that belong to the currently selected scenario. Each card contains the following information: Charterer, cargo booking status, trade , first load and last discharge port, as well as the laycan and arrival window dates. The unallocated cargoes can be filtered by charterer, commodity, trade, load area and discharge area (see [Filters of Open Position Board](/release-5.37/fleet-allocation-and-scheduling/getting-started/fleet-plans/open-positions-board.md#filtering) for comparison). ### Cargoes on the Voyage Card On the right side of a voyage card, the *cargo cards* allocated to the voyage are showing. Each cargo has a load port, discharge port, charterer, cargo gross weight and cargo status displayed. These cargoes can be moved by dragging and dropping between the voyages of the same trade. ![Cargo Management Card](https://797708323-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Liw6C9Fe7rohFtkU25j%2F-Mb16gJCux9M20KdVRSK%2F-Mb1F6TtS4io0m9BlgiW%2FScreenshot%202021-05-20%20at%2010.42.47.png?alt=media\&token=2e08ca0a-5f94-4e93-bedc-92ec2e1a7783) With the newest design of the cargoes on the voyage card, you will be able to graphically see at which ports a cargo has its load- and discharge ports. You can easily track all the port call rows of the cargo by looking at the vertical span of the specific cargo card (the blue area). It is also possible to scroll to the right to see all the cargoes allocated on the same port calls. ### Lay Days and Arrival Window Indication ![Indicators](https://797708323-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Liw6C9Fe7rohFtkU25j%2F-Mb16gJCux9M20KdVRSK%2F-Mb1G3qkY7ReKO-W-7Eg%2Fimage.png?alt=media\&token=16922413-d8e8-450f-b1be-6536aaff24b6) The cargo cards also has indication lines to help you interpret the lay days and arrival windows for each cargo graphically. **Lay days:** indication line at the top of the cargo. \ **Arrival window:** indication line at the bottom of the cargo. **Color indicator:** * if **early**: blue * if **late**: red * if **on time**: normal / no colour ## Actions In the **Cargo Management Board**, you can drag and drop cargoes between voyages. When moving a cargo, you can either move it 100% or split it and just move a part of it. Clicking on a cargo opens the [cargo drawer](/release-5.37/voyage-management-system/step-by-step-guides/cargoes.md) and gives you access to additional information and actions. --- # 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, and the optional `goal` query parameter: ``` GET https://docs.dataloy.com/release-5.37/fleet-allocation-and-scheduling/getting-started/fleet-plans/cargo-management-board.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.