Our safeguarding lead asked how teacher-pupil comms were structured on day three. I walked her through the per-show channel model, she signed it off the same week, we've not had a single comms concern since. That's a first for a school production.
End-of-year shows, house plays, summer festivals. Limelight is the bit that lets the head of drama actually go home at half past five - because the call sheet went out without her having to do it.
Four shows running in parallel without crossed wires. Each house has its own channel; the head of drama sees everything; pupils only see their own.
Push reminders ahead of every rehearsal go to the phone in the pupil's blazer pocket. The schedule updates live, so nobody is reading last week's plan.
When drama, music and dance teachers collaborate on a single production, each owns their slice as a co-director. Pupils see the show as one; staff keep their patches.
All teacher-pupil show comms happen inside Limelight. Push notifications reach the phone. The personal mobile stays personal.
Every message routed through one channel and logged server-side. DPA, sub-processor list and security overview on request. If a disclosure needs evidence retrieved, the founder will help your DSL with it.
Pre-rehearsal notifications go to the phone in the blazer pocket. The schedule lives in the app, so cast can check tomorrow's call between lessons.
Drama, music and house plays each get their own show space. Teachers admin their own, pupils only see what they're cast in. SLT sees the lot.
Our safeguarding lead asked how teacher-pupil comms were structured on day three. I walked her through the per-show channel model, she signed it off the same week, we've not had a single comms concern since. That's a first for a school production.
Bring your DSL to the walkthrough. We'll show you the audit log first.