How to Log Cluster Sets in a Workout App

What counts as a cluster set?

A cluster set is one planned set broken into smaller bursts of reps, called mini-sets, with short rests between them. For example, instead of doing 8 reps in a row, you might do 2 reps, rest 20 seconds, and repeat that three more times. The short pauses are intra-set rests because they happen inside the planned set. Resting for 3 minutes after the full cluster is between-set rest.

The structure is set before you start: the number of mini-sets, reps per mini-set, load, and usually the short rest interval. There is no single rest length that defines every cluster set. Follow the prescription you are using, and write down the actual rest if it differs. That detail is part of what makes the session reproducible.

Enter each mini-set as it happened

If your app lets you add individual set entries, log each mini-set as a separate row with its actual weight and reps. Do not combine the whole cluster into one entry if you want to see how the reps were distributed.

For example, say you squat 100 kg for four mini-sets of 2 reps, with 20 seconds between them. Enter four rows, each showing 100 kg and 2 reps. The session record then shows that you completed 2+2+2+2, rather than one uninterrupted set of 8. If you finish a mini-set with only 1 rep instead of the planned 2, record 1. Your log should describe what happened, not the plan you meant to complete.

Give the four rows a shared marker, such as C1 for cluster one, if your app has a suitable note or label field. If it does not, use a notebook or a phone note alongside the app. A simple line works: “C1: 100 kg, 2+2+2+2, 20 sec between mini-sets.” Keep the marker consistent from workout to workout so it is easy to match the note to the right exercise and entries.

Keep the two kinds of rest separate

Write intra-set rest and between-set rest as different details. A useful record might say: “C1: 4 mini-sets of 2, 20 sec intra-set rest; 3 min before C2.” That makes clear that the 20-second pauses belong inside one cluster, while the 3-minute pause comes before the next cluster.

This distinction matters when you compare sessions. If you used 20 seconds between mini-sets last week and 40 seconds this week, the same load and reps do not describe the same setup. Longer pauses can make it easier to maintain reps, so do not treat the rep total alone as proof that performance improved. Note the changed rest and compare the next session under similar conditions if you want a fair read.

If you rely on a rest timer, start it after each mini-set and use the same cue each time. Start a separate timer after the final mini-set for the rest before the next cluster. Even when your app cannot store both intervals, writing them down takes only a few seconds and protects the detail you need later.

Keep rep totals and set counts distinct

A log may show four rows for the example above, but that does not automatically mean you performed four ordinary programmed sets. A cluster can be one planned set made up of several mini-sets. If your program prescribes one cluster, count it as one planned cluster when you review your program’s set total, while keeping the four rows in your history to preserve how the work was done.

Also track the total reps. Four mini-sets of 2 add up to 8 reps. The volume-load (weight multiplied by reps) is 800 kg for the example: 100 kg times 8 reps. That total is useful for checking the amount of work completed, but it is not a full measure of how hard the cluster felt or how much training effect it produced. Rows, set totals, and volume-load answer different questions. Keep them separate instead of turning every app row into a full set in your weekly review.

If your program uses several clusters for the exercise, number them separately. For example, C1 and C2 each have their own mini-set sequence. That way, you can distinguish two planned clusters from one cluster with twice as many mini-sets.

Compare cluster sets under matching conditions

When you review progress, compare the same exercise, load, mini-set pattern, and rest timing. Moving from 4×2 with 20-second pauses to 4×2 with 10-second pauses changes the task. So does changing from 4×2 to 3×3, even though both add up to 8 or 9 reps across the cluster. Record the pattern instead of relying only on a total-reps number.

If the pattern stays the same and you complete the prescribed reps with the same short rests, you have a cleaner basis for judging progress. Depending on your program, the next step might be a small load increase or an extra rep in one mini-set. Do not add weight just because the app’s row count went up; check what changed in the actual work first.

A simple logging routine

Before the lift, note the plan: load, mini-set pattern, and intra-set rest. During the session, enter each mini-set with the reps you actually completed. After the cluster, record the short-rest timing and the longer rest before the next cluster. At the end, total the reps and keep the planned cluster count separate from the number of mini-set rows.

GymLog logs exercise, weight, and reps for each tapped set, but it does not have set notes or labels. If you use it for cluster training, keep the cluster marker and rest timing in your own notebook or phone note. That small extra habit lets the app’s set entries stay accurate without making the session look like more programmed sets than you performed.

The goal is not to make a cluster look like a conventional set. It is to preserve both views: each mini-set as it happened, and the cluster as one planned block. When you can see the rep pattern, the short rests, and the total work together, your next comparison is much more useful.