CORPSRequest a season review

Controlled automation for ballet companies

Prepares the cast change. Never calls the curtain.

Corps reads the injury flag, checks hours and contracts, and drafts every call and notice a substitution needs. Then it stops, until the ballet master signs. Every change keeps its evidence and a one-step way back.

Map your seasonReview the controls
Corps does
Read, check, draft, record
People do
Approve, release, overrule
Workflow trace · sample dataRun 0187 / Review required

Giselle, Act II — Thursday & Saturday

  1. 09:12:0401 · IntakePhysio flag receivedM. Okafor (Myrtha) — rest 72 h, cleared from Thu 14:00 call
  2. 09:12:0602 · PolicyFour checks recordedWeekly hour cap · contract role · partnering history · rest gap
  3. 09:12:0903 · ActionCast change preparedL. Varga to Myrtha, Thu + Sat. Call sheet redrafted, not sent
  4. 09:12:1104 · AuditEvidence packet attachedPhysio ref PX-2291 · hours ledger · draft notices to 6 people
Human approval gateOwner · Ballet master

Nothing reaches the studio until the ballet master reviews the cast, the hours and the rollback plan.

L. Varga · load this week if approved25.5 / 30 h cap
4 / 4Checks recorded
1Approval pending
1 stepRollback to original cast
Sample workflow trace for run 0187: a physio rest flag for one dancer leads to four recorded checks, a prepared cast change and an evidence packet. The change is waiting for the ballet master's approval and can be rolled back in one step.

01 — The problem

One sprained ankle on a Tuesday rewrites the whole week.

14calls to rewriteStudio, stage and costume calls that named the injured dancer
6people to tellDancer, understudy, partner, ballet master, wardrobe, stage management
3contracts to readRole tier, overtime clause and touring rider for the understudy
47minby hand, start to sentTimed once by the company office, one substitution, Oct 2025

Scope: one substitution in a sample week at Northbank Ballet, 2025–26 season, counted from their office’s schedule export. Not a benchmark, not an average.

02 — Workflows

Four workflows. Each one shows its permissions, its approver and its way back.

Open a row to see what Corps may read and write, who signs, what it records, what stops it, and how the change is undone.

  • Intake → Checks → Draft → Approval → Release → Audit

    Summary
    Reads the rest flag, finds eligible understudies, checks hours and contract tier, and drafts the cast change with every notice it implies.
    Permissions
    Read: casting grid, rehearsal calendar, physio clear/rest flag (never the note). Write: drafts only.
    Action
    Drafts a cast change, a redrafted call sheet and six notifications. Nothing is sent.
    Approval
    Ballet master, or the artistic director as deputy. A rehearsal assistant can view but not approve.
    Output
    Published call sheet, updated casting grid, notices to dancer, partner, wardrobe and stage management.
    Audit
    Who flagged, which checks ran with their inputs, who approved, when each notice was read.
    Exception
    No eligible understudy under the hour cap: the run stops and names the constraint instead of breaking it.
    Rollback
    One step back to the last approved cast. Sent notices are retracted with a correction, not deleted.

03 — Product

Run 0187, every state it can be in.

Sample data, deterministic. Act as the ballet master or as a rehearsal assistant, approve or deny, then roll back — or jump to any state from the list.

Acting as

States

Corps · Northbank Ballet · GiselleData as of 09:12
Awaiting approvalRun 0187

Cast change ready for your review

Corps did

    Corps did not

        04 — Security & governance

        Each control answers a specific risk.

        There are no badges on this page. In the review we show you the current security assessment, the sub-processor list and the data processing agreement — and say plainly what we do not have yet.

        RiskControlWhere you see it
        A dancer is cast against medical adviceA rest flag is a hard block. Corps cannot clear it; only the physio’s own system can.Trace · Policy
        The schedule changes without anyone decidingEvery change is a draft until a named owner approves it. Drafts never reach dancers.Approval gate
        Too many people can change too muchRoles are scoped per company, studio and production. New users start read-only.Permissions
        Health information spreadsMedical notes stay in your physio system. Corps stores a flag, a date and a reference.Audit packet
        A bad change is releasedOne step back to the last approved state; sent notices are corrected, never silently erased.Rollback
        The model drafts something wrongRule checks run before and after every draft. A failed check halts the run and names it.Exception

        05 — Case studies

        What was connected, what was approved, what they said.

        Northbank Ballet

        Leeds · 62 dancers

        substitutions

        Implementation facts

        • Live since 3 Feb 2026 on one production, then the full repertoire from 1 Apr
        • Connected: rehearsal calendar, casting grid, physio rest flags (read-only)
        • Not connected: payroll, ticketing
        • 118 substitutions approved, 9 denied, 2 rolled back to 30 Sep 2026

        In their words

        “I still make the call. I just make it with the call sheet already written and the hours already counted.”

        — Ines Halloran, Ballet Mistress

        Interpretation

        Our reading: the ballet master’s review moved from building the change to judging it.

        Ask about a pilot like this →

        Lindqvist Dance Theatre

        Gothenburg · 34 dancers, 2 tours a year

        touring

        Implementation facts

        • Pilot on the spring 2026 tour: 11 venues, 5 countries
        • Connected: touring party list, venue riders, freight manifest
        • Per diems drafted in Corps, released from their finance system
        • 22 per diem batches approved, 1 withdrawn before release

        In their words

        “The batch is ready when I land. Finance still presses the button, which is how we want it.”

        — Johan Ek, Tour Manager

        Interpretation

        Our reading: approval time fell because the evidence came with the batch, not because anything skipped review.

        Ask about a pilot like this →

        06 — Questions buyers ask

        Ownership, data, failure, procurement.

        Who owns a change once Corps drafts it?

        The person who approves it. Corps records itself as the drafter and the approver as the owner; the audit packet names both. If nobody approves, nothing happens.

        What data does Corps read, and what does it keep?

        Calendars, casting grids, room bookings and touring lists through read-only connections. From the physio system it reads only a rest/clear flag, a date and a reference. Drafts and audit packets are kept for the season plus two years, or as your policy sets.

        Which systems does it connect to?

        Google and Microsoft calendars, the common casting spreadsheets, two physio record systems and CSV exports for anything else. If your system is not on the list, we say so in the first call instead of promising a connector.

        Who reviews what the model writes?

        Your named approvers, every time, for every workflow on this page. Deterministic checks run first and again after the draft; a human signs before anything leaves Corps.

        What happens when something fails mid-run?

        The run stops at the failed step, keeps everything it prepared as a draft and tells the owner which step failed and why. Partial releases are listed item by item with a one-step rollback.

        How does procurement work?

        A season licence per company, priced by ensemble size. We send our data processing agreement, sub-processor list and the current security review status before you sign — including what we do not have yet.

        07 — Season review

        For companies with a resident ensemble and a ballet master who signs the call sheet.

        We map one workflow from your current season — usually substitutions — against your systems, roles and approval rules, and tell you whether Corps fits. If it doesn’t, you keep the map.

        Who receives it
        Our two-person implementation team, not a sales queue.
        Response
        A reply within two working days with three proposed times.
        Data use
        Only to arrange the review. Deleted after 90 days if we don’t work together.
        Request a season reviewSample form · nothing is sent

        ← All skills