Management Reporting | Scheduled Reports
Reports that arrive, not reports someone remembers to pull.
Any dashboard or report on a daily, weekly, monthly or custom cadence. Excel for the controller, PDF for the board, JSON for the data team. Delivered by email, Slack, S3 or webhook, as a snapshot plus the live link, so the recipient has both the number as it was and the number as it is.
What the system does
Capability, input, output.
| Capability | Input | Output |
|---|---|---|
| Cadence | Any saved report | Daily, weekly, monthly, or tied to a close event rather than a date |
| Format | The recipient | Excel, PDF or JSON, chosen per recipient rather than per report |
| Delivery | A schedule | Email, Slack, S3 or webhook |
| Snapshot and link | A delivered report | The figures as at delivery, plus a live link for the current position |
| Access respected | The recipient’s scope | Delivered content honours their permissions, not the sender’s |
| Failure handling | A delivery that did not land | Surfaced, rather than silently not arriving |
| Audit of access | Report distribution | Who received what and when, which the privacy question eventually needs |
-
Cadence
- Input
- Any saved report
- Output
- Daily, weekly, monthly, or tied to a close event rather than a date
-
Format
- Input
- The recipient
- Output
- Excel, PDF or JSON, chosen per recipient rather than per report
-
Delivery
- Input
- A schedule
- Output
- Email, Slack, S3 or webhook
-
Snapshot and link
- Input
- A delivered report
- Output
- The figures as at delivery, plus a live link for the current position
-
Access respected
- Input
- The recipient’s scope
- Output
- Delivered content honours their permissions, not the sender’s
-
Failure handling
- Input
- A delivery that did not land
- Output
- Surfaced, rather than silently not arriving
-
Audit of access
- Input
- Report distribution
- Output
- Who received what and when, which the privacy question eventually needs
Scheduled Reports FAQ
What buyers ask.
Why send a snapshot and a link rather than just a link?
Because the two answer different questions. A month-end pack should say what the numbers were at month end even when read in March. A link alone silently rewrites history; a snapshot alone goes stale. Both together is the honest answer.
Does a scheduled report respect permissions?
It honours the recipient’s scope, not the sender’s. A schedule set up by the CFO does not hand a department head the whole company, which is an easy and common leak in report distribution.
What if a delivery fails?
It is surfaced. A report that quietly did not arrive is worse than one that visibly failed, because nobody investigates a silence until a decision has already been made without it.
Can we tie a schedule to close rather than a date?
Yes, and most teams should. A pack dated the fifth is wrong whenever close runs long; a pack triggered by close is right every time.
Is there a record of who received what?
Yes. Distribution is logged, which matters both for the privacy question and for the more common one of who was actually told.
Put your recurring reports on a schedule.
Connect your books, free. Set the cadence, the format and the recipients, and stop pulling reports by hand.