> 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/lender/completing-the-assessment/supporting-information/data-quality-and-validation.md).

# Data Quality and Validation

An overview of GRESB's data quality practices -- including data validation, Assessment Corrections, and data estimation requirements.

## Introduction

<details>

<summary>GRESB's Data Quality Commitment</summary>

As part of its value proposition to investors, managers, and operators participating in the assessments, GRESB conducts both automated and manual data quality checks on data submitted through the Portal.&#x20;

These checks are designed to reduce the risk of misreporting and ensure the integrity of the data submitted to GRESB.&#x20;

Together, the validation and data quality mechanisms outlined within this Appendix aim to improve the consistency, reliability, and integrity of reported data across the assessment.

Please note that these checks should be viewed as an additional safeguard in addition to indicators covering data assurance and verification. While GRESB’s scoring system promotes the use of third-party assurance and/or verification, it does not yet mandate it as part of GRESB submissions, making these additional controls essential.

</details>

## GRESB Validation

Data quality procedures in the Lender Assessment are made up of one component:

<details>

<summary>Qualitative Approach</summary>

Also referred to as '**Manual Validation**,' this process involves reviewing all submitted evidence documents using a combination of human reviewers and automated tools.

<a href="/lender/completing-the-assessment/supporting-information/data-quality-and-validation/validation-qualitative.md" class="button primary">Qualitative Approach</a>

</details>

## Additional Quality Mechanisms

<details>

<summary>Assessment Correction Period </summary>

The Assessment Correction Period allows participants to respond to flagged issues and amend their data submissions before results are finalized. This step not only improves data quality but also builds confidence in the process by giving participants an opportunity to correct unintended reporting errors, either flagged by GRESB (as mentioned in the previous section) or by their own recognition.

The Assessment Correction Period being supported by targeted outreach and validation flags ensures that data issues are addressed in a transparent and timely manner before results are locked in.

</details>

<details>

<summary>Data Estimation Requirements</summary>

As a general rule, **GRESB Participants are required to use actual data** (i.e., non-estimated data) when reporting on aspects of Energy, GHG, Water, and Waste in the Performance Component.

However, when actual data is partially unavailable, GRESB allows participants to estimate in line with its data estimation requirements. The page below outlines these requirements in detail.

<a href="broken://pages/thcy0KqqqKPrgt9Om5DY" class="button primary">Data Estimation Rules</a>

</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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guides.gresb.com/lender/completing-the-assessment/supporting-information/data-quality-and-validation.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.