Build a Dashboard-Style Output
Dashboard-style outputs present the key reporting metrics in a compact, scannable layout. Stakeholders read the dashboard before they read detailed records — it sets the context and highlights what needs attention.
This tutorial builds a single-page dashboard output from a monthly progress blueprint. The finished page includes a header, KPI cards, a trend chart, a RAG grid, and an action summary table.
Prerequisites
- A published blueprint with sections for: project metadata, overall status, schedule, cost, risk, and actions.
- An approved edition with data entered.
- At least Report Owner or Admin role to access the Output Designer.
Step 1: Create a new output
- Open the blueprint in the Blueprint Designer.
- Click the Outputs tab in the header.
- Click + New Output.
- Name it (e.g. "Monthly Dashboard") and click Create.
- The Output Designer opens with a blank canvas.
Step 2: Configure the page
- Right-click the page thumbnail → Page settings.
- Set: A4 Landscape, Layout mode: Grid, Margins: 12mm all sides.
- In the Header section, add:
- Left zone: project name field (bind to the project metadata section).
- Centre zone: report type label (static text: "Monthly Progress Report").
- Right zone: reporting period end date field.
Step 3: Add an info grid header block
- Insert an Info Grid component at the top of the canvas.
- Bind to the project metadata section.
- Configure cells: Project Name, Client, Contract Value, Data Date, Report Author, Reporting Period.
- Set: 6 columns, label-above-value style, compact padding.
- Add a Divider component below.
Step 4: Add KPI cards
- Insert 4 KPI Card components in a row below the divider.
- Bind each to the overall status section:
- Card 1: Overall Schedule RAG → bind the RAG field as the status colour, label: "Schedule".
- Card 2: Overall Cost RAG → label: "Cost".
- Card 3: Open Risks count → bind a count aggregation, label: "Open Risks".
- Card 4: Overdue Actions count → label: "Overdue Actions".
- Format all 4 cards consistently: same height, same font size, card border radius 8px.
Step 5: Add a trend chart
- Insert a Chart component (line/area style) below the KPI row.
- Bind to the cost or progress section:
- X axis: period date field.
- Y axis: planned % and actual % (two series).
- Set: Legend below, Y axis label as "%", enable area fill for Planned series.
- Resize to span approximately half the page width.
Step 6: Add a RAG grid
- Insert a RAG Grid component beside the trend chart.
- Configure rows (static): Schedule, Cost, Safety, Quality, Risk, Resourcing.
- Configure columns: Current period RAG, Prior period RAG, Trend (select the trend arrow option).
- Bind each column to the corresponding field in the overall status section.
- Resize to fill the remaining half of the page.
Step 7: Add an action summary table
- Insert a Table component below the chart and RAG grid.
- Bind to the actions section.
- Add columns: Action title, Owner, Priority, Due date, Status.
- Apply a row filter: Status != Closed.
- Apply sort: Due date ascending.
- Set Max rows: 8 (to keep the table within the page).
- Add conditional row formatting: rows where Due date < today AND Status != Closed → red row background.
Step 8: Add footer notes
- Insert a Text component below the table.
- Bind the text body to the "Notes / Commentary" rich text field from the status section.
- Set font size 9pt, italic style, muted colour.
- Add a Divider above the notes block.
Step 9: Preview and adjust
- Click Preview in the ribbon.
- Check:
- KPI cards align at the same height.
- Chart and RAG grid don't overflow the row.
- Table fits within the page without being cut off.
- Notes text doesn't push the layout off the page.
- If the table overflows, reduce Max rows or enable Compact mode.
- If the chart is too tall, reduce its height and redistribute the space to the RAG grid.
Step 10: Publish and generate
- Click Save then Publish in the ribbon.
- Navigate to the edition.
- Click Generate output → select "Monthly Dashboard".
- Click View when generation completes.
- Export as PDF.
Dashboard design principles
| Principle | Why |
|---|---|
| Put the most important status top-left | Western reading order — eye lands there first. |
| Use RAG for status, numbers for magnitude | RAG is scanned; numbers are read. Don't swap them. |
| One trend chart maximum per dashboard page | Multiple trends compete — pick the one that matters most. |
| Tables for detail, not for every metric | A table of 40 rows on a dashboard is not a dashboard. |
| Keep the page count to 1–2 | A dashboard that requires scrolling is a report, not a dashboard. |
| Don't duplicate measures | SPI from the chart and SPI from a KPI card side-by-side is noise. |