Capture & Ingest
Records land in CEDX Tasks already linked to the canonical customer, employee, or vendor ID.
Tasks keeps the small work (renewals, approvals, requests, follow-ups) and scores each one for deadline risk. Then it does the sum nobody else does: your 107 tasks today estimate to 60h 9m against an 8-hour day.
"Having identity, least-privilege access, audit trails, and business applications on one kernel cut our security review..."
| Program / Client Engagement | Milestone & Sprint Phase | Delivery Principal | Budget / Billable Margin | Capacity Utilization | Delivery Health |
|---|---|---|---|---|---|
| Meridian Global ERP RolloutCEDX Tasks · Record #1040 | Phase 03 · Data Migration | K. Vance · Principal Architect | $680,000 · 44% Margin | ● 88.5% Billable Util | On Schedule |
| Q4 Core Kernel Release v4.8CEDX Tasks · Record #1041 | Sprint 22 · 64 Story Points | A. Rostova · Staff Eng Lead | 18 Engineers Allocated | ● 92.0% Sprint Velocity | Zero Blockers |
| Harbor Retail POS DeploymentCEDX Tasks · Record #1042 | 180 Stores · Wave 2 Cutover | M. Okafor · Program Dir | $510,000 · 41% Margin | ● 85.2% Field Capacity | Milestone Billed |
| SOC-2 & ISO Continuous AuditCEDX Tasks · Record #1043 | Control Evidence Automation | R. Lin · Security PMO | $140,000 Internal Cap | ● 100% Evidence Linked | Audit Ready |
The quick-add reads “Renew MSA fri 90m p1 Legal” and parses the lot: day, estimate, priority, list. The point of a task tool is that capturing is cheaper than remembering.
Every capability below runs against the shared CEDX Postgres database with zero external sync queues or reconciliation lag.
My day totals the estimate of everything you planned: 60h 9m of remaining work against an 8h 0m day, a utilisation of 752%, headroom zero. Most tools let you plan that day. This one prints what it costs before you promise it.
Every open task carries a miss forecast. The top of the table reads TSK-1011 at 90% (40 minutes of estimated work, due yesterday, stuck waiting), and the model's average across the workspace is 32%, with 51 tasks rated high.
The week lays estimated minutes against an 8-hour day-capacity line, per day. Planned load is 43h 13m of a 56h week, over-capacity days read zero, because the 37 overdue tasks, 23h 15m of them, sit in their own lane below, pulled into the week honestly.
Every figure below is directly inspectable in the running CEDX Tasks application workspace with zero synthetic projections.
Click any screen below to inspect how CEDX Tasks moves from initial intake to verified cross-estate completion.
220 open tasks, 107 on your day, 14 due today, 63 overdue, 45 waiting on someone else. The alerts do the triage for you: a vendor renewal at 90% miss risk, one person at 107% day utilisation with 9 overdue, and the overdue queue sitting above its 4-week median.
Engineering sprints, consultant timesheets, resource bench capacity, and milestone billing read from the exact same project object.
Records land in CEDX Tasks already linked to the canonical customer, employee, or vendor ID.
Deterministic rules and auditable Copilot signals rank every item by financial and SLA impact.
Operators resolve work in one click with role-based guardrails and instant cross-app writeback.
Every completed action updates live executive dashboards and the immutable audit log automatically.
Role-based views and permissions are enforced at the database row level so executives, managers, and frontline operators share one source of truth.
Owns the shared lists (Legal, Office, Finance, Hire) and watches heat instead of chasing people: 95 on the Inbox means the intake is the bottleneck.
Works the customer follow-ups out of the queue: waiting is a status with a count (45), not a place tasks go to be forgotten.
Access requests, vendor renewals, runbook edits: the tasks that keep a site running, each with an estimate and a due date instead of a hallway promise.
CEDX Tasks is not an isolated point tool. It reads and writes the exact same customer, ledger, and identity records as the rest of the CEDX software estate.
The 48-issue backlog and the sprint commitment are the delivery half of the same week your tasks fill.
The 8-hour day-capacity line the calendar stacks estimates against is the Calendar day, meetings and all.
A task going late is a notification decision (who gets told, on which channel, and how often), and that policy lives in Notify.
Customer follow-ups in the queue are Desk conversations with a task attached, not a second copy of the request.
"Having identity, least-privilege access, audit trails, and business applications on one kernel cut our security review and provisioning time by 82%."
"We started with one application to fix our most painful bottleneck, and added five more modules on the same login without a single migration project."
"Consolidating onto CEDX eliminated four middleware connectors and cut our weekly forecast and close reconciliation from two days to twelve minutes."
Drag the seat slider to compare your current stitched stack (Jira Align + Kantata (Mavenlink) + Asana Enterprise + Float + Tempo) against running CEDX Tasks natively on the unified CEDX estate.
Explore the live CEDX Tasks workspace on canonical demo data at /app/tasks, or book a 30-minute architecture session to map your first entity rollout.
Instant browser access to CEDX Tasks pre-loaded with canonical demo records and connected across the 132-application CEDX estate.