PRISMAvailable in the dashboard
An organiser proposes a date. Start with the event category, genre and show size; compare the surrounding calendar and two years of performance-date history before committing.
One calendar, three levels
3Explore the month, inspect the week, compare two dates. Every level uses when the show takes place.
◇ Illustrative preview · not live market data
Possible lines of enquiry. The questions that matter most would be defined with your team.
Filter the next thirteen weeks by category or genre and show-size band. Inspect daily competition, then compare two proposed dates side by side. The previous one and two years use matching weekdays, with Ramadan and Eid context shown separately.
A multi-date event occupies every recorded show date. A continuous run spans its dated interval. Month and week totals count the event once; ticket volumes count each show once within the displayed window.
Read the historical genre mix and aggregate paid-ticket demand alongside current competition. Size is based on registered ticket capacity per show, not tickets sold. A busy date and a proven audience are different signals: the comparison explains the evidence and its limits.
Platinumlist coverage only. A quiet date does not prove weak demand or venue availability; a busy date does not prove overbooking. Audience overlap, permits, holidays and the organiser’s brief still matter. Repertoire or language is not inferred from an unrelated genre tag.
Catalogue listings with and without paid sales, performance dates and dated runs, paid tickets allocated to their shows, canonical categories, music tags and registered ticket capacity. Current source date is shown in the dashboard.
Calendar management connects a monthly view, weekly context and daily date comparisons. Filter by event category or music genre and registered show capacity. Compare events selling now with the same lead time last year, then examine what actually took place in the previous two years. Multi-date events occupy each relevant day and count once in period totals. Historical ticket demand is shown only at a safe aggregate level. A nearby-date shortlist explains lower competition and historical activity, without presenting counts as a demand forecast. Ramadan shifts and incomplete coverage remain visible when interpreting a date.
The rhythm / DailyThe government view protects individual customers and businesses. It does not disclose named events, organisers, venues or artists. Small or concentrated groups are withheld.