> 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.28/voyage-management-system/step-by-step-guides/planning/budgets/create-budget-scenario.md).

# Create Budget Scenario

#### Creating a New Scenario

A new budget scenario is created from the **Scenario** module under *Planning*. Select *Create Budget Scenario* from the Create dropdown and enter a name and budget year. The new scenario starts empty; template voyages and occurrences are added afterwards.

[The most common way to create a new scenario is to copy an existing one.](broken://pages/eyg1LCVaAGbUHRRE3BYa)

| **Field**     | Description              |
| ------------- | ------------------------ |
| Scenario Name | Unique Scenario Name     |
| Budget Year   | Defaults to current year |

{% hint style="info" %}
On clicking **Create**, a budget scenario will have the naming format "Budget Year Scenario Name", e.g. "2021 Incoming Bookings". 
{% endhint %}

<figure><img src="/files/PVEtGp3dmzvf1spJ1q2a" alt=""><figcaption><p>Create Budget Scenario Dialog</p></figcaption></figure>

Read about copying budget scenarios [here](broken://pages/eyg1LCVaAGbUHRRE3BYa).&#x20;


---

# 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:

```
GET https://docs.dataloy.com/release-8.28/voyage-management-system/step-by-step-guides/planning/budgets/create-budget-scenario.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.