> 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/completing-gresb-assessments/completing-the-assessment/2026-asset-assessment/entity-and-reporting-characteristics/entity-characteristics/ec3-entity-commencement-date.md).
# EC3: Entity Commencement Date
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 year of operation commencement?**
{% columns %}
{% column width="33.33333333333333%" %}
{% endcolumn %}
{% column width="66.66666666666667%" %}
{% endcolumn %}
{% endcolumns %}
## Assessment Instructions
Intent: What is the purpose of this indicator?
Establish the age of the entity.
Input: How do I complete this indicator?
**Operation commencement:** State the year when the entity first commenced or is expected to commence operation.
If the reporting entity represents a single facility, then the year entered should be when that facility commenced operation. If the reporting entity represents a portfolio of facilities being assessed as one asset (i.e. multi-facility asset) then it should be when the first facility in the portfolio commenced operation.
If the entity is still under construction, the expected year that operations will commence should be given.
If the entity is both in construction and operational, then enter the year in which the first part of the project commenced operations.
Validation: What evidence is required?
No evidence required.
## 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 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/completing-gresb-assessments/completing-the-assessment/2026-asset-assessment/entity-and-reporting-characteristics/entity-characteristics/ec3-entity-commencement-date.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.
