> For the complete documentation index, see [llms.txt](https://help.metaforms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.metaforms.ai/data-processing/python/step-4-running-checks-and-reviewing-results.md).

# Step 4: Running Checks and Reviewing Results

Once you have reviewed your scripts and are confident they are correct, it is time to execute them against the dataset.

![](https://usercontent.in.prod.clueso.io/743138ba-7933-4a1a-90b2-26ddeb90ccbd/f92caeff-fe49-434b-a35f-fb2b01d97783/f5a37142-3fd8-412d-9b9c-82bb70a8fc4d/images/1b9ee3a6-4dbb-40d9-806e-022e77e0bdc4.png)

### Step 1: Run All Checks

Click **Run All Checks** to execute every validation script in the project. The platform runs all checks against your respondent data and returns results within seconds, regardless of dataset size.

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

Once the checks have run, the yellow dot next to each question would indicate that there are respondents flagged for the checks run for that question.

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

### Step 2: View Flagged Respondents

For any check that failed, click the **View** button next to it. This takes you directly to the Respondents tab, automatically filtered to show only the respondents who failed that specific check. The columns are also filtered to display only the relevant variables, so you can immediately see the problematic data without sifting through the full dataset.

This makes it straightforward to understand exactly which respondents were flagged and why.

### Step 3: Export the Validation Report

Once you have reviewed the results, click **Export** to download a comprehensive validation report.

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

The report is an Excel file that includes:

* **Summary sheet** — Overall pass rate, total respondents, number of checks run, and counts of flagged respondents.<br>

  <figure><img src="/files/BjN7ldd1g3vzHl9HnuGt" alt=""><figcaption></figcaption></figure>
* **Detailed findings** — Each failed check listed with the question text, the validation condition, the number of respondents who failed, and their respondent IDs.<br>

  <figure><img src="/files/R2jtvVeF2ANX08Zzn3m0" alt=""><figcaption></figcaption></figure>
* **Per-respondent breakdown** — Grouped by question and check, showing exactly which respondents failed and what checks.<br>

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

This report can be shared with your programming team, QA team, or clients to communicate data quality findings and drive corrective action.


---

# 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://help.metaforms.ai/data-processing/python/step-4-running-checks-and-reviewing-results.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.
