> 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/hvac/hvac-templates/managed/heat-recovery-ventilation.md).

# Heat Recovery Ventilation

A heat recovery ventilation (HRV) system is designed to improve indoor air quality while minimising energy loss. It typically consists of supply and exhaust fans, a heat exchanger, filters and controls. The system draws in fresh outdoor air and removes stale indoor air simultaneously. The heat exchanger transfers thermal energy between the incoming and outgoing air streams, reducing heating or cooling demands on the building. Filters remove particulates from both air streams, and controls regulate airflow rates and system operation based on occupancy, indoor air quality or time schedules.

It is composed of:

* Air Handling Unit(s)
* Air Terminal(s)


---

# 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/hvac/hvac-templates/managed/heat-recovery-ventilation.md?ask=<question>&goal=<user_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.
