Turkish get-up programming for kettlebell

The Turkish get-up attracts a particular kind of confusion in intermediate kettlebell programming. The movement itself is well-described across the methodological literature. The programming of the movement is not. Most sources prescribe sets and reps the way they prescribe swings or presses, which produces results that do not match what the get-up is actually doing inside the block.

The disconnect comes from treating the get-up as another grind. It is not. Eight reps of a strict press on the right side compounds peripheral fatigue in a predictable way. Eight reps of a get-up on the right side compounds something different: tonic load through the contralateral chain, time under tension across a multi-joint sequence, and central cost that does not register on a per-rep basis.

This article describes how to program the get-up inside an intermediate kettlebell block. It does not describe how to perform the get-up; that question lives in a separate lexicon entry. Mixing the two is the most common source of bad get-up programming on the kettlebell side of the internet.

What this article is and what it is not

The distinction matters because the search intent on "turkish get-up" splits cleanly into two questions, and the two questions need different pages.

The lexicon entry covers the movement; this article covers the programming

The lexicon entry on the get-up defines the seven phases of the movement, the technique cues per phase, the load reference points, and the way the movement fits into the broader kettlebell vocabulary. That entry is the right destination for the search intent that asks what a turkish get-up is and how to perform one.

This article is the right destination for the programming intent: where the get-up fits in a block, what sets and reps to prescribe per session, how to integrate it with surrounding work. The two intents have different answers and need different page structures. Mixing them produces a page that serves neither audience well.

Audience: intermediate athletes past the technique base

The reader this article addresses has clean technique on the get-up at moderate load (typically 16 kg or above for male athletes, 8 to 12 kg for female athletes). The seven phases run without coaching cues. The lockout overhead is stable through the half-kneeling transition. The descent reverses the ascent cleanly without dropping the bell.

If the technique is still in progress, the programming questions below are premature. Build the technique first using the lexicon entry as the reference; then come back to the programming questions when the movement holds at load.

Where the get-up fits inside a kettlebell block

The first programming decision is structural: where does the get-up sit inside the microcycle, and what other movements does it interact with on the same day or across days.

The get-up as Skill day anchor versus Strength day anchor

The get-up can serve two different roles. On a Skill day, it is a technical primer at low to moderate load, alongside other slow-moving patterns like the windmill and the cossack squat. The session goal is movement quality and pattern reinforcement, not adaptation under maximal load.

On a Strength day, the get-up functions differently. The load climbs (typically 80 percent or above of the practical ceiling), the reps drop, and the rest interval extends. The session goal is overhead stability and contralateral chain strength under near-maximal load. The same movement, played as Skill versus played as Strength, produces different adaptations and carries different recovery costs.

A program that uses the get-up only as a Skill movement loses access to the strength adaptation. A program that uses it only as a Strength movement loses access to the technique-reinforcement value. The choice is not one or the other; the choice is which day plays which role.

As warm-up versus working set

The get-up is sometimes used as a session warm-up, particularly in programs anchored on heavy ballistics. One or two reps per side at light load activates the contralateral chain and the overhead position before the main work. Used this way, the get-up is not the training stimulus; it is the on-ramp.

The distinction matters because the volume that counts as "get-up training" is the working set volume, not the warm-up volume. A program that records the warm-up reps as training volume overestimates the get-up dose and miscounts the central cost.

As Sunday standalone versus mid-microcycle

A traditional StrongFirst convention places the get-up on its own day (often Sunday), separated from the ballistic and grind work that fills the rest of the week. The reasoning is that the get-up's central cost compounds with everything else and is best isolated.

Mid-microcycle placement (Thursday Skill day, for instance) is a different choice that integrates the get-up into the alternation logic. Both choices work; they encode different views of what the get-up is doing. The Sunday convention treats the get-up as a recovery-protected technical practice. The mid-microcycle convention treats it as a working component of the protocol's central-load distribution.

Sets, reps, and intensity prescription

The dose questions live in three variables: reps per side, total session volume, and intensity by load or tempo. The integer constraint on the kettlebell load ladder shapes all three.

Reps per side: the integer constraint

The get-up is prescribed in integer reps per side. The reps must be matched across sides (an asymmetric get-up program produces asymmetric adaptation, which is rarely the goal). The minimum useful working set is one rep per side. The maximum useful working set per round is five reps per side, and even that is rare at intermediate-to-heavy load.

