Page pattern

Forecast / Planning

“Derived from the page purpose; write it explicitly before implementation.”

Understand the expected future state and compare it with targets or capacity.

[ Current state ] [ Forecast KPIs ] [ Trend + forecast ] [ Assumptions / drivers ] [ Breakdown ]

Simulation of native Power BI behaviour

Zone 1

Current state

Zone 2

Forecast KPIs

Zone 3

Trend + forecast

Zone 4

Assumptions / drivers

Zone 5

Breakdown

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

Designer

Components: Line chart, Cards, Slicers, Analytics features where supported

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: **Scenario or plan detail**.

Navigation: Scenario or plan 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