> 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/publicdisclosure/completing-the-assessment/2026-public-disclosure-guidance.md). # 2026 Public Disclosure Guidance #### **How is the assessment organized?** The **GRESB Public Disclosure Assessment** framework breaks down portfolio evaluation into increasingly detailed levels:
Assessment Levels
LevelDescription
AspectThe Public Disclosure Assessment comprises several aspects that group together related themes (e.g., Disclosure Methods, Governance of Sustainability).
IndicatorThe most detailed level of the hierarchy. Indicators are specific, measurable questions used to assess performance within an aspect (e.g., “Sustainability performance via a stand-alone Sustainability Report”).
:block-brick: Aspect:bullseye: Max Score
Entity CharacteristicsNot Scored
Disclosure Methods13 Points
Governance of Sustainability22 Points
Implementation6 Points
Operational Performance16 Points
Stakeholder Engagement13 Points
--- # 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/publicdisclosure/completing-the-assessment/2026-public-disclosure-guidance.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.