Hi Syead,

Our use case is schedule quality, gap analysis and coverage planning for our Rosters.
Two goals:
Forecast — we pull per-interval staffing requirements (required staff per 30-min interval, per workstream/task: Phone, Sync, Triage). We compare these against actual scheduled headcount to find under/over-staffed intervals and drive coverage recommendations (which agents to move between queues to close gaps). Without Forecast in the warehouse, we can't measure schedule adequacy — only what was scheduled, not what was needed.
Schedule Events — we use the event definitions (team meetings, 1:1s) with their recurrence and attendee rules (teams/roles/users) to validate attendance: who is supposed to be in a given meeting/event vs who is actually scheduled for it. This catches missed tasks and agents missing required to assist X events.

 Calendars — we'd also like this table if it isn't already in scope. The recurrence pattern for each event (frequency/interval/anchor date) lives here, and we need it to reconstruct when each recurring meeting/1:1 should occur for attendance reporting across historical and future periods.

 Together with the shift/schedule data we already sync, these let us report on: coverage vs. forecast by interval/queue, cross-queue reallocation opportunities, and meeting/1:1 attendance compliance.

The Forecasting Table is also relevant in providing actual volume influx and the two different forecast methodologies we have in place for most of our worsktreams, allowing us to report on forecasts' accuracy amongst other things.