Costume Change Planner
Check quick-change windows against wardrobe and travel time, with performer-level conflict summaries.
- 1Explore the example
- 2Edit your assumptions
- 3Compare & export
Loading the worked example…
Your working data
Edit cells directly or import a CSV. Download “Input CSV” for the required column names. Up to 200 rows; scroll the table sideways for additional fields.
Detailed analysis
Exports include all results, regardless of the search filter. The HTML report includes assumptions and source data; use your browser’s Print command for PDF.
Chart shows the first 20 rows; negative values use a warm color. Click table headers to sort.
Compare up to four scenarios
Capture the current inputs, change assumptions and capture again. Scenarios are included in downloaded projects.
What this model includes
Uses entered time estimates only. Does not account for mobility needs, crew availability or physically rehearsed change times.
Import and save safely
CSV imports use your current assumptions. Project files restore assumptions, rows and saved scenarios. No automatic saving: download a project before closing this page. Imports are limited to 10 MiB and 200 rows. Calculations run in your browser; the site’s advertising and analytics follow its privacy policy.
Using Costume Change Planner
Check quick-change windows against wardrobe and travel time, with performer-level conflict summaries.
- Review the preloaded example and the model limits before entering real data.
- Adjust extra buffer minutes.
- Edit the performer rows or import a CSV using the Input CSV column template.
- Open Results & chart to inspect details, sort columns and filter rows.
- Capture alternative scenarios, then download a project, result CSV or printable report.
Example
The worked example includes Alex, Sam. Change the first extra buffer minutes setting and compare the result with a saved baseline.
Questions & answers
What does Costume Change Planner calculate?
Check quick-change windows against wardrobe and travel time, with performer-level conflict summaries.
What are the important limitations?
Uses entered time estimates only. Does not account for mobility needs, crew availability or physically rehearsed change times.
Can I continue my work later?
Yes. Save a project JSON file and reopen it with Import CSV / project. It contains the working data, assumptions and up to four scenarios. Nothing is saved automatically.
What CSV columns do I need?
performer, change, exit, entrance, wardrobe, travel. Download Input CSV for a compatible example. CSV imports keep your current assumptions.
Are these example figures current industry benchmarks?
No. They are illustrative values to demonstrate the model. Replace them with figures appropriate to your situation.
Help improve this tool
Report a problem or suggest an improvement
Describe the issue without pasting private tool input. Feedback goes to our admin inbox.
