CEDX Tasks · Projects & Delivery
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.
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.
Runs on demo data. The miss-risk percentages are the deadline model reading the seeded demo set.
What it is
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.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/tasks.
01 — Overview
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.
02 — My day
One list: everything planned for today, with priority, status, remaining estimate, due date, list and owner. The capacity ring next to it reads 752% — which is the point. You triage the day before the day triages you.
03 — Calendar
Mon Aug 3 to Sun Aug 9: each day's cards stack their estimated minutes against the day-capacity line, with today marked. Nothing is over the line this week — planned load 43h 13m of 56h — and the overflow lanes keep the 37 overdue and 103 unscheduled visible.
04 — Lists
System, shared and personal lists in one table: open count, overdue count, estimated minutes and a heat score. The Inbox is hottest at 95 with 16 open and 8 overdue; one personal list carries 25 open and 10 overdue — 935 estimated minutes of one person's queue.
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 shared lists — Legal, Office, Finance, Hire — and watches heat instead of chasing people: 95 on the Inbox means the intake is the bottleneck.
shared lists · 9 of 12
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.
waiting · 45 external deps
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.
office list · 24 openThe 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
Quick-add parses the sentence — “Renew MSA fri 90m p1 Legal” becomes a 90-minute P1 on the Legal list due Friday. Capturing has to be cheaper than remembering.
The task lands on My day or the calendar, where its minutes count against the 8-hour line. A 752% day gets rebuilt before it gets lived.
Status moves inbox → todo → doing → done, with waiting as a first-class state — 45 tasks are parked on named external dependencies, not buried.
The miss-risk model re-scores as dates pass. Overdue tasks surface in their own lane — 63 of them — for an explicit reschedule, not a quiet reddening.
One record
A task is not a separate universe from the delivery board. The renewal, the approval and the follow-up share identity, owners and calendars with everything else the estate runs.
The 48-issue backlog and the sprint commitment are the delivery half of the same week your tasks fill.
CEDX CalendarThe 8-hour day-capacity line the calendar stacks estimates against is the Calendar day, meetings and all.
CEDX NotifyA task going late is a notification decision — who gets told, on which channel, and how often — and that policy lives in Notify.
CEDX DeskCustomer follow-ups in the queue are Desk conversations with a task attached, not a second copy of the request.
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 lists, your people
Tasks 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/tasks. It runs on demo data.
The sum of remaining estimates on today's tasks against your working hours. The demo day carries 60h 9m of planned work on an 8h 0m day, so the ring reads 752% — an absurd plan made visible before it is made a promise.
From what the task knows: due date, remaining estimate, status and age. TSK-1011 scores 90% because 40 minutes of work is due and the task is stuck waiting. The model is a triage aid — it sorts the reschedule conversation, it does not run it.
A blend of open count, overdue count and estimated minutes per list. The Inbox reads 95 with 16 open and 8 overdue; the scale runs down to 60 on the calmest personal list in the demo set.
That is what the waiting status is for. 45 tasks sit in it with the external dependency named, the Overview counts them as a pile, and they still carry miss risk — parking a task does not silence its deadline.
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 add the task you are currently holding in your head.