Negative Split Strategy Using a Min/km Pace Table

A negative split is not two paces, it is a table

The definition is easy: a negative split means the second half of the race is faster than the first. What makes it work on the day is not the intention but the arithmetic — a specific finish time, a specific half-distance split, and a checkpoint table that tells you whether you are on plan at 5, 10, 15 and 20 kilometers.

Most runners run a negative split badly for one of two reasons. They treat it as two paces rather than as a schedule, so they have no way to tell at 15 km whether they are ahead or behind. Or they decide the split difference by feel, which on a race morning means it is usually too small.

State the split difference as arithmetic

A negative split plan has exactly one free parameter: how many seconds per kilometer faster the second half will be than the first. Call it the delta.

If the first half is run at average pace plus the delta and the second half at average pace minus the delta, the two halves average out to the target pace, and the difference between the two halves is:

split difference = 2 × delta × half distance

For a half marathon the half distance is 10.54875 km, so the multiplier is about 21.1. A delta of 5 seconds per kilometer produces a two-half difference of 105 seconds. A delta of 10 produces 211 seconds. That single relationship is what reconciles the two pieces of advice you will find everywhere.

The widely repeated guidance says to run the first half 5 to 10 seconds per kilometer slower than goal pace. It also says a good negative split is 2 to 3 minutes. Those two statements are only consistent at the bottom of the range: 5 seconds per kilometer gives 1:45, and 10 gives 3:31. To land in the 2 to 3 minute window you need a delta of about 5.7 to 8.5 seconds per kilometer. Eight is the clean compromise, and it is the value used for the table below.

Building the checkpoint table

Target a 1:45:00 half marathon, which is 6,300 seconds over 21.0975 km. Average pace is 4:58.6 per kilometer. With a delta of 8 seconds, the first half runs at 5:06.6 and the second half at 4:50.6.

Print this, or write the four checkpoints on your forearm. The table exists precisely because the first half is supposed to feel wrong.

You are meant to be behind at halfway

Look at the lag column. At the halfway point a correct negative split is 84 seconds behind even pace, and at 10 km it is 80 seconds behind. That is not a rounding error or a sign of a bad day; it is the plan working exactly as designed.

The failure mode is nearly always the same: a runner reaches 10 km, sees a time that is more than a minute slower than the even-pace figure they memorized, decides the plan is not working, and speeds up to close the gap. The gap was the plan. Closing it in the third quarter converts the race into an even split at best and a positive split at worst, because the acceleration comes out of the same reserves the last 5 km were counting on.

The trick that makes this reliable is to memorize only the negative-split column. If the even-pace numbers are not in your head, there is nothing to be alarmed by.

The first 3 to 5 km are a separate problem

A negative split assumes the first half should be slower than average, and the opening kilometers of a race are already faster than average whether you intend it or not. Crowd energy, downhill sections and fresh legs push the first two kilometers anywhere from 10 to 20 seconds per kilometer under target, and a runner who tries to keep the whole first half at 5:06 from the gun will spend the opening kilometers fighting their own instinct.

The practical compromise is to treat the first 5 km as a slightly deeper version of the same curve and accept a marginally faster second half to compensate. Take the 5 km checkpoint as the first real reference point rather than trying to hold the first-half pace from the start, and check the cumulative time there rather than the instantaneous pace on your watch.

Reading the table on the day

• Set the watch to show average pace for the current kilometer plus total elapsed time. Cumulative time against the table is the only number that decides anything.
• Check at 5 km. Being 30 to 45 seconds behind even pace is on plan; being ahead of even pace means the delta is not being honored and the second half will be harder than budgeted.
• Check at 10 km and confirm the lag is still around 80 seconds. A lag of two minutes or more means the first half was too slow and the second half now has to be faster than 4:51.
• Check at 15 km. The lag should have shrunk to about 49 seconds, which means the second half is now running faster than the first — the split has turned and it should feel like it.
• Check at 20 km. Nine seconds behind even pace is the platform for the final kilometer, which is where a properly executed negative split spends its remaining reserve.

Where the plan does not apply

A negative split is a flat-course strategy. On a hilly half marathon the elevation profile decides the split, and the plan should be built from effort rather than from min/km. Take the downhills at the pace the terrain offers and hold the uphills to a level of effort you can repeat, then read the cumulative time as information rather than as an instruction.

The same caution applies in heat, where a fast first half can be affordable early and catastrophic late, and in a first half marathon, where the second-half pace of 4:51 for the last 11 km is a genuine physical demand rather than a pacing adjustment. For a first race, an even split executed honestly is a better result than a negative split abandoned at 15 km. A negative split is a way of spending your reserves deliberately; it requires reserves to spend, and it rewards runners who can hold a pace that feels too easy for fifty-three minutes.