Padlock feature

The first question we have for you is about how you use the padlock function on future workouts.

Do you understand what it does?
How often do you use it?

We would love your insights so our designer @Levidps can build a better looking and more intuitive app.

1 Like

TBH, initially I thought it was just to avoid accidentally moving a session manually, but is it safe to assume locking a session means the AI can’t change that session if the training program is re-calculated?


I use it to lock in workouts that I enjoy (vo2) to make sure they’re not reduced. I also unlock my custom sessions so it AI wants to remove them it can.


I notice if I move a session, it becomes locked. I’m not sure that is necessary. I usually find myself unlocking it after I move it because I don’t mind if the AI engine adjusts the parameters. When I move a workout, it is because I cannot do the workout on the designated day, but I am OK if the AI adjusts the workout. (I presume the lock stops the AI from adjusting the workout)


I use when I don’t want the AI to adjust a session. I would also like it if setting the padlock prevented accidentally editing the session.


I use the padlock to keep my long run and long rides locked. I have the most time on the weekend so I would rather the other sessions be modified, if reduction is required.

My long ride already caps out at my maximum allowed per my time restrictions so there won’t be any additions there.


I’m with @Paw on this one.

I often switch around workouts based on my schedule. But most of the time this doesn’t mean AI can’t then change the workout a bit based on its new position in the week. Actually, most of the time I actually want the AI to make some small adjustments.

For example, let’s say I moved a VO2 session to the day after a Threshold session. I know this isn’t ideal, but if that’s what my schedule allows, that’s fine. But I do want the AI to re-evaluate the training and maybe adjust. I think that should be, or is, a strength of an AI-based plan instead of a fixed training schedule.

The only times I lock a session is when I’m certain I can/want to do the session, or when I don’t want it to be changed into a longer session.


Do you understand what it does?
My understanding is that a locked workout will not be modified by the ai.

How often do you use it?
I almost always use it to unlock a locked workout so that the ai will modify it to keep the load in range. Like others have mentioned, that typically happens when I move workouts around and they become locked - and I move workouts around every week.

I do also use it to lock longer workouts that I don’t want the ai to scale back, but that’s less frequent.


This is all great feedback. It’s good to see the general awareness that the lock effects the AI adjustment of workouts. Curious what thoughts are on the auto locking of a workout that’s been moved in the calendar.

I’m sure it’ll vary by person.

Generally when I’ve moved a session I’m just re sequencing the order of the sessions in the week. I’m happy for the AI engine to adjust them and don’t need them locked.

Even where I’ve manually added my own sessions. I’m generally okay with them being adapted as long as the shape of the session isn’t radically altered. Sometime I might be converting a rest day followed by a 3 hour aerobic endurance day into two days of 1.5 hours each or 1 hour then 2 hour. I’d be reasonably comfortable with the AI adapting those within reason.

It’s easy enough to unlock but perhaps a user default would be nice. Then the user just has to unlock / lock exceptions to their general preferences.

Do you think that locking the workout from moving is even necessary? E.g. the lock simply locks it from being modified by the AI but all workouts can be freely moved in the calendar by an athlete?


I don’t see any value in a lock preventing you moving a workout. Moving a workout is a deliberate action, due to the nature of the interface, and cannot be done by mistake.

Don’t see the padlock feature here…, :wink:

I agree that it’s not necessary to lock a workout from being moved - but I’ve never had the ai move a workout. Knowing my schedule is super important to me, and if the ai started moving workouts around, I would need to lock the workouts from being moved for scheduling reasons.

Scaling a workout is training-related, so it’s separate from moving a workout. The ai scales for “progressive overload”, but I have never found that schedule-disrupting. But sometimes there are workouts that I don’t want the ai to modify, so I lock them.

My vote would be that:

  • locking a session only impacts whether or not the ai adapts the workout
  • moving a workout does not have anything to do with locking a workout - i.e., that moving a workout does not lock it, and locking a workout does not prevent it from being moved
  • If the ai starts moving workouts, then I could see the need to prevent them from being moved, but I think should be different from locking it from the ai adjustment (maybe a user setting)