> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/how-to-and-best-practices/data-intelligence-and-reporting/automating-reports.md).

# Automating Reports

Schedule automated employee productivity and attendance reports in We360.ai with recurring email digests for workforce analytics.

Eliminate manual data pulls by scheduling recurring reports that are automatically generated and delivered to the right stakeholders.

## Setup Steps

{% stepper %}
{% step %}

#### Open the Reports Module

Navigate to **Universal Tools → Reports**. Browse the list of available report types including Daily Attendance, Group Insights, Productivity Summary, and Device Reports.
{% endstep %}

{% step %}

#### Configure a Report Schedule

Select a report type and click **Schedule**. Configure:

* **Frequency** — Daily, Weekly, or Monthly.
* **Recipients** — Add manager or leadership email addresses.
* **Date Range** — Whether the report covers the previous day, week, or month.
  {% endstep %}

{% step %}

#### Save and Activate

Save the schedule. The system will automatically generate and email the report at the configured cadence, with no manual action required.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
Scheduling a **Weekly Attendance Summary** for department heads every Monday morning is the most commonly used report automation in We360.ai.
{% endhint %}


---

# 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.we360.ai/how-to-and-best-practices/data-intelligence-and-reporting/automating-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.