Field note

Why the third week of a workout log goes quiet

12 March 2026 · Aira Cheah

The first week of a new plan is theatrical. People photograph the shoes, tap complete, and send the screenshot to a group chat. The second week is still fuelled by that small audience. The third week is when the tracking app starts to tell a story the gym floor does not recognise.

In George Town the weather does part of the work. An evening run that felt easy in week one feels heavy once the inter-monsoon humidity sits on the Esplanade. Members still go. They log the session as “easy” or they skip the log because the pace looks embarrassing. The app, which only sees a missing tap or a slow kilometre, treats the week as decline.

There is a second, smaller cause we see in boutique rooms. Class check-in is handled by the front desk in week one as a welcome ritual. By week three the desk is busy and members are expected to tap themselves. Many do not, especially after spin, when hands are wet and the cooldown screen is still asking for a rating.

When we read a third-week dip we now ask three questions before anyone rewrites a training plan. Did the member still attend? Did the session type in the app match what happened (a recovery walk logged as a skipped run)? Did the complete-workout prompt appear while they were already in the showers?

None of those questions requires a new badge. They require a coach or a desk person to look at the log beside the timetable. That is slower than a streak warning. It is also how you avoid scolding people who are still in the room.