Counting repetitions consistently in exercises performed one side at a time

Decide what one repetition means

In a one-sided exercise, the word “repetition” can refer to one completed movement by one limb, one count after both sides have worked, or one movement cycle that alternates sides. A lifting log can use any of those conventions if it states which one it uses. Trouble starts when the same chart silently combines them. A person may then appear to perform twice as much work in one session, or half as much in another, even when the exercise routine was similar.

I recommend recording the side and the counting rule with the set. An entry might show repetitions for the left side and repetitions for the right side separately, or it may show a single total that explicitly counts each completed limb action. The system should also distinguish “per side” from “combined.” That makes the entry easier to compare with the plan and helps a later reader understand whether a one-sided set was completed on both sides.

These fields are not decoration. Training research describes the movement pattern and how total work is calculated. A study that compared unilateral and bilateral resistance exercise calculated total volume from repetitions and load lifted per repetition, and treated the two limbs in the unilateral condition as part of the session total. A different app might summarize the set in a different way, but it should disclose the rule it uses.

Three common counting rules

In a “per side” convention, the record stores the repetitions for each limb separately. If a person performs the same number on both sides, the chart can show two matching values. If one side performs fewer, that difference remains visible instead of being hidden inside a combined count. A session total can still be calculated later, but it should be labeled as the sum of both sides' completed actions.

In an “each action” convention, every completed movement by either side counts as one repetition. For alternating lunges, the count increases after each completed lunge, regardless of which leg moves. This can be convenient during a timed or continuous set, but the final entry should say that the number counts individual actions rather than full left-right pairs.

In a “pair” convention, one repetition is counted after both sides have completed one movement. A bilateral total can then match the number of full left-right cycles. This can make the count intuitive for some alternating exercises, but it can also create a mismatch if a plan or another app defines each limb action as a repetition. The software should never convert between pair counts and action counts without naming the conversion.

The name of the exercise matters too. “Single-arm row” may describe a set performed on one side and then repeated on the other; “alternating curl” may switch limbs on each action; and a split squat may use one side for a block before the other. The entry should preserve the exercise variation and the side sequence rather than infer a standard from the exercise label alone. A review of exercise-variable reporting discusses why protocols need more detail than load and repetitions alone.

Exercise identity also affects how a repetition count is interpreted. Ten repetitions of one movement do not necessarily represent the same task as ten of another, even when both use one limb at a time. A meta-regression on repetitions completed at different percentages of 1RM found differences across exercises in the available evidence. For a personal log, the practical response is to preserve the movement name and counting rule together. The count then describes the action that occurred rather than appearing to be a universal unit of strength work.

Side-specific records and session totals

Separate side records are useful when a movement is intentionally performed one limb at a time or when the user wants to see whether both sides completed the same work. A session summary can then calculate a combined total while keeping the left and right entries available. If a log stores only the combined number, it can no longer show whether each side completed the same repetitions or whether the set ended before one side was trained.

The summary should explain whether it adds repetitions, load, or both. For example, if each side uses an equal load and completes a separate set, a volume calculation that includes both sides will differ from one that reports only the per-side set. There is no single display that answers every question. A chart about exercise frequency may count sets. A chart about total external load may include both sides' work. A chart about a particular limb may need to filter one side. Labels should name the calculation rather than calling each one simply “volume.”

Training adaptations also depend on the movement being trained. A recent systematic review comparing unilateral and bilateral training reported that strength changes can be specific to the testing task, while the included evidence did not show a clear difference in muscle hypertrophy between these training modes. That supports a careful data design: the record should show whether the exercise was unilateral or bilateral, rather than treating the two patterns as interchangeable because both use a load and repetition count.

The idea of “equal work” needs care. A left-side set and right-side set can have the same repetition count but differ in load, range, tempo, or effort. A single matching number does not establish that the limbs received identical training. In an older study on lateral specificity in resistance training, strength changes differed between unilateral and bilateral training conditions. That research does not prescribe how an app must count, but it reinforces that movement mode belongs in the record.

What to check in a confusing log

First, find the exercise instructions or set details. Look for “per side,” “each rep,” “alternating,” or “pair.” If the description is missing, inspect whether the log provides separate left and right fields. A count of ten may mean ten actions on each side, ten total actions, or ten full cycles. The number by itself cannot answer that question.

Next, look at how the app calculates its summaries. Does a weekly total count sets or repetitions? Does it combine the sides? Does the chart use one limb or the whole session? The resistance-training prescription overview describes training variables such as load, frequency, and volume in the context of study outcomes. A consumer log should make its own definition clear before it compares a personal record with those research concepts.

If you are moving data between apps, keep the original rule when it is known. If the destination uses another convention, convert only when the source entries show enough information to do so. A pair count can be doubled to represent each limb action only if both sides completed each pair. A simple count cannot be split into left and right values if the original side-level information was never stored. In that case, preserve the unknown status instead of inventing symmetry.

An app can prevent most confusion by showing a short prompt when someone logs a unilateral exercise: “Count each side separately” or “Count every alternating action.” The selection can be remembered for that exercise but should remain visible and editable. It should not be buried in a global setting that changes how older entries are interpreted. A guide to recording dumbbell load conventions covers a related issue: a strength record needs to state what its numbers represent.

Consistency does not mean that every exercise must use one universal rule. It means that the rule is explicit for the exercise and that changes are shown. If the software updates its default, it should preserve the earlier convention or mark the point where interpretation changed. That way the user can compare like with like, or at least see where a comparison needs caution.

When I review an alternating exercise, I ask two questions: what counted as one repetition, and where is the side information stored? If both answers are clear, a set total can be useful without obscuring how much each limb completed. If one answer is missing, the log should not imply a side-specific conclusion that the record cannot support.

FAQ

If I do ten repetitions on each side, should my log show ten or twenty?

It depends on the stated convention. A per-side view can show ten for each side, while a session total that counts each limb action could show twenty. The app should label the values so one cannot be mistaken for the other.

Should alternating repetitions be counted as pairs?

Only if the plan or logging rule defines one repetition as a completed left-right cycle. Many logs count each completed limb action separately. The important step is to use the same definition when planning, recording, and reviewing the exercise.

Can a combined repetition total show whether both sides did equal work?

No. A combined count does not reveal how the actions were divided between sides. Keep left and right counts separate when that comparison matters, and preserve any differences in load, range, or exercise setup.