CEDX Reports · Data & Analytics
Reports schedules and delivers the estate's packs — board decks, digests, scorecards — and keeps the uncomfortable parts on the record: opens, failed runs, orphan owners, and how old the data was when it shipped.
The alert list leads with the pack nobody wants to discuss: Weekly P&L (legacy) still delivering with 14-day-old data, and the stopped incremental load named as the cause.
Runs on demo data — the header says “demo seed · no live SMTP” on the screen itself.
What it is
320 packs carry folder, owner, format, cadence, recipients, opens and data age. The watchlist is mechanical: 107 packs at five days or older, and owners marked Orphan when the person leaves the roster.
The 400-run ledger records status, duration, rows, channel and recipients per delivery — successes at 136s next to partials, and a failed headcount scorecard at 15s with 70K rows attempted.
Stale-report risk scores every pack on age and reach: an AR incidents pack at 20 days old scores 1122.7. 63 high-blast packs are counted separately, because a stale pack with 48 recipients plus three lists is worse than a quiet one.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/reports.
01 — Overview
320 packs, 44 live schedules, 400 sampled runs at 51.5% success, 61% open rate, 3.4-day average data age. The header carries its own honesty: demo seed · no live SMTP.
02 — Library
The plant ops digest: PDF, daily, 48 recipients, 890 opens, 0 days old. A margin digest: monthly, 84 recipients, owner Orphan, 5 days old. The table sorts by opens or age — both are management signals.
03 — Runs
400 sampled runs with channel breakdown — email, chat, webhook, portal — and recipients per send. 164 failed or partial runs sit one filter chip away, queued for retry.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
The named people on each pack who watch opens and data age — and decide whether the weekly digest still earns its 48 recipients.
opens · 890 on the daily digestAssembles the board packs: monthly cadence, slide and PDF formats, and a hard eye on the stale score before anything reaches the board folder.
board packs · monthly cadence
Owns the run ledger: retries the 164 failed or partial sends, watches bounce storms, and keeps recipient lists current as owners change.
runs · 400 sampledThe shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
A pack is defined — format, folder, cadence, recipients — and joins the 320-pack library.
44 live schedules fan packs out daily, weekly, monthly or on demand, across email, chat, webhook and portal.
Each send writes a run: status, duration, rows, channel. Opens are tracked per pack over 30 days.
Stale scores, blast radius and orphan owners surface the packs that need fixing, retiring or a new owner.
One record
Reports is not a mail merge. The packs deliver the estate's certified definitions, and their staleness traces back to the same freshness record everything else reads.
The packs deliver the governed metrics Insight certifies — a stale pack usually means a stale metric upstream.
CEDX WarehouseData age on a pack traces to freshness SLAs on warehouse tables; the 14-day-old P&L is a stopped load, not a PDF problem.
CEDX EmbeddedThe same definitions ship live as embeds; Reports is the scheduled, portable form of the same numbers.
CEDX BooksMonth-end close produces the numbers the board P&L pack delivers — the ledger upstream of the library.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your packs, on the record
Reports with the rest of it
Questions
Yes. Every screenshot is a capture of the running build, and you can open the same build at /app/reports. It runs on demo data with no live SMTP, which the header states on screen.
A score per pack from data age and reach. The AR incidents pack at 20 days old scores 1122.7 and tops the stale movers list; the alerts root-cause it — a stopped incremental load, a skipped weekend refresh — rather than just flagging the age.
Recipients plus distribution lists per pack. 63 packs are counted as high-blast; the plant ops digest reaches 48 recipients plus three lists, so staleness there matters more than on a quiet pack — and the scoring reflects that.
They stay on the ledger. The fail-and-partial filter lists 164 runs with duration, rows and channel, queued for retry — the failure count is on the overview precisely because it is the number most tools hide.
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. Everyone has a weekly pack nobody has opened in a month; the demo estate's are on screen.