> 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.8/voyage-management-system/step-by-step-guides/operations/laytime-calculations/maintain-laytime-calculation/manage-cargo-ports/synchronizing-events-and-deductions.md). # Synchronizing Events and Deductions Starting with Release 8.7, it is now possible to synchronize [events](/release-8.8/voyage-management-system/step-by-step-guides/operations/laytime-calculations/maintain-laytime-calculation/manage-cargo-ports/statement-of-facts.md) and deductions[ (not to counts) ](/release-8.8/voyage-management-system/step-by-step-guides/operations/laytime-calculations/maintain-laytime-calculation/manage-cargo-ports/timesheet.md)between a relet and the corresponding spot cargo, and vice versa. This reduces the manual effort needed when [reletting a cargo](/release-8.8/voyage-management-system/step-by-step-guides/cargoes/maintain-cargoes/cargo-drawer-actions/relet-cargoes.md#relet-a-cargo) since you no longer have to copy the events and deductions manually. ## How It Works When synchronizing the relet or spot cargo, all[ laytime events](/release-8.8/voyage-management-system/step-by-step-guides/operations/laytime-calculations/maintain-laytime-calculation/manage-cargo-ports/statement-of-facts.md), as well as the ["not to count"](/release-8.8/voyage-management-system/step-by-step-guides/operations/laytime-calculations/maintain-laytime-calculation/manage-cargo-ports/timesheet.md) events, will be copied from the corresponding cargo. For example, if you synchronize a spot cargo with a relet cargo, all events from the relet cargo will be copied to the spot. Figure 1-3 illustrates this process.

Figure 1: The Relet Cargo we are syncing from

Figure 2: The Spot Cargo we are going to sync

Figure 3: The Results of Synchronizing

## Synchronizing Events and Deductions To synchronize a relet with its corresponding spot cargo, follow these steps: 1. Open the [Related ](/release-8.8/voyage-management-system/step-by-step-guides/voyages/maintain-voyages/related.md)tab in the Voyage Drawer. 2. Expand the Laytime Calculations to access the Cargo Port Panel List. 3. In the Cargo Port Panel List, a *Synchronize Events and Deductions* button will be available for all relet and corresponding spot cargo ports. To make it easier to identify which cargoes are relet and connected to a spot cargo, a **chip** has been added to the section header. See the figures below. {% tabs %} {% tab title="Relet Cargo" %}

Figure 4: Relet Cargo

{% endtab %} {% tab title="Spot Cargo" %}

Figure 5: Corresponding Spot Cargo

{% endtab %} {% endtabs %} **NOTE:** When copying synchronizing the events and deductions, existing events and deductions ***will be overwritten***! To prevent accidental overwrites, a confirmation modal will appear with a brief explanation. You must confirm your choice before synchronization. See Figure 6.

Figure 6: Synchronize Events & Deductions Warning Modal

## Deletion of Cargo Deleting either the relet or its connected spot cargo does not affect the other. Synchronization only occurs when you manually click the button and confirm the action. --- # 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-8.8/voyage-management-system/step-by-step-guides/operations/laytime-calculations/maintain-laytime-calculation/manage-cargo-ports/synchronizing-events-and-deductions.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.