> 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.20/fleet-allocation-and-scheduling/step-by-step-guides/scenarios/create-scenario.md).

# Create Scenario

There are three possibilities to create a scenario:

* create from scratch
* create from master fleetplan
* copy existing scenario

In the scenario list you have a button on the top left to create a new scenario. You can create a scenario from scratch or create a scenario from the master fleetplan. You can also copy an existing scenario.

![](/files/-LyAlbtzBXPnH80n7Ar4)

#### Create from Scratch

When creating a scenario from scratch you follow the following four steps:

1. Enter scenario name
2. Select the vessels to be included in the scenario by clicking on them.
3. Select the voyages to be included in he scenario by clicking on them.
4. Save the scenario.

{% hint style="info" %}
To deselect vessels or voyages when creating the scenario, click on them.
{% endhint %}

All voyages in the scenario will be commitments in the new scenario. For each vessel an open position is created. 

#### Create from Master Fleetplan

When using the master fleetplan to create a scenario, all voyages in the master fleetplan and their allocation are copied. Thus, unallocated voyages will be unallocated in the scenario and allocated voyages will be allocated to the same vessel. The first position of each vessel in the scenario schedule is defined by the start of the first voyage on the vessel.

The new scenario is called Master Fleetplan Scenario with a date and time stamp of the creation.

#### Copy existing scenario

To copy a scenario open its drawer in the scenario list. Select the action copy in the drawer to create a copy of the scenario.


---

# 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.20/fleet-allocation-and-scheduling/step-by-step-guides/scenarios/create-scenario.md?ask=<question>&goal=<endgoal>
```

`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.