One schedule from Command Center syncs to every Edge unit. Single source of truth.
One schedule.
Every location.
Identical.
When every site plans independently, quality drifts. The Tuesday HIIT class at the flagship looks nothing like the Tuesday HIIT class in the suburbs. Choccy Box gives you central design with local execution — schedule from HQ once, run identically across every Edge unit, even when sites are offline.
Quality drifts. Brand suffers. Members notice.
Three locations was manageable. Five became inconsistent. Seven means HQ is firefighting. The system that worked when you knew every coach by name doesn't work when staff turnover happens at three sites simultaneously.
The symptom: members at site A get a tighter, better-presented class than members at site B. The cause: every site is reinventing the same workout from a shared spreadsheet, with different coaches interpreting timing, transitions, and station setups differently.
The fix isn't more rules. It's removing the interpretation step. Design the class once. Push it to every location. Let the Edge unit at each site execute it identically — same timing, same cues, same station layouts, same audio.
Central control without central dependency.
When a site needs to deviate (different equipment, different class size), override locally without forking the master schedule.
Every schedule and workout change is tracked. Roll back when something doesn't work as planned.
Same workout = same exercises, same timing, same audio cues, same station layouts. Across every site, every class, every week.
See which locations run on time, where members drop off, which class formats sell out. (Without sending member data anywhere it shouldn't go.)
Every TV in every site looks identical. Members travelling between locations get the same experience.
Local execution, fully resilient.
Each Edge unit runs the day's class library locally. WiFi out? Sync issue with HQ? Class still runs.
Coaches at each site drive class from their iPhone. No remote-control nonsense from HQ during a live class.
If a TV at one site drops connection, it rejoins the local cluster automatically. HQ doesn't need to be involved.
Each site sees its own performance — class fill rates, on-time starts, member checkouts.