> 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/completing-gresb-assessments/welcome.md). # Welcome **Welcome to GRESB Guides for the Infrastructure Asset Assessment.** This resource is organized to mirror the assessment process, helping you navigate every stage of the GRESB cycle from preparation through results analysis. **Learn about why GRESB launched this resource and how guidance has improved in 2026** [**here**](/completing-gresb-assessments/welcome/whatsnew.md)**.** #### *Prepare* **Getting Started:** Understand initial setup and assessment basics, including portal access, portfolio scoping, scoring principles, and GRESB's governance and vision.
Cover image
Setup & NavigationAssessment Portal Guide
Structure & ScopeAssessment Structure & Scope
Scoring BasicsScoring Basics
#### *Execute* **Completing GRESB Assessments:** Review everything needed to complete an assessment, including indicator instructions, evidence requirements, scoring methodologies, and frequently asked questions.
Assessment Guidance2026 Asset Assessment
Supporting InformationSupporting Information
#### *Engage* **Leveraging your Data:** Learn about benchmarking, analytics, and data management tools to maximize insights engagement.
Cover image
Results InsightsBenchmark Report
Analysis ToolsPortfolio Analysis Tool
Data ManagementBroken link
--- # 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/completing-gresb-assessments/welcome.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.