*Pages, groups, and sections

Create well-structured reports using pages, page groups, and sections

Think of organizing a report like planning a city council meeting. You need different areas for different topics. You also need clear navigation so attendees can find what they need. And finally, a logical flow that makes sense to everyone present.

The three-tier system

The report structure uses three types of organizational elements that work together to create clear, navigable documents:

Pages (Content Areas)

Pages are where your actual content lives - like individual rooms in a building:

• Executive Summary - High-level overview with key metrics

• Budget Analysis - Detailed financial breakdown and charts

• Department Performance - Individual department reports

• Recommendations - Action items and next steps

Pages contain:

• Rich text blocks

• Data visualizations (insights)

• Images and media

• Column layouts

• All your actual content

Think of pages as: Individual presentations or documents within your larger report

Groups (Containers)

Groups organize related pages together - like departments in a building:

• Overview Group - Contains summary and introduction pages

• Financial Group - Contains all budget and financial analysis pages

• Departmental Group - Contains individual department performance pages

• Appendices Group - Contains supporting documentation and detailed data

Groups contain:

• Multiple related pages

• Logical organization

• Collapsible navigation

• Hierarchical structure

Think of groups as: Chapters in a book or sections in a large presentation

Sections (Headers)

Sections are simple dividers - like signs in a building:

• Introduction - Header before opening content

• Methodology - Header explaining your approach

• Data Sources - Header for technical information

• Acknowledgments - Header for credits

Sections contain:

• Just a title/header

• No child content

• Visual separation

• Topic indicators

Think of sections as: Chapter titles or topic dividers that don't need sub-content

When to use each type

Use pages when:

• You have substantial content to present

• Topics need separate focus and space

• Different audiences might access different content

• You want rich formatting and multiple content blocks

Examples:

• Comprehensive budget analysis with charts and explanations

• Department performance review with metrics and commentary

• Executive summary with key highlights and recommendations

Use groups when:

• You have multiple related pages

• Content needs logical organization

• Users benefit from hierarchical navigation

• You want collapsible sections for better overview

Examples:

• All financial pages grouped under "Budget & Finance"

• Multiple department reports grouped under "Department Performance"

• Various appendices grouped under "Supporting Documentation"

Use sections when:

• You need simple topic separation

• Headers don't require child content

• Visual breaks improve readability

• Simple organization is sufficient

Examples:

• "Methodology" - just explains approach, no sub-pages needed

• "Executive Summary" - single topic, not multiple pages

• "Acknowledgments" - simple header for credits

Building your report structure

1

Plan your content hierarchy

Before creating structure elements, outline what you need:

Simple Report

Basic structure for focused reports:

• Executive Summary (Page)
• Methodology (Section)
• Analysis Results (Page)
• Recommendations (Page)
• Data Sources (Section)

Good for: Single-topic reports, brief analyses, focused presentations

Departmental Report

Structure for multi-department analysis:

• Overview (Group)
  ├─ Executive Summary (Page)
  └─ Key Findings (Page)
• Department Analysis (Group)
  ├─ Public Safety (Page)
  ├─ Health Services (Page)
  └─ Public Works (Page)
• Recommendations (Page)

Good for: Multi-department reviews, comparative analysis

Comprehensive Report

Structure for complex, multi-audience reports:

• Executive Overview (Group)
  ├─ Key Highlights (Page)
  └─ Strategic Recommendations (Page)
• Financial Analysis (Group)
  ├─ Budget Summary (Page)
  ├─ Revenue Analysis (Page)
  └─ Expenditure Details (Page)
• Operations (Group)
  ├─ Service Delivery (Page)
  └─ Performance Metrics (Page)
• Methodology (Section)
• Appendices (Group)
  ├─ Detailed Data (Page)
  └─ Technical Notes (Page)

Good for: Annual reports, comprehensive reviews, multi-stakeholder presentations

2

Create your structure elements

Build your organization step by step:

1. Add main elements:

   • Click "Add Page", "Add Group", or "Add Section"

   • Give each element a clear, descriptive name

   • Think about the logical flow and order

2. Organize hierarchically:

   • Drag pages into groups to create nested structure

   • Reorder elements by dragging up or down

   • Rename elements by clicking on their names

3. Test navigation:

   • Click through your structure

   • Ensure logical flow for your audience

   • Verify groupings make sense

Start simple and expand as needed. You can always reorganize later by dragging elements around.

3

Add content to pages

Once structure is ready, populate your pages:

1. Click on a page to open it for editing

2. Add content blocks using the "+" button:

   • Text for explanations and analysis

   • Insights for data visualizations

   • Images for supporting visuals

   • Columns for professional layouts

3. Keep content focused:

   • Each page should have a clear purpose

   • Use headings to break up long content

   • Include context and explanations for data

Pro tip: Write a brief summary at the top of each page explaining what readers will find. This helps with navigation and sets expectations.

4

Optimize for different audiences

Consider how different people will use your report:

Executive Readers

Create executive-friendly structure:

• Put key findings up front

• Group detailed analysis at the end

• Use clear, descriptive naming

• Include navigation aids

Example structure:

• Executive Summary (Page) ← Start here
• Key Recommendations (Page)
• Detailed Analysis (Group) ← Optional reading
  └─ Various analysis pages

Department Users

Make department-specific content easy to find:

• Group by department or function

• Use familiar terminology

• Include department-specific insights

• Provide context for cross-department data

Example structure:

• Overview (Page)
• By Department (Group)
  ├─ Your Department (Page) ← Highlighted
  ├─ Related Departments (Page)
  └─ All Departments Summary (Page)

Public Audiences

Create accessible structure for external readers:

• Start with background and context

• Use plain language in navigation

• Group technical details separately

• Include explanatory content

Example structure:

• What This Report Shows (Page)
• Key Findings (Page)
• Background (Section)
• Detailed Data (Group) ← Optional technical content

Best practices

Naming conventions

• Use clear, descriptive names that indicate content

• Avoid internal jargon especially for public-facing reports

• Be consistent with naming patterns across similar elements

• Consider your audience - use terminology they understand

Structure depth

• Limit nesting to 2-3 levels for clarity

• Group related content but avoid over-categorization

• Test navigation with actual users when possible

• Keep similar content together for easy comparison

Content distribution

• Balance page lengths - avoid overly long or very short pages

• Group complementary information in the same section

• Use sections sparingly - only when simple headers are sufficient

• Consider reading flow and logical progression

Remember: Good structure serves your readers, not just your organization. Test your structure with people from your intended audience to ensure it makes sense from their perspective.