A split table is a mile-by-mile plan for how fast you intend to run each mile of a race, adjusted for course profile, weather, and the tactical realities of running in a crowd. Elite runners have coaches who produce these tables for them. Everybody else usually writes their goal pace on a wristband and hopes for the best. This is a walkthrough of how to build a real split table, in about 30 minutes, for a first marathon.
Photo by Vijay Saiwal on Pexels
Step 1: Pick a goal pace your training actually supports
The starting point is not aspirational. It is your training data. Use the pace from the last four miles of your best 20-mile long run as the anchor. Subtract roughly 20 to 40 seconds per mile to estimate marathon pace. That estimate is your ceiling.
If your best 20-mile long run finished at 9:45 per mile, a defensible marathon goal is somewhere around 9:15 to 9:25 per mile. That produces a 4:02 to 4:07 marathon. Anything faster is aspirational and the split table should be built for the honest number.
Step 2: Compute average pace for the goal
Average pace equals goal time divided by 26.2 miles. Do the arithmetic yourself even if the tool does it for you, because errors in this step compound across the whole race.
For a 4:00 goal: 240 minutes divided by 26.2 miles equals roughly 9.16 minutes per mile, which is 9:09.5 per mile. Round to 9:10 for the plan, or 9:09 if you want a small buffer. The free race pace calculator from EvvyTools produces this to two decimal places and shows the exact per-mile total.
Step 3: Build the miles 1-3 conservation
Race adrenaline and crowd energy will make you feel faster than you are. Your first 3 miles should be planned at 10 to 15 seconds per mile slower than goal pace. For a 4:00 goal at 9:10 average, the first 3 miles are 9:20 to 9:25.
The split table for miles 1 through 3 looks like:
Mile 1: 9:22 (elapsed 9:22)
Mile 2: 9:22 (elapsed 18:44)
Mile 3: 9:20 (elapsed 28:04)
This is not banking time later. It is refusing to spend energy that you will need in the second half.
Step 4: Fill in miles 4-16 at goal pace
Once you have thinned out from the starting crowd, settle into goal pace. This is the aerobic middle of the race, and it should feel repeatable and steady.
Miles 4-16: 9:10 per mile
Elapsed at mile 16: roughly 2:26:14
If you feel great in this section, ignore it and hold pace. If you feel bad, ignore it and hold pace. Neither feeling is a reliable signal for the second half. The Wikipedia entry on the marathon explains the physiology of why the middle miles are misleading. The lesson is to trust the plan more than the legs in this window.
Step 5: Fill in miles 17-20, the honest miles
This is where the plan continues at goal pace, but effort will noticeably rise. You are approaching the wall in glycogen terms and your form will start compensating.
Miles 17-20: 9:10-9:15 per mile
Elapsed at mile 20: roughly 3:03:04
If you have to slow slightly to 9:15 for a mile or two to stay controlled, that is fine. The goal is to arrive at mile 20 with enough left to hold the last 10K without a collapse.
Step 6: Plan the final 10K by contingency, not by wishful thinking
The last 10K is where positive splits come from. Do not plan a fixed pace here. Plan two variants:
Variant A (if you feel controlled at mile 20): Hold 9:10 to 9:15 pace for miles 21-26.2. Small negative split possible if the last 5K feels manageable.
Variant B (if effort has climbed sharply by mile 20): Slow to 9:20-9:25 for miles 21-24, then reassess. Do not force a pace that has stopped being sustainable. Losing 30 seconds a mile is a small cost. Losing 90 seconds a mile because you tried to force 9:10 and blew up is a large one.
The runner who plans for both variants finishes near their goal. The runner who plans only for variant A and is forced into variant B at mile 22 usually finishes 15 minutes slower than they should have, because they did not switch modes fast enough.
Step 7: Apply weather adjustments
Every 5 degrees Fahrenheit above 55 costs roughly 4 to 10 seconds per mile at marathon pace. Humidity above 70 percent compounds. If race-day forecast is 65 degrees and 75 percent humidity, revise the goal pace by 10 to 20 seconds per mile before the race. Do not force the pre-planned pace into an environment it was not built for. Runner's World publishes standardized heat adjustment tables, and the Jack Daniels coaching formulas are worth reading before you finalize.
Step 8: Apply course elevation adjustments
Flat course: no adjustment. Downhill start (Boston, New York): expect the first 5 miles to feel deceptively easy and hold conservative pace anyway. Rolling hills: mentally mark the uphill miles as 10 to 20 seconds slower and downhills as 5 to 10 seconds faster. Hilly finish (Newton hills): reserve 30 to 60 seconds of buffer specifically for those miles.
Draw the elevation profile once and annotate the split table with which miles are the hardest. This is the difference between a plan built for the race in front of you and a plan built for a flat treadmill run.
Step 9: Print two copies
One goes on your race bib or wristband. One goes to your support crew if you have one. Both should include the goal times at miles 5, 10, 13.1, 20, and 26.2, so you can check yourself at each mile marker and adjust in real time if you are running consistently ahead of plan (slow down) or consistently behind plan (either accept the new pace or diagnose why).
Photo by Aedrian Salazar on Pexels
The check most first-timers skip
Before you leave for the race, verify the total of the split table equals your goal time exactly. If your table adds up to 3:58:47 for a 4:00 goal, either your average pace is slightly too fast, or you have a rounding error. Fix it before race day.
The companion guide on pacing a first marathon walks through how to translate this table into actual pacing discipline during the race, and the EvvyTools tools directory has the calculators for splits, race prediction, and unit conversion in one place. The most important thing about a split table is that you built one. The second most important thing is that you trust it more than your legs in the first hour.
The mistake most runners make with the table on race day
The single most common failure mode of a split table is not that it was built badly. It is that the runner threw it away by mile 5 because the pace felt too slow. The plan on paper says 9:22 for miles 1 through 3, and the crowd is running 8:50, and the runner decides the plan was too conservative and speeds up. This is the exact mistake the table was built to prevent.
The mental discipline is to accept that the first 5K is going to feel slow to easy, and that this feeling is the plan working correctly. If your first mile felt exhausting at goal pace, either the goal is too fast or you did not warm up properly. If the first mile felt easy, that is what the plan intended. Speeding up because it felt easy is how you turn a 4:00 finish into a 4:18 finish. The runners who trust the table finish near goal. The runners who abandon it usually miss by 10 to 20 minutes and blame the training rather than the pacing.
What to do if you fall off pace by mile 15
If by mile 15 you are consistently 15 to 30 seconds per mile behind the split table, do not try to make up the time in miles 16 to 20. That is the exact strategy that produces the wall. The right move is to accept a slightly slower finish, hold the current pace steady, and let the final 10K unfold at whatever pace stays sustainable. A 4:07 finish with a controlled last 10K feels vastly better than a 4:15 finish that included a 20-minute walk. Your body will thank you the next morning as well.
The corollary is that a split table is not sacred. It is a starting hypothesis. The mid-race version of the plan is to hold whatever pace is honest for the next 10K, using the table as a benchmark rather than an obligation. That is the mature use of the tool, and it separates first marathoners who finish strong from those who suffer.
Top comments (0)