Complete examples
The examples on this page show dashboards built from scratch, from the form to the saved dashboard. Each one brings together several features from the previous pages and can serve as a starting point for similar dashboards. The names of sites, divisions and fields are illustrative: adjust them to the names in your form, as checked in Discover.
| Example | Features used |
|---|---|
| 5S audit: monthly closing and year to date | Cards with color by value, per-chart time range, target line, several metrics, ranking, heat-map table, chained controls. |
| Several forms in one dashboard | Data source with wildcard, Filters grouping with _index, stacked bars, per-chart filter. |
| Rates and funnels of a field survey | Formulas with count(kql=...), funnel with Filters, age bands, weekly trend. |
| Tank levels from readings | Formula with last_value, card with progress bar per tank, gauge. |
| Defect count in a transposed index | Sum of the value field, ranking by label, monthly trend. |
5S audit: monthly closing and year to date
A 5S audit form with five sections (Sort, Set in order, Shine, Standardize and Sustain), applied monthly at several sites. The target is 70% compliance. The dashboard should show each month's closing, the year to date, the result by pillar and the site ranking.
1. Prepare the form
Calculated fields by tag, one per pillar and one for the total, with the percentage from 0 to 100. Question names following the standard:
| Field | Content |
|---|---|
perc-total-5s | Total audit percentage |
perc-sort | Sort pillar percentage |
perc-set-in-order | Set in order pillar percentage |
perc-shine | Shine pillar percentage |
perc-standardize | Standardize pillar percentage |
perc-sustain | Sustain pillar percentage |
division, region, site | Identification of the audited site |
Submit a test audit and check in Discover that every perc-* field arrives as a number.
2. Dashboard structure
| Position | Content | Time range |
|---|---|---|
| Top | Controls: Division, Region, Site | — |
| Row 1 | 6 cards: 5S Total and one per pillar | Year to date (own) |
| Row 2 | 5S Total month by month, with target line | Dashboard's |
| Row 3 | Trend by pillar (5 lines) | Dashboard's |
| Row 4 | Site ranking and site × pillar table | Dashboard's |
3. Year-to-date cards
For each of the 6 indicators:
- Add → Visualization, type Metric.
- Primary metric: Average of
perc-total-5s(then one card for eachperc-*). - Name: "5S Total" (or the pillar name).
- Value format: Number, 1 decimal,
%suffix. - Color: Dynamic, with the ranges:
| From | Color |
|---|---|
| 0 | Red #E53E3E |
| 60 | Yellow #ECC94B |
| 70 | Light green #9AE6B4 |
| 80 | Green #48BB78 |
| 85 | Dark green #2F855A |
- Save and return.
- In the dashboard, ⋯ → Settings on the card → Apply custom time range → year to date (see Most used ranges).
- Card title: "5S Total – year to date".
After creating the first card, use ⋯ → Duplicate and change only the field and name for the other five.
4. 5S Total month by month
- Type Bar (vertical).
- Horizontal axis:
date, Date histogram, Minimum interval: Month. - Vertical axis: Average of
perc-total-5s, Name "5S Total", Number with%suffix. - Add layer → Reference lines: Static value
70, Name "Target 70%", dashed line. - Value labels: Show.
- Vertical axis: Bounds → Custom, from 0 to 100. Axis title → Custom: "Compliance (%)". Horizontal axis: Axis title → Custom: "Month".
- Title: "5S Total – Monthly Closing (%)".
5. Trend by pillar
- Type Line.
- Horizontal axis:
date, Month. - Vertical axis: five metrics, all Average, with the same format (Number,
%suffix):perc-sort,perc-set-in-order,perc-shine,perc-standardize,perc-sustain. Give each the pillar name and its own color. - Target line at 70 and axis from 0 to 100.
- Legend: Bottom.
- Title: "Trend by Pillar (%)".
In stacked bars, the five percentages would be added, and each month would get close to 400% or 500%. To compare percentages, use lines or side-by-side bars.
6. Site ranking
- Type Bar, orientation Horizontal.
- Categories:
site, Top values, Number of values 20, Rank by the average ofperc-total-5s, Descending, without the "Other" group. - Metric: Average of
perc-total-5s,%suffix. - Target line at 70.
- Value labels: Show.
- Title: "Site Ranking – 5S Total (%)".
7. Site × pillar table
- Type Table.
- Rows:
site, Top values, 20 values. - Metrics: six Average metrics:
perc-total-5sand the five pillars, with short names ("Total", "Sort"…). - In each metric: Color by value → Cell, with the same ranges as the cards.
- Summary row: Average in each column, for the overall average row.
- Title: "Result by Site and Pillar (%)".
8. Controls and saving
- Add → Controls, in order:
division,region,site, all Options list, with a readable Label. - In the dashboard time picker, choose Last 1 year (or year to date).
- Save, with the title "5S – Monthly Closing and Year to Date" and Store time with dashboard selected.
- Test: choose a site and check that the cards, charts and table change together. The cards stay on year to date.
Several forms in one dashboard
Each division has its own best-practices form, with the same questions and the same question names. The indices have descriptions with a common part: best-practices-division-a, best-practices-division-b, best-practices-division-c. The dashboard should show how many best practices each division registered per month and the approval status by site.
Fields used:
| Field | Content |
|---|---|
site | Site that registered the best practice |
bp-own | 1 when the best practice is the site's own |
bp-adopted | 1 when the best practice was adopted from another site |
approval | Evaluation result: "Approved", "Rejected" or "Needs adjustments" |
1. Data source
- ☰ → Stack Management → Data Views → Create data view.
- Name: "Best Practices – All Divisions".
- Index pattern:
*best-practices-division*. Check that the three indices appear on the right. - Timestamp field:
date. - Save.
2. Check in Discover
- Open Discover with the new data source and a wide time range.
- Click the
_indexfield: the three indices should appear, with the number of records in each. - Search for
siteandapprovalin the field list: each should appear only once. If different names appear for the same question, the forms are not standardized.
3. Best practices by month and division
- Type Bar, Stacked.
- Horizontal axis:
date, Month. - Vertical axis: Count of records, Name "Best practices".
- Breakdown: the Filters function, with one filter per index:
| Expression | Label |
|---|---|
_index : *division-a* | Division A |
_index : *division-b* | Division B |
_index : *division-c* | Division C |
- Value labels: Show. Legend: Bottom.
- Title: "Best Practices Registered by Month and Division".
To check: the sum of all bars should equal the total responses of the three forms in the time range. If it is lower, a filter is not matching the right index.
4. Own and adopted by site
- Type Bar, Horizontal, Stacked.
- Categories:
site, Top values, 20 values, Descending, without "Other". - Metrics: Sum of
bp-own("Own") and Sum ofbp-adopted("Adopted"). - Title: "Best Practices by Site".
5. Not-approved card
- Type Metric, Count of records, Name "Not approved".
- In the editor's search bar:
approval : "Rejected". - Color: Static, red
#E53E3E.
6. Status by site
- Type Bar, Horizontal, Stacked.
- Categories:
site, Top values. - Metric: Count of records.
- Breakdown:
approval, with Include documents without this field on, to also show those not yet evaluated. - Fixed colors per category: "Approved" in green, "Needs adjustments" in orange (
#ED8936), "Rejected" in red. - Title: "Best Practices Status by Site".
Rates and funnels of a field survey
A screening form applied in the field records whether the person was tested, the result and whether they were referred. The dashboard should show screening volume, positivity and referral rates, the care funnel and the profile by age band.
Fields used: tested ("Yes"/"No"), result ("Positive"/"Negative"/"Indeterminate"), referred ("Yes"/"No"), tested-before ("Yes"/"No"), age (number), region.
1. Indicator cards
| Card | Formula | Format |
|---|---|---|
| Screenings performed | count() | Number |
| First-time testers | count(kql='tested-before : "No"') / count() | Percent |
| Positivity | count(kql='result : "Positive"') / count(kql='tested : "Yes"') | Percent |
| Referral of positives | count(kql='result : "Positive" and referred : "Yes"') / count(kql='result : "Positive"') | Percent |
In each card: type Metric, Primary metric with the Formula tab, and the format from the table.
2. Care funnel
- Type Bar (vertical).
- Horizontal axis: the Filters function, with three filters in funnel order:
| Expression | Label |
|---|---|
tested : "Yes" | Tested |
result : "Positive" | Positive |
result : "Positive" and referred : "Yes" | Referred |
- Vertical axis: Count of records.
- Value labels: Show.
- Title: "Care Funnel (people)".
3. Profile by age band
- Type Bar, Horizontal.
- Categories:
age, the Intervals function, Create custom ranges: from 15 to 20, from 20 to 25, from 25 to 35, from 35 to 50 and from 50 up, labeled "15–19", "20–24", "25–34", "35–49" and "50+". - Metric: Count of records.
- Title: "People Screened by Age Band".
4. Weekly trend
- Type Line.
- Horizontal axis:
date, Week. - Vertical axis: two metrics: Count of records ("Screenings") and Count of records with Filter by
result : "Positive"("Positives"). - Title: "Screenings and Positives per Week".
5. Controls
region and, if available, the organization and the service location, from general to specific.
Dashboards with health data should not display individual identifiers or individual-level tables. Agree with the data owner on a minimum group size for disclosure. See Handling sensitive data.
Tank levels from readings
A daily measurement form records, for each tank, the tank code (tank) and the empty space measured from the top down to the product (empty-space). Every tank has a capacity of 500. The level of each tank is the capacity minus the empty space, in the most recent reading.
The larger the empty space, the smaller the stock. That's why the indicator is calculated as capacity minus the reading, not as the reading itself.
1. One card per tank, with a progress bar
- Type Metric.
- Primary metric, Formula tab:
500 - last_value('empty-space', kql='empty-space : *')
- Name: "Current level". Value format: Number, 0 decimals.
- Maximum value: Static value
500. The card now shows a progress bar. - Break down by:
tank, Top values, with the number of tanks. One card per tank appears. - Color: Dynamic, with Number ranges: red from 0 to 100 (up to 20% of capacity), yellow from 100 to 200 (20% to 40%) and green from 200 up.
- Title: "Current Tank Levels".
2. Gauge for one tank
To highlight a specific tank:
- Type Gauge, shape Vertical bullet.
- Metric: the same formula as the card.
- Minimum value:
0. Maximum value:500. Goal value: the minimum safety level. - In the editor's search bar:
tank : "TK-01".
3. Level trend
- Type Line.
- Horizontal axis:
date, Day. - Vertical axis: the formula
500 - average('empty-space'). - Breakdown:
tank.
If tanks have different capacities, record the capacity in the form (for example, in a calculated field based on the selected tank) and use last_value(capacity) - last_value('empty-space', kql='empty-space : *'). The same formula then works for every tank.
Defect count in a transposed index
A quality control records the quantity of each defect type in its own question. In the integration, the questions were transposed into two fields: defect-type (the label) and defect-value (the quantity). See Transposed index.
1. Defects by type
- Type Bar, Horizontal.
- Categories:
defect-type, Top values, Rank by the sum ofdefect-value, Descending, without "Other". - Metric: Sum of
defect-value, Name "Occurrences". - Value labels: Show.
- Title: "Defects by Type (occurrences)".
2. Defects by month
- Type Bar, Stacked.
- Horizontal axis:
date, Month. - Vertical axis: Sum of
defect-value. - Breakdown:
defect-type, Top values, 5 values, with the "Other" group on for the rest. - Title: "Defects by Month and Type (occurrences)".
3. Distribution of a measure
To see the distribution of a numeric measure from the same control (for example, part weight), use the form's original index:
- Type Bar.
- Horizontal axis:
weight, the Intervals function, automatic ranges. - Vertical axis: Count of records.
Unexpected values (negative weights, for example) appear at the ends of the chart and indicate entry errors.
In a transposed index, Count of records with defect-type on the axis shows the same number for every type, because each collection generates one record per type. Always use Sum of defect-value.