> 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/2.-completing-gresb-assessment/data-center-assessment.md).

# Data Center Assessment

### How is the assessment organized?

The **GRESB Data Center Assessment** framework breaks down portfolio evaluation into increasingly detailed levels:

<table><thead><tr><th width="195.6484375">Level</th><th width="540.55859375">Description</th></tr></thead><tbody><tr><td><strong>Component</strong></td><td><p>The highest-level category in the assessment. Each component represents a broad area of sustainability evaluation (e.g., Management, New Development &#x26; Operations, New Development, Operations, Innovation).<br></p><p>Choosing the assessment component(s) to submit is at the participant’s discretion. </p></td></tr><tr><td><strong>Aspect</strong></td><td>Each section is made up of several aspects, which group together related themes. For example, within the <em>Management</em> component, there are aspects such as <em>Leadership, Strategy, Transparency, Value Chain Engagement, Physical Risk &#x26; Resilience, and Certifications.</em></td></tr><tr><td><strong>Indicator</strong></td><td>The most detailed level of the hierarchy. Indicators are specific, measurable questions used to assess performance within an aspect (e.g., “TR1: Formal Sustainability Disclosure”). </td></tr></tbody></table>

<p align="center"><a href="/data-center-assessment/2.-completing-gresb-assessment/data-center-assessment/indicator-summary.md" class="button secondary" data-icon="book-open-lines">See Indicators List</a></p>

***

### How is indicator-level guidance organized?

Each indicator page in the GRESB Data Center Assessment is structured to provide both a high-level overview and detailed completion guidance:

1. At the top of each indicator page, **summary cards** provide a concise overview of the indicator’s key characteristics:

<table data-column-title-hidden data-view="cards" data-full-width="false"><thead><tr><th></th><th></th><th></th><th data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-bullseye">:bullseye:</i> Maximim Points</td><td><strong>Number of Maximum Points</strong></td><td><i class="fa-circle-info">:circle-info:</i> The maximum scores for the <a href="/data-center-assessment/2.-completing-gresb-assessment/data-center-assessment/material-issues/new-development.md">New Development</a> and <a href="/data-center-assessment/2.-completing-gresb-assessment/data-center-assessment/material-issues/operations.md">Operations</a> components are calculated based on split between development and operational sites. <a href="/data-center-assessment/1.-getting-started/scoring-basics.md#variable-score"><strong>Therefore, actual scores will vary based on each portfolio composition</strong>. </a></td><td></td><td></td><td></td></tr><tr><td><i class="fa-shield-check">:shield-check:</i> Validation</td><td><strong>Evidence required (or not)</strong></td><td>Indicates whether supporting evidence is required to validate the response and receive the maximum available points.</td><td></td><td></td><td></td></tr><tr><td><i class="fa-eye">:eye:</i>  Control dependent?</td><td><strong>Yes/No</strong></td><td>Shows whether the indicator's score is adjusted the entity's reported level of control in the Transparency Score, <em>Control-Weighted</em></td><td><a href="/data-center-assessment/1.-getting-started/scoring-basics.md#transparency-score-control-weighted">Scoring Basics</a></td><td></td><td></td></tr></tbody></table>

2. Below the summary cards, the **detailed indicator** **guidance** is provided:

<table><thead><tr><th width="188"></th><th></th></tr></thead><tbody><tr><td><strong>Indicator Question</strong></td><td>The exact question as presented in the assessment.</td></tr><tr><td><strong>Indicator Visual</strong></td><td>An image of the indicator, including all answer selections.</td></tr><tr><td><ul><li><strong>Intent</strong></li></ul></td><td>Explains the purpose of the indicator within the assessment.</td></tr><tr><td><ul><li><strong>Input</strong></li></ul></td><td>Provides instructions on how to complete the indicator and clarifies relevant terminology.</td></tr><tr><td><ul><li><strong>Validation</strong></li></ul></td><td>Outlines validation requirements for submitted evidence (where applicable).</td></tr><tr><td><strong>Scoring</strong></td><td>Breaks down how the indicator is scored, including how selections affect the final score.</td></tr></tbody></table>


---

# 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/data-center-assessment/2.-completing-gresb-assessment/data-center-assessment.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.
