> 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/entity-characteristics/ec1-reporting-entity.md).
# EC1: Reporting Entity
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
***
**Reporting entity:**
{% columns %}
{% column width="83.33333333333334%" %}
{% endcolumn %}
{% column width="16.666666666666657%" %}
{% endcolumn %}
{% endcolumns %}
## Assessment Instructions
Intent: What is the purpose of this indicator?
Identify the reporting (participating) entity. The entity name will be used to identify the entity on the GRESB portal and will be displayed in the entity’s SFDR Report.
Input: How do I complete this indicator?
Complete all applicable fields.
\*Values in the Entity Characteristics (EC) aspect are fixed to one entity, regardless of assessment year. In order to update these please select the 'Manage Entity' setting in the 'Assessment Portal').
#### Terminology
**Entity name**
> Name of the fund or portfolio for which the Assessment is submitted. In the case of listed funds, the entity name is the legal name of the fund, also used for identification on international stock exchanges. In the case of non-listed entities, the entity name identifies the investable fund or portfolio for which the Assessment is submitted.
**Fund Manager Organization name (may be same as entity name)**
> Legal name of the organization responsible for the overall management, governance and oversight of the entity.
***
---
# 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/entity-characteristics/ec1-reporting-entity.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.
