> For the complete documentation index, see [llms.txt](https://help.modelreef.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.modelreef.io/syntax/chart-and-table-syntax/picking-chart-types.md).

# Picking Chart Types

This article explains how to **pick chart types** for time series in Model Reef.

You will learn:

* Which chart types are available.
* When to use each type.
* How to match chart types to business questions.

Choosing the right chart type makes patterns and differences easier to understand.

{% stepper %}
{% step %}

### Available chart types

Depending on context, you can usually choose from:

* Line charts.
* Bar charts.
* Stacked bar charts.
* Area charts.
* Combined line and bar charts.
* KPI cards.
* Table views.

All chart types operate on the same underlying time series.
{% endstep %}

{% step %}

### Line charts

Use line charts for:

* Trends over time.
* Comparing multiple series with similar units.
* Visualising growth or decline paths.

Examples:

* Revenue vs EBITDA.
* Cash balance under different cases.
* Headcount over time.

Lines are best when the shape and direction of change matter.
{% endstep %}

{% step %}

### Bar and stacked bar charts

Use bar charts for:

* Comparing magnitudes across periods.
* Viewing contributions of different series by period.

Use stacked bar charts when you want to see:

* How categories add up to a total in each period.
* The composition of revenue, costs or capex by component.

Examples:

* Revenue split by product.
* Opex split by department.
* Capex by project per year.
  {% endstep %}

{% step %}

### Area charts

Area charts are useful when:

* You care about both trend and magnitude.
* You want to emphasise cumulative feel without literal cumulative sums.

They work well for showing totals where the fill visually encodes size.
{% endstep %}

{% step %}

### Combined line and bar charts

Combined charts can be helpful when:

* You want to plot a primary series as bars, for example revenue.
* You want to overlay a secondary series as a line, for example margin percentage or headcount.

Use this when two related metrics have different units but share a time axis.
{% endstep %}

{% step %}

### KPI cards and tables

KPI cards show single numbers such as:

* Latest period EBITDA.
* Peak cash requirement.
* NPV or IRR.

Tables show more detailed breakdowns and may complement charts when you need precise values.
{% endstep %}

{% step %}

### Choosing chart types by question

Match chart types to questions such as:

* "How is this changing over time?" → line or area.
* "What is the composition by period?" → stacked bar.
* "How do two metrics move together?" → combined line and bar.
* "What is the latest or total value?" → KPI card or table.

Choosing appropriately keeps dashboards focused and legible.
{% endstep %}
{% endstepper %}

***

## Related articles

* [Category Picker](/syntax/understanding-the-interface/category-picker.md)
* [Category Selection](/syntax/variables-syntax/category-selection.md)
* [Mapping Variable Types](/help/importing-and-data-inputs/mapping-variable-types.md)
* [Build a Board Reporting Pack](/how-tos/dashboards-and-reporting/build-a-board-reporting-pack.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.modelreef.io/syntax/chart-and-table-syntax/picking-chart-types.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.