How to log supersets and drop sets without wrecking your history

First, what the log is for

It is worth being clear about the goal, because it decides every question below. You are logging so that next time you can answer: what did I do, and can I beat it?

That means the format that preserves comparability wins, even when it looks less like what physically happened. A record that captures the *drama* of a brutal drop set but cannot be compared to next week's is worse than a boring one that can.

Rule of thumb: log every distinct load as its own set. That single principle solves most of what follows.

Supersets

A superset is two exercises performed back to back with little rest. The temptation is to record it as one combined entry. Do not — you lose the ability to progress either movement.

Log them as two separate exercises, each with its own sets, reps and weight, exactly as if you had done them apart. The pairing is a scheduling decision, not a property of the sets.

If your app supports grouping or tagging, use it for the pairing information. If it does not, it genuinely does not matter: what you need next week is "incline press, 3×10 at 50" and "cable fly, 3×12 at 30", and you have both.

In Superset, saying "incline dumbbell press superset with cable fly, three rounds, ten and twelve" records two exercises with three sets each, which is the form you want. You can also just name them in sequence.

Drop sets

A drop set is one working set taken to near failure, then immediately continued at a lower weight, sometimes two or three times.

Log each drop as its own set. A set at 100 for 10, then 80 for 8, then 60 for 6 is three sets, recorded in that order. Do not average the weight — an "80 lb" entry that never happened is worse than useless when you are trying to beat it.

The first drop is the one to progress. Treat the top weight and its reps as the number that matters and let the subsequent drops fall where they fall; they are a fatigue product, not a progression target.

Spoken, this is straightforward: "lateral raise, drop set — twenty for twelve, then fifteen for ten, then ten for eight."

The other awkward cases

• Pyramids — same rule. Each weight is its own set. Progression tracks the heaviest one.
• Rest-pause — log the total reps achieved at that weight, and note the rest-pause somewhere if your app allows it. Splitting a rest-pause into micro-sets makes the history unreadable.
• AMRAP sets — log the reps you actually got. This is the cleanest data in your whole log; do not round it.
• Failed sets — log them at the reps completed. A set of 5 when you wanted 8 is exactly what tells a coach, or an app, that a deload is coming.
• Warm-up sets — do not log them at all. They add noise and can drag your apparent working weight down.
• Bodyweight with added load — log the added weight, consistently. Switching between "25" and "bodyweight plus 25" between sessions breaks the comparison.
• Unilateral work — log one side's reps and weight, and keep to that convention forever. Doubling it some weeks and not others is the most common way people corrupt their own history.

Keeping progression readable

1. 1Pick a convention and never change it. Consistency matters more than which convention you picked.
2. 2Log every distinct load as its own set, in the order performed.
3. 3Treat the top set as the progression target for drops and pyramids.
4. 4Skip warm-ups so your working history stays clean.
5. 5Record what happened, not what was planned — especially the sets that went badly.
6. 6Check the review screen if you are logging by voice, since intensity techniques are where phrasing is most likely to be misheard.