> For the complete documentation index, see [llms.txt](https://guides.gresb.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.gresb.com/data-center-assessment/1.-getting-started/data-quality-and-validation/validation-quantitative.md).

# Validation: Quantitative

## Automatic Data Validation

*The GRESB Portal has a built-in automatic validation system that flags inconsistencies as participants complete their assessment response.*

<details>

<summary><strong>Scope</strong>: What is automatically validated?</summary>

Automatic validation consists of errors and warnings displayed in the GRESB Assessment for **entity-level** responses to ensure that all quantitative data input is complete and accurate.&#x20;

</details>

<details>

<summary><strong>Criteria</strong>: What checks are conducted?</summary>

### General Requirements

* **Information completeness**: The portal ensures mandatory evidence uploads are present, that all required open text boxes are completed, and that answers are provided for all indicators.
* **Data types**: Certain fields must adhere to specific data types, such as numbers, percentages, text, etc.
* **Information accuracy**: percentage values must range between 0 and 100, and metrics are restricted to absolute values (i.e., only non-negative numbers).

</details>

<details>

<summary><strong>Outcomes</strong>: What are errors and outliers, and how are they handled?</summary>

### Errors

Errors appear in red and are generated per assessment as a result of logical checks amongst the different data fields in the assessment response.

{% hint style="danger" %}
Participants cannot submit their assessment until all validation errors are resolved.
{% endhint %}

</details>


---

# 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://guides.gresb.com/data-center-assessment/1.-getting-started/data-quality-and-validation/validation-quantitative.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.