The wedge
Most calendars are an inbox of meeting invites. Odexy Calendar is the operational schedule — every module that schedules something publishes here, so the team sees one timeline of what's actually happening this week.
What ships today
- Cross-module aggregator — interviews, project deadlines, payroll runs, support SLAs, leave, recurring billing dates.
- Views — month / week / day / agenda. URL-persisted filter + range.
- Today's highlights — dashboard widget summarizing the next 24 hours per role.
- Per-event entity link — every event links back to the source (the interview, the cycle, the run).
- ICS export — subscribe to your Odexy calendar from any external client.
How it integrates
- Recruitment — interview events published here; reschedules re-publish ICS.
- Projects — cycle deadlines + task due dates surface.
- Payroll — run finalize dates and disbursement dates surface.
- Support — SLA breach risks surface as warnings.
- HRM — leave overlays the team view.
How the AI helps
- "What's on my calendar Thursday — and which of those can move?"
- "Find a 30-minute slot next week when all four of these people are free."
- "Subscribe Jane to the recruitment-interview feed for the team she's joining."
Built for scale
- Realtime updates — cross-module event changes broadcast over WebSocket.
- Audit log — event publish + reschedule recorded with the originating module.
- Permissions — per-module event visibility respects the requester's role.
> What's queued, not shipped: external two-way sync (Google Calendar, Outlook, iCloud). Currently outbound ICS subscription only. See Doc 01 §9.
Odexy Calendar vs. the category
| | Odexy Calendar | Google Calendar | Outlook |
|---|---|---|---|
| Aggregates events from your real work tools | ✓ | manual integrations | manual integrations |
| AI sees the schedule context | ✓ | partial | partial |
| One audit log with the rest of your work | ✓ | — | — |
Google Calendar and Outlook own personal scheduling. Odexy Calendar is the operational layer that lives next to them — bringing the work-schedule perspective into one place.
Design-partner take
> "We stopped maintaining a 'team availability' spreadsheet. The schedule is real, and it updates when anyone takes leave or moves an interview." — Design partner, 24-person team