> 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.md). # Master Events List The **Master Events List (MEL)** is the primary way to create an exercise in the Editor. This is the **timeline** of your scenario. It presents the exercise content in sequential time order. In the Facilitator Dashboard, it's where the Facilitator controls the pace of the exercise. | Benefit | Feature | | -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | | Automated scheduling: set content to go live at specific times to allow for a seamless exercise delivery |

Import MEL from .csv files
Organise MEL using tabs and serials

| | Structured progress: ensure a clear flow of events, guiding participants through the scenario step-by-step |

Drag and drop to reorder injects
Automatically adjusts timings for moved injects

| | Efficient management: organise and centralise all of the exercise events in one place for streamlined planning and control |

Publish individual content items or inject sequences for efficient testing and development

| ## Running In the Facilitator Dashboard you can skip, pause and publish injects. Do so using the buttons at the bottom of the MEL which allow you to manage the flow of events seamlessly. Each button serves a distinct function: * **Skip** lets you bypass an inject if it's no longer relevant * **Pause** halts the exercise temporarily * **Publish** pushes selected injects to participants in real-time This flexibility ensures that the exercise can be dynamically adjusted based on the evolving scenario or participant needs.

The MEL can be easily collapsed at your convenience.

### Reset options In the Facilitator Dashboard, you have the ability to reset the MEL. Here's an overview of the rest options available:

Reset option	Clears
Reset messages	All messages from all channels (from Editor and user) Social Watch words and filters
Reset data	Timeline Pulse pie charts After Action Review (AAR) observations Checklist data
Reset live exercise configuration	Contact lists

*** ## Designing As a designer you have different options available to you on how to structure and organise your exercise in the Editor.

### Events You can use events in your MEL to plot out the narrative shape of your exercise, focusing on the key events which push the crisis forward. Using events also allows you to pre-configure pauses in your MEL (when *Advance manually* is toggled on) in the form of a customisable button which the Facilitator must press to continue the exercise.

Most exercises tend to follow a 3 or 5 Act structure to aid good storytelling.

### Serials Using serials within your events allows you to plot how players will experience the key events of the crisis. All of the information you provide as a designer should feed into how players will make decisions throughout the exercise. By opening up the serial and clicking `Show serial details` you can add a description to the serial which is purely for your own note-taking during the planning and designing process.

{% hint style="info" %} Players won't be affected by serials, they're just a way for designers to organise their exercise. {% endhint %} ### Injects Injects are the components used to build the MEL; they are the specific pieces of content that the players interact with during the exercise. #### Creating an inject Open the serial and click the `+` as shown below to add an inject:

Select the persona and channel you'd like this inject to come from (in this example no persona is selected due to the inject being a ransom notification).

**Content creation**

Feature	Description
What method?	This is the channel to which the message will be published
Subject	Only present on channels such as email, blog posts, and news articles
Text block	Content body (if using AI to generate content, the content is generated according to the method e.g. if the method is tweeting on MicroBlog, then the message will automatically look like a tweet)

**Organisational attributes and inject details**

Detail	Description
Time	Expressed using 24hr clock because all times are relative to the start of the exercise
Tag	Tag is a way to highlight an inject using a dot for emphasis
Asset ID	Refers to a unique identifier assigned to each inject, used to track and manage content within the exercise
From	This is the persona from whom the content will be published from
To	Which player(s) will receive this content

You can also use the *AI Assistant* to help generate text-based content. Enter a description of the content, then click the "magic icon" to generate.

{% hint style="info" %} The *AI Assistant* knows the channel you have chosen, saving you from having to type commands like "write an email". {% endhint %} #### Further actions

Facilitator guidance in the Facilitator Dashboard and Editor

Action	Description
Question	Adding a question creates a data point, which appears as a pie chart on the Facilitator Dashboard, allowing the Facilitator to quickly see participants' choices at a glance
Past comments	Past comments allows you to simulate replies on social media posts
Facilitator guidance	This is both a note to the exercise control team and a reminder in the MEL of which inject is coming up
Inject grid	Inject grid enables you to send specific injects at any point during the exercise. To create an inject grid navigate to `Inject grid` at the bottom of the inject window and give your button a title (this will add the inject to the grid)

### Possible actions #### Reorganise Click the 6 dots as shown below to drag-and-drop and move injects:

#### Publishing content during development Right-click on the row. * Select `Publish to player` to publish that inject to players * Select `Publish to Facilitator` to jump to that part of the MEL in the Facilitator Dashboard

--- # 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://helpdocs.conducttr.com/feature-documentation/designing-and-running/master-events-list.md?ask=&goal= ``` `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.