A typical working set is two to three reps per side at moderate load, or one rep per side at heavy load. The reason the upper bound is so low is that the get-up takes 45 to 90 seconds per rep depending on load. Five reps per side becomes a four-to-eight-minute time under tension per round, which the structure of the movement does not support without form breakdown.

Volume per session: the five-to-ten-rep ceiling per side

Total session volume on the get-up is typically five to ten reps per side on a dedicated Skill or Strength session. Beyond ten reps per side, the cumulative time under tension exceeds what the methodology can program for adaptation versus exhaustion.

A six-rep-per-side session at moderate load might look like three rounds of two reps per side, with three minutes rest between rounds. A ten-rep-per-side session at light-to-moderate load might look like five rounds of two reps per side at tighter rest. The total session time on the get-up is typically 25 to 45 minutes, depending on load and rest interval.

Intensity by load and by tempo

Get-up intensity is captured by two variables, not one. The load matters (a 16 kg get-up is different from a 32 kg get-up), but the tempo matters at least as much. A 16 kg get-up performed at five seconds per phase carries a different stimulus than a 16 kg get-up performed at fifteen seconds per phase. The slower version is more demanding, not less, because the time under tension at each transition extends.

RPE training captures the combined load-plus-tempo intensity better than load alone. An RPE 7 get-up at 20 kg might run at fast tempo; the same RPE 7 at 16 kg might require slow tempo to reach the same rating. The prescription frame is RPE; load and tempo are the variables the athlete adjusts to hit the prescribed rating.

Density and the get-up

Density training is the primary progression variable on most intermediate kettlebell work. It applies to the get-up differently, and that difference is the source of much programming confusion.

Why density does not apply the way it does on ballistics

Density compression on ballistics means shortening the rest interval while keeping total reps constant. A 60-second-rest swing session compressed to 45-second-rest with the same total reps produces a different glycolytic stimulus. The compression is the adaptation.

On the get-up, the per-rep time is the dominant variable, not the rest interval. A get-up cannot be performed faster than the movement permits without compromising the pattern. Compressing rest intervals on a get-up session forces the athlete to start the next rep before the previous rep's central cost has cleared, which produces form breakdown rather than adaptation.

The methodological consequence is that density-as-rest-compression does not apply to the get-up the way it does to the swing or to the snatch. A different substitute variable carries the progression.

Tempo and tension as the substitute density variable

On the get-up, tempo and tension carry what density carries on ballistics. The progression across a block is not "less rest between get-ups." It is "more time under tension per phase, more tension held at each transition, slower descent under load."

A week-one get-up session might run at five seconds per phase. A week-three get-up session might run at ten seconds per phase. Same load, same rep count, longer time under tension. The adaptation accumulates in the contralateral chain and the overhead stability, not in glycolytic capacity.

Long versus short get-up timing

The "long get-up" convention runs a full slow get-up at extended tempo: 60 to 90 seconds per rep with deliberate pauses at each transition. The "short get-up" convention runs a brisker movement: 30 to 45 seconds per rep with continuous flow between phases.

Both have a place. Long get-ups build the contralateral isometric strength and the overhead stability that the movement is best at training. Short get-ups build the movement integration and the ability to express get-up technique under modest time pressure. A block can use one or the other or both, but the prescription has to specify which; "do five get-ups per side" without naming the tempo is ambiguous prescription.

Integration with the rest of the block

The get-up's central cost compounds across the microcycle. Programming it well requires accounting for what surrounds it on the days before and after.

Pairing with grinds versus pairing with ballistics

Pairing the get-up with grind work on the same day (get-up plus strict press, for instance) doubles up the central nervous system load and the shoulder demand. The combination works on Strength days when central recovery is protected on the surrounding days, but it does not work on Skill days where the goal is lower-intensity pattern reinforcement.

Pairing the get-up with ballistic work (get-up plus heavy swing or clean) plays differently. The ballistic work is metabolic-dominant; the get-up is neural-dominant. The two systems do not compete for the same recovery resource, so the pairing tolerates more total session volume than a grind-plus-get-up pairing would.

Recovery cost across the microcycle

A heavy get-up session leaves the contralateral chain and the overhead position fatigued for 48 hours minimum. The day after a heavy get-up session should not feature another heavy overhead day (no strict press at near-maximal load, no snatch test). The same logic applies to the day before; arriving at a heavy get-up session with fresh shoulders matters.

