Compare exercise sequence options using priority, fatigue sensitivity and overlapping demand so the most important work receives intentional placement.
Priority 1 = most important. Fatigue 5 = most sensitive to pre-fatigue. Overlap 5 = high shared demand.
Exercise order affects what is performed early, when the user is comparatively fresh, and what is performed after several demanding movements. That means sequence can change the conditions under which priority work is performed even when the exercise list itself stays unchanged.
This optimizer therefore treats order as a constrained decision. It does not alter the exercises or prescribe loads; it simply compares the entered priority, fatigue sensitivity and overlap information.
Priority-first is appropriate when one or two exercises clearly matter most. Fatigue-first is useful when protecting fatigue-sensitive movements is the main concern. Balance is a compromise that also penalizes high overlap.
The correct mode depends on the session purpose. A sport practice, technical lift, machine availability or coaching requirement can make a manually chosen sequence more appropriate than a generic score.
The optimizer changes sequence, not the exercise list, sets or repetitions. That distinction matters because the application is intended to answer a narrow question: which movement deserves an earlier position under the selected emphasis? The result can then be compared with the user’s current sequence rather than replacing the entire workout design.
Priority tells the tool what matters most to the user. Fatigue sensitivity tells it which movements are more affected by work performed earlier. Combining the two produces a transparent sequence signal. Overlap is also included so exercises with shared demand are not treated as completely independent.
Real sessions include constraints that a simple optimizer cannot see: rack availability, supersets, coaching cues, warm-up progression, sport-specific order, technical practice and equipment sharing. Those constraints can justify a different sequence. The application makes its rule visible so the user can understand the trade-off and intentionally override it.
If a high-priority squat has high fatigue sensitivity and is currently placed after several demanding leg movements, the optimizer will normally move it earlier. If the session goal changes to pre-fatigue or a different sport-specific sequence, the user can keep the original order.
The output can serve as a discussion document: compare the current sequence, review the proposed order, and identify which exercise positions are being protected. This makes programming conversations more concrete without pretending that the application can replace coaching judgment.
Often that is a sensible starting point when performance on that exercise is the priority, but technical, equipment and session-specific reasons can justify another order.
It represents how much an exercise shares demand with other exercises in the session. It is a user-entered planning signal, not a laboratory measurement.
Yes, although the tool is most useful when you enter the relative fatigue and priority of each component honestly.
No. It focuses on sequence. Use it alongside tools that handle time, rest, volume or exercise substitution.