Your Spring Marathon Nutrition Plan Starts Now — Not in January

You just registered for a spring marathon. The confirmation email is in your inbox, the training plan starts in January, and nutrition is filed under "deal with it later."

That instinct will cost you.

The athletes who nail race-day nutrition aren't the ones who panic-Google "marathon gel timing" during taper week. They're the ones who spent the months before training even started testing products, building tolerance, and collecting data. By the time their training plan kicks in, their fueling plan is already half-built.

Here's exactly what to do, month by month, from now through the start line.

Why the off-season is your nutrition testing lab

Training blocks are for building fitness. They're a terrible time to experiment with nutrition because every long run has a training purpose — you can't afford a GI disaster at mile 16 when the session is supposed to build aerobic endurance.

The off-season is different. The stakes are low. Your runs are shorter, your intensity is moderate, and a bad reaction to a new gel won't derail a key workout. That makes November through January the ideal window to answer three questions that determine everything on race day:

1. What is your sweat rate? Not a guess. An actual number from a weigh-in test.
2. What is your personal carb ceiling per hour? The maximum grams of carbohydrate your gut can absorb without distress at race intensity.
3. Which products work for you? Not which ones your training partner uses or which ones a podcast recommended.

If you show up to your first 20-miler in February without answers to those three questions, you're running a 16-week fueling experiment with a race entry fee on the line.

November: Establish your baselines

Sweat rate test

You need one number: how much fluid you lose per hour at an easy-to-moderate effort. The test is simple.

Weigh yourself before a 60-minute run — dry skin, minimal clothing. Run at your planned easy pace. Don't drink anything during the run. Weigh yourself again immediately after — same conditions. The difference in kilograms, multiplied by 1,000, is your sweat loss in millilitres.

If you lost 0.8kg, your sweat rate is roughly 800ml per hour at that temperature and intensity.

Do this twice in November at different temperatures if possible. Your sweat rate changes with heat, humidity, and fitness, so one data point isn't enough. Write the numbers down. You'll use them when you build your race-day hydration plan in February.

Product audit

Buy three to four different gel brands and two electrolyte products you haven't tried before. Over the next four weeks, test one new product per run on your regular easy runs. You're not testing performance — you're testing tolerance. Does it sit well? Does it cause bloating, cramping, or nausea? Can you stomach it 45 minutes into a run?

Keep notes. "Brand X was fine at easy pace" is useful data. "Brand Y made me nauseous at mile 3" eliminates a product before it ruins a long run.

Save your fall data

If you raced or trained through the autumn, your watch has months of data sitting in Garmin Connect, Apple Health, or Strava. Before you lose track of it in the off-season shuffle, pull out the numbers that matter for spring:

• Average heart rate at your target marathon pace
• Heart rate drift patterns on long runs (how much does your HR climb in the final third?)
• Any sweat loss estimates from your Garmin (directional, not precise)
• Which fueling products you used on your longest runs and how they went

This data is the starting point for your spring race-day plan. It's easier to find now than it will be in March.

December: Start gut training

Your gut is a muscle in the context of race fueling — it adapts to what you ask it to do. If you never practise eating during runs, your gut won't be ready to absorb 60+ grams of carbs per hour on race day.

Gut training is simple but takes consistency. Once per week on a moderate-effort run (tempo or steady state, 45–75 minutes), practise taking in fuel at race-like intervals.

Week 1–2: 20–30g carbs mid-run. One gel or a few chews at the 30-minute mark. Note how your stomach responds.

Week 3–4: 30–40g carbs across two intake points. One at 25 minutes, one at 50 minutes.

The goal isn't to hit race-day volumes yet. It's to teach your gut that fuel is coming during effort so it starts prioritising digestion alongside exercise. By the time your training plan starts and long runs begin, your gut will have four weeks of practice behind it.

Choose your carb source type

This is also when to decide between glucose-only and glucose-fructose blends. Dual-source gels (a 2:1 or 1:0.8 glucose-to-fructose ratio) allow higher absorption rates — up to 90g per hour versus roughly 60g for glucose alone — because they use different intestinal transporters.

If your target is 60g per hour or below, single-source gels are fine. If you're aiming higher, start testing dual-source products now. Switching carb types in March is too late for your gut to adapt.

January: Build your fueling framework

Your training plan is starting. Your long runs will gradually extend from 90 minutes to two-plus hours. This is where your November baselines and December gut training pay off.

Set your hourly targets

Use your sweat rate data and body weight to set starting targets:

• Fluid: Your November sweat rate minus roughly 200–300ml (you don't need to replace 100% of sweat loss during the run). If your sweat rate was 800ml/hr, start with 500–600ml/hr.
• Carbs: Start at whatever your gut training reached in December (likely 30–40g/hr) and plan to increase by 5–10g every two weeks through your long runs.
• Sodium: 300–600mg per hour is the standard range. If you're a heavy sweater or notice salt crust on your kit after runs, start at the higher end.

These are starting points, not final numbers. Every long run is a chance to refine them.

First long-run fueling test

Your first long run over 90 minutes is the first real rehearsal. Carry your chosen products, set a timer for your intake intervals (every 20–30 minutes), and execute.

After the run, ask yourself three questions:

1. Did my stomach tolerate the fuel? (If not, reduce volume or switch products.)
2. Did I run out of energy in the final 30 minutes? (If so, increase carbs next time.)
3. Did I feel bloated or waterlogged? (If so, reduce fluid volume or slow your drinking rate.)

Write the answers down. One run is one data point. You need six to eight long-run data points across your training block to build a confident race-day plan.

February: Refine and pressure-test

By now you should have three to four long runs of fueling data. Your gut should be handling 50–70g carbs per hour without distress. Your hydration volumes should feel dialled in.

February is when you increase the pressure.

Race-pace fueling test

On one of your long runs, run the final 30–45 minutes at goal marathon pace while fueling at your target rate. Intensity changes everything — your gut diverts blood away from digestion toward working muscles as effort increases. A fueling plan that works at easy pace might fall apart at marathon pace.

If it holds, you have a race-day plan. If your stomach rebels, you know to reduce your carb target by 10g per hour at race pace or switch to a more dilute product.

Conditions check

Your spring race will likely be warmer than your winter training runs. If you've been training in 5°C and your race is forecast at 15°C, your sweat rate will be higher. Re-do your sweat rate test in conditions as close to race day as possible, even if it means running in extra layers to simulate warmth.

Sweatr does this automatically — it adjusts your plan based on the forecast and your historical sweat rate data. But if you're building your plan manually, this conditions check is non-negotiable. A plan built for winter training won't hold in April sunshine.

March: Lock it in

Your final four to six weeks before race day should involve zero nutrition experiments. By now you know:

• Your fluid target per hour (adjusted for race-day temperature)
• Your carb target per hour (tested at race pace)
• Which specific products you'll carry and use
• Your intake timing (every X minutes, aligned with aid stations if possible)

Your last two long runs before taper are dress rehearsals. Execute your exact race-day plan: the same products, the same quantities, the same timing, the same pre-run meal. If anything feels off, you have one more long run to adjust. After that, the plan is locked.

Build your race-day kit

Decide what you're carrying versus what you'll pick up at aid stations. Check the race website for on-course nutrition — many marathons provide specific gel brands and sports drinks at designated miles. If the on-course gel isn't one you've tested, carry your own.

Pack your kit the way you'll race with it. Practise opening gels one-handed. Know which pocket or belt slot holds what. Race morning is not the time to fumble with packaging.

The cost of waiting

Every week you delay is a week of data you won't have. A runner who starts this process in November arrives at their first long run in January with a sweat rate number, a tested gel brand, and a gut that's already adapted to mid-run fueling. A runner who waits until January arrives with nothing and spends their first five long runs figuring out basics instead of refining.

By March, the first runner has a personalised plan built from three months of data. The second is still guessing.

Sweatr builds this plan from your Apple Watch or Garmin data — your sweat rate trends, your training load, your pace, and the conditions on race day. It turns months of testing into a single personalised race-day plan that adjusts as your training evolves. But whether you use an app or a spreadsheet, the principle is the same: start now, not in January.

Your spring marathon nutrition plan doesn't start when your training plan starts. It starts the moment you register.