Case Studies/Equinox

What the Best Trainers Knew (and Nobody Had Written Down): Equinox

Equinox’s top trainers had years of programming know-how in their heads — periodization, injury modifications, how to progress members. None of it was documented in a way others could use. ADL structured it into a training knowledge base new trainers could access from day one. Ramp-up dropped 70%; member churn from trainer turnover dropped 45%.

Equinox

Snapshot

Client
Equinox
Domain
Personal training operations & coaching methodology
Timeline
7 months
Team
2 Design Engineers, 1 Fitness Domain Lead
Services
Knowledge Architecture Ontology Design Workflow Integration
Environment
Existing scheduling platform, trainer tablets, member app (no new tools introduced)

Results

70%

faster new-trainer ramp

45%

reduction in churn from trainer turnover

1

shared knowledge base across clubs

About Equinox

Equinox. 100+ locations in the U.S. and abroad. Premium gym. Personal training is the core offer.

Trainers are highly credentialed. The best ones build multi-month progressions, adapt for injuries and goals, keep members for years. That’s what people pay for. And most of it lived in people’s heads.

The Problem

The best trainers carried years of programming knowledge. Periodization, injury modification trees, progression logic for different body types and goals. None of it written down in a form anyone else could use.

When a senior trainer left or moved clubs, members felt it. New trainer started from scratch — different philosophy, progressions, language. Churn wasn’t about the new trainer being bad. Continuity broke.

New trainers shadowed for months before they could program on their own. Tier 3+ methodology lived in PDFs, Slack threads, and the heads of trainers who’d been there a decade. Earlier “standardization” pushes had failed. Trainers rejected rigid templates that didn’t match how they actually worked.

What We Built

A training knowledge system that captured how the best coaches program — without turning it into a script. Wired into the tools trainers already use.

  • Mapped programming variables — goals, phases, movement patterns, contraindications, progression triggers — into a structure that matches how experienced trainers think
  • Senior trainers’ periodization, modification logic, and member-progression frameworks documented as reusable decision trees, not fixed templates
  • Structured handoffs so when a trainer leaves or a member transfers, the next trainer gets context: history, preferences, injuries, what’s been tried
  • Lives in the existing trainer tablets and scheduling platform. Suggestions show up at session prep, not in a separate system
  • Knowledge base grows as trainers contribute. Gets richer with use.

The Shift

Before
After
Programming expertise in senior trainers’ heads
Structured methodology anyone can reference
Months of shadowing before new trainers could program alone
New hires get frameworks from day one
Trainer leaves, member loses their program
Handoffs preserve continuity
Modification knowledge verbal or missing
Injury and adaptation logic as searchable decision trees
Standardization = “too rigid”, rejected
Captures nuance without prescribing a script
Methodology in PDFs, Slack, memory
One knowledge base that grows with use

“Twelve years in. First system that actually captured how I think about programming. Not the dumbed-down version.”

Marcus WebbTier 3+ Personal Training Manager

Ready to scope your project? We'll map, design, and build the right solution.