Log a drop set in one breath

You hit the heavy stage, didn't rack — stripped a plate and went again, stripped another and went one more time. The bar is on the ground now. Three drops, no rest between them, logged as one set.

What the agent needs to hear

Behind your sentence, the agent works backwards to four pieces: which exercise, the starting weight and reps, each drop’s weight and reps in order, and that this is one cluster, not three sets. You don’t have to spell every one out — the active exercise gets assumed, and the phrasing « X for Y, drop to A for B, drop to C for D » carries the rest. Two drops, three drops, four — the count follows your sentence.

The agent shows you a card with the cluster laid out in order — heaviest stage at the top, each drop descending below — and waits for a nod. One row per drop, just like the bar saw it.

Weights and stages

Stages go top to bottom. The first weight you say is the starting (heaviest) stage; every drop after is lighter. If you call a drop heavier than the previous one, the agent flags it — drop sets descend by definition, so an ascending stage is almost always a mis-said number. Correct it on the card: « the second drop was 45, not 55 ».

You can log the whole drop set in one sentence after the fact, or stage by stage as you go. « Starting drop set, 60 for 10 » opens the cluster; later « drop to 50 for 8 » adds the next stage, and so on until you say « last drop, 40 for 6 » or call it complete. Mid-set logging is for sessions where you want the rest periods captured cleanly; one-shot is for when you remember the whole thing afterward.

What counts as the working weight

A drop set is one set, logged as N stages. The system reads the first stage — the heaviest — as the working weight, which is what feeds PR detection, exercise progression, and your strength trends. Drop from 60 to 50 to 40 and the PR ledger still sees 60; log the whole thing as three independent sets at descending weights and the 60 gets averaged with the lighter ones, and the cluster’s intensity signal disappears.

The drop-set shape also tells the system that the lighter stages were continuous effort, not fresh sets. That changes how volume and fatigue read downstream. Logged as separate sets, the system would assume rest between them and treat the back two as fresh — which they weren’t.

When the agent gets it wrong

The card is where you catch mistakes. If a rep count is off, say the right one — you don’t have to point at the stage position: « the middle drop was 7, not 8 ». If the agent split your sentence into three separate sets instead of one cluster, push back: « that’s one drop set, not three sets ».

If the exercise got attached wrong, correct it the same way: « that was on lat pulldown, not on rows ». If you wanted to add a fourth drop you forgot to mention, just say it: « one more drop, 30 for 5 », and the cluster grows by a stage.

What makes the log worth keeping

Three things decide whether this set helps you later: the shape is one cluster (so the strength signal stays intact, not buried as volume), the first stage is the real starting weight (so PR detection reads the heaviest, not the average), and the stages descend in the order you hit them (so progression on the cluster reads cleanly over time). The system uses these for PR detection, intensity, and continuous-effort volume; logging a drop set as three regular sets is the single biggest way to corrupt this signal. Say the cluster the way you hit it — heaviest first, drops in order — and let the agent group it.