Ride Cadence and Track Tempo on One Number
An instructor building a class profile juggles two numbers that look unrelated: the tempo of the next track, printed in beats per minute, and the cadence the room should hold, which the bike console reports in revolutions per minute. Put a 90 BPM track on the speakers, ask everyone to pedal on the beat, and every console in the studio settles on 90 RPM. The two readings are the same figure because they tally the same kind of event over the same window: one crank turn per beat, sixty seconds of it.
The identity holds only while each beat gets exactly one downstroke. Drop into half time on a heavy climb and the console reads half the tempo; chase a slow track in double time and it reads twice it. Knowing which of those three relationships is in play is most of the skill in reading a playlist as a workout.
What the match does and does not tell you
One Stroke per Beat
Half Time on the Hill
Cadence Is Only Half the Effort
Turning a Playlist Into Cadence Targets
Work through the tracks in the order they will play and write the cadence beside each one before you ever get on the bike.
Type the track tempo in
Put the tempo of the next track into the BPM field, which opens at 1 and rewrites the cadence side while you type. A comma or a dot both read as the decimal mark for tempos written as 128,5.
Halve or double it for the segment
For a seated or standing climb, enter half the printed tempo instead. For a spin-out on a slow track, enter double. What you type is the beat the legs will actually follow, and the cadence side answers to that.
Copy the figure onto the ride sheet
The copy button beside each field lifts the bare number with no unit attached, which drops cleanly into a spreadsheet column of cadence targets. Ctrl+C inside the field does the same.
Work backwards from the cadence you want
If the profile calls for a 100 RPM surge and you need a track to carry it, type the cadence into the revolutions field or press the swap arrows to put that side first.
Cadence Targets Across a Class Profile
A forty-five minute ride is usually cut into six or seven blocks, each anchored to a track whose tempo suits the effort. The skeleton below shows the tempo as printed on the track, how the legs meet it, and what the console should read while the block runs.
| Ride segment | Track tempo | Legs to the beat | Console cadence |
|---|---|---|---|
| Warm-up, light flat | 84 BPM | Every beat | 84 RPM |
| Seated climb | 128 BPM | Every second beat | 64 RPM |
| Standing climb | 140 BPM | Every second beat | 70 RPM |
| Endurance flat | 96 BPM | Every beat | 96 RPM |
| Jumps and transitions | 100 BPM | Every beat | 100 RPM |
| Flat sprint | 110 BPM | Every beat | 110 RPM |
| Recovery | 76 BPM | Every beat | 76 RPM |
Outdoors the same figures describe a different picture. Trained road riders spend most of a long day between 80 and 95 RPM, seated climbing drops them into the 60s and 70s, and a sprint out of the saddle can touch 120 RPM for a few seconds.
Read a Playlist as a Cadence Plan
Every tempo in the queue becomes a target the room can hold, halved or doubled, with no arithmetic between tracks.
Plan From Either End of the Block
Start from a track you love or from the cadence the profile demands — the swap arrows let the search run either way round.
Restate a Cadence in Other Rate Units
Both unit menus are searchable, so a cadence can also be read as revolutions per second when a coaching app asks for it that way.
Cadence and Tempo Questions From the Saddle
Why is a 90 BPM track the same number as a 90 RPM cadence?
Because both units count events across the same sixty seconds. Beats per minute tallies beats, revolutions per minute tallies crank turns, and if the legs put one turn under each beat the two tallies are identical. A frequency in hertz counts across one second instead, which is why the same ride reads as 1.5 Hz — the unit changed the window, not the pedalling.
When should the room ride half time instead of on the beat?
Whenever the track is too fast for the effort you want out of it. Climbing tracks are commonly written at 120 to 150 BPM, which nobody can grind against real resistance, so the legs take every second beat and land in the 60 to 75 RPM range that suits a hill. Double time is the mirror case: a slow, heavy 55 BPM track ridden two strokes per beat becomes a 110 RPM flat.
What cadence range suits a seated climb, a flat and a sprint?
Studio convention puts climbs at roughly 60 to 80 RPM, seated flats and running efforts at 80 to 110 RPM, and treats about 110 RPM as the ceiling for anything held under load. Past that the hips bounce and the rider is fighting the bike rather than the hill. If a track pushes the room over that ceiling, halve the beat rather than stripping resistance to survive it.
Does hitting the cadence target set the intensity of the block?
No. Cadence sets how fast the legs turn; resistance sets how hard each turn is, and the effort comes from both together. A 64 RPM climb with the knob barely engaged is easier than a 96 RPM flat under a serious load. Use the tempo to choose the rhythm of the block, then cue resistance separately in turns or gear numbers.
How do I build a playlist around the cadence blocks I want?
Sketch the profile first as a list of efforts with their target cadences, then shop for tracks whose tempo, halved or doubled, lands within a few revolutions of each target. A gap of two or three is invisible to a room; a gap of ten means riders drift off the beat. Keep tempo, ride style and cadence in three columns so the ride can be re-checked when one track gets swapped out.
No comments yet. Be the first to comment!