Generate Production Packs and Stage Exports
Create scoped production packs, contact sheets, running-order change logs, public schedule exports, and Document Centre artifacts from published versions.
Article guidance
Exports are for turning the current SmartGig record into a file someone can brief from, carry, archive, or send. Generate them after the relevant schedule and production information has been reviewed, not while important fields are still changing.
Main Stage Manager exports
- Running-order CSV or PDF for schedule sharing and archive records.
- Default all-stage/all-day production pack PDF queued automatically when a running order is published.
- Stage/day-scoped production packs with running order, stage specs, act contacts, rider notes, structured technical profile fields, production notes, and file index.
- Default all-stage/all-day performer contact sheet CSV queued automatically when a running order is published.
- Performer contact sheet CSV with scheduled contact fields only.
- Running-order change-log CSV comparing a published version with the previous published or archived version.
- Document Centre artifacts for generated running orders, production or tech packs, contact sheets, and change logs where available.
What publishing queues
- Publishing a clean running order queues the running-order CSV and PDF, the running-order change log, the default production pack PDF, and the default performer contact sheet CSV.
- Default publish artifacts cover every stage and every event day for that published version.
- Use scoped exports when a crew member only needs one stage, one day, or a narrower handoff.
Generate a production pack
- Publish the running order version: Production packs should usually be generated from a stable published version.
- Choose the scope: Select the version, stage, and event day needed by the recipient or team.
- Generate the pack: SmartGig queues the export and includes the latest relevant rider, technical, contact, stage, and file-index data for that scope.
- Record delivery: When you send the pack, record who received it, the channel used, and any useful notes.
- Watch stale indicators: If a newer published version or performer technical follow-up lands after delivery, the delivery can be flagged for follow-up.
- Message crew from Communications: Use the Stage crew recipient selector when a production recipient needs an email or SMS update that is not tied to a stale pack or link.
Use contact sheets carefully
- Contact sheets are designed for scheduled contact details.
- They exclude rider notes, technical requirements, production notes, files, and custom answers to avoid oversharing.
- Choose the same version, stage, and day scope you would use for the team that needs the contact list.