CEDX Leave · People & HR
Leave runs time off the way support runs tickets: every request has a type, an age and an SLA; every approval checks coverage first; and long leave — parental, medical, family — runs as a case with an entitlement meter and a return-to-work plan.
The alert that says the most costs the least: four of nine Support L1 out the same week in August, priced at $48K. Nobody booked anything wrong. The coverage score caught what the calendar could not.
Runs on demo data. The workspace names itself Northline Leave · H2 2026 on screen.
What it is
Fifty-two pending approvals showing type, days, start, age, SLA state, coverage impact and approver — 27 already over the soft SLA at three days or more, 19 flagged elevated impact. The oldest in view has waited twenty days.
Fourteen open statutory and long-leave cases — parental, medical, family, intermittent — each with a stage from Opened to Return-to-work, an entitlement meter like 42 of 60 days, and a docs column chasing certifications.
The overview prices absence against the roster: a Support L1 gap the week of Aug 18–22 at $48K, on-call thin during blackout-adjacent days at $92K, a critical role's five-day request mid-sprint at $148K. Approval is where coverage should be argued, and here it is.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/leave.
01 — Overview
Fifty-two pending approvals, eighteen people out today, 2,032 days used year to date, 48 severe coverage gaps and a leave health composite of 45. Alerts arrive root-caused: coverage gaps, backlog over the soft SLA, a critical role's request mid-sprint.
02 — Requests
Three hundred twenty requests across PTO, Sick, Parental, Unpaid, Bereavement, Jury and Volunteer — with status, start, days and approver per row. Nineteen pending requests are flagged critical; a 65-day parental approval reads next to a one-day PTO.
03 — Approvals
The approver's view: age in days on every row, SLA state, coverage impact. Twenty-seven rows sit over the soft SLA, and the queue itself admits the backlog in its own alert — 52 requests still pending.
04 — Leave cases
Cases move Opened → Docs pending → Approved → Active → Return-to-work. Entitlement meters show 0 of 112 days on a new parental case, 42 of 60 on one nearing return, and the docs column counts the certifications still missing.
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 cases: entitlement meters, certifications, return-to-work plans — the parts of leave that run for months, not days.
14 cases · 10 docs outstanding
Works the approval queue against coverage — a yes is easy; a yes with 4 of 9 of the team out the same week is a decision.
52 pending · 27 over SLA
Files by type — PTO to bereavement — and sees the same status the approver sees, not a black box.
7 types · status per rowThe shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your team — it is the state of the demo data.
How it runs
The employee files by type — PTO, Sick, Parental, Unpaid, Bereavement, Jury, Volunteer — with days and dates; critical roles are tagged at filing.
The request enters the queue with an age and a coverage score. Twenty-seven of fifty-two are over the soft SLA right now; the queue says so.
Coverage is scored per team before approval — the $48K Support L1 gap alert is four overlapping approvals, caught before the week, not after.
Long leave ends in a staged return-to-work plan; two are active in the demo, with entitlement meters showing exactly what remains.
One record
Leave reads the roster and writes back to the products that schedule, pay and review the same people.
The 11 on leave and 45 pending approvals on the People overview are this queue, on the same roster.
CEDX ShiftsAn approved absence empties a seat — the Shifts captures show seats filled 3 of 4 the week a leave lands.
CEDX TimeTracked hours stop where approved absence starts; the two products read the same person record.
CEDX PayrollLeave type and entitlement are exactly what a pay run needs to know; the record carries both.
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 policies, your teams
Leave 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/leave. It runs on demo data, which the workspace labels on screen.
Per team, per week, against the roster — the demo alert for Aug 18–22 is four of nine Support L1 out the same week, priced at $48K before approval, not after the phones went quiet.
Statutory or long leave — parental, medical, family, intermittent — managed as a case with a stage, an entitlement meter in days, a documents checklist and a return-to-work plan, instead of a row in the requests table.
A soft target of 2.0 days for an approval decision. The demo shows 27 of 52 pending requests at age three days or more — and a monthly actual of 1.8 days when the queue is worked.
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 count how many of your own approvals are quietly past three days.