> For the complete documentation index, see [llms.txt](https://docs.vitaracharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vitaracharts.com/ibcs-user-guide/certified-charts/multi-tier-column-chart.md).
# Multi-tier Column chart
## Multi-tier column chart
### **Description**
A multi-tier column chart can be used to compare different situations (actual, planned, anticipated, etc.) over a specified time period (months in a year, several years, etc.).
### **Demo video**
{% embed url="" %}
## **Scenario planning**
Please review mapping scenarios for a better understanding of how scenario planning in VitaraCharts.
For this type of chart, the scenarios are mapped using **metrics**. So the user will need to define separate metrics (for the same set of category elements) representing each scenario. As an example, if you are looking at sales data across months and are interested in looking at how the actual and planned scenarios compare, you will have to define two metrics
* first one for the actual sales data
* second one for the planned sales data
---
# 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.vitaracharts.com/ibcs-user-guide/certified-charts/multi-tier-column-chart.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.