> 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/entity-and-reporting-characteristics/reporting-characteristics/rc3-floor-area-metrics.md).

# RC3: Floor Area Metrics

<table data-column-title-hidden data-view="cards" data-full-width="false"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><i class="fa-bullseye">:bullseye:</i> Maximum Score</td><td><strong>Not scored</strong></td><td></td><td></td></tr><tr><td><i class="fa-pen-to-square">:pen-to-square:</i> Prefill</td><td><i class="fa-check">:check:</i> <strong>Eligible</strong></td><td></td><td></td></tr><tr><td><i class="fa-shield-check">:shield-check:</i> Validation</td><td><strong>None</strong></td><td></td><td></td></tr></tbody></table>

***

**Metrics are reported in:**

{% columns %}
{% column width="41.66666666666667%" %}

<figure><img src="/files/IhVAi1ZNWw7EOyoOuYXC" alt=""><figcaption></figcaption></figure>
{% endcolumn %}

{% column width="58.33333333333333%" %}

{% endcolumn %}
{% endcolumns %}

## Assessment Instructions

<details>

<summary><strong>Intent</strong>: What is the purpose of this indicator?</summary>

Metrics are needed to ensure comparability for reporting purposes. Set the reporting units used by the entity.&#x20;

</details>

<details>

<summary><strong>Input</strong>: How do I complete this indicator?</summary>

Select one of the options, and use it consistently when reporting the floor area of the portfolio.

</details>

<details>

<summary><strong>Validation</strong>: What evidence is required?</summary>

No evidence required.

</details>

## Scoring

This indicator is not scored.

***


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guides.gresb.com/lender/completing-the-assessment/2026-lender-assessment/entity-and-reporting-characteristics/reporting-characteristics/rc3-floor-area-metrics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.