> 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/workflows/energy-efficiency/advanced-hvac/demand-controlled-ventilation.md).
# Demand-controlled ventilation
Demand-controlled ventilation is a ventilation control strategy that maintains indoor air quality by continuously adjusting the ventilation rate provided to a Space in response to changes in occupancy, usually measured by indoor carbon dioxide levels. The observable effects of modelling demand-controlled ventilation, compared to a fixed ventilation rate, would include;
* Decreased outside air flow rate at decreased occupancy rates (see HVAC Nodes report on Design Day simulation)
* Decreased space cooling energy
* Decreased space heating energy
Advanced HVAC enables demand-controlled ventilation on Air Handling unit systems to be considered.
{% hint style="success" %}
Model demand-controlled ventilation by selecting ‘Air Terminal’ settings and nominate ‘Yes’ for Control of Outdoor Air. Next, select the corresponding Air Handling Unit under the 'Outside Air System' settings, and then set Demand-Controlled Ventilation to 'Yes'. Hit 'Update, then 'Save'.
{% endhint %}
---
# 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/workflows/energy-efficiency/advanced-hvac/demand-controlled-ventilation.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.
