# Build your Own Prompts (BYOP)

Bring your Own Prompts (BYOP) lets you apply your own analytical frameworks to After Action Review (AAR).&#x20;

Instead of relying on default prompts, **create custom AI prompts that assess player responses against your organisation's standards**.&#x20;

BYOP is then used by AAR observers to generate structured AI-supported observations.

<table><thead><tr><th width="334">Benefit</th><th>Feature</th></tr></thead><tbody><tr><td>Apply your own analytical frameworks to player responses</td><td>Create and test up to 3 prompts per exercise</td></tr><tr><td>Deliver consistent, client-specific AI assessment</td><td>Prompts carry over when a scenario is uploaded, keeping set-up consistent across runs</td></tr></tbody></table>

{% hint style="info" %}
To learn more about AAR, visit the page below:
{% endhint %}

{% content-ref url="/pages/H7o1n3mUcpot6akEztVf" %}
[After Action Review (AAR)](/feature-documentation/designing-and-running/observation/after-action-review-aar.md)
{% endcontent-ref %}

### When to use

* You have a client-specific evaluation framework
* You want consistent responses across observers
* You need structured, repeatable AAR outputs

## Running

{% stepper %}
{% step %}

### Assign AAR special permission

In the Facilitator Dashboard, ensure the intended participant (likely an observer logging in as a participant from within the Facilitator Dashboard) is **assigned the special permission for AAR**:

<figure><img src="/files/laqqG6MdpvHklFb2zo9K" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Open AAR (Click the :cloud:)

Within the exercise, observers with the assigned AAR special permission will see **a thought bubble** :cloud: **icon** next to written content within the exercise. Click here to access AAR:

<figure><img src="/files/c1sBUr5sHuVlXG1oAZEp" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Select prompt and generate observation

This will open a window that allows observers to **select a custom prompt**.

{% hint style="info" %}
The drop-down list will include both Conducttr's default AAR prompts as well as the custom prompts created by the designer.
{% endhint %}

<figure><img src="/files/OtlMrmn1jKPVDH5pdMZ1" alt=""><figcaption></figcaption></figure>

Click the magic icon to **generate an observation with AI**.

{% hint style="danger" %}
:zap:If you can't see your prompt in the drop-down list, it's likely because it has Context enabled but the player message isn't in response to something. **You'll only see your Context prompts when analysing a player message which is a response**.&#x20;
{% endhint %}
{% endstep %}

{% step %}

### Save observation

<figure><img src="/files/do82G3QA8BJNcoO8bIMF" alt=""><figcaption></figcaption></figure>

Once the AI-generated observation is saved, the :cloud: **icon will turn green**.
{% endstep %}
{% endstepper %}

***

## Designing

{% stepper %}
{% step %}

### Navigate to BYOP

Find all prompt creation and management in the Editor under `Configuration` > `Exercise` > `BYOP AAR.`&#x20;

<figure><img src="/files/zPMu5GsLLOoG1TK1aC8c" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Create prompts

Click `+ New Prompt`:

<figure><img src="/files/6iXe6jLWp4266ucREjLz" alt=""><figcaption></figcaption></figure>

Each prompt includes:

* **Prompt name**: what observers will see when selecting the prompt
* **Prompt description**: the instructions the AI uses to assess player responses

{% hint style="danger" %}
You can create up to 3 custom prompts per exercise. Conducttr will alert you if you exceed your prompt limit.
{% endhint %}

Remember to click `Save` when finalising a prompt. The test area is not stored otherwise.

You'll see your created prompts organised in a list on the left-hand side of the screen so you can navigate between them easily.
{% endstep %}

{% step %}

### Test prompts

On a selected prompt you'll see the option to `Test`. Input an example message to test your prompt and make any necessary changes before using it in a live exercise.

<figure><img src="/files/lvkoSuUxA5dw11q4PUzi" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### :zap:(Optional) Using context

Enable *Context* **when your prompt depends on situational information** (e.g. scenario background/prior events).&#x20;

{% hint style="danger" %}
**Prompts with the&#x20;*****Context*****&#x20;enabled only appear when analysing content that includes context information** i.e. when a player is responding to something. This could be anything from emails to messages to tweets, and could be persona or player content.
{% endhint %}

When enabled, you can include context during testing and the AI will use it alongside the message to produce a more informed assessment:

