CEDX Calendar · Workplace
Fourteen calendars, 320 events, 72 open double-book conflicts — and the six per cent of the week that is still protected for focus. The calendar scores its own collisions so you can fix them before Thursday does.
Most calendars show you what is booked. This one shows what is broken: 37 critical conflicts, 15 overloaded people, and a focus policy whose effect on cancels it prints next to the chart.
Runs on demo data. People named on screen belong to the demo workspace.
What it is
Type “1:1 with Priya Tue 10:00 30m” and the event is built as you type — title, person, day, duration. The catalogue underneath holds 320 events with code, type, status and organiser, so the fast path and the ledger stay the same record.
Seven primary calendars, five shared or team, one room resource and one holiday calendar. Visibility is per calendar: the rooms calendar at HQ West is fully visible with 140 events; primary calendars default to busy-only; US holidays is shared with 120 people.
Twelve people, 180 slots sampled this week: 86 busy, 25 free, 32 tentative, 37 out of office. Each slot names its event — ops handoff 11:00 to 11:45, design review, churn review — so “find us an hour” is a query, not a thread.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/calendar.
01 — Overview
Open conflicts 72 — up to 24 with 8 critical on Wednesday and Thursday. Three engineers past a load score of 75 with a focus deficit over 60%. A demo scheduling link whose show rate dipped from 91% to 72%. Each alert arrives root-caused, with the fix attached.
02 — Events
182 upcoming, 101 completed, 38 flagged for conflict. A product critique with five people sits next to a one-person OOO — both first-class, both searchable by title, organiser or code.
03 — Calendars
Every calendar lists its kind, owner, event count, shared count and visibility. Finance close runs full visibility for 15 people; most primaries stay busy-only. You can read who sees what without asking.
04 — Free / busy
The grid shows this week's 180 slots across 12 people with state and event per slot. Free slots are visible as free — 25 of them — which is the whole point of the exercise.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Reads the load table, not the room. Three engineers past 75 load score and a focus deficit over 60% is a staffing conversation with evidence attached.
load score · 95 peak
Owns the conflicts queue. The mid-week double-book spike — 24 open, 8 critical — is theirs to clear before it becomes Thursday's apology.
open conflicts · 72
Lives in the free/busy grid. Finds the 25 open slots across twelve people without sending a single “does Tuesday work” message.
free slots · 25The 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
Events land by quick add or by scheduling link — 41 links are active, with show rates tracked per link.
Focus blocks are scheduled like meetings. The focus-default policy ran in week 2 and the overview prints what it did to cancels.
Conflicts get flagged as they form — 72 open now, 37 critical — instead of being discovered when two meetings start at once.
The load table shows who is over 75 before the week does. Managers move work; the calendar shows the effect.
One record
Events are not isolated rectangles. They are the same people, meetings and bookings the rest of the estate already knows about.
The meetings on these calendars are scored after they end — attendance, no-show rate and ROI live in Meet.
CEDX BookingsThe 41 active scheduling links are booking pages; their show rates and no-show risk are Bookings' home turf.
CEDX ChatThe on-call and standup calendars meet the channels where the same teams actually talk.
CEDX MailInvites and demo requests arrive in the shared inbox and land here as events on the same record.
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 calendars, your rooms
Calendar 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/calendar. It runs on demo data — the people, events and conflicts belong to a demo workspace, not to a customer.
Open conflicts are counted as they form — 72 in the demo view, 37 of them critical — and the overview root-causes the spike: mid-week, concentrated on Wednesday and Thursday. The point is to see the collision while there is still time to move one side of it.
A per-person meeting-load figure visible in the highest-meeting-load table — the top of the demo table sits at 95 with 37.6 hours. Three engineers past 75 with a focus deficit over 60% triggered the capacity alert.
Yes, as calendar kinds. The calendars view lists one resource calendar — rooms at HQ West, 140 events, fully visible — alongside primary, shared and holiday calendars, each with its own sharing line.
Six per cent of the scheduled week is blocked as focus time. The overview also prints the policy experiment: a week-2 focus-default rule correlated with roughly 12% fewer cancels — on this demo dataset, stated on screen.
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 your own Thursday conflicts.