> For the complete documentation index, see [llms.txt](https://docs.betterbuilding.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.betterbuilding.io/user-guide/2d-building/building/modelling/reporting.md).
# Reporting
Reporting enables the preferred nomination of Levels and Zones when running a simulation and producing a report. This feature is useful for meeting specific reporting requirements, such as a zone-by-zone reporting requirement for daylight modelling.
## **Level Name**
Levels are equivalent to floors, with the total number of Levels equal to the total number of floors in the building. A Level Name can be customised via the {level.title} and {level.number} variables.
To account for a Level Name, navigate to 'Modelling' and select 'Reporting'. Next, copy the variable, such as {level.number} and click Save. The {level.number} will now be included in your reporting.
## Zone Name
Zone Names are provided when a Zone is created. A Zone Name can be customised via the {level.title} , {level.number}, {zone.title} and {zone.number} variables.
To account for a Zone Name, navigate to 'Modelling' and select 'Reporting'. Next, copy the variable, such as {zone.number} and click Save. The {zone.number} will now be included in your reporting.
## Zone Name (Grouped)
If using the Grouping feature, A Zone Name (Grouped) can be customised via the {level.title} , {level.number}, {zone.title}, {zone.number} and {group.title} variables.
To account for a Zone Name (Grouped), navigate to 'Modelling' and select 'Reporting'. Next, copy the variable, such as {zone.title}, and click Save. The {zone.title} will now be included in your reporting.
---
# 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://docs.betterbuilding.io/user-guide/2d-building/building/modelling/reporting.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.
