CEDX Shifts · People & HR
Shifts builds the week from templates, fills it against declared availability, and prices what is left open: 183 seats short across six locations, 365 overtime hours at a $22K premium, 17 swaps waiting on a manager.
The overnight SRE seat in Denver is open and the backup is already over weekly hours. The alert prices it at $2.4K — before Monday night, not after the incident review.
Runs on demo data. The schedule names itself Northline Schedule · Week of Aug 4 2026.
What it is
Three hundred twenty shifts with day, window, role, location, assignee, status, fill and hours per row — a Support L1 seat filled 3 of 4, an overnight SRE window open 0 of 2. Generate schedule is a button on the board, not a separate tool.
Lead shadows, night cover, weekend surge, on-call blocks and float pools — each template carries role, window, days, locations and applied count. Six hundred sixty-six instances on the schedule came from forty-eight templates.
One hundred twenty rows of person-by-window preference: Preferred, Available, Limited, Unavailable — with hours and a conflict flag. Forty rows are blocked against the schedule, which is why the schedule knows its own gaps.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/shifts.
01 — Overview
Coverage health sits at -11: 65% filled, 174 high-understaff slots, $22K of overtime premium and 17 swaps past the internal SLA. Alerts name the nights: Denver NOC understaffed at $2.4K, weekday support short at $950 after a leave.
02 — Schedule
Filter by location chip — SF Support, Austin CS, Denver NOC, Chicago Floor, Remote Support, London Desk — or by day. Overnight windows show 22:00–06:00 with the fill fraction that decides whether the night is covered.
03 — Templates
Templates like “Lead shadow · Sales Floor” and “Night cover · CSM Desk” carry their window, days and locations with an applied count beside them — 29 instances each at the top. Drafts stay visible until reviewed.
04 — Availability
Preference per person per window: an SRE preferred for Friday days, limited to four hours on Thursday nights, unavailable Wednesday. Conflicts against the schedule are flagged per row, so a bad assignment is caught at publish.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Builds the week from 48 templates, publishes, then works the 17 pending swaps before the SLA alert fires.
320 shifts · 17 swaps
Declares availability by window and claims open seats — 43 are claimable this week.
43 claimable · 8h shifts
Reads coverage as money: 365 overtime hours at $22K, concentrated on NOC and CSM desks, is a staffing decision, not a surprise.
$163K week · $22K OTThe shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your schedule — it is the state of the demo data.
How it runs
Forty-eight templates define the recurring week — lead shadows, night cover, weekend surge — 666 instances from 48 patterns.
Generate schedule lays the week out by location and day; publishing is what starts the coverage clock.
People claim open seats against declared availability; swaps queue for a manager — 17 are waiting now.
What stays short gets priced: the $2.4K Denver night and the $950 weekday gap are decisions made with numbers, before the shift, not after.
One record
Shifts reads the roster, the leave queue and the time record — because the schedule is where all three collide.
Assignees come from the same 303-person roster; role and location on the shift row are roster fields.
CEDX LeaveAn approved absence empties a seat — the overview alert for seats filled 3 of 4 cites a leave directly.
CEDX TimeClock-in and tracked hours close the loop: the schedule plans the week, Time records what happened.
CEDX ContractorsThe float and surge seats are where contingent coverage shows up on the same board.
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 locations, your templates
Shifts 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/shifts. It runs on demo data, which the schedule labels on screen.
Open and short seats carry a cost figure in the alerts — $2.4K for an understaffed overnight, $950 for a short weekday — alongside the 365 overtime hours at a $22K premium for the week. Demo figures, shown because they are legible in the captures.
Declared per person per window: Preferred, Available, Limited, Unavailable, with hours. Forty rows in the demo conflict with the schedule and are flagged before publish.
Reusable shift patterns — role, window, days, locations — that generate the week. The demo week is 666 applied instances from 48 templates, 8 of them still in draft.
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 the seats in your own week that are quietly 0 of 2.