Loading...

2026.10.08

Why Do Multimillion-Dollar Events Still Run on Spreadsheets?

Author
Juliano Wahab
CEO, Monet
Wireframe arena stage standing on a grid of spreadsheet cells, with one red cell beneath a corner.

It is the industry's open secret. What spreadsheets do well, and what they can't do.

Producers run huge shows on spreadsheets, and the sheet deserves more credit than it gets. This post shows what sheets do well, the five ways they break, and the modest fixes that work. You also get a health check, a guide to where each kind of data belongs, and a template whose tabs link instead of copy.

Event production spreadsheets survive for good reasons. They bend to fit any show, everyone can open them, and they cost nothing. They fail where data must stay the same across people, versions and drawings. Plenty of multimillion-dollar events still run on messy Excel sheets. The sheet has earned both its defense and its critics.

The confession

Here is the confession. Many big shows run on a handful of familiar tabs, such as the run of show and the labor grid. A run of show is the timed script of the event. A labor grid shows which crew work when. Producers rebuild those same tabs for every new project.

These workbooks age with the team, and some tabs outlast the staff who built them. None of this means the events are badly run. Some of the best-run events work from very well-built sheets.

What spreadsheets do well

The case for the sheet is strong. Everyone can open one, there is no monthly fee, and it bends to fit any show. A run of show is a table by nature. So are a labor grid, a gear list and a budget.

A well-built schedule in Google Sheets is also easy for a client to open, with no new login to learn. A sheet refined over years holds know-how that most software never captures. That is why planners and producers alike keep theirs.

Where event production spreadsheets break

They fail in five specific ways. The first is a single point of failure. A sheet is fragile when everything lives in one person's head. The second is copy drift. Each show clones last year's file, and the copies slowly drift apart.

The third is cells that depend on each other. One late client change can mean updating dozens of cells by hand. The fourth is versions and access, when nobody is sure which file is current or who may edit it. The fifth is that a sheet cannot check itself against the room. A gear list made years ago may not match a venue that has changed since.

A late change exposes all five at once, as the guide to last-minute event changes shows.

The tool-stack trap

The usual answer is more software. A team ends up with one tool for registration, another for messages and a third for tracking. Each one works on its own. Together they can feel heavier than the event itself.

The trade-off is simple. You can use the best tool for each job and be the glue yourself. Or you can use one platform with less depth and fewer handoffs. The guide to event design software covers the drawing side of that choice.

Email alone is no answer either. Run suppliers by email with no plan, and deadlines slip. Email plus a strict project plan can work well. The plan does the work, not the tool.

Fixes that work

The fixes are modest.

  1. Keep one cloud master per show, with a named owner and a deputy.
  2. Build templates whose tabs link to one data table instead of copying it.
  3. Put shared data such as sessions, speakers, rooms and crew in database-style tables. Airtable is one tool built this way.
  4. Use data validation and drop-downs, so each room name is spelled one way.
  5. Keep a change log of what changed, who changed it and when.
  6. Map every place one change must land. This is the "one change, six touches" problem.

Spreadsheet health check

  • Owner: One named owner and one deputy
  • Master: One cloud file per show, no emailed copies
  • Links: Every tab looks up from one data table
  • Validation: Shared fields use drop-downs
  • Change log: Every edit after sign-off is logged

Where each kind of data belongs

  • Run of show, labor grid, gear list, budget: A sheet
  • Sessions, speakers, rooms, crew, suppliers: A database-style table
  • Floor plans, room sets, sightlines, exits, clearances: A drawing

A template that links instead of copies

  • A Data tab, with one row per session, room, crew member and item.
  • A Run of show tab that looks up session, room and time from Data.
  • A Labor grid tab that looks up crew and calls from Data.
  • A Gear list tab that looks up rooms and items from Data.
  • A Change log tab with the date, the change, the owner and the tabs affected.

Where the spreadsheet stops

Spatial data does not fit in cells. Floor plans, room sets, sightlines, exits and clearances need a drawing. So the work splits in two. Room lists stay in a sheet, and floor plans live in a drawing tool such as SketchUp.

The gap between the drawing and the labor and gear sheets is where late changes break. A production-ready drawing is only useful if the sheets agree with it.

One source for the drawings

Keep the sheet for what it does well. Move what must stay in step into one source. Then a change made once reaches the plan, the drawings and every sheet that depends on them.

Frequently asked questions

Is Airtable better than Excel for event production?

For shared data such as sessions, speakers, rooms and crew, a database-style tool stops you copying the same row into many tabs. For a budget or a one-off grid, a spreadsheet is quicker. You can use both, as long as one of them is named the source of truth.

What should a run of show spreadsheet include?

Each line needs a time, a length, the segment and the speaker or act. Add the room, the audio, video and lighting cues, any stage moves and an owner. Put a version date at the top. Link speaker and room names to one data table, so one change shows up everywhere.

How do you keep event spreadsheets in sync?

Keep one cloud master per show with a named owner. Make every other tab look up from it. Lock shared fields with drop-downs, and log every change after sign-off. Emailed copies are where versions drift apart, so stop sending them.

What is a labor grid in event production?

It is a table of crew roles against time. It shows who is called, when, where and for how long, often with rates and totals. It drives crew booking and cost. So it has to change whenever the run of show or the room set changes.

For the spatial side, Monet can be that one source. One change regenerates the plan, renders and drawings, and the layout checks re-run, so the drawing never lags behind the sheets that depend on it.

:: Share

Loading...