Browse documentation

Building a report

Reports are composed rather than configured. You pick the pieces, arrange them, and see the result before anyone else does.

Widgets

A widget is a saved piece of a Cost Explorer view: a chart, a breakdown table, a headline figure. Save one from the Explorer and it joins your library, ready to drop into any report.

The point of the library is reuse. The chart you keep screenshotting into a monthly update is the one to save first.

Built-in sections

Alongside your own widgets there are ready-made sections for the things most reports want: the headline summary, the period-over-period comparison, the top movers. Use them for the frame and your widgets for what makes your report yours.

Arranging the page

The composer is a grid you drag things around in. Order matters more than it looks: a report is read top-down and mostly on a phone, so the number that would make someone act belongs above the detail that explains it.

Scoping the data

Filters set on the report apply to every widget in it. This is how one composition serves several audiences: the same layout, scoped per team, is a different report to each of them without being a different report to maintain.

Preview before you send

The preview renders the report as it will arrive. It can run against your real data or against sample data, which is the safer choice when you are still arranging things and do not want a half-built layout in front of real numbers.