Your Crew Is Your Kitchen
In a long ultra, falling behind on fuel is one of the most common reasons a race starts to unravel. Your body's carbohydrate stores only last a few hours at race effort, so for most of the day you're running on what you eat and drink. Later on, your stomach gets fussier, and the food you loved at mile 10 can make you gag. What keeps you moving is what goes in at every stop.
A crew changes the problem completely. Instead of carrying everything or relying on whatever the aid station has, you can have your own food, your own drink mix and a backup plan waiting at every crew stop. That only works if your crew knows what to hand you, when, and what to do when you won't take it.
This guide covers both sides: what the runner should decide before the race, and what the crew does at the aid station.
For Runners: Build the Fueling Plan Before the Race
Your crew can only follow a plan that exists. Work it out in training, on long runs at race effort, eating the foods you'll actually use. Race day is the wrong time to find out how your stomach handles a new gel.
Start From Common Ranges, Then Make Them Yours
Every runner is different, and heat, altitude and effort change what you need hour to hour. These are common starting points that many runners and coaches use. Test them in training and adjust, and talk to a sports dietitian if you can:
- Calories: many runners aim for roughly 200 to 300 calories an hour, mostly from carbohydrate
- Carbohydrate: around 60 grams an hour is a common target; some runners train their gut to handle more
- Fluid: often somewhere around 400 to 800 ml (about 14 to 27 oz) an hour, more in heat, guided by thirst
- Sodium: commonly a few hundred milligrams an hour, more for heavy or salty sweaters
These are general ranges, not medical advice. The right numbers are the ones you've tested on long runs. Write yours down for your crew.
Plan for the Late Miles, Not Just the Start
What works at mile 15 often stops working at mile 70. Sweet gels and drink mix get harder to face, and savory, salty, warm food gets more appealing. Plan for that change:
- Early stops: whatever you trained on, such as drink mix, gels, chews, bars
- Later stops: savory options like broth, potatoes with salt, quesadillas, noodle soup, rice balls
- Overnight: something warm, and caffeine if you use it (many runners save it for the night so it still works)
- Always: a backup for when you can't face the main plan, such as ginger chews, flat soda, plain crackers
Put it on paper station by station. "Food" isn't a plan; "two potato squares with salt, a cup of broth, both bottles refilled with drink mix" is.
Need a place to write it down? Use the free crew plan template
For Crews: What to Do at the Aid Station
Before Your Runner Arrives
- Check the plan for this stop and lay out exactly what's on it, plus the backup
- Mix bottles and have them filled, capped and ready to swap
- Heat anything warm so it's ready, not boiling, when they arrive
- Have a trash bag ready for wrappers and empty bottles
When They Come In
Hand things over; don't offer a menu. A tired runner struggles with "what do you want?" but can usually take what's put in their hand. Ask two quick questions instead:
- "What have you eaten and drunk since the last stop?" The answer tells you if they're keeping up
- "How's your stomach?" Nausea or bloating changes what you hand them next
Swap the bottles, put food in their hand, and send them out with something to eat on the move. The goal is a stop of a few minutes, not a sit-down meal.
Keep Track of What Went In
Write down what your runner took at each stop and roughly what they said they ate between stops. Over a long race, patterns show up that nobody can remember at 3 AM: they've skipped food at two stops in a row, or they're drinking much less than planned. A short log lets the next crew member know what's happened.
In UltraCrew, crew with logging permission can log nutrition and fluids at each aid station while the runner keeps moving, even with no signal: the log syncs once you're back online. The Starter plan is free.
Get Started FreeWhen Fueling Goes Wrong
Stomach trouble is one of the most common reasons runners stop. Some of it is normal and can be managed; some of it isn't.
Usually Manageable
- Can't face sweet food: switch to the savory and backup options
- Mild nausea: slow down for a few minutes and try small bites, ginger or flat soda. If they've been drinking a lot, don't push more fluid; see the signs below
- Not hungry: offer small amounts often rather than a big amount once
Get Help
Agree on these with your runner before the race. If you see any of them, get your runner to the race's medical staff. For confusion, slurred speech or collapse, call the race's emergency number, or 911 if medical help isn't close:
- They can't keep food or fluids down for two stops in a row
- Confusion, slurred speech, or acting very unlike themselves
- Swelling in the hands or face, a bad headache, nausea or vomiting while they've been drinking a lot. Drinking far beyond thirst can be dangerous, even with electrolytes or salt
- Little or no urine for many hours, or very dark urine
More on spotting trouble early: How to read your runner at aid stations
Put It in the Plan
Fueling is easiest when nobody has to make it up on the day. The runner decides what they want at each stop and what the warning signs are; the crew has it ready, hands it over, and keeps track. Bring both into your crew briefing, and pack with the checklist so the backup food actually makes it into the car.
Packing for race day? The ultra marathon crew checklist
Still building the rest of the plan? How to make a crew plan for your first 100-miler