Why spreadsheets break down for multi-department show design

For one department, a spreadsheet is a fine way to build a show. A lighting designer can build sixty rows of cues, color them by song section, and be done. But once lasers, video, pyro, and lighting are all designing against the same set at the same time, a spreadsheet stops being a workflow and starts being a liability. It was built to hold rows and columns. It was never built to hold time, and a show is nothing but time.

What do spreadsheets actually get right for show design?

Give credit where it's due. A spreadsheet is free, everyone already knows how to use it, and it's genuinely good for a single department's cue list. Color coding cues by act, sorting by timestamp, dropping in notes for the LD or laser op, all of that works fine when one person owns the file and everyone else just reads it.

The trouble starts the second "reads it" becomes "edits it."

Where does a shared spreadsheet start to break?

For my whole career, a spreadsheet has been on literally every show bigger than a simple production. The shape is almost always the same: one row per song, columns for each department, checkboxes for coverage (is lasers on this song or not), then colors, notes, and some kind of status. I could go on for a while about where it breaks down, but here are the questions that actually come up:

• For this version of the set, what needs to be done?
• What colors do you want at this particular moment?
• What do you actually want at any given moment? Timestamps aren't intuitive to design against, and the alternative is a sheet where one cell equals one beat?!
• Who's working on this song right now? Not who it's assigned to. Who is actually in it at this moment.
• Has this section been programmed yet? Signed off yet? Because every time a song breaks down from one component into multiple moments, phases, cues, or beats, you duplicate the row.

Underneath every one of those questions is the same pattern. Department A adds a row for a new moment at 2:14 in the set. Department B was already using that same 2:14 for their own cue and didn't see A's edit because their tab hadn't refreshed yet. Now there are two versions of the truth for the same fifteen seconds of the show, and nobody notices until tech rehearsal, when the LD calls a cue the laser op has never seen.

Google's own help pages on collaborating in Sheets point to version history and named versions as the fix for exactly this kind of conflict. That's a reasonable safety net for a document. It's a bad way to run a live show, because by the time you're restoring a named version, the show is already tomorrow.

What happens when the track changes two days before doors?

This is where multi-department spreadsheets really fall apart. A DJ swaps a track, or a headliner cuts sixteen bars out of the bridge, two days before doors. Every row below that edit point, in every department's tab, is now off by however many beats got cut. Lighting has to renumber. Lasers have to renumber. Video has to renumber. And because each department has its own tab, or its own separate file entirely, there's no single place where "the track changed" automatically ripples through everyone's cues. Someone has to notice, then tell everyone, then hope everyone actually updates their copy before the next run-through.

Paul Bradley, founder of the touring platform Master Tour, described the same failure mode in PLSN's coverage of Master Tour's venue data push: "One missed email, attached pdf, text or errant spreadsheet entry has the potential to have downstream effects that incur unplanned event costs and consume margin." That's true up the chain between tour and venue. It's just as true across the table between departments on the same show.

Why doesn't "just add more tabs" fix it?

More tabs means more places for the same fifteen seconds of a song to have four different descriptions. It also means whoever is coordinating the show, usually the production manager or show director, has to manually cross-check every department's tab against every other one before every rehearsal. That's not coordination. That's babysitting a filing system, and it eats a production week without adding anything to the show itself.

The deeper issue is that a spreadsheet has no concept of musical time. Rows are just rows. If your show runs on bars and beats instead of a fixed clock, and most DJ and festival sets do, a spreadsheet can't tell you that beat 64 moved when the track changed. A human has to catch that, every time, in every tab, and humans miss things two days before doors.

What actually replaces the spreadsheet?

Not a bigger spreadsheet, and not a heavier desktop tool either. What multi-department shows need is one shared timeline, locked to the actual beats of the track, that every department edits in real time and sees update the moment anyone else makes a change. That's the planning layer: the layer that sits before lighting, lasers, and video ever touch a desk, where the whole show gets designed together against the same clock.

This doesn't replace GrandMA, ShowKontrol, or whatever desk your show runs execution on. It just means everyone shows up to programming day already agreeing on where the cues are, because they designed them together instead of reconciling five spreadsheets the night before.