CEDX People · People & HR
People is the record the rest of the estate reads: a directory where every row carries title, department, manager, status, tenure and an engagement score — with flight risk flagged per person and every team run through a bench-and-gap coverage model.
The Ask HR panel on the overview answers “How does PTO accrual work?” and ends with its source: PTO policy, section 2, updated May 2026. An answer that cites its row is one a person can check.
Runs on demo data. The workspace names itself Northline US Inc. on screen.
What it is
303 people, 1–25 per page, with title, department, manager, status, tenure in months and an engagement score on every row — Support L2 to Controller to Sysadmin. Department tabs run Engineering, Product, Design, Sales, Customer Success, Marketing, Finance, People, and the chips split Active, On leave and Onboarding.
Fourteen teams scored on the same five columns: headcount, risk heads, bench multiple, gap score and impact. One 24-person team runs a 3× bench and still scores gap 100, Severe; another holds an 8× bench at gap 98. The model reads succession depth, not just seats.
The flight-risk board names a risk percentage per flagged profile — 92, 92, 84 at the top of the current view — and the alerts panel attaches a cause and a dollar figure: flight risk at $235K, a support coverage gap at $198K, 45 leave requests past the internal SLA.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/people.
01 — Overview
Headcount 303 against plan, open roles 48, high flight risk 34, on leave 11 with 45 pending approvals behind it, engagement 61 on a 0–100 scale and 12 teams with coverage gaps. The health composite reads 64, and each alert arrives root-caused and priced.
02 — Employees
Search by name, title or email across 303 people. Every row carries title, department, manager, status, tenure and engagement — and the roster counts itself: 285 active, 34 high flight risk at ≥55%, 11 on approved absences.
03 — Org
The org screen scores every team on headcount, risk, bench, gap and impact — 303 people across 14 managers and 12 departments. The weakest coverage in view is gap 100, Severe, on a team with a 3× bench; the strongest sits at gap 20, Watch.
04 — Performance
180 reviews in the H2 2026 cycle — 100 in flight, 37 complete — with tabs for Not started, Self review, Manager review, Calibration and Complete. The rating distribution prints its own rule: 1–2 need action plans; 4–5 feed promotion and retention lists.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Keeps the directory true: statuses, managers, tenures. The 45 pending leave approvals on the overview are their Monday morning.
303 people · 8 departments
Works the flight-risk board and the coverage model — a 92 risk score or a gap-100 team is a conversation, not a chart.
34 flagged · gap to 100
Reads headcount against the hiring plan: 48 approved requisitions against a 303-person roster, by department.
48 open reqs · plan vs actualThe 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
Approved requisitions — 48 in view — sit on the overview next to headcount, so the plan and the actual are read off the same chart.
Every person carries an engagement score, and risk ≥55% lands them on the flight-risk board with a percentage, not a colour.
Each team is scored on bench multiple and gap, so a 24-person team with a 3× bench still reads gap 100, Severe, when the wrong person is single-threaded.
Alerts arrive root-caused and priced — flight risk at $235K, coverage gaps at $198K — and Ask HR answers policy questions with the section it relied on.
One record
People is the record; the rest of the domain is what happens to it. The counts on these captures are the same 303 people.
The 48 open approved requisitions on the People overview are the reqs the pipeline is working.
CEDX LeaveThe 11 on leave and the 45 pending approvals behind them are Leave's queue, on the same roster.
CEDX PerformanceThe 180-review H2 2026 cycle visible inside People is the cycle Performance runs.
CEDX BenefitsEligibility starts here: 251 of the same people are benefits-eligible in plan year 2026.
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 roster, your policies
People 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/people. It runs on demo data, which the workspace labels on screen.
From the software's demo scoring over seeded records — 303 synthetic people with per-person scores. The page cites the figures because they are legible in the captures, not because we claim they predict your workforce.
Bench and gap, per team. The org screen shows headcount, risk heads, a bench multiple from 0.8× to 8×, a gap score and an impact band — so a team can be fully staffed and still read Severe when one person holds a role nobody else can cover.
In the demo it answers from seeded policy content and prints its source — “PTO policy · §2 accrual · updated May 2026” — and the screen says the assistant is scripted. Your policies are a pilot conversation, not something we are demonstrating here.
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 check the coverage score of the team you worry about most.