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

# Scheduling Reports

Send a report on a cadence from Neo, or run a routine on a schedule, a data alert, a prompt check, or a webhook.

You can email or Slack a report on a repeating cadence. You can also set up a routine that does recurring work in chat.

## Schedule a report in Neo

1. Open the report.
2. Click **Schedule** in the top bar. The side rail lists the deliveries for this report.
3. Click **Add schedule**.
4. Choose **Daily**, **Weekly**, or **Monthly**, then the day and the time. Times use the company account timezone.
5. Choose **Email** or **Slack**. For email, enter one or more addresses, separated by commas. For Slack, pick a channel. Invite Drivepoint to a private channel before it can post there.
6. Click **Save schedule**.

The report's current filters are saved on the schedule. Edit or remove a delivery from the same rail.

These deliveries also appear under **Routines**, on the **Report deliveries** tab.

{% hint style="info" %}
A daily send can lag when newer source data has not reached the warehouse yet. The Data Sources screen shows how fresh each source is.
{% endhint %}

## Routines

A routine is recurring work for the company. Open **Routines** in the left navigation.

* **Your routines** are workflows you set up. Each one has a prompt, the data it reads, and one way it starts.
* **Report deliveries** are the schedules created from a report's Schedule rail.

Click **New routine** to start from a template or from scratch. A routine stays a draft until you enable it. **Run routine** starts it in chat right away. **Edit routine** opens the prompt, the trigger, and where the result goes.

### How a routine starts

* **Schedule.** Daily, weekly, or monthly, at a time in the company account timezone. Choose manual when it should run only when someone starts it.
* **Data alert.** Runs when a source's data is older than the hours you set, when a custom import is stale, or when the latest month's discounts or ad spend cross an amount. Comparisons are above, below, at least, and at most. It fires once, then waits until the condition clears. It does not watch sales, revenue, margin, orders, or inventory.
* **Prompt check.** Runs on a daily, weekly, or monthly cadence and sends only after the prompt's check passes. You can attach one saved report. When the check fires, that report goes out through its existing delivery. The assistant cannot swap that report.
* **Webhook.** Saving the routine creates a signed URL. It is shown to people who can edit the routine. A signed request can start a run, and the routine can also keep a schedule.

Email recipients and a Slack channel are set on the routine. A test shows the email or briefing in chat. It does not send until you confirm the saved recipients.

## In the legacy app

1. Open the report.
2. Click the clock icon at the top right.
3. Click **New Schedule**.
4. Enter a Drivepoint user's name, or an email address for someone without an account. You can add more than one.
5. Choose daily, weekly, or monthly, then the day and the time.
6. Choose CSV or PDF.
7. Click **Schedule report**.

To see every legacy schedule, open any report, click the clock, then **Other Reports**. You can view, edit, or delete them there.

### Examples

* Weekly LTV by first-order segment, from **LTV by Dimension** in the Cohort Analysis bundle
* Monthly operating income, from **Profit and Loss Statement** in the Finance Core bundle
* Daily sales by SKU, from **Sales by Product** in the DTC Sales bundle


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.drivepoint.io/using-the-web-app/reports/scheduling-reports.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
