> 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/supporting-information.md). # Supporting Information Use these pages alongside the indicator guidance to understand key concepts, define your reporting scope, and complete the assessment accurately.

			Cover image
Defining the Reporting Portfolio	Before you start: how to define your reporting scope and split your portfolio into reporting entities.	Defining the Reporting Portfolio	GRESB Guides Icons (30).png
Control Input	For RC4 and control-dependent indicators: how to report site-level control and how it affects your Transparency Score, Control-Weighted.	Control Input	GRESB Guides Icons (29).png
Terminology	Find definitions for key concepts used throughout the assessment	Terminology	GRESB Guides Icons (28).png

--- # 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/supporting-information.md?ask=&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.