> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/copilot-assistant/improving-results.md).

# Improving Results

Prepare your building data and prompts to get more useful Copilot Assistant results.

Copilot Assistant works best when your building data has clear structure and your questions define the intended scope. Use these pages to improve the quality, relevance, and usefulness of its answers.

## Prepare Your Data

[Data Requirements](/collection/copilot-assistant/improving-results/data-requirements.md) explains the asset hierarchy, names, types, measurements, units, time series, freshness that help the Copilot Assistant understand your building data and produce more useful results.

## Write Better Prompts

[Prompting Guide](/collection/copilot-assistant/improving-results/prompting-guide.md) shows how to specify locations, assets, metrics, units, and time ranges. It also covers common ambiguities and ways to refine a request when the result does not match your intent.

Start with the data requirements, then use the prompting guide to turn a business question into a precise request.


---

# 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.buildings.ability.abb/collection/copilot-assistant/improving-results.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.