About this block

Report Comparison View sets a current period, Jun 1 to Jun 30, 2026, against the previous May 1 to May 31 with a swap control between the two labelled chips and a summary line counting how many metrics improved. The table below runs six rows, revenue, new customers, churned customers, active users, average order value, and trial conversion, each showing the current value, the previous value, a signed change figure with an up or down arrow, and paired mini bars that size the two periods side by side.

Rows are one typed array where an improved flag, rather than the raw direction, decides whether a change reads as positive, so a fall in churned customers still counts as an improvement. The footer note spells that rule out, and the paired bars give a proportional read of each metric without pulling in a chart.

When to use

Reach for this block on a reporting page where two windows need a direct read against each other, wired to your metrics API with both period ranges. The swap control should flip current and previous and recompute every change figure in place.

A natural flow around it on an Application Pro page:

Before

• Report summary header
• Report filters bar

After

• Data table
• Charts

What you can display

One strong use is month over month business metrics. Other comparison views:

• Plan comparison. Two pricing tiers side by side with per metric current values and the gap between them.
• Team comparison. Two squads across the same set of delivery metrics with paired bars per row.
• Forecast versus actual. Planned figures against realised ones with the variance in the change column.

Tip: the improved flag, not the arrow direction, decides tone, so a lower churn number can still read as a win.