How do I set up stage management software for building run sheets and distributing updates to multiple departments?

To set up stage management software for run sheets and multi-department updates, think in terms of one master source of truth, then controlled sharing to each department.

1) Define your workflow first

Before configuring software, decide:

• Who creates the run sheet
• Who approves changes
• Who receives updates
• What departments need separate views
  (e.g., stage management, audio, lighting, video, wardrobe, props, automation, company management)

A good rule:
One master schedule → department-specific call sheets / run sheets → change notifications.

2) Choose software that supports:

Look for features like:

• Version control / revision history
• Role-based permissions
• Collaborative editing
• Export to PDF / print
• Mobile access
• Notifications or alerts
• Document templates
• Timecode / cue linking if needed for shows

Common options include:

• Google Workspace / Microsoft 365 for lightweight collaboration
• Airtable / Notion / Smartsheet / Monday.com for structured run sheets and updates
• Dedicated stage management tools if your production is more advanced
• PDF workflow + email/Slack/Teams if your team prefers simple distribution

3) Build a master template

Create a standard run sheet template with sections like:

• Date / show / venue
• Call times
• Rehearsal blocks
• Scene or cue sequence
• Department notes
• Breaks
• Special instructions
• Contacts / emergency info
• Revision number and timestamp

Use consistent columns if it’s tabular:

• Time
• Item
• Department
• Responsible person
• Status
• Notes

4) Set up department-specific views

Instead of sending the whole document to everyone, create filtered views by department:

• Lighting sees lighting cues, notes, and deadlines
• Audio sees sound checks and pickup times
• Wardrobe sees quick changes and preset info
• Stage crew sees scene shifts and backstage traffic

This reduces confusion and keeps people focused on what matters to them.

5) Use a change-control system

Changes should be tracked clearly:

• Assign a revision number
• Log what changed
• Log when it changed
• Log who made it
• Mark urgent changes as “UPDATED” or “TIME-SENSITIVE”

A simple change log at the top or bottom of the sheet helps a lot.

6) Automate distribution

Set up a repeatable distribution method:

• Master document stored in one shared location
• Automated export or PDF snapshot for each revision
• Email, Slack, Teams, or SMS alerts when a new version is posted
• Department mailing lists or group chats for each team

Best practice:

• Send a short summary of changes
• Attach or link the revised run sheet
• Highlight what each department needs to know

7) Control permissions

Not everyone should be able to edit everything. Typical setup:

• Stage manager / assistant stage manager: full edit access
• Department heads: comment or limited edit access
• Crew: view-only
• Production management: view-only or approval access

This prevents accidental edits and conflicting versions.

8) Create a daily update routine

For show days, establish a rhythm:

• Morning: publish the latest run sheet
• Pre-call: send any updates
• Half-hour before call: final confirmation
• Post-show: archive notes and revision

Consistency matters more than software complexity.

9) Archive and name files clearly

Use a naming convention like:

• ShowName_RunSheet_2026-07-25_v03
• ShowName_DepartmentUpdate_Lights_v03
• ShowName_DailyReport_2026-07-25

Keep an archive folder by date and version so the team can always find the latest approved file.

10) Test it with a small workflow

Before opening night:

• Send one sample run sheet
• Make a fake update
• Check who receives it
• Confirm everyone can access the correct version
• Make sure the latest file is obvious

---

Simple recommended setup

If you want a straightforward system:

1. Create master run sheet in Airtable / Google Sheets / Smartsheet
2. Keep department-specific filtered views
3. Export PDF after each revision
4. Send via email/Slack/Teams with revision number
5. Maintain a change log
6. Store all versions in a shared drive

---

If you want, I can also help you with:

• a sample run sheet template
• a department update workflow
• a software recommendation based on your budget and team size
• a step-by-step setup in Google Sheets, Airtable, Notion, or Excel