> For the complete documentation index, see [llms.txt](https://docs.valq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.valq.com/simulate/create-initiatives-in-a-scenario.md).

# Create Initiatives in a Scenario

Initiatives are particularly useful when multiple assumptions need to be simulated, either individually or in a desired combination, and evaluated based on their potential outcomes. They are quite effective for a quick and seamless scenario analysis as opposed to creating multiple scenarios for each of the combinations. This aids in strategic value driver planning.

### How do Initiatives work?

1. You can create many initiatives within one scenario.
2. By default, the simulation impact of all the initiatives is included in a scenario.
3. Choose to include or exclude required initiatives in a scenario to assess their individual/combined impact.

<figure><img src="https://261229348-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmXNCTvPRjJZj6UunHBgb%2Fuploads%2Fbvtsz0wI7aMc5h3lYS7F%2Finiti%20newest.gif?alt=media&amp;token=ea2563a1-651e-425e-848c-fac3847b82ce" alt=""><figcaption><p><strong>Working with Initiatives</strong></p></figcaption></figure>

### Use-cases and advantages of initiatives

1. Create what-if scenarios for smaller organizational units as initiatives and merge them as required to understand the total impact. Alternatively, you can drill down a scenario by excluding a few initiatives to understand the unit-level impact.
2. Simulate possible risks that can occur in the course of your project/business by adding them as initiatives within your base case/best case/worst case scenarios. This can help you in contingency planning.
3. Multiple driver combinations can be simulated on the fly without having to start from scratch.
4. Both micro-level and macro-level scenarios can be analyzed quickly.

Let us now see how to create and add them to the scenarios in the next section.


---

# 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://docs.valq.com/simulate/create-initiatives-in-a-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 `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.