> 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.md).
# Data Quality and Validation
## Introduction
GRESB's Data Quality Commitment
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.
These checks are designed to reduce the risk of misreporting and ensure the integrity of the data submitted to GRESB.
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.
## GRESB Validation
Data quality procedures are made up of two complementary components:
Quantitative Approach
This process focuses on individual data points uploaded to the portal. It applies additional controls to quantitative data points that are not subject to Manual Validation - i.e., where no supporting evidence is required. The emphasis is on data points that are prone to errors because they are generally more complex and granular to calculate.
Quantitative Approach
Qualitative Approach
Also referred to as '**Manual Validation**,' this process involves reviewing all submitted evidence documents using a combination of human reviewers and automated tools.
Qualitative Approach
## Additional Quality Mechanisms
Data Estimation Requirements
As a general rule, **GRESB requires participants to use actual data** (i.e., directly measured from utilities or meters, documented, or derived using recognized standards) when reporting material performance data to the infrastructure asset assessments. Broad extrapolations of data and general estimates should not be reported.
---
# 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.md?ask=&goal=
```
`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.