Cricket Pace Bowling Run-Up Velocity Protocol: Timing the Final Approach Acceleration

A regional academy fast bowler I worked with last winter was convinced his pre-season had failed. Six weeks of hill sprints and sled pulls, and the radar gun behind the stumps still read the same 128 km/h it read in October. His coach had watched the run-up on video and called it clearly quicker — longer stride, more purpose in the last few steps. Both were reading real signals and drawing the wrong conclusion: neither release speed nor an eye test on the approach tells you which part of the sequence to back foot contact (BFC) is where pace is made, or quietly leaks away.

Release speed is an outcome, not a diagnosis. It sums the whole kinetic chain — run-up, delivery stride, trunk rotation, arm and wrist — into one number, which is why two bowlers post an identical reading for opposite reasons, and why one bowler's number sits flat for a season even as a specific link genuinely improves. This protocol isolates one link directly: the final 5 meters of the run-up, where built-up momentum either keeps climbing into BFC or bleeds away before it reaches the delivery stride — telling you whether a stalled speed number points at the legs or the arm.

Run-up velocity's link to release speed is not a hunch — it shows up clearly in the literature, more strongly than most technique variables coaches obsess over. Glazier, Paradisis, and Cooper (2000) filmed nine collegiate fast-medium bowlers and found horizontal velocity in the pre-delivery stride — the last full stride, immediately before BFC — correlated with release speed at r = 0.728 (p < 0.05), against a cohort mean of 31.5 ± 1.9 m/s. That's one of the stronger single-variable relationships in fast-bowling kinematics, explaining roughly half the variance in release speed alone. Angular velocity of the bowling arm itself correlated far more weakly (r = 0.358, not significant) in the same sample.

The catch: this relationship is invisible from a release-speed number alone. A bowler generating strong horizontal velocity into BFC but losing it through a soft, over-long delivery stride shows the same radar reading as one who never built that velocity at all — two different problems, one flat number. That's the whole reason to measure the approach segment directly instead of reverse-engineering it from where the ball ends up.

The full run-up is not evenly informative. Most fast bowlers spend the opening two-thirds of their approach simply settling into a comfortable rhythm — that phase is remarkably consistent and tells you little about a speed problem. What varies, and what actually predicts the ball, is what happens in the last few strides before the bound, where a bowler converts accumulated horizontal momentum into the vertical and rotational energy the delivery stride needs. This protocol fixes that window as a standardized 5-meter zone ending at BFC, rather than the single pre-delivery stride Glazier's team measured, because a fixed distance is far easier to mark and compare across sessions than a stride boundary that shifts delivery to delivery.

Two numbers matter inside that zone: velocity entering it (entry velocity, at the 5-meter mark) and velocity leaving it at BFC (exit velocity). The difference — net zone acceleration — is what this protocol cares about, because it separates two bowlers reaching BFC at the same absolute speed but getting there completely differently. One is still building speed into the crease; the other peaked earlier and is already decelerating when the ball needs the momentum most. A single average run-up speed, what most GPS units report by default, cannot tell them apart.

Placement matters more than the sensor spec sheet. A wearable IMU/GPS pod — PoinT GO's unit works, as does any device reporting velocity at 10Hz or better — sits at the lower back, close to centre of mass, secured with a snug belt so it doesn't bounce independently of the trunk and blur the entry/exit distinction the test depends on. Bowlers without a wearable can run the same test with two sets of timing gates instead, at some cost in resolution.

Marking the Zone

1. Locate BFC first, not last: review two or three normal deliveries and mark where the back foot actually lands, not where the crease line theoretically sits — bowlers routinely land 20 to 40cm short of, or past, their own mark.
2. Measure back 5 meters from that landing point and place a cone or entry timing gate there.
3. Leave the run-up mark untouched. Changing run-up length mid-test contaminates the number you're tracking.
4. Confirm sample rate and battery before the first delivery of the session.

Run the test inside a normal bowling session, into a keeper or stumps at match effort — not an isolated sprint drill into an empty net. Approach mechanics change once the delivery loses a real target, and won't match match day.

Session Steps

1. Bowl a standard 6-ball over, or two for a longer sample, at genuine match intensity.
2. The device logs entry velocity at the 5-meter marker, exit velocity at BFC, and time in the zone for every delivery automatically.
3. Discard the first delivery — typically still settling into rhythm — and any with an obviously broken approach: a chopped stride, a stutter-step, a re-set run-up.
4. Calculate zone acceleration per delivery: (exit velocity − entry velocity) ÷ time in zone.
5. Take the median of the remaining 5 as that session's number, logged alongside actual release speed from the same over.

Median, not mean, is deliberate: one mis-timed delivery skews an average badly with only 5 or 6 points, while a median absorbs it. Build a baseline from at least 3 clean sessions before treating any single number as meaningful — one session tells you what happened that day, not what's normal for that bowler.

These bands are practical field categories built from applied fast-bowling speed testing rather than a single formal norm table — treat them as a rough map of where a bowler sits, not a pass/fail line. Approach-velocity work using resisted sprint analysis on bowlers has repeatedly put the ideal exit velocity into the crease somewhere around 7 to 8 m/s for genuinely fast bowlers, broadly consistent with the pre-delivery-stride velocities implied by Glazier and colleagues' cohort bowling at 31.5 m/s ball speed.

A bowler's absolute band matters far less than whether zone acceleration is positive, flat, or negative — that pattern, covered next, is what actually points at a fixable problem.

Salter, Sinclair, and Portus (2007) make the case for running this at the individual level, not against a population chart. Their pilot study tracked one elite semi-open fast bowler across 20 deliveries, comparing a within-bowler correlation approach against the conventional between-bowler design used in most fast-bowling research — and found the within-bowler method surfaced technique-to-speed relationships that group-level analysis missed entirely. The lesson: a bowler's own zone-acceleration history beats any external band above. The single-subject design is also its clearest limitation, which is why this protocol tracks each bowler against their own baseline rather than a universal cutoff.

Coaches most often misdiagnose the decelerating pattern as an arm or wrist problem, since the delivery action, filmed alone, looks fine. It isn't broken; it simply has less momentum than top-end run-up speed suggests. Chasing more overall sprint speed here usually pulls the plateau earlier — the fix is timing of the last few strides, not raw pace.

Test every 2 to 3 weeks through pre-season, not every net session — zone acceleration doesn't move week to week, and over-testing adds noise. A workable cadence: baseline across 3 sessions in week one, then a re-test every 2 to 3 weeks, logged against release speed from the same over.

In-season, drop to a monthly check unless something prompts an earlier look — a bowler back from injury, a reported rhythm change, or an unexplained pace dip. A sudden shift from a stable positive-acceleration pattern to a flat or decelerating one mid-season flags a compensating injury earlier than the pace number alone, since drift shows up in the approach before the ball.

Key References

• Glazier, P. S., Paradisis, G. P., & Cooper, S. M. (2000). Anthropometric and kinematic influences on release speed in men's fast-medium bowling. Journal of Sports Sciences, 18(12), 1013–1021.
• Salter, C. W., Sinclair, P. J., & Portus, M. R. (2007). The associations between fast bowling technique and ball release speed: A pilot study of the within-bowler and between-bowler approaches. Journal of Sports Sciences, 25(11), 1279–1285.