> 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/supporting-information/asset-and-portfolio-classification.md).

# Asset & Portfolio Classification

[Indicator RC4](/lender/completing-the-assessment/2026-lender-assessment/entity-and-reporting-characteristics/reporting-characteristics/rc4-property-geography.md) of the GRESB Lender Assessment asks participants to identify the location associated with the reporting entity. 

This page aims to help participants understand the locations available for selection and how an entity's asset composition determines its overall portfolio classification.

***

Every reporting entity must have a **primary** location (i.e., the location in which the majority of the portfolio's assets exist). GRESB uses this information to assign the entity to a predefined peer group and establish benchmarks. 

GRESB identifies an entity's primary location through the following scenario:

* The entity must self-identify its portfolio-level/primary location via indicator RC4. 

Regardless of which scenario above applies, participants can refer to GRESB's thresholds below to understand an entity's primary classification.

<details>

<summary><strong>Primary Location Thresholds</strong></summary>

#### Primary Location Thresholds

An entity’s primary property location is based on the most specific geography that accounts for at least 60% of its Gross Asset Value (GAV).

For example, if 60% or more of an entity’s GAV is located in one country, this country becomes the entity’s primary location.

However, if less than 60% of an entity’s GAV is located in one country, but 60% or more of the entity’s GAV is located in a subregion (e.g., Eastern Asia), this subregion becomes the entity’s primary location.

The logic above also applies to the subregion and region.

</details>


---

# 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/supporting-information/asset-and-portfolio-classification.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.