GridMagik's internal calendar combines published availability, holds, reservations, payment state, and racing-event overlays. Weekly, monthly, agenda, and list views are available today. Drag rescheduling, staff shifts, and external provider sync are separate roadmap items.
Operators can change the date range, choose a location and booking item, and filter the visible reservation and slot states. Reservation detail remains one click away instead of being flattened into a decorative calendar block.
Visual conflict warnings are useful, but they do not prevent two simultaneous requests from winning. GridMagik now reacquires deterministic resource locks and rereads overlapping reservations inside the booking transaction before committing capacity.
Drag-to-reschedule, automatic guest notifications, shift scheduling, Google Calendar, Microsoft 365, iCal, and CalDAV are not production features today. They require conflict-safe mutations, delivery status, provider webhooks, renewal jobs, and timezone regression coverage.
Move booking → reacquire capacity → preserve money state → deliver notification → record outcome.
Every item names both the capability and its present delivery state.
Navigate operational windows with timezone-aware date handling.
Use dense alternatives when a grid is not the clearest staff view.
Narrow by location, item, payment, status, and slot state.
Display the selected venue and its configured timezone.
Show racing-event windows alongside booking availability.
Rosters, coverage, swaps, and time-clock workflows are not live.
Conflict-safe editing and notification delivery need implementation.
Google, Microsoft, iCal, and CalDAV remain on the roadmap.
The calendar includes a location filter and organization-level context. Any required cross-location portfolio behavior should be demonstrated against the configured workspace before it is included in rollout scope.
Not as a production workflow today. Rescheduling must validate the new server-generated slot, reacquire capacity, preserve payment and communication state, and provide recoverable feedback before drag editing is released.
There is no blanket automatic-notification promise. Communication delivery must be explicit and recorded; advanced reschedule notifications are part of the editing roadmap.
Not yet. The internal operations calendar is live; external two-way connectors are planned and described on the calendar-sync status page.
30-minute walkthrough. Your pricing, your calendar, your receipts — running live in a sandbox on your data. No slides.