<figure><img src="/files/2ZzlK0fBKBb2peIGdkfQ" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Upload your prompts

You can upload your prompts directly to your space under `Configuration` > `Facilitator Dashboard`:&#x20;

<figure><img src="/files/BiJ3NlmMX79frBlajM1O" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

## :star:Example prompts

The following are example prompts for specific scenarios, with test messages and outputs too:

#### 1. Flood emergency public communication

**Prompt:** Evaluate this public alert message for plain English readability, actionability (does it tell people what to do?), tone, and whether vulnerable populations are considered. Score each 1/10

**Message:** *Flooding has been reported in several areas. Residents should be aware of the situation and take necessary precautions. Updates will follow.*

**Outpu**&#x74;*:*\
Plain English readability: \*\*7/10\*\*\
Actionability (does it tell people what to do?): \*\*3/10\*\*\
Tone: \*\*7/10\*\*\
Vulnerable populations considered: \*\*2/10\*\*

#### 2. Information accuracy under stress

**Prompt**: You are reviewing a message sent during a crisis. The writer had three things they needed to communicate: the problem, what is being done about it, and what the audience should do next.\
For each of the three, write exactly 2 sentences.

First sentence: what was covered

Second sentence: what was missing

Format your response exactly like this:\
The Problem\
\[2 sentences]\
What Is Being Done\
\[2 sentences]\
What the Audience Should Do Next\
\[2 sentences]\
Overall Rating: \[X/10]\
What would have made this stronger: \[one sentence, maximum 15 words]

**Message**: *There has been a chemical spill at the warehouse on Dock Road. The fire brigade have been called and we are monitoring the situation closely. Please avoid the area if possible.*

**Output***:*\
The Problem\
The message states there has been a chemical spill at the warehouse on Dock Road. It is missing details on the severity, specific chemicals involved, and immediate risks to people.\
What Is Being Done\
The message says the fire brigade have been called and the situation is being monitored closely. It is missing what containment or cleanup actions are underway and who is leading the response.\
What the Audience Should Do Next\
The message instructs people to avoid the area if possible. It is missing clearer guidance on boundaries, what to do if already nearby, and where to get updates.\
Overall Rating: 7/10\
What would have made this stronger: Specify hazards, safety perimeter, update channels, and clear instructions for nearby individuals.

#### 3. (Context enabled) Holding the line

**Prompt**: Did the player answer what was actually asked? Were they too open or too guarded? Was the tone right for who they were speaking to? Keep the response under 20 words.

**Context**: This is Reuters. We have received reports of an explosion at your base. Can you confirm casualties? We are publishing in 20 minutes.

**Message**: *Yes there was an incident this morning. There may have been some injuries but we cannot confirm numbers yet.*

**Output**: Partially answered; acknowledged incident but didn’t confirm casualties. Appropriately guarded, not overly open. Tone professional for Reuters.

#### 4. (Context enabled) Operational security

**Prompt**: Read the reply in the context of the incoming message. Does this response meet the standard expected of someone in this role? Where does the language fall short and what should it have sounded like?

Response format: Return the results under 500 chars each in English and Spanish.

**Context**: From the mayor's office: Residents in sector 4 are calling in saying they have received no evacuation instructions. What is happening?

**Message**: *We sent the alerts out this morning so I'm not sure why people are saying that. Maybe they didn't check their phones. We can resend if you want but I thought we already handled this.*

**Output**: English (≤500 chars): No. It’s defensive, speculative, and dismissive (“maybe they didn’t check”), lacks urgency, verification steps, and accountability. It should acknowledge the gap, commit to immediate validation (alert logs, carrier delivery, geo-targeting), provide a clear action plan (resend via multiple channels, door-to-door/sirens), give an ETA, and report back to the mayor’s office.

Español (≤500 chars): No. Es defensiva, especulativa y despectiva (“quizá no revisaron”), sin urgencia, verificación ni responsabilidad. Debió reconocer la brecha, comprometer validación inmediata (registros de alertas, entrega por operadoras, geocercas), dar un plan claro (reenviar por varios canales, brigadas/altavoces), indicar un ETA y confirmar reporte al despacho del alcalde.


---

# Agent Instructions: 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:

```
GET https://helpdocs.conducttr.com/feature-documentation/designing-and-running/observation/after-action-review-aar/build-your-own-prompts-byop.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
