CEDX Prep · Data & Analytics
Prep turns recurring operations — month-end close, evidence collection, deploy checklists — into templated runs with owners, due dates and sign-offs, and it puts the blocking step in a column called Stuck step.
The Active queue's most honest column isn't Status. It's Stuck step: AP aging exceptions, exception approvals, control sample pull. Blockers you can read are blockers you can clear.
Runs on demo data — the Ops Readiness workspace and the 2026-08-05 board date are the demo seed.
What it is
18 templates carry steps, version, SLA, run counts and done-percent on every row — Month-end close prep on v2.4 with 18 steps and a 3.0-day SLA. Source is declared per template: authored, AI-generated, or captured from a recording.
The Active queue lists 130 runs with the blocking step spelled out — RUN-2380 Month-end close prep sits overdue at 61% on “AP aging exceptions”; RUN-2410 Payroll pre-run validation waits on “Exception approvals” at P0.
The overview scores completeness risk per run — six runs at 95% — and counts 60 runs past SLA, 16 pending sign-offs and an average risk of 54%. Alerts arrive root-caused: RUN-2380 is past SLA with four delayed steps, and the alert says so.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/prep.
01 — Overview
130 active runs, 197 open, 60 overdue, 116 complete. Run health reads 58% with the arithmetic beside it: 197 open runs at 34% average completion, 81 high-risk, 16 sign-offs pending.
02 — Templates
SOC evidence collection: 16 steps, v1.5, 10-day SLA, 25 runs, 19 open, 24% done — marked AI-generated. Weekly backup restore drill: 6 steps, 12-hour SLA, captured from a recording. Drafts can be generated, then reviewed.
03 — Runs
All 320 runs with status, priority, done-percent, due date, team and owner. The tabs do the triage: All 320, Open 197, Overdue 60, Complete 116 — and the overdue tab is the recovery list.
04 — Active
130 active runs with the stuck step named: Customer comms draft, Manager 30-day plan, Canary health gate, Security questionnaire review, Pack QA, Restore sample dataset. 31 are waiting on something external or an approval.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Owns the queue: watches the 60 overdue runs, works the 31-strong waiting list, and reads the stuck-step column before the morning standup.
active queue · 130
Runs SOC evidence collection and control sample pulls — 16-step templates where a rejected sign-off sends the run back with the reason attached.
RUN-2372 · sign-off rejected
Maintains the 18-template library: versions steps, retires stale procedures, and keeps authored, AI-generated and captured sources clearly marked.
18 templates · 11 criticalThe shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your operation — it is the state of the demo data.
How it runs
A procedure becomes a versioned template — authored, AI-drafted, or captured from a recording — with steps, SLA and required proof.
Runs spawn from templates with owners and due dates; 320 are on the demo board, 197 of them open.
Each active run names its stuck step, so the queue reads as a list of blockers to clear rather than statuses to report.
Critical steps require sign-off; a rejection returns the run with the reason — RUN-2372 went back for incomplete evidence.
One record
Prep is not a checklist app with an export button. Its runs, sign-offs and SLAs sit on the same record the data estate measures.
Completion rates, SLA breaches and sign-off lag are exactly the governed metrics Insight certifies and alerts on.
CEDX WarehouseThe warehouse outbound release run coordinates the physical side of what the data estate measures — operational SLAs meet freshness SLAs.
CEDX ReportsThe month-end close run ends in a delivered pack; Reports carries the schedules, opens and stale-report risk for it.
CEDX WorkflowThe approval chains behind the 16 pending sign-offs — exception approvals, dual control — are Workflow's home ground.
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 runbooks, templated
Prep 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/prep. It runs on demo data — the board date and workspace on screen are the demo seed.
It is the template's declared source: a procedure recorded once becomes steps. Weekly backup restore drill and Warehouse outbound release carry that label; authored and AI-generated templates carry theirs. The origin of a procedure is never hidden.
Each template declares an SLA — 6 hours for the deploy checklist, 3.0 days for month-end close. RUN-2380 passed its 3.0-day SLA with four delayed steps, and the overview raised a root-caused alert rather than just reddening a cell.
The run goes back with the reason attached. RUN-2372 SOC evidence collection was rejected for incomplete evidence, and the rework alert names the run, the rejection and the missing proof.
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. Then list the three procedures your team re-learns every quarter.