This recovery cost is what makes the Sunday-standalone convention attractive. The day before (Saturday) is often a lighter conditioning day; the day after (Monday) restarts the microcycle with fresh shoulders. A mid-microcycle placement requires more careful sequencing.

When to skip the get-up entirely

Some intermediate kettlebell programs do not include the get-up. The choice can be coherent: the movement is technique-heavy, central-cost-heavy, and time-heavy, and a block focused on strength endurance under glycolytic load (the kind that runs heavy ballistic days and density progression) may not have room for the get-up without compromising the primary adaptation.

A program that includes the get-up needs to justify its inclusion against the cost. A program that excludes the get-up needs to be honest about what is being foregone. Neither choice is universally correct.

The get-up across the eighteen sessions of Program 01

Program 01 is the worked example. The get-up appears on the Skill day each week, with deliberate progression across the three-week mesocycle.

Skill day primary placement

The Thursday Skill day in Program 01 anchors on the get-up alongside the windmill, bottoms-up press, and armbar stations. The placement is mid-microcycle (not Sunday-standalone), which reflects the program's view that the get-up is a working component of central-load distribution, not an isolated technical practice.

The Skill day is sandwiched between the Wednesday Power Endurance day (low density, high intensity, ballistic-dominant) and the Friday Strength & Stability day (grind-dominant). Both surrounding days run low enough central load that the Thursday get-up session does not arrive at compromised shoulders.

Rest interval prescription

Program 01 holds sixty seconds rest between get-up reps across the whole block. Pavel Tsatsouline's Simple and Sinister scales get-up rest with the load: thirty to sixty seconds at a moderate bell, one to three minutes at a heavy one. Program 01 sits at the sixty-second floor because the get-up never climbs past the moderate bell. The floor holds across W1/W2/W3: S4 and S10 run the get-up at the light bell, S16 steps it to the moderate bell, and the rest stays at sixty seconds throughout. Sub-floor rest intervals erode bracing quality on reps seven through twelve, exposing the alignment failure modes (arm tremble, eyes off bell, hip drift) that compound the central cost of the movement. The rest interval is the variable that protects skill integrity under cumulative session fatigue, and the protocol does not negotiate on it.

Where the get-up progresses across the block

Week one Skill day (S4) runs four reps per side at the light bell with sixty seconds rest. Week two Skill day (S10) repeats four reps per side at the light bell with sixty seconds rest. Week three Skill day (S16) steps the get-up to the moderate bell, four reps per side at the same sixty seconds rest, with extended tempo discipline. The total per-block get-up volume is twelve reps per side across three sessions, twenty-four get-ups in all, the rest holding at sixty seconds throughout.

The progression is not linear in any single variable. The get-up holds the light bell through weeks one and two, steps to the moderate bell in week three, and tightens its tempo discipline across the block. The combination produces adaptation in the contralateral chain and the overhead stability that compounds across the eighteen-session block.

The programming reasoning

The get-up programming in Program 01 is not the only valid choice. Other programs place the get-up on Sunday (standalone), use it as warm-up only, or skip it entirely. Each choice corresponds to a different view of what the get-up trains and what the block is trying to produce.

The Program 01 choice reflects the block's goals: strength endurance under glycolytic load (the ballistic and Force days) plus overhead stability and contralateral chain integrity (the Skill day get-up). The deeper analysis of why the complex format anchors this block, and how the get-up plays inside it, is in the complex programming analysis. The broader case for what the get-up trains independent of programming context lives in turkish get-up benefits. The placement decisions for other ballistic movements across the same block are covered in snatch programming for intermediates. The single-bell choice that constrains all of this is examined in single-bell versus double-bell training.

Sources

The seven-phase get-up technique reference is Tsatsouline, Enter the Kettlebell (2006), with refinements in his later Kettlebell Simple & Sinister (2013). The Sunday-standalone convention is documented in the StrongFirst SFG I curriculum (StrongFirst Inc., ongoing). The contralateral-chain and shoulder-stability framing follows McGill, Ultimate Back Fitness and Performance (4th edition, 2009) and Cook, Movement: Functional Movement Systems (2010). The integer-rep ceiling and tempo-as-density-substitute argument is grounded in StrongFirst programming convention and Neupert, Kettlebell Strong (2014) on time-under-tension methodology.

Ready to apply Kettlebell Complex methodology to a real block?

Program 01 — Kettlebell Complex is built on this methodology. Block-periodized, density-tracked, designed for intermediate athletes training six days a week alongside another discipline.

See Kettlebell Complex — Kettlebell Complex