> 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/neo/guides/what-a-routine-is.md).

# What a routine is

A routine is recurring work Drivepoint runs for your company. It is not a saved report.

{% hint style="warning" %}
Draft. Running a routine depends on server work that is not finished. Steps may change.
{% endhint %}

A routine is recurring work your company sets up once. Drivepoint runs it on a cadence or when you choose, using your connected data.

## What a routine has

| Part                 | What it means                                                                    |
| -------------------- | -------------------------------------------------------------------------------- |
| Name and description | What the routine is for.                                                         |
| Function             | The team it serves.                                                              |
| Cadence              | Manual, daily, weekly, or monthly.                                               |
| Data domains         | The kinds of data it needs. A domain is met when a matching source is connected. |
| Destination          | Drivepoint chat, always. Email or Slack too, if you add them.                    |

{% hint style="info" %}
Not confirmed yet: the full list of functions. The page does not name them.
{% endhint %}

## Where routines live

Open **Routines** in the sidebar. The page has two tabs:

* **Routines.** Your company's routines. Start one from a Drivepoint template or build one from scratch.
* **Report deliveries.** Saved reports on a schedule. You add those from a report's own page.

## Run a routine

Choose a routine's actions, then **Run routine**. Run is off when:

* the routine is disabled, or
* a data domain it needs has no connected source.

A disabled routine shows a **Disabled** badge. Use **Enable routine** to turn it back on.

{% hint style="info" %}
Not confirmed yet, and left off this page: pause, last run, and whether you can set a data-alert trigger. Those controls are not established for customers.
{% endhint %}

## How this differs from a saved report

A scheduled report sends that one report. A routine runs a task and delivers the result.

## Next

Create a routine. That page is not in this preview.


---

# 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/neo/guides/what-a-routine-is.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.
