> For the complete documentation index, see [llms.txt](https://docs.countercyclical.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.countercyclical.io/relations/scheduling-and-delivering-reports.md).

# Scheduling & Delivering Reports

Set a delivery cadence, choose recipients, and verify scheduled report delivery.

Use **Schedule Reports** on a dashboard to deliver selected Reports or the entire Dashboard on a recurring schedule. This is useful for regular coverage reviews, investment committee updates, and other work where reviewers should receive the same set of reports on a known cadence.

### Choosing What to Deliver

Open the dashboard and use **Schedule Reports** in the report toolbar where available. Choose **Entire Dashboard** if the delivery should follow its full set of reports. Choose **Specific Reports** to keep the delivery focused on a defined set of tabs. Confirm the report names before saving, especially if the dashboard includes extra working material.

Scheduling depends on access to Relations and permission to manage the dashboard schedule. Review the dashboard's sharing settings before choosing the audience.

### Choosing a Delivery Method

| Delivery Method | What to Configure                                                                                                                                                                     |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Email           | Choose **All Collaborators** or **Individual Collaborators**. For individual delivery, select the intended workspace members. The **Attachment** setting lets you choose PDF or DOCX. |
| Webhook         | Enter the receiving HTTPS URL and provide a signing secret if your receiver expects one. Use this when the recipient is a system that will handle the delivery.                       |

Scheduled delivery identifies the dashboard and reports included. Email gives eligible recipients a link back to the dashboard. Verify the test delivery before relying on a particular document format.

{% hint style="warning" %}
**Review the Audience Before Starting**

Check both the report scope and the destination. If a dashboard includes restricted diligence, choose only the reports and collaborators appropriate for that audience.
{% endhint %}

### Setting the Schedule

{% stepper %}
{% step %}

#### Choose the Frequency and Time Zone

Set the cadence and the local time at which the delivery should start. Review applicable days and start and end dates. Select the time zone that matches the intended audience or review schedule.
{% endstep %}

{% step %}

#### Send a Test Delivery

Select **Test** to confirm the routing and contents. Email tests are addressed to the requesting member. Check the result at the selected destination before relying on the recurring schedule.
{% endstep %}

{% step %}

#### Start the Schedule

Review the reports, timing, and audience again, then select **Start**. Check **Next delivery** in the scheduling controls.
{% endstep %}
{% endstepper %}

### Updating or Pausing Delivery

Reopen **Schedule Reports** to review the current schedule, update timing or delivery settings, or pause future deliveries. After changing recipients, destination, or scope, send a new test to verify the updated configuration.

A report schedule delivers existing reports. To run analysis or update the workspace on a recurring basis, configure the appropriate Orchestration separately, then decide what the report should deliver.

### If a Delivery Is Missing

Check that the schedule is active and that its next delivery, time zone, and date range match what you expected. For email, confirm the intended recipient is still eligible to access the dashboard and has the relevant notifications enabled. For a webhook, confirm the destination is still available and check whether it recorded the delivery.

Review available activity on the resource for changes or delivery outcomes, then test again if needed. If a schedule still fails, record the dashboard, report selection, expected delivery time and time zone, and the delivery method when contacting support.

#### Related Pages

{% content-ref url="/pages/w6VNPCwkiWXCrXdnXC3p" %}
[Dashboards](https://docs.countercyclical.io/relations/dashboards.md)
{% endcontent-ref %}

{% content-ref url="/pages/0xvOQOgiI0hROKrC8ZzU" %}
[Reports](https://docs.countercyclical.io/relations/reports.md)
{% endcontent-ref %}

{% content-ref url="/pages/LhVkzvuDsdjbaA1OjjvI" %}
[Channel Preferences](https://docs.countercyclical.io/notifications/channel-preferences.md)
{% endcontent-ref %}

{% content-ref url="/pages/WayERz3yGWac0t09JJuk" %}
[Webhooks](https://docs.countercyclical.io/developers/webhooks.md)
{% endcontent-ref %}

{% content-ref url="/pages/U8A8RPCDt7CQ2VNFGySE" %}
[Runs](https://docs.countercyclical.io/agents/orchestrations/runs.md)
{% endcontent-ref %}
