> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/feature-documentation/designing-and-running/master-events-list/multiple-master-events-lists.md).
# Multiple Master Events Lists
Using multiple Master Events Lists (MultiMELs) allows you to **design and manage independent MELs within the same scenario**. The MELs can be run in parallel or as alternatives.
{% hint style="info" %}
MultiMELs can be used to create branching:
{% endhint %}
{% content-ref url="/pages/3DqsrFnCE9SFv7H1sCzI" %}
[Branching](/concepts/designing/exercise-design/branching.md)
{% endcontent-ref %}
## Running
Monitor player actions via the `Review` tab and start the MEL that corresponds best with their actions.
{% hint style="success" %}
Consider sending notifications to the Facilitator (by creating a Facilitator position) to inform them when to start the next MEL / utilising Facilitator Guidance.
{% endhint %}
### In the Facilitator Dashboard
This is how MultiMELs look in the Facilitator Dashboard. You'll find them in the right-hand side of your screen:
You can start and stop MultiMELs by pressing **play/pause/continue** at the bottom of individual MELs:
{% hint style="warning" %}
Once one MEL has finished, you'll need to manually start the next by clicking `Continue`.
{% endhint %}
You may find facilitating exercises with all MELs open distracting. To **collapse/open** a specific MEL, click the arrows as shown below:
***
## Designing
{% hint style="success" %}
Consider using questions (data points) in your exercise to prompt players to make difficult choices. This can then determine the "branching" route the exercise takes.
{% endhint %}
{% content-ref url="/pages/ooX7smRQSqoNEo1Stgdi" %}
[Questions & Data Points](/feature-documentation/designing-and-running/master-events-list/questions-and-data-points.md)
{% endcontent-ref %}
### Creating MultiMELs
Each tab at the top of the editor is an independent MEL - click the `+` to create a new MEL.
{% hint style="warning" %}
Give the MEL a title that will be easily understood by the Facilitator.
{% endhint %}
---
# 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://helpdocs.conducttr.com/feature-documentation/designing-and-running/master-events-list/multiple-master-events-lists.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.
