Scheduled Report Delivery: Who, When and How
Every morning, or only when needed? Recipient, timing, format and data-freshness decisions behind scheduled delivery, and where Floemdata stands.

The sales manager wants the report on Monday morning, finance on the first working day of the month, the warehouse only when something goes wrong. A report existing is not enough; it has to reach the right person, at the right moment, in the right form. Scheduled delivery automates that, but set up without four decisions it becomes a new source of noise.
1. Who: roles, not people
If you keep the recipient list by personal name, the report goes into a void when someone leaves. Define it by role (sales management, finance, warehouse) and decide separately which report each role sees and in what scope. Should the sales manager see only their own region? That question is answered before delivery is set up, not after.
2. When: after the data has refreshed
The most common mistake is scheduling the report for 08:00 while the data load finishes at 08:30. The report then sends yesterday's half-loaded data and nobody notices. The rule is simple: tie delivery to the event of the data pipeline finishing successfully, not to a clock time. If the load failed, the report should either not go out at all or go out with a 'data is stale' warning.
3. In what form: file or link
- Attachment (PDF, Excel): easy to open on a phone, but it leaves your control the moment it is sent; it gets forwarded, copied, and old versions circulate.
- Link to the live dashboard: always current and tied to permissions, but the reader has to sign in.
- Short summary plus a link: usually strikes the balance, with the three most important figures in the body and the detail behind the link.
For reports containing personal data an attachment is especially risky; who may receive what, in which form, should be tied to your privacy policy.
4. How often: consider exception reports
A daily report that arrives while everything is normal stops being read within weeks. The alternative is a report that sends only when there is an exception (stock fell below a threshold, overdue receivables rose). Regular summaries stay weekly or monthly; the daily one is kept for deviations only.
Where Floemdata stands
In Floemdata, scheduled tasks run the data pipeline and the API that serves the dashboard, so the data is refreshed at set intervals. Reports and alerts are served in the dashboard and through the API. We did not find a mechanism in the code that sends a scheduled report by e-mail or as a file (SMTP, link delivery and the like), so the delivery pattern in this article is not a feature of the product today. A record saying it is on the roadmap is not verified either.
To begin, list the three reports that arrive regularly today and ask of each: who opens this, for which decision, and how often? Questions are welcome at info@floemdata.com or via Floemdata.