Reports
Validated, repeatable answers with provenance. Reports keep the spec — not just a moment in time.
Scheduled reports
3
2 destinations
Deliveries · 7d
128
+1899.2% delivered
Failed deliveries
1
+1fleet utilization
Median freshness
1h 48m
at read time
| Report | Status | Dataset | Timeframe | Schedule | Destinations | Last run | |
|---|---|---|---|---|---|---|---|
| Revenue by teamWeekly team revenue with comparison against the prior period. | Scheduled | Billing replica | Rolling 7 days | Weekdays · 09:00 ET | TelegramDiscord | Today, 09:002h ago | |
| Delayed ordersOrders past the provisioning SLA with age and owner. | Scheduled | Orders replica | Rolling 48 hours | Every 4 hours | Telegram | Today, 09:002h ago | |
| MRR movementNew, expansion, contraction, and churn for the month. | Paused | Billing replica | Month to date | Weekly · Mon 08:00 | EmailDiscord | Nov 11, 08:001d ago | |
| Support quality rollupResolution outcomes, response speed, and source gaps. | Scheduled | Support warehouse | Previous calendar week | Weekly · Mon 07:00 | Telegram | Nov 10, 07:002d ago | |
| Fleet utilizationRemote device availability and utilization by account. | Failed | AIO fleet API | Yesterday | Daily · 18:00 | Discord | Nov 11, 18:001d ago |
How report trust works
Every report keeps a specification: dataset, metric definitions, filters, comparison, and timezone.
Totals are calculated in SQL. The model explains the verified result and never estimates a number.
Delivery permissions are rechecked at execution — a channel move can break a schedule.
Runs snapshot the data cutoff so a repeated run is reproducible.
Start from a question
Ask in plain language. Tandem interprets the timeframe, shows the SQL-backed result, and lets you save the validated spec as a recurring report.