Dance Showcases Schedule Import

This guide explains dance showcases schedule import for dance event organisers and backstage coordinators. Start by preparing clean scheduling data and checking a small sample. Then use the example and checks below to agree a practical next step with the people who run the schedule.

Dance showcases organise company arrivals, approved warm-up sessions, dressing-area use, stage preparation and the presentation sequence. Performers and group leaders may appear in several programme items, while backstage spaces and technical resources are shared. A practical timetable connects those duties without deciding artistic content or performer suitability. It should make the next stage handover and preparation owner clear to company leaders. Participant records and costume or production files remain in their established processes, while the operational schedule uses neutral group and item labels to show confirmed people, spaces and agreed transitions.

Dance Showcases Schedule Import: worked example

Illustrative planning example. The numbers and timings below explain a possible situation; they are not customer results or required staffing standards.

An illustrative production workbook combines participant records, costume notes and operational duties. The schedule needs neutral company codes and approved windows. Repeated appearances use similar item names, which can cause accidental merging during import preparation.

Create stable item and company identities, extract approved duty fields and omit participant-level records. Import one company’s two-appearance sequence and verify distinct stage calls before adding the remaining showcase programme.

Check the result: The sample preserves both appearances and their preparation ownership, while participant and costume records remain outside routine scheduling labels and broadly shared volunteer duty outputs.

Dance Showcases Schedule Import: setup checklist

Separate the operational schedule from the register

Event and programme workbooks may contain participant names, contact details, payments, pastoral notes or tentative ideas alongside the timetable. Create a scheduling-only source using approved activity codes, supported date and time fields, confirmed people and stable resource identities. Omit personal or transactional information that the duty view does not need. Distinguish proposals from confirmed activities before importing. Normalise room and volunteer names across worksheets so the same resource or person does not appear under several aliases.

This preparation gives the organiser a source that can be checked against the intended programme without turning every register row into a scheduled duty.

Reconcile one complete activity sequence

Choose a representative activity that includes preparation, the session itself and a closing or equipment handover. Count the intended duties in the checked source, then inspect the imported dates, owners and resource identities. Include a dated availability exception or shared resource if it is central to the programme. Correct the source before importing the remaining period. Keep the approved staging file and a short record of the checks so another planner can repeat the process.

Accurate import is a data step; the organiser still needs to approve the resulting assignments and prepare the current references that the programme team will use.

Questions to ask before choosing software

Test scheduling with multiple companies, a shared warm-up area and one performer appearing in successive items. Ask backstage leaders to follow the complete preparation route. Artistic direction, participant arrangements and technical approval stay with the event team. The scheduler supports the approved programme’s space allocation, staff duties and handovers around those decisions.

Bring a representative example to your evaluation. Review the current VeloRoster plan and its limits and Try interactive demo → that reflects your team’s people, spaces and timing needs.

Frequently asked questions

What should we avoid when planning dance showcases?

• Assigning a group leader to simultaneous warm-up and stage duties.
• Treating empty backstage space as approved for any group.
• Omitting changes between appearances by the same performer or company.

Review these points with the activity owner before you approve the plan.

Should attendee registers be imported into the roster?

Use only information needed for approved scheduling duties. Neutral group codes often suffice. Participant contacts, payments or sensitive personal notes can remain in their established systems. Review the intended operational fields before importing a programme workbook that contains several kinds of information.

How can duplicate duty imports be spotted?

Compare the expected activity count and neutral references in a small checked source with the imported result. Review whether proposals, actual-time records or repeated register rows have become extra duties. Resolve those source issues before extending the import to the full programme.

What should be checked after an accurate import?

Review people availability, approved role assignments, room use, shared resources and handovers with the organiser. A file can import correctly while its plan still contains an operational conflict. Distribute the timetable only after the responsible leaders accept the relevant assignments.

Take the next step. Explore the VeloRoster interactive demo with sample data, then check your requirements against the current access and pricing details. Keep the operational decisions in this guide with the people responsible for your organisation’s schedule.