Income is up. The team needs to know how much came from selling more tickets, higher prices or a different performance schedule.
Make the reporting window clear
Agree the Monday–Sunday window, performance dates and venue sources. Mark missing or late reports and make corrected information flow through to the totals. Everyone in the meeting should be able to tell whether they are looking at a complete week.
Choose a fair comparison
Compare equivalent production weeks, considering performance count and the stage of the run. Year-on-year views help when the underlying periods are comparable. Agree that basis with the team before labelling a change as growth or decline.
Show what sits behind the income
Put ticket quantities, attendance and average ticket price alongside the total, with clear gross or net definitions. Weather and competing events may provide useful context, but a shared date alone does not establish the cause of a change.
Keep future bookings in their own view
Tickets sold this week may be for a later performance. Show advance bookings separately from income attributed to performances already given, using definitions agreed with finance. That keeps demand ahead distinct from the week just delivered.
Bring the report back to a decision
Use the first dashboard to answer one recurring meeting question. Let the team inspect the figures behind it, flag gaps and decide the next action. Add further views when they help answer another real question.
What this gives your team
A total starts the conversation; the comparison makes it useful.
A well-defined report helps the team see where growth is coming from and which questions remain open.