Supersets: make exercise grouping clear

Show exactly which exercises are included

MCI’s selection screen places checkmarks beside chosen exercises and asks which content should be included. Boostcamp numbers the workout exercises and puts the selected count in Create Superset (2). Both provide more useful feedback than a generic Create action because a group’s membership is the core decision.

Retain exercise identity, including equipment and variants, when selecting members. Two exercises can share a short title while having different set records. Distinguish the source exercise instance from its library definition; grouping a session instance should not rewrite every future occurrence of that movement. If fewer than the required number are selected, explain what is missing instead of leaving an inexplicably disabled button.

Keep selection stable during filtering, scrolling and thumbnail loading. A count should include the selected exercises outside the visible viewport, with a way to review them. If another edit removes one of the members, resolve that conflict before grouping. Do not create an empty placeholder or pair the next row automatically merely because the original selection is no longer available.

Distinguish selection from a saved group

Strong’s Create Superset dialog includes Cancel and Save and explains that two or more exercises are required. MCI’s later Create Super Set surface uses Group as super set (2). These are clear transaction boundaries: selecting rows is not itself proof that the workout structure has changed.

Stage changes until the person confirms the group. Cancellation should preserve the prior workout exactly, including order, notes and logged sets. After saving, show the members together with a readable group label. Preserve the person’s location in the workout rather than scrolling to the top and making the result difficult to inspect.

Implement the group as a stable relationship among existing exercise instances, not as a destructive delete-and-recreate operation. That makes it possible to retain history and recover a failed save. If grouping is unavailable while a set is being recorded, explain the restriction. Do not accept an action optimistically and then silently drop the active set or its partially entered values.

Explain what previous and next refer to

Alpha Progression offers Superset with previous exercise and Superset with next exercise. MacroFactor Workouts exposes Superset with next in an exercise sheet. These compact actions save space, but their meaning depends on the visible order. If the sheet covers the neighboring exercise, the person must remember which movement is next.

Where possible, name the neighbor in the action or show a preview of the resulting group. Define whether previous and next mean the workout’s saved order, a filtered list or the sequence in a current round. A search or collapsed section should not change the target behind the same label. Disable impossible actions at the start or end of a list with an explanation when useful.

When an exercise is moved, decide whether it takes the group with it or becomes detached. Provide explicit move-group and move-exercise operations if both are supported. Keep the saved execution order visible after the edit, and support an accessible alternative to dragging. A reorder should never duplicate the same set into two groups because the client and server interpreted adjacency differently.

Keep rounds, sets and rest distinct

Caliber’s Create Superset sheet exposes Rounds and Rest separately. Fitbod’s group menu shows four rounds and actions including Log all Superset Exercises, Duplicate Superset and Unbundle Superset. These labels reveal several independent concepts: the plan’s repetition structure, a rest preference and a logging action.

Do not silently normalize every member to the same number of sets. If members have different targets, show the resulting execution rule or ask before changing it. A group round and an individual completed set need distinct identities, particularly when someone skips a movement or changes a target midway through a session. Keep the historical record of what was actually logged.

Rest also needs a named boundary. Is the value applied between member exercises, after a full round or as a default that can be overridden? Explain the supported rule and connect it to the timer only when relevant. An action that logs several exercises should show what it will record, especially when some member sets are already complete. Repeating the action must not double-log completed work.

Keep pairing context and a reversible exit

Hevy’s superset sheet names an exercise to pair and shows a selected candidate. Befit’s Add to Super set sheet offers existing exercises plus Other Exercises. Both need to answer the same question after selection: did this add a new workout member, pair an existing instance or replace an existing relationship?

If a candidate already belongs to another group, explain whether the app merges, moves or rejects the relationship. Ungrouping should detach members without deleting logged sets unless a separate explicit operation requests that deletion. If removing the group also resets rest or order, disclose those consequences before applying it.

Failures need the clarity shown in the mobile error-state collection. Test an active workout with completed sets, one unlogged member, an offline edit and a later server conflict. Ask users to predict membership and order after grouping and unbundling. Measure mistaken group changes and lost-log recovery, not whether a particular exercise pairing produces better physical results.

Test grouping after logging has begun

Start with a workout containing three exercises and different set counts. Log a set in the first exercise, enter but do not save a weight in the second, and then attempt grouping. Specify what happens to that entered value and the historical log before implementing the modal. A successful group creation should not silently copy an unfinished value into every member or recreate completed sets.

Next, move one grouped exercise, remove another and unbundle the remainder. Verify that exercise instances retain their identifiers and history while group membership changes. Test an interrupted save and a conflicting edit from a second client. A group should either be applied coherently or remain visibly pending; a bracket around half the intended members is not a complete transaction.

Use logging tests that include unequal rounds, skipped members and an already completed set. A group-level Log all action must identify exactly what it will record and avoid repeating completed events. Show partial success if the backend cannot save all members together. The person should be able to retry the missing log without producing duplicate set history.

Finally, observe whether someone can predict the next exercise and rest boundary from the saved group. This is a usability check on the execution sequence, not a judgment about the training plan. If participants disagree, improve the group label, order preview or rest description before adding more animation to the creation dialog.

Review grouping with an active workout

Use these checks on a working build, not only on the polished reference state.

• ✓Track exercise instances and group membership separately from library definitions.
• ✓Make selected count, membership, order and confirmation visible before grouping.
• ✓Preserve notes, partially entered values and already logged sets on Cancel or failure.
• ✓Name the adjacent target when previous or next could be ambiguous.
• ✓Explain rounds, uneven set counts and exactly where group rest applies.
• ✓Prevent duplicate logging when a group action includes completed sets.
• ✓Define merge, move and unbundle behavior without silently deleting exercise history.