> For the complete documentation index, see [llms.txt](https://move-solutions.gitbook.io/untitled/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://move-solutions.gitbook.io/untitled/how-to-schedule-a-report.md).
# How to schedule a Report?
MyMove allows you to automate the generation and delivery of reports. This is useful for sending regular project updates to clients, partners, or internal teams.
***
### 1. Enable Scheduling
After creating a report or selecting an existing one, click on “Schedule Report” from the report actions menu (⋮).
Report page
***
### 2. Configure the Schedule
Fill in the following settings:
* Report Interval: Choose how often the report should be sent. You can select standard intervals (e.g., daily, weekly, monthly) or configure a custom recurrence pattern.
* Time Range Reference: Define the logic used to calculate the report’s data window (e.g., “last 30 days,” “previous month,” etc.).
* Recipients: Add one or more email addresses. The report will be delivered automatically to these contacts.
***
### 3. Save and Activate
After defining your preferences, click “Save Schedule”. The system will automatically generate and send the PDF report at the configured frequency with up-to-date data.
{% hint style="info" %}
Each scheduled report is regenerated just before being sent, ensuring the data is always current.
{% endhint %}
***
You now have both manual and automated reports set up in MyMove. These tools help streamline communication, enhance project visibility, and ensure all stakeholders stay informed.
For more information, see the [Reports section](https://move-solutions.gitbook.io/untitled/mymove-manual/reports) of the MyMove Documentation.
---
# 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://move-solutions.gitbook.io/untitled/how-to-schedule-a-report.md?ask=&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.
