Recurring Reports Setup

Recurring Reports Setup

Scheduled Reports automate repeat questions and keep stakeholders aligned.

If you only need a personal future nudge, use a reminder instead. If the question should run and produce output on a cadence for a group, use a Scheduled Report.

What Scheduled Reports Include

Each scheduled report can include:

• A saved analytics question
• A run cadence (daily, weekly, or monthly)
• A run time based on your organization timezone
• Recipients (team members, stakeholders, and optional custom emails)
• An AI-written executive summary for the run
• Optional visualization output

Setup Workflow

1. Start from a proven question or widget-driven workflow
2. Give the report a clear title
3. Set cadence and run time
4. Select recipients
5. Enable visualization if useful
6. Save and verify first delivery

If you are unsure where to start, use a question that already works well in chat before trying to operationalize a new prompt directly in reporting.

Cadence Selection Guide

• Daily: shift performance and fast-moving operations metrics
• Weekly: downtime patterns and improvement rollups
• Monthly: leadership summaries and quality trend reviews

Choose the slowest cadence that still supports decision-making. This keeps signal high.

Recipient Strategy

Use a role-based list:

• Team members: active operators and analysts
• Stakeholders: leaders or partners who need visibility
• Custom emails: external distribution where appropriate

Manage recurring recipients from People & Team so names, roles, and ownership stay current.

Review recipients at least quarterly.

Writing Better Scheduled Questions

Use explicit time logic and output intent.

Examples:

• "Every Monday, summarize last week's downtime by line and top causes."
• "On the first day of each month, summarize prior month reject trends by SKU family and top changes."

Questions that already work well in chat usually work best as reports after only light cleanup.

Best Candidates for Scheduled Reports

Good report candidates:

• shift or daily summaries
• weekly downtime reviews
• quality trend rollups
• production versus demand snapshots
• leadership summaries that already follow a standard structure

Poor report candidates:

• one-off investigations
• prompts that depend on constantly changing manual context
• exploratory questions that need follow-up every time
• personal nudges that do not need DashboardGenius to rerun the analysis

Scheduled Reports vs Reminders

Use Scheduled Reports when the team needs DashboardGenius to answer a question on a cadence.

Use Reminders when you need to remember to revisit an existing thread, decision, or future condition.

Examples:

• Scheduled Report: "Every Monday, summarize last week's downtime by line and top causes."
• Reminder: "Remind me next Friday to check whether the short-stock items recovered."

Manage Existing Reports

From Scheduled Reports, you can:

• Review active versus paused reports from one list
• Open report details when you need a quick audit
• Pause or resume reports
• Edit settings and recipients
• Delete reports you no longer need

Treat paused reports as intentional backlog, not permanent storage.

Report Ownership Hygiene

Every important scheduled report should have:

• a clear business owner
• a clean recipient list
• a question that still matches the current meeting or decision process

If any of those drift, update the report instead of letting a stale automation keep running.

Troubleshooting

Report output is not useful

Refine the underlying question first, then save again.

Too much email volume

Reduce cadence or narrow recipient lists.

Missing key recipients

Add team members or stakeholders in People & Team, then update the report recipient list.

The summary is technically correct but not decision-ready

Tighten the original question. Specify the metric, period, scope, and desired output so the report does not guess what matters.

A report exists, but nobody trusts it anymore

Re-validate the underlying question against the live source and current routing before deleting it. Many trust problems come from drift in the question, recipient list, or data source rather than the scheduling surface itself.

Next Guide

Continue with Visualizations and Sharing Insights.