> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/setup/cookbook/pilot-design.md).

# Pilot Design

## Designing the Participant Mix

The point of the pilot is to feel what MOSIP behaves like for real residents, not for an idealised, average user. Aim for a participant pool that mirrors the country's population mix, with deliberate inclusion of harder edge cases.

### Recommended demographic distribution

The following distribution is recommended as a starting point. The country team owns the final mix and can adjust to reflect the local population profile and the coverage they want to validate during the pilot.

| Group                            | Why include them                                                                                                                                           | Suggested share              |
| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------- |
| Adult males                      | Reference registration path; surfaces the most common workflow.                                                                                            | ≈ 50% of adult registrations |
| Adult females                    | Validates the same reference path with diverse face capture conditions.                                                                                    | ≈ 25% of adult registrations |
| Elderly residents (60+)          | Lower fingerprint quality is common; iris and face fall-back paths are exercised; OTP-based authentication is deliberately tested.                         | ≈ 25% of adult registrations |
| Children below 5 years           | Biometric thresholds differ; guardian linkages and consent flows are tested.                                                                               | ≈ 5% of total population     |
| Adults with biometric exceptions | Residents who cannot present fingerprints, iris or both. Exception biometric flow, missing-biometric reason capture and supervisor approval are exercised. | ≈ 5% of total population     |
| Minors (6--17 years)             | Fingerprint and iris capture works but operators must handle consent and guardian linkage flows.                                                           | Country to decide            |
| Persons with disabilities        | Includes residents in wheelchairs, with limited mobility, or low vision. Validates Center accessibility and operator scripts.                              | Country to decide            |

{% hint style="info" %}
**Consent and ethics** Residents participating in the pilot must give informed consent. Make sure the consent form makes clear that this is a pilot, what data is collected, how long it is retained and whether the credential will continue to work after pilot closure.
{% 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 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://docs.mosip.io/1.2.0/setup/cookbook/pilot-design.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.