> 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-qualitative.md).

# Validation: Qualitative

## Manual Evidence Validation

### Validation Scope

<details>

<summary>What is manually validated?</summary>

GRESB and subject matter experts from [Sustainability Assurance Services (SAS)](https://www.sustainabilityassured.com/) manually verify the following content:

1. **Evidence uploaded to the indicators that require it.** In most cases, GRESB and its third-party validation provider validate this evidence against GRESB’s requirements. Refer to the' Criteria' section below for a summary of indicators subject to manual validation and their specific requirements.
2. **All** **scored ‘Other’ answers**. Most indicators allow participants to report an additional option if it is not already included in the indicator’s assessment choices. These ‘Other’ answers are also subject to manual validation. ‘Other’ answers should not be duplicates or subsets of existing options. Multiple ‘Other’ answers can be reported, but only one will count toward the final score, as long as it meets the acceptance criteria.
3. **Information related to third parties**, such as assurance, audit, and certification standards.

</details>

### Validation Criteria

<details>

<summary>Evidence Format</summary>

**Document**: Participants may upload multiple documents of any file type. GRESB encourages participants to follow the following documentation best practices to ensure that validators can identify relevant information as efficiently and clearly as possible:

* Use an evidence cover page (see GRESB’s template [here](https://gresb-prd-public-eu.s3.eu-central-1.amazonaws.com/2025/Evidence_Cover_page_2025.pdf)) or open text box to specify where evidence for each selection can be found.
* Participants may upload evidence as a document or an active hyperlink.
* When using multiple documents, consolidate them into one file (but avoid using zip files).
* Make sure section headings and page numbers are clear.

**Hyperlink**: The evidence must be accessible within two clicks. Note that to support selections pertaining to public availability, participants must upload a hyperlink.

</details>

<details>

<summary>Reporting Year Applicability</summary>

Regardless of whether the indicator is manually validated, **all assessment answers must refer to the reporting year identified in indicator&#x20;*****RC1: Reporting year*****.**

A response to an indicator must be true at the close of the reporting year; however, the response does not need to have been true for the entire reporting year.&#x20;

* For example, if a policy was implemented one month before the end of the reporting year, this is acceptable; it does not need to have been in place for the entire reporting year.

**For manually validated indicators, it is mandatory to clearly specify the year to which the evidence corresponds within the evidence or open text box.**

</details>

<details>

<summary>Reporting Entity Applicability</summary>

Answers must directly apply to the entity identified in EC1, i.e., the investable entity for which participants submit an Assessment response, regardless of whether the indicator is manually validated.

When a participating entity belongs to a larger investment entity, management organization or group of companies (the 'organization'), it must clearly explain the relationship between the entity and the organization. This ensures that group-level answers or evidence are appropriately linked to the reporting entity. This clarification can be provided within the evidence itself or in an open text box.

* **Note for indicator PR1 ‘Physical Climate Risk & Resilience Management’ in the Management component** (i.e., "processes in place to identify, assess, and manage physical climate risks"): GRESB requires evidence to be specific to the reporting entity identified in EC1. References to the overarching organization cannot be used as substitutes for entity-level risk assessment outcomes.

</details>

<details>

<summary>Indicator Applicability</summary>

GRESB does not consider evidence submitted under other indicators or evidence from previous submissions.

Participants must upload evidence directly under the relevant indicator for the validation team to consider it.

</details>

<details>

<summary>Language </summary>

As of 2025, GRESB accepts evidence in any language. However, the systems must be able to read the text contained in the file. Information or text contained in pictures will only be accepted if accompanied by a translation.

Note that information provided in open text boxes that appear in the Reports will be displayed exactly as submitted, in the original language.

</details>

<details>

<summary>Summary of Indicator-Specific Requirements</summary>

The table below highlights the manually validated indicators in the Data Center Assessment. For detailed guidance on the evidence required for each indicator, refer to the ‘Validation’ section on the specific page for that indicator.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><h4><strong>Management Component</strong></h4></td><td><p></p><ul><li>LE3
</li><li>ST1
</li><li>TR1
</li><li>TR2
</li><li>VC1
</li><li>VC2
</li><li>PR1</li></ul></td></tr><tr><td><h4><strong>Operations &#x26; New Development Component</strong></h4></td><td><ul><li>HS2
</li><li>HS3
</li></ul><p>
</p><ul><li>GH2
</li></ul><p>
</p><ul><li>GH4
</li><li>ES2
</li><li>CO2
</li></ul></td></tr><tr><td><h4><strong>New Development Component</strong></h4></td><td><ul><li>SD2
</li><li>SD3
</li><li>PC2
</li><li>PC4</li></ul></td></tr><tr><td><h4> <strong>Operations Component</strong></h4></td><td><ul><li>EN2
</li></ul><p>
</p><ul><li>EN4
</li></ul><p>
</p><ul><li>WT2
</li></ul></td></tr></tbody></table>

</details>

### Validation Outcomes

<details>

<summary>What are the impacts of each validation decision?</summary>

**Validation Outcomes are provided at the selection level**. Validators will make one of the two decisions below depending on the degree to which evidence meets GRESB’s requirements.&#x20;

Each validation outcome corresponds with a scoring weight that impacts the selections' final score. See the [Scoring Basics](https://app.gitbook.com/o/Bveezar1nazy8275RL7l/s/31ovOsfsdlwYDiJclXFF/outcomes/scoring-basics) page for more information.

#### 'Other' Answers

<table><thead><tr><th width="134.0390625">Validation status</th><th>Explanation</th><th>Scoring impact</th></tr></thead><tbody><tr><td>Accepted</td><td>'Other' answer falls outside the provided options and fulfills indicator requirements.</td><td>Full points</td></tr><tr><td>Duplicate</td><td>'Other' answer fulfills indicator requirements but duplicates an already selected answer.</td><td>No points will be awarded for this answer</td></tr><tr><td>Not Accepted</td><td>No points will be awarded for this answer'Other' answers do not fulfill indicator requirements.</td><td>No points will be awarded for this answer</td></tr></tbody></table>

#### Evidence and Open Text Boxes

| Validation Status | Explanation                                                                               | Scoring Impact                                                                                    |
| ----------------- | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
| Accepted          | Evidence fully meets the validation requirements.                                         | Full points, resulting in the application of the full multiplier (100%) to that selection's score |
| Not Accepted      | Evidence does not meet general requirements and/or does not support the selected options. | No points, resulting in a 0% multiplier to that selection's score                                 |

</details>

## Reporting Boundaries Review

***

**Download GRESB's Evidence Cover Page Template**

{% embed url="<https://gresb-prd-public-eu.s3.eu-central-1.amazonaws.com/2025/Evidence_Cover_page_2025.pdf>" %}


---

# 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-qualitative.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.