When a coach updates an activity after it has already been assigned to a client, the client continues to see the original version. The only workaround is to resend the program, which creates a duplicate in the client's portal and causes confusion.

This is a significant issue for coaches who are actively building and refining a new program. Iterating based on client feedback is a normal part of launching a new coaching program. The current architecture does not support this workflow.

The requested feature: when a coach updates an activity, push the updated version automatically to any enrolled client who has not yet opened or started that activity. Clients who are already in progress or have completed the activity stay on their version — protecting their existing work. Only clients who have not yet started the activity receive the update.

This would make Quenza genuinely usable for coaches who are actively building and improving new programs — without forcing them to choose between leaving clients on outdated content or creating duplicate programs in their portal.