> 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/sfdr-reporting-solution/2026-sfdr-fund-assessment/reporting-characteristics/rc4-nature-of-entitys-business.md).
# RC4: Nature of Entity's Business
Cover image
:bullseye: Maximum Score
Not scored
:pen-to-square: Prefill
:check:Eligible
:shield-check: Validation
Evidence is not required
:arrow-trend-up: 2026 Updates
None
***
**What is the entity's core business?**
{% columns %}
{% column width="75%" %}
{% endcolumn %}
{% column width="25%" %}
{% endcolumn %}
{% endcolumns %}
## Assessment Instructions
Intent: What is the purpose of this indicator?
The entity’s primary business activities during the reporting year is useful for distinguishing infrastructure funds.
Input: How do I complete this indicator?
Select the option applicable to the reporting entity.
#### Terminology
**Major Renovations**
> Alterations that affect more than 50 percent of the total asset or cause relocation of more than 50 percent of regular building occupants. Major renovation projects refer to assets that were under construction at any time during the reporting year.
**New Construction**
> Includes all activities to obtain or change building or land use permissions and financing. Includes construction work for the project with the intention of enhancing the asset's value. Development of new facilities and additions to existing facilities can be treated as new constructions. New construction projects refer to facilities that were under construction at any time during the reporting year.
**Standing Investments**
> Assets where construction work has been completed and which are owned for the purpose of providing a service in exchange of an income. Also known as an operating asset.
***
---
# 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/sfdr-reporting-solution/2026-sfdr-fund-assessment/reporting-characteristics/rc4-nature-of-entitys-business.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.
