> 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/bill-of-lading/create-bill-of-lading.md).
# Create Bills of Lading
In the top right corner in the Bills of Lading screen, click the create
icon. You will then see a modal where you need to enter the required information in order to create a Bill of Lading.
Start typing in vessel name and select from the drop down. Once the appropriate vessel is selected you may select port call from the drop down. The port call drop down will show discharge ports and voyage reference for the selected vessel. Choose the correct voyage/discharge port.
Next you need to choose Consignee and Notify party from the drop-downs. These fields are retrieved from the sub-cargo level of a cargo. Please see screenshot below from the sub-cargo modal where the two fields for consignee and notify party is highlighted in red:
When the required fields are filled in, you select the corresponding sub-cargo(s) from the table, and click create in the Bills of Lading modal.
---
# 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/bill-of-lading/create-bill-of-lading.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.