Chart types
The chart type decides what the reader sees first. A card highlights a number; a line shows whether it is improving or getting worse; bars compare sites; a table brings the detail to whoever needs to act. Choosing the right type makes the dashboard readable in seconds. Choosing the wrong type hides what matters, even with the correct numbers.
This page presents each available chart type, when to use it and how to configure it.
Which chart to use
| The question is… | Use | Example |
|---|---|---|
| How much? How many? | Card (Metric) or Gauge | Year-to-date result; audits performed this month |
| How did it evolve? | Line or Bars with dates | Month-by-month closing |
| Who is higher or lower? | Sorted horizontal bars | Site ranking |
| How is the total split? | Pie/Donut, Treemap, Waffle, stacked bars | Status of nonconformities |
| How do two categories cross? | Heat map, Mosaic, Table with colors | Result by site and by section |
| Are we close to the target? | Gauge, card with progress bar or target line | Survey sample achieved × target |
| Which are the cases? | Table | List of audits below target |
| Which words appear most? | Tag cloud | Most cited terms in notes |
| Where? | Map | Collections by location |
Bars
When to use: compare categories (sites, shifts, types) or show quantities by period.
| Variation | On screen | Use |
|---|---|---|
| Vertical bars | Bar (vertical) | Periods on the horizontal axis: month by month, week by week. |
| Horizontal bars | Bar (horizontal) | Rankings and categories with long names. |
| Stacked | Stacked | Total per group split by category. |
| Side by side | Unstacked | Compare categories within each group. |
| Percentage | Percentage | Share of each category, with 100% bars. |
Typical ranking setup:
- Type Bar, orientation Horizontal.
- Categories: the field (for example,
site) with Top values, Number of values large enough for all, Rank by the metric, Descending and without the "Other" group. - Metric: for example, Average of the result.
- Value labels visible and a target line.
Bar width and spacing are calculated automatically, based on the number of groups and the chart size in the dashboard. For wider bars, reduce the number of groups (for example, a monthly interval instead of daily) or make the chart wider in the dashboard.
Line
When to use: show how one or more indicators evolve over time.
- Horizontal axis: dates, with Date histogram and a fixed interval.
- Vertical axis: one or more metrics. Each becomes a line.
- Breakdown (optional): one line per category (for example, per region).
In the toolbar's appearance options, you can choose the line shape (straight, curved or stepped) and how to treat intervals without data: leave a gap, connect the points or use zero.
More lines than that make the chart hard to read. Use dashboard controls to let readers choose categories, or split into more than one chart.
Area
When to use: show volume over time, when the total also matters. A stacked area shows the total and the share of each category; a percentage area shows only the share.
Configuration is the same as for lines.
Card (Metric)
When to use: highlight a key number, usually at the top of the dashboard.
| Dimension | On screen | What it receives |
|---|---|---|
| Main value | Primary metric | The card's number (for example, the year's average). |
| Secondary value | Secondary metric | A smaller supporting number below the main one (for example, the same indicator last year, or the number of collections). |
| Maximum | Maximum value | Turns the card into a progress bar up to that value (for example, the interview target). |
| Break down by | Break down by | Creates one card per category, in a grid (for example, one card per site). |
Main value options:
- Name — the title shown on the card.
- Value format — number, percentage, decimals and suffix.
- Color — fixed color (Static) or color by value (Dynamic), with ranges. See Color by value.
- Trend line — a trend line in the card's background, when the data source has a time field.
Whenever possible, give the card context: a color by range, the target as the secondary metric or the comparison with the previous period. "82%" informs; "82% (target 70%)" in green guides.
Gauge
When to use: show a value against a scale, with minimum, maximum and target. For example, a tank level, the sample achieved in a survey or an audit score.
| Dimension | On screen | What it receives |
|---|---|---|
| Value | Metric | The measured value. |
| Minimum | Minimum value | The start of the scale. Can be a fixed value (Static value). |
| Maximum | Maximum value | The end of the scale (for example, the tank capacity or 100%). |
| Target | Goal value | A mark on the scale. |
Shapes available in the toolbar:
- Horizontal bullet and Vertical bullet — a straight bar, horizontal or vertical. The vertical one works well for tank and reservoir levels.
- Arc, Major arc and Circle — circular shapes.
Gauge color bands follow the same logic as color by value.
Without a maximum, the scale is calculated automatically from the data, and the gauge always looks "full". Set the maximum and the target as fixed values or by formula.
Table
When to use: show exact values, several metrics side by side, detailed rankings or the list of cases that require action.
| Dimension | On screen | What it receives |
|---|---|---|
| Rows | Rows | The row groupings (for example, site). Can have more than one, in sequence (region, then site). |
| Metrics | Metrics | The value columns (for example, one average per audit section). |
| Columns by category | Split metrics by | Creates one column per value of a field (for example, one column per month). |
Options for each column:
- Color by value — colors the cell or the text according to the value, creating a heat map in the table.
- Summary row — a summary row at the end of the table: sum, average, minimum, maximum or count.
- Alignment — left, center or right alignment.
- Hide column — hides the column (useful to sort by a value that doesn't need to appear).
In the table, column headers allow sorting. Clicking a cell creates a filter with that value in the dashboard.
To list individual collections (for example, audits below target with date, site and owner), use a Discover saved search added to the dashboard. See Save a search.
Pie and donut
When to use: show how a total is split, with few categories (up to 5 or 6).
- Slice by — the category of each slice.
- Size by — the metric that defines slice size, usually the number of collections.
- In the toolbar: labels inside or outside the slices, display as value or percentage, legend and the size of the center hole (donut).
With more than 6 categories, slices become too small to compare. Sorted horizontal bars show the same information more clearly.
Treemap
When to use: show proportions in nested categories, such as region and site. Each rectangle has an area proportional to its value, and rectangles of the same region are kept together.
Configure it like a pie, with two levels in Group by (first the general, then the specific).
Mosaic
When to use: compare proportions between two categories, such as status by site. Each column is a category, split by the other category, and the column width is proportional to its total.
Waffle
When to use: show a proportion as a grid of 100 squares. It is an alternative to the pie chart, easy to read in dashboards for non-technical audiences ("72 out of every 100 audits were approved").
Heat map
When to use: show patterns in two dimensions, such as result by site and by month, or occurrences by weekday and shift.
- Horizontal axis — the first category or the dates.
- Vertical axis — the second category.
- Cell value — the metric that defines each cell's color.
The palette and color bands are in the Cell value options.
Tag cloud
When to use: show the most frequent terms of a text field, such as the causes reported or the most repeated notes. The size of each word is proportional to its frequency.
It works best with option fields or short texts. In long notes, each full text is treated as one term.
Maps
When to use: see where collections were made, concentration by region or the geographic coverage of a field survey.
The map needs a location field in the data source (globe icon in the field list). Check in Discover whether the form's index includes this field before planning a map.
With the dashboard in edit mode, add the map from the Add menu. The most used layers are:
- Documents — each collection as a point.
- Clusters — points grouped by proximity, with the count in each group.
- Heat map — concentration of collections by area.
With thousands of collections, one point per collection makes the map slow and unreadable. Use the clusters layer or the heat map.