Page pattern

Target / Budget Tracking

Track progress towards a target: where we are, where we should be, and what closes the gap.

OrientationIntermediateArchetype: KPI / Scorecard
Typical user questions
  • Are we going to make the target?
  • How much is left?
  • Which drivers close the gap?

Target / Budget Tracking — clickable example

Shared retail dataset. Every control works; the log shows what Power BI would change.

Simulation of native Power BI behaviour
Filter contextDepartment:All
Target selectorfilters
DepartmentAll
Actual / target / variancekpi
Actual€8.4M
Target€8.5M
Difference€-89kvs Budget€8.5M -101%Attention

Gap €-89k (-1%) against target.

Progress visualcomparison
€8.4Mtarget €8.5M
Trend to targettrend
W1W2W3W4W5W6W7W8W9W10W11W12W13
Driversdriver
Level: department

Bars: Revenue · vertical marker: Budget

Breakdown tabledetail
5 rows
vs Budget
Fresh€2.4M€2.5M€608k -0.9%
Beverages€1.7M€1.7M€426k -0.7%
Grocery€1.7M€1.7M€426k -0.8%
Non-food€1.4M€1.4M€346k -1.4%
Household€1.2M€1.2M€291k -1.7%
Total€8.4M€8.5M€2.1M-1.0%
What Power BI would do
  • Interact with a slicer, a bar or a navigation button to see the native behaviour described here.

KPI / Scorecard — archetype wireframe

[ Context + filters ] [ KPI cards ] [ Target comparison ] [ KPI trends ] [ Breakdown ]

Simulation of native Power BI behaviour
Zone 1
Context + filters
Zone 2
KPI cards
Zone 3
Target comparison
Zone 4
KPI trends
Zone 5
Breakdown

Reading order follows the zones above, top-left to bottom-right.

Designer

Components: Cards, KPI visual, Bar/Column charts, Matrix, Sparklines

Hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.

Developer

Interaction: Use only interactions that support the page's next analytical step; typical next level: **KPI analysis or detail**.

Navigation: KPI analysis or detail

Implementation: Compose from the listed native visuals/controls and the standard interaction patterns in this guide; custom visuals are exceptions.

Common mistakes
Treating the archetype as a rigid screen; adding unrelated analytical tasks; duplicating controls already handled globally.
Related entries