The Staff Engine

The failure mode this prevents

Every gym eventually grows a hero: the staff member who knows where the spare fobs live, which member needs a gentle reminder about chalk, how the class waitlist actually works, and what to do when the aircon trips. Then the hero resigns with two weeks' notice, and you discover that your operations manual was a person. The fortnight after they leave, standards drop shift to shift, members notice before you do, and you are back on the floor doing a job you thought you had hired out. The Staff Engine's premise is blunt: if a job lives in someone's head, it is not a system yet. Operator experience That is the standing rule at our gym: every recurring job has one named owner and a written handover, or it is treated as undocumented and gets documented.

The operating system

The procedure

1. The role charter. One page per role listing every recurring job it owns, each with a cadence and a definition of done. “Clean the floor” is not a job; “machines wiped and racked by close, photo standard met” is. Every recurring job in the gym appears on exactly one charter. Jobs on zero charters are owned by the owner by default, which is the trap this whole system exists to spring you from.
2. The handover document. For each role, a written doc good enough that a competent stranger could run the role for a week: logins and where credentials live, supplier and contractor contacts, the weekly rhythm, the five most common problems and their fixes, and what to escalate. Written by the person in the role, verified by someone else actually following it, refreshed every HANDOVER_REFRESH.
3. Shift standards. Open and close checklists with a photo standard for the floor, so “clean” and “set up” mean the same thing on Tuesday night as Sunday morning. The standard is the photo, not the adjective.
4. The escalation ladder. Three tiers, thresholds written down: decide alone (under ESCALATE_SPEND, routine member issues), decide and report (ESCALATE_MESSAGE items, logged same day), and call now (ESCALATE_CALL items: injuries, police, media, anything involving a child, building emergencies). Staff who do not know the thresholds will either interrupt you constantly or, worse, sit on something serious.
5. The ops meeting. Short, fixed cadence per OPS_CADENCE, same agenda every time: incidents since last meeting, standards drift, handover gaps found, one improvement shipped. Cancel it twice in a row and the engine is off.