> 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/observation/capturing-observations/checklist.md).

# Checklist

The checklist feature is a customisable tool for creating and monitoring objectives. As players achieve these objectives can be actively monitored and checked off in real time through the Facilitator Dashboard.&#x20;

Its versatility is useful for confirming training objectives or reminding players of expected activities.

{% hint style="info" %}
Assign special permission 'checklist' for it to be visible.
{% endhint %}

{% tabs %}
{% tab title="Benefit" %}

* Provides a date & time-stamped record of activities completed, available in the exercise report
  {% endtab %}

{% tab title="Features" %}

* Fully customizable objectives and tasks
* Only accessible to designated players
* Checking objective auto-checks all items
* Evaluation (AAR) feature functions within the checklist - allowing observers to leave comments alongside the checklist objectives to qualify the check &#x20;
* Player checklist responses are exported in the AAR report
  {% endtab %}
  {% endtabs %}

{% stepper %}
{% step %}

### Activate the checklist

1. Create the list
2. Activate it
3. Assign the special permission to a player

{% hint style="warning" %}
Only players with the special permission assigned will see the checklist.
{% endhint %}
{% endstep %}

{% step %}

### Create your objectives

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

Navigate to `Configuration` > `Exercise setup` in the Editor to create your objectives. Click `Add objective`.

Create sub-objectives/goals by clicking `Add goal`.

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

{% step %}

### Upload your checklist

Upload your checklist to your space in Configuration to see these changes.

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

{% endstep %}

{% step %}

### Assign the checklist special permission

When running the exercise as Facilitator, you can access the teams table via the Facilitator Dashboard.

Here you can assign players the checklist special permission.

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

{% hint style="info" %}
Visit the page below to learn more about assigning special permissions:
{% endhint %}

{% content-ref url="/pages/sP1Q6uHHQCXjoOPm6RuB" %}
[Positions and Special Permissions](/feature-documentation/designing-and-running/facilitation/facilitator-dashboard/positions-and-special-permissions.md)
{% endcontent-ref %}

### Checklist & Exercise report

The checklist status of all players with access to the channel is presented in the AAR report. The AAR report can be downloaded from the Review tab.

<div align="left"><figure><img src="/files/NKTNOucLQUbM6waEhAN5" alt=""><figcaption></figcaption></figure></div>

Refer to the example below to see how Checklist and AAR comments are exported into the Exercise report:&#x20;

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


---

# 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/observation/capturing-observations/checklist.md?ask=<question>&goal=<endgoal>
```

`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.
