- Sag first, damping last — always.
- Front rider sag belongs in the 30–38 mm window; rear in 25–30 mm.
- Rebound controls return speed; compression controls how it absorbs.
- Diagnose by the corner phase where the symptom shows up, not the symptom alone.
- Change one variable at a time. Log every change.
- Tires drive the chassis — pressure and temperature come before any clicker.
01The fundamentals: what suspension is actually doing
Every fork and shock on a modern motorcycle is built around the same two elements: a spring and a damper. The spring stores energy when the wheel moves toward the chassis and releases it when the wheel moves away. The damper — a piston pushing oil through orifices — converts that motion into heat so the spring doesn’t oscillate forever.
Spring rate sets how much force is needed to compress the suspension a given distance. Get it wrong and no amount of clicker fiddling will save you: too soft and the bike bottoms or wallows under load; too stiff and the tire skips across the surface instead of tracking it. Damping then shapes howthe spring moves — how quickly it gives under a bump, how quickly it returns afterward.
On the front, compression resists fork dive under braking and turn-in; rebound resists extension as the load comes off. On the rear, compression resists squat under drive and big hits; rebound resists the shock pushing the chassis back up. Every cornering force you feel through the bars is the sum of those four behaviours acting in sequence.
02Setting sag — your geometry baseline
Sag is the amount the suspension compresses under weight. It is the foundation of every other setting, because it sets the bike’s ride height, and ride height sets rake, trail, and weight distribution. If sag is wrong, your chassis is the wrong shape, and damping changes will only chase the symptom.
Two numbers matter. Static sag is how far the suspension settles under the bike’s own weight. Rider sag is how far it settles with you on board in full gear. The formulas are simple:
- Static sag = fully extended length − bike-weight compressed length
- Rider sag = fully extended length − rider-loaded compressed length
Targets
For street and track sportbikes, aim for 30–38 mm of front rider sag and 25–30 mm of rear rider sag. Supermoto and off-road bikes run much more — often 100 mm or more — because they need stroke to absorb large impacts. Always check the OEM service manual before assuming a number.
How to measure
For the front, slide a zip-tie down the fork stanchion against the dust seal, then lift the bike on a paddock stand until the fork fully extends. Measure from the seal to the zip-tie — that’s your reference. Drop the bike, settle the fork by gently pushing down and releasing, then measure again with the rider on board.
For the rear, pick two fixed points — the rear axle and a mark on the subframe directly above it — and measure the distance between them in each state. Always release the suspension the same way before each measurement: a small lift and gentle drop is enough to break stiction.
Adjust front sag with the preload caps on the forks. Adjust rear sag with the shock preload collar. Preload doesn’t change spring rate; it changes where in the spring’s travel the bike sits at rest. If you’ve cranked preload to its limit and still can’t hit target, you have the wrong spring rate for your weight.
03Rebound damping — controlling the return
Rebound damping controls how fast the suspension extends after a compression. It’s the brake on the spring’s return stroke. Too much and the suspension can’t recover between events; too little and it overshoots and oscillates.
Too slow (over-damped)
The classic symptom is pack-down: across a series of bumps, the suspension compresses but doesn’t fully return before the next hit, so it rides lower and lower in the stroke. The bike feels harsh, ride height drops, and grip vanishes because the spring is barely doing its job. On the rear, slow rebound often shows up as a loss of traction over patched pavement.
Too fast (under-damped)
The bike feels like a pogo stick. After a bump or a transition, the chassis bounces and takes time to settle. On the rear, fast rebound causes the bike to push the rider forward as the shock extends; on the front, it makes the bars want to wave after a hit.
How to adjust
Move in one or two clicks at a timefrom the OEM baseline, and ride the same section of track or road both before and after. Note the direction (in = more damping, out = less) and the count. Resist the temptation to make a big change because the small one “didn’t do anything” — sometimes the right click is the second one.
Fork and shock interact
Rebound on the two ends talks to each other. A rear shock with rebound set too soft will extend quickly under drive, lifting the rear and steepening the rake — the front tucks. A front fork with rebound too slow keeps the nose low through transitions, so the bike feels lazy turning side-to-side. Tune them as a pair, not in isolation.
04Compression damping — high and low speed
Compression damping controls how fast the suspension compresses under load. Modern forks and shocks usually split it into two adjusters because the forces you’re managing happen at very different speeds.
Low-speed compression (LSCD)
LSCD governs slow, deliberate weight transfer: trail braking into the apex, throttle pickup off the corner, chassis pitch as you change direction. These are inputs you make with your hands and your right wrist, not events forced on you by the surface. If the bike dives too much under braking or squats too much under drive, this is the adjuster you reach for first.
High-speed compression (HSCD)
HSCD governs sudden, sharp hits: kerbs, expansion joints, paint, potholes. It only activates when the suspension shaft is moving quickly. If the bike feels harsh over kerbs but fine under braking, that’s an HSCD signal. If it feels plush over kerbs but wallows under braking, the LSCD is the culprit.
Practical advice
Most riders should leave HSCD alone until LSCD is dialled. The OEM HSCD baseline is usually within a click or two of correct for a wide range of bumps, while LSCD is far more sensitive to rider style and tire choice. Touch LSCD; verify; only then consider HSCD if a specific high-speed harshness remains.
05Diagnose by corner phase, not symptom alone
“The bike runs wide” is not a diagnosis. The same words can describe four mechanically different problems depending on when in the corner the bike does it. Break every lap into four phases and ask which phase produced the symptom before you reach for a tool.
Braking and turn-in
Front forks compress hard as weight transfers forward; the rear shock extends as the rear unloads. Symptoms here are usually front-end: chatter under brakes, lost contact patch, vague turn-in, or the bike refusing to fall into the corner. Suspect front LSCD, front rebound, or front rider sag.
Mid-corner
Brakes are released, throttle hasn’t opened. The chassis is settled and the geometry — rake, trail, ride height — is doing most of the work. Symptoms here often point to spring rates, ride height, or tire pressure rather than damping. Bumps mid-corner that upset the line are usually a high-speed compression issue.
Acceleration and exit
The rear shock compresses under drive; the front fork extends as weight transfers back. Symptoms are typically rear-end: spinning, sliding, the bike running wide as the rear squats and the rake steepens. Suspect rear LSCD, rear rebound, or rear sag.
Worked example: “runs wide”
A bike that runs wide on entry usually has too much front dive: the rake steepens, trail shortens, and the front wants to tuck or push. Add a click of front LSCD or check that rider sag isn’t at the slack end of the window. A bike that runs wide on exit usually has too much rear squat: the rake steepens from the back this time, and the rear tire is asking for more grip than the geometry will let it use. Add rear LSCD, or check rear sag and rebound. Same words from the rider; opposite ends of the bike.
06A repeatable session protocol
Tuning is a loop, not a sprint. The riders who get fast quickly are the ones who run the same loop every session and log everything. Here’s the protocol:
- 1. Set tire pressures cold to a known baseline. Tire pressure changes more between cold and hot than any clicker will move the chassis. Start from a number you trust before you change anything else.
- 2. Verify sag, front and rear. Bikes lose preload over time; springs settle; you may have ridden with a different load last weekend. Re-measure rather than assume.
- 3. Confirm the clicker baseline. Count every clicker back to fully closed, then out to the OEM or last-known-good setting. If you don’t know where you are, you can’t know where you’re going.
- 4. Run a reference of three clean laps. No experiments, no overriding. Just ride. This is the lap you’ll compare every change against.
- 5. Identify the worst symptom and the phase it appeared in. One symptom, one phase. Write both down.
- 6. Make exactly one change, one or two clicks. Note the adjuster, the direction, and the count. Resist the urge to combine changes — you won’t know which one helped.
- 7. Re-run, compare, log. If the change helped, keep it and pick the next worst symptom. If it didn’t, return to baseline and try something else.
This loop is exactly what Apex Wizardautomates: a setup logbook for clickers and sag, a side-by-side session comparator, and a troubleshooter that maps phase-specific symptoms to the adjuster most likely to fix them. The protocol stays the same whether you use paper or the app — the app just means you don’t lose the logbook in a tank bag.
Stop guessing in the pits.
Apex Wizard turns this protocol into a one-screen workflow — log clickers, compare sessions, get phase-specific recommendations.