> 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/completingassessments/2026-real-estate-assessment/re/perf/en/en1-non-operational-energy.md).
# EN1: Non-Operational Energy
## Assessment Instructions
{% hint style="info" %}
Participants must report this metric at the asset level.
GRESB automatically populates this indicator in the assessment response once participants have aggregated asset-level data from the Asset Portal.
When using the Asset Spreadsheet to upload asset-level data, GRESB recommends reviewing the instructions below in conjunction with the corresponding spreadsheet tab. The Cell Code column in the Input section indicates where to report each metric in the spreadsheet.
Asset Portal Guide
Click here to download a read-only version of the Asset Spreadsheet.
{% endhint %}
***
Input: How do I complete this metric?
| | |
|---|
| :chart-simple: Data | :file-xls: Cell Code | :message-pen: Instructions |
Non-Operational (EV Charging Stations) | BJ7 | Report energy consumption related to Electric Vehicle (EV) Charging Stations installed in the asset.
The scope of this field is limited to EV charging stations as it represents the most common and material type of energy consumption considered non-operational for a standing asset. |
Validation: What evidence is required?
This indicator is subject to automatic validation. No evidence is required.\
\
Refer to the page below for guidance on how to resolve automatic validation errors and warnings.\
\ Validation Basics
## Scoring
This metric 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/completingassessments/2026-real-estate-assessment/re/perf/en/en1-non-operational-energy.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.
