Run the shift, not the monthly deck.
Throughput, exceptions and SLA breaches change hourly. Ask for the count now, get told when it crosses a line, and act while it matters.
Activity
Meridian Outfitters
- PR12m ago
Priya Raman pinned a chart Net revenue by region
Revenue analytics · Dashboard
- 07:00
Scheduled run completed Weekly revenue digest
6 tiles refreshed · 3.2s
- DOYesterday
Daniel Okafor saved a query New customers by channel
Verified · semantic
- Yesterday
Compiler refused a query Revenue by campaign
Ambiguous join path on campaigns
- MSMon
Marco Silva connected a source Warehouse
ClickHouse · 118 tables · read only
The questions that come up daily.
Operations questions have a short shelf life. By the time a report answers one, the shift it described is already over.
What is stuck now
How many orders have missed their promised delivery window this week, and which carrier are they on? Asked at eleven, answered at eleven.
Where the backlog sits
Which sites are running above capacity today? Break it down by shift, by line, by region, without waiting for the weekly extract to land.
A report built for yesterday
The dashboard your team watches was built against an export. It answers the question somebody had last month, at the freshness of last night.
Counting the same event twice
A shipment picks up many scans, a ticket many updates. Count orders across those and the exception rate looks worse than the day actually was.
Net revenue by region
Quarter to date
Why you can act on it
Somebody moves trucks on this number.
A stale number and an inflated one fail the same way here. Both send people, vehicles and overtime to the wrong place.
Refresh asks it again
A pinned tile holds the question, not a picture of the answer. Refreshing asks it again against live data, so what you read is what the system says now.
Nine scans, one order
An order with nine scans against it is still one order. iDash reduces to one line per order before it counts, so the exception rate is real.
Refuses rather than guesses
If the data gives it no reliable way to tell two records apart, iDash says so instead of handing you an SLA figure to move people on.
Alerts watch a real number
A watch asks the same checked question on a schedule and tells you when it crosses your line. Nothing fires on a cell somebody forgot to refresh.
The question
What was revenue by region last quarter?
- 1Used your definitionNet revenue, the way your finance team already defines it.
- 2Counted each order onceAn order with six items is still one order, so the total is not inflated.
- 3Grouped by regionFollowed the one clear link from an order to the customer's region.
- Only one way to connect orders to regions, so no ambiguity
- Each order counted once, whatever it contains
- Read only connection, capped at thirty seconds
Ask again tomorrow and it runs the same way.
What changes about the day.
The standup has the number
Ask the question during the meeting and get the count, the split and the chart before the conversation has moved on.
Exceptions come to you
Watch the measures that decide a call, get told when one crosses, and send the result to the channel where the shift already lives.
One board, always current
Pin the tiles the floor actually reads and let them refresh on a schedule, so nobody is rebuilding the same view every Monday morning.
Automation
1 trigger · 1 condition · 2 outcomes
Every weekday at 07:00 UTC
Compared with the trailing 4 week mean
#revenue-alerts
No notification sent
Ask it while it still matters.
Connect a read-only copy of your data, ask what shipped late yesterday, and put a watch on the same question every morning after that.