> ## Documentation Index
> Fetch the complete documentation index at: https://docs.statusstack.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Scheduled Reports

> Set up recurring email reports for uptime, incidents, and usage metrics

## Overview

Scheduled Reports let you automatically send recurring email reports to your team and stakeholders. Configure daily, weekly, or monthly reports covering uptime, incident summaries, and usage metrics — delivered to the right people at the right time.

<Info>
  **Pro or Enterprise plan required.** Scheduled Reports are part of the Analytics feature, available on [Pro and Enterprise plans](/account/subscription-plans). Upgrade your plan to access automated reporting.
</Info>

***

## Report Types

<CardGroup cols={3}>
  <Card title="Uptime Report" icon="arrow-up">
    Uptime percentages and availability trends for your monitored services
  </Card>

  <Card title="Incident Summary" icon="triangle-exclamation">
    Incident counts, severity breakdown, and resolution times
  </Card>

  <Card title="Usage Report" icon="chart-bar">
    Platform usage metrics across your organization
  </Card>
</CardGroup>

***

## Creating a Scheduled Report

<Steps>
  <Step title="Navigate to Scheduled Reports">
    In the customer dashboard, go to **Analytics** → **Scheduled Reports** or visit `/dash/analytics/scheduled-reports`.
  </Step>

  <Step title="Click Create">
    Click **Create Scheduled Report** to open the configuration form.
  </Step>

  <Step title="Configure Report Settings">
    Fill in the report details:

    * **Name** — A descriptive name (e.g., "Weekly Uptime Summary")
    * **Report Type** — Uptime, Incident Summary, or Usage
    * **Lookback Period** — How far back to include data (7, 14, 30, 60, or 90 days)
  </Step>

  <Step title="Set Schedule">
    Choose when and how often reports are sent:

    * **Frequency** — Daily, Weekly, or Monthly
    * **Day of Week** — For weekly reports, which day to send
    * **Day of Month** — For monthly reports, which date (1–31)
    * **Send Time** — Time of day to deliver (HH:MM format)
    * **Timezone** — The timezone for scheduling
  </Step>

  <Step title="Add Recipients">
    Enter email addresses for report delivery. You can add up to 25 recipients per report.
  </Step>

  <Step title="Optional: Scope to Team">
    By default, reports cover your entire organization. Optionally select a specific team to narrow the report scope.
  </Step>

  <Step title="Save Report">
    Click **Create** to activate the scheduled report. The first report will be sent at the next scheduled time.
  </Step>
</Steps>

***

## Configuration Options

### Frequency

| Frequency   | Description                          | Additional Settings               |
| ----------- | ------------------------------------ | --------------------------------- |
| **Daily**   | Sent every day at the specified time | Send time, timezone               |
| **Weekly**  | Sent once per week                   | Day of week, send time, timezone  |
| **Monthly** | Sent once per month                  | Day of month, send time, timezone |

### Lookback Periods

The lookback period determines how much historical data the report includes:

| Period      | Best For                         |
| ----------- | -------------------------------- |
| **7 days**  | Weekly summaries, sprint reviews |
| **14 days** | Bi-weekly reviews                |
| **30 days** | Monthly executive summaries      |
| **60 days** | Quarterly trend analysis         |
| **90 days** | Long-term reliability reporting  |

### Team Scoping

Reports can cover your entire organization or a single team:

* **All Teams** — Aggregates data across every team in your organization
* **Specific Team** — Limits the report to a single team's services and incidents

***

## Managing Reports

### Viewing Reports

The Scheduled Reports list shows all configured reports with:

* Report name and type
* Frequency and next scheduled send
* Number of recipients
* Active/inactive status
* Total sends to date

### Editing a Report

Update any report configuration from the edit page — change the frequency, recipients, lookback period, or scope without losing send history.

### Enabling and Disabling

Toggle reports on or off without deleting them. Disabled reports retain their configuration and can be re-enabled at any time.

### Deleting a Report

Remove reports you no longer need. This action is permanent and cannot be undone.

***

## Best Practices

<AccordionGroup>
  <Accordion title="Match Frequency to Audience">
    * **Executives**: Monthly reports with 30-day lookback for high-level summaries
    * **Engineering leads**: Weekly reports with 7-day lookback for operational awareness
    * **On-call teams**: Daily reports to review the previous day's incidents
  </Accordion>

  <Accordion title="Keep Recipient Lists Focused">
    Send reports to people who will act on them. Use the 25-recipient limit wisely — create separate reports with different scopes for different audiences rather than one report for everyone.
  </Accordion>

  <Accordion title="Use Team Scoping">
    For organizations with multiple teams, create team-specific reports so each team sees only the data relevant to their services.
  </Accordion>

  <Accordion title="Coordinate Timezones">
    Set the report timezone to match your recipients. A weekly report scheduled for Monday 9:00 AM in your team's timezone arrives at the start of their work week.
  </Accordion>
</AccordionGroup>

***

## Related Documentation

<CardGroup cols={2}>
  <Card title="Customer Dashboard" icon="gauge" href="/guides/customer-dashboard">
    Overview of dashboard features
  </Card>

  <Card title="Status Monitoring" icon="chart-line" href="/guides/status-monitoring">
    Real-time monitoring capabilities
  </Card>

  <Card title="Notification Setup" icon="bell" href="/guides/notification-setup">
    Configure real-time alerts
  </Card>

  <Card title="Subscription Plans" icon="credit-card" href="/account/subscription-plans">
    Compare plan features
  </Card>
</CardGroup>