> For the complete documentation index, see [llms.txt](https://help.visuary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.visuary.com/guide-visuary-en/visualization/variants.md).
# Variants
To create a new scenario:
* Go to **the Renovation floor plan tab**
* Click on **Scenario**
* Click on **New Scenario**
{% hint style="info" %}
**Note:** Scenario B is created automatically **based on the first version of your Renovation floor plan**.
{% endhint %}
Create a new scenario from the Existing floor plan
{% embed url="" %}
1. Start by creating a new scenario by clicking on Scenario > New Scenario
2. **Go to the scenario you want to reset**
3. Click the **3 dots** at the top right of the screen.
4. Click on "**Reset**" \
This scenario will then return to its initial state, identical to the Existing floor plan.
Rename a scenario
{% embed url="" %}
1. Click on Scenario at the top of the screen
2. **Select the scenario** whose name you want to change
3. Click the**pencil icon** that appears
4. Enter the new name you want to give it
5. Click on "**Finish**" and remember to save the project so the change is saved.
Delete a scenario
{% embed url="" %}
1. Click on Scenario at the top of the screen
2. **Select the scenario** you want to delete
3. Click the**pencil icon** that appears
4. Click on "**Delete**" then confirm the action by clicking on "**Yes**"
{% hint style="info" %}
All scenarios from the Renovation floor plan can be deleted, **except for Scenario A**.
{% endhint %}
Create a new scenario from a Renovation floor plan
{% embed url="" %}
1. **Go to the scenario you want to use as the base for the new scenario**
2. Click again on "Scenario" at the top of the screen
3. Click on **"New Scenario"**
4. So the scenario you were originally on will be duplicated into a new 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.visuary.com/guide-visuary-en/visualization/variants.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 `automate deployments from our CI pipeline` 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.
