> 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/planning/budgets/copying-an-existing-scenario.md).

# Copying an Existing Scenario

The most common way to create a new scenario is to copy an existing one. The copy action opens a three-step modal to select which vessels, template voyages, and Budget Voyage Starts to carry across. The copy gets a new name; all other data is independent of the source. Changes to the copy do not affect the original.

This is the recommended approach for creating variants (for example, copying a base case and adjusting freight rates to produce a high case).The **Budgets** module is located in the menu under *Planning*. 

A budget consist of:

* Senario (e.g. "2026 Budget")
  * Template Voyages (full voyages) 
    * Budgeted Voyages ("planning placeholder" containing voyage start and laycan dates. 

*All levels are copied.* 


---

# 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/planning/budgets/copying-an-existing-scenario.md?ask=<question>&goal=<user_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.