> For the complete documentation index, see [llms.txt](https://twbvoiceplaybook.clearglobal.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://twbvoiceplaybook.clearglobal.org/5.-recording-and-validation/5.2-guidelines-for-validation.md).

# 5.2 Guidelines for validation

Validation is the process where another contributor (not the speaker) listens to the voice sample to check the quality.

In [TWB Voice](#user-content-fn-1)[^1], this is a separate step from recording. It has its own guidelines. The contributor can approve or reject the voice sample. The reasons for this will be as follows:

* **Approve** (Pass) - if a recording is clear, matches the prompt, and meets quality standards - a clear voice, no slurring, mumbling, or rushing.
* **Reject** (Fail) - if a recording has major issues. For example, it includes offensive language, or some words are missing (if it’s based on a prepared prompt). There may also be loud background noise, unclear speech, or several voices.

A user can also **report a recording**. They can do this if the content is unacceptable or the language is incorrect. It may be very unclear so you can’t understand it. Reporting is like a feedback mechanism. It helps to improve the process and the platform itself.

<br>

[^1]: **TWB Voice:** A platform for collecting voice data. It was developed by CLEAR Global, who also own it. Users can make voice recordings to help with active data collection projects in TWB Voice by [signing up to the TWB Community](https://translatorswithoutborders.org/join-the-twb-community/). The main goal of TWB Voice is to help to develop voice technology for speakers of marginalized languages. For example, by creating the voice datasets that are needed to build language models for TTS and ASR.


---

# 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://twbvoiceplaybook.clearglobal.org/5.-recording-and-validation/5.2-guidelines-for-validation.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.