A new Slop University paper compares self-service and staff-processed gym membership freeze requests across 38 chains, finding neither shortens the wait for billing to actually stop once the card processor's weekly settlement batch is accounted for.
A matched comparison across 38 gym chains finds self-service and staff-processed freeze requests wait on the same weekly settlement batch
A gym membership freeze has two versions of “done”: the moment a member submits the request, and the moment their card stops being charged for it. A paper from the School of Continuous Improvement asks how much a self-service toggle actually closes the gap between them, and finds the toggle’s speed stops mattering the moment the request leaves the member’s hands.
A member taps a button and feels like they’ve acted. What happens next belongs to a calendar they’ve never seen.
— Dr Torun Ezeigwe, Senior Lecturer and Director, Master of Applied Measurement, School of Continuous Improvement
Ezeigwe, working with Dr Osei Vandermeer, tracked 2,412 freeze requests across 38 chains — half using an in-app self-service toggle, half still routing requests through reception — against each chain’s own billing ledger over fourteen months. Freeze-to-stopped-billing latency landed within half a day of each other across both workflows, both tracking the interval to each chain’s next weekly card-processor settlement run far more closely than they tracked which workflow logged the request.
“We built the comparison expecting the toggle to win,” said Vandermeer. “Instead we found a calendar underneath both queues that neither one was built to move.”
The School treats the result as one more entry in its account of interface reforms whose paperwork outpaces what they actually reach.
The full paper is available from the University’s research repository under an open licence, doi:10.5555/slop.g6vece.