The scheduling problem nobody talks about

This is not a story about technology. It is a story about people who give up their evenings and weekends to put on shows that matter to their communities, and the invisible administrative weight that sits on the shoulders of the small number of people who make those shows happen.

If you run, direct, choreograph, or manage a performing arts organisation, you will recognise what follows. The specifics might differ. The frustration will not.

Most performing arts productions begin the same way. You advertise. People audition. And somewhere in that process, you ask them to tell you when they are not available during the rehearsal period.

This is sensible. You need to know. And for a brief moment, you have exactly the data you need, collected in one place, reasonably accurate, reasonably complete.

Then casting happens. Rehearsals are scheduled. And that data immediately begins to age.

Life does not pause because your production has started. A cast member books a family holiday they forgot about when they auditioned. Someone's work rota changes. A child gets ill. A business trip appears. The availability that felt solid in September looks very different by November.

For most organisations, the process of managing that change falls to one person. Usually a production secretary or administrator. Sometimes an organiser. Occasionally a director who already has enough to think about. That person becomes the single point of contact for every change, every question, every update. They carry the spreadsheet in their head as much as on their screen.

The tool of choice, almost universally, is a spreadsheet. And to be fair to the spreadsheet, it is not a bad tool for this job. It is flexible. Everyone can open it. It holds a lot of information in a small space.

The problem is not the spreadsheet itself. The problem is everything around it.

Who owns it? Who updates it when something changes? How does the production team know it has changed? How does the cast know the rehearsal schedule has been updated? How does a cast member check whether they are needed on Thursday evening without sending a message to someone who is trying to have their dinner?

The spreadsheet answers none of these questions. It just holds the data and waits to be looked at by someone who knows it exists and remembers to check it.

We ran productions this way for years. We built availability matrices that we were genuinely proud of. We shared rehearsal schedules as Word documents. We updated them when things changed and sent them out again. We answered the same questions on WhatsApp that were already answered in the document we had just sent.

It worked, in the way that things work when everyone involved is committed enough to make them work despite the friction.

The next logical step, for organisations with a web presence, is to put the information online. Password protect a page. Share the login details with the cast. Keep the rehearsal schedule there, updated in real time.

We tried this. It solved part of the problem. The information was at least in one place, and it was always current.

But it introduced a new problem: you were still asking people to come to the information. You were relying on cast members to remember the URL, remember the password, remember to check the page, and then filter through a full organisation schedule to find the rehearsals that were relevant to them.

Most people did not do this consistently. Not because they did not care, but because checking a website is an extra step in an already full life. The information was available. It was simply not findable in the moments when people needed it.

The questions kept coming. The group chat kept filling up. The person managing the schedule kept answering the same things.

The most elegant solution we found before building something of our own was a Google Sheet embedded inside the organisation's website. The production team would update the sheet directly, and the embedded version on the website would reflect those changes immediately.

It was a genuine step forward. No more sending updated Word documents. No more version confusion. The schedule was always current, and it was visible to anyone who found their way to the right page.

But it still showed everything to everyone. A cast member looking for their own rehearsals had to read through the full schedule and work out which sessions applied to them. And they still had to remember to go and look. The information was better organised. The fundamental behaviour problem remained unsolved.

The question that shifted everything was a simple one.

Every cast member already has a calendar on their phone. They check it before they book plans, before they commit to anything, before they tell their employer they need to leave early. That calendar is the one place in their life where time-sensitive information actually reaches them.

So why were we asking them to check somewhere else?

The answer was not to build a better website page or a smarter spreadsheet. The answer was to put the right information into the place people were already looking. Personalised to each cast member. Showing only the rehearsals they were called for. Updated automatically when anything changed.

And if a cast member could update their own availability in the same system, the production team would see those changes immediately, without anyone having to send a message to anyone else.

This was the foundation of what became The Rehearsal Hub.

The first version was functional rather than beautiful. It allowed cast members to log in, see their personal rehearsal schedule, and declare their unavailability. It generated a personal iCal feed that each member could subscribe to in their phone's calendar app.

The effect was immediate and measurable. The questions on the group chat reduced significantly. Cast members arrived at rehearsals knowing what was being rehearsed and whether they were needed. The production team spent less time answering messages and more time preparing.

What we also learned was that the cast member experience was only part of the picture. The production team needed their own tools. The ability to see, at a glance, who was unavailable for an upcoming rehearsal. To take an attendance register on the night. To track patterns over time and identify cast members who might be falling behind.

And the organiser needed something different again. An overview of the whole organisation. The ability to invite members, manage multiple productions, track membership fees, and have confidence that the information flowing through the organisation was accurate and current.

Three different roles. Three different views of the same information. One system that connects them.

Everything described here happened within one organisation. But in speaking to production secretaries, administrators, and directors across the performing arts world, we have not yet found an organisation that does not recognise the problem.

The tools vary. Some organisations use Facebook groups. Some use dedicated WhatsApp channels for each production. Some have built remarkably sophisticated spreadsheet systems that work beautifully until the person who built them steps back from the role.

The pattern is consistent. Valuable information exists somewhere. Getting it to the right people, at the right time, in a form they will actually engage with, relies on a combination of manual effort, good intentions, and institutional memory that walks out of the door whenever a key person moves on.

Performing arts organisations deserve tools built for how they actually work. Not adapted from project management software. Not repurposed from sports club apps. Tools that understand the difference between a principal and an ensemble member, between a show date and a rehearsal, between someone who is unavailable and someone who simply has not been called.

The Rehearsal Hub is built by people who have sat in the rehearsal room, managed the spreadsheet, answered the WhatsApp messages, and wondered whether there was a better way.

There is. And we would like to show it to you.