EirDance · 0.1.2 · Illustrated guide

Give every dancer time to change.

Build a recital order, see where costume changes are tight, and hand the same checked order to your backstage team. Work stays in your browser. The example below is entirely fictional.

1. Open the app and try a show

After obtaining the separately purchased app, extract the whole EirDance-0.1.2.zip. Open EirDance-0.1.2/eirdance.html in desktop Google Chrome. No installation, account or server is required. Choose Try the synthetic sample for a fictional 42-routine show with 90 dancers. Keep the extracted folder; the HTML is the app.

The first screen offers CSV import and a clearly labelled fictional sample.

For your own show, use Import CSV and a row per routine: ID, Title, Class, Style, Duration, Dancers. Separate names with a semicolon in Dancers; use minutes:seconds such as 3:05 for Duration. A one-row-per-dancer format with a Dancer column is also supported. The app’s Help & CSV format tab explains optional fixed positions and acts. Check the preview before importing: it replaces the current routines, with Undo available.

2. See what needs attention

The card above Run order shows the current hard conflicts. This sample begins with 157 hard conflicts across 38 groups and 33 individual quick-change flags. A group may contain several dancers; the number of rows is not the number of dancer changes.

The fictional sample starts with 157 hard conflicts; the next action is beside the finding.

Open Rules before optimizing your own show. The sample requires at least two routines and five minutes between a dancer’s routines. A soft flag marks fewer than four routines or ten minutes. Transition time is 30 seconds. The 15-minute intermission is after routine 21; by default a change across it is considered sufficient. Confirm that these assumptions fit your dancers and venue.

3. Find an order with fewer conflicts

Choose Find a lower-conflict order above Run order, or focus the button and press Enter. It uses the effort selected under Optimize. With this sample and the default Standard search, hard conflicts fall from 157 to 0. There are still 10 quick changes to review. Search is bounded; that result is not guaranteed for another roster.

The checked sample keeps 42 routines and reports zero hard conflicts, with ten quick changes left.

At a narrow browser width the result and follow-up action remain visible. This is browser emulation, not a physical-phone test.

The fixed opener and finale remain first and last. The end of Act I and beginning of Act II stay beside the intermission. The result table compares Before and Result. Undo restores the previous order and conflict count; Redo restores the checked order. Manual moves also re-check the order.

Choose Review tight changes to open the backstage list. Discuss every remaining change with the people who will run the show. Zero hard conflicts means the configured rules pass for the entered data; it does not validate a real show.

The quick-change list groups the ten flagged dancer transitions by pairs of routines.

4. Export the same checked order

Export offers run order, individual change sheets, quick-change list and a re-importable roster as CSV. PDFs include the same sheets and a complete packet. If hard conflicts remain, the export menu warns you before you download; exports are still available so you can review them.

The export menu warns when the current order still has 157 hard conflicts.

Included example	What to inspect
Run-order CSV / PDF	42 routines plus an intermission; opening and finale fixed. The show lasts 2:28:15, starting at 6:00 PM.
Change-sheet CSV / PDF	All 90 fictional dancers and every appearance, with the next routine and time to change. The PDF has 16 pages.
Quick-change CSV / PDF	Ten individual dancer transitions, grouped by routine pair.
Complete PDF packet	19 pages: two-page run order, 16 pages of dancer sheets and a one-page quick-change list.
Saved project / Roster CSV	Open the saved project in the separately purchased app to inspect the exact rules and order, or use the roster as a format example.

Actual first page of the exported run order: times, dancers, fixed routines and the intermission.

Actual final page of the dancer sheets; fictional names only.

Direct PDF export uses built-in Latin fonts. For names in non-Latin scripts, use Print and Chrome’s Save as PDF, then inspect every name. This walkthrough checked the downloaded PDFs digitally; physical printing was not tested.

5. Save a project backup

The app restores the show from this browser, but browser storage can be cleared. Use File → Save project file after important changes. Use File → Open project file to restore that .eirdance.json file. Our exported backup reopens with all 42 routines and zero hard conflicts. It is safer to keep a project file with each issued set of sheets.

When an import fails

A malformed CSV disables Import and explains the problem. Correct the header and add at least one routine row, then choose the file again. An empty or invalid file should not be treated as a successfully imported show.

The import preview rejects an empty roster; choosing the valid sample recovers normally.

Know what was checked

Desktop Chrome 152 on Linux, offline file opening and fictional rosters. Other browsers, operating systems, real studio exports and physical phones remain unverified.
The optimizer is bounded and may leave conflicts. Review hard rules, remaining quick changes, names, fixed routines, acts and every issued sheet.
One show per project, no per-dancer rule exceptions, cloud sync, email delivery or studio-software API.
Names entered in the roster stay local. Use fictional or anonymized data when requesting support; do not send children’s details unnecessarily.
The free guide and finished example files do not contain the app. The purchased version is a one-time download; no subscription or future update is promised.

Product and purchase details · Support