> For the complete documentation index, see [llms.txt](https://www.center.daxium-air.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.center.daxium-air.com/user-documentation/build/building-the-reporting.md).

# Building the Reporting

Generate professional reports from your field data in Word, Excel or PowerPoint.

Daxium-Air includes a powerful reporting engine that lets you generate documents from your submission data using customizable templates. Supported formats are Word, Excel, PPT & PDF. The reports can then be sent automatically or periodically by email to receivers (either Daxium-Air users, or external users).

This section covers:

* [General Concepts](/user-documentation/build/building-the-reporting/general-concepts.md) — templates, tags, and delivery fundamentals.
* [Syntax & Functions](/user-documentation/build/building-the-reporting/syntax-functions.md) — full tag reference and available functions.
* [Report Templates](/user-documentation/build/building-the-reporting/report-templates.md) — format-specific guidance for Word, Excel, and PowerPoint.
* [Report Types](/user-documentation/build/building-the-reporting/report-types.md) — scheduled and automatic report delivery.


---

# 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://www.center.daxium-air.com/user-documentation/build/building-the-reporting.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.