> 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/lender/completing-the-assessment/2026-lender-assessment.md).

# 2026 Lender Assessment

#### **How is the assessment organized?**

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

<details>

<summary>Assessment Levels</summary>

<table><thead><tr><th width="145.6484375">Level</th><th width="540.55859375">Description</th></tr></thead><tbody><tr><td><strong>Component</strong></td><td>The highest-level category in the assessment. Each component represents a broad area of sustainability evaluation (e.g., Management and Performance).</td></tr><tr><td><strong>Aspect</strong></td><td>Each component 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>Policies</em>, <em>Reporting</em>, and <em>Risk Management</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., “Does the lender track GHG emissions data for standing assets in its loan portfolio?”). See more on what makes up an indicator <a href="#indicator-architechture">below</a>.</td></tr></tbody></table>

</details>

<table data-header-hidden data-full-width="false"><thead><tr><th width="446.3125"></th><th width="228.3046875"></th></tr></thead><tbody><tr><td><i class="fa-block-brick">:block-brick:</i> Component</td><td><i class="fa-bullseye">:bullseye:</i> Max Score</td></tr><tr><td><a href="/lender/completing-the-assessment/2026-lender-assessment/entity-and-reporting-characteristics.md" class="button primary" data-icon="address-card">Entity &#x26; Reporting Characteristics</a></td><td><strong>Not</strong> <strong>Scored</strong></td></tr><tr><td><a href="/lender/completing-the-assessment/2026-lender-assessment/management-component.md" class="button primary" data-icon="ranking-star">Management</a></td><td><strong>94 Points</strong></td></tr><tr><td><a href="/lender/completing-the-assessment/2026-lender-assessment/performance-component.md" class="button primary" data-icon="building-magnifying-glass">Performance</a></td><td><strong>6 Points</strong></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/lender/completing-the-assessment/2026-lender-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.