> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/features/reports/challenge-requirements.md).

# Challenge Requirements

This report provides an analytical overview of participant engagement and progress for various requirements in a given challenge. It includes metrics on completion rates, participation levels, and filters to refine data by specific challenges and join statuses. This insight aids businesses in gauging the effectiveness of their challenges and participants' engagement.

#### Report Columns

* **Challenge**: The name of the challenge.
* **Requirement**: The name of the requirement.
* **People completed**: Number of people that completed the requirement.
* **People with some progress**: Number of people who earned progress toward the requirement, but did not complete it.
* **People with no progress**: Number of people that joined or were invited to join the challenge, but did not earn any progress towards the requirement.
* **Percent completed**: The '**People completed**' number divided by the total number of participants[^1].
* **Percent with some progress**: The '**People with some progress**' number divided by the total number of participants.
* **Percent with no progress**: The '**People with no progress**' number divided by the total number of participants.

#### Report Filters

* **Challenge Selection:** The report includes a filter to select specific challenges by name, allowing businesses to generate insights for one or multiple challenges.
* **Challenge Join Status**: Include clients that joined the challenge or include all statuses (Joined, Pending, Opted out).

[^1]: Participants are defined as the number people who were invited to the challenge, joined the challenge, or completed the challenge.


---

# 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.perkville.com/features/reports/challenge-requirements.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.
