How to create decisions report in Confluence
Collect Confluence decisions with the Decision report macro, choosing the source spaces and filters.
This is a report over recorded decisions, not a tool that infers decisions from any meeting paragraph. Use a product-area report to make decisions findable without replacing the original discussion and rationale.
Step-by-step guide
Locate decisions worth reporting
Choose two existing pages that contain recorded decisions in the relevant product area. For example, a checkout authentication decision and a pricing experiment decision should have clear outcomes and rationale before they are aggregated.
Insert Decision report
Edit the overview page and type /decision, then select Decision report. Choose Current space or the named spaces to aggregate. Avoid pulling every space into a product-specific overview merely because access allows it.
Apply a meaningful filter
Use a label or another CQL field to narrow the result. An ancestor boundary can distinguish current checkout decisions from an archived product area. Set Show to a maximum that fits the report’s purpose and inspect the result while configuring.
Validate the reader’s route to rationale
Publish, open reported decisions and check that readers can understand the decision beyond its headline. If an expected decision is absent, inspect the source and report scope rather than creating a second, inconsistent decision page.
Common mistakes
Using a summary as the authoritative record
The report helps readers find decisions. Keep the original evidence and rationale with the source decision.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.