How I PRed My 100k Time

I’ve been training for a big goal of mine: running a 100k in a specific amount of time. Yes, I’ve run farther than that before: last year I ran ~82 miles. However, I had someone in my family network who ran 100k last year, and I realized their time made a reasonable goal for me. I’m competitive, so the extra motivation of striving for a certain time is helpful for channeling my “racing”, even if I’m “racing” someone virtually (who ran a year ago!).

Like last year, I decided I would run my 100k (which is 62+ miles) as a solo or DIY ultramarathon. I originally plotted five laps of various lengths, then figured out I could slightly alter my longest route by almost a mile, making it so I would do 2 laps of the same length, a third lap of my original longest length, and then a fourth lap of a shorter length that’s also one of my preferred running routes. Only four laps would be mentally easier than doing five laps, even though it would end up being exactly the same distance. Like last year, I leveraged extensive planning (most of it done last year) to plan my electrolytes, enzymes, and fueling in advance. I had a lot less work to do this year, because I simply refreshed the list of gear and prep work from last year, shortened of course to match the length of my expected race (less than 18 hours vs ~24+ hours). The main thing I changed in terms of preparation is that while I set out a few “just in case” supplies, most of them I left in their places, figuring they’d be easy enough to find in the house by Scott (my husband) if I needed to ask him to bring out anything in particular. The few things I laid out were emergency medical supplies like inhaled insulin, inhaled glucagon, a backup pump site, etc. And my usual piles of supplies – clothes, fuel to refill my vest, etc – for each lap.

My 100k run supplies set out on the floor. I have a bag of OTC enzymes (for exocrine pancreatic insufficiency), 8-10 individually packaged snacks ranging from Fritos to yogurt pretzels to sandwich cookies, cashews, and beef sticks, a bag of electrolyte pills, and eye drops and disposable tooth brushes. Each lap (4 total) has a set of each of these.

One thing that was different for my 100k was my training. Last year, I was coming back from a broken toe and focused on rebuilding my feet. I found that I needed to stick with three runs per week. This year, I was back up to 4-5 runs per week and building up my long runs beginning in January, but in early February I felt like my left shin was getting niggle-y and I backed down to 3 runs a week. Plus, I was also more active on the weekends, including most weekends where we were cross-country skiing twice, often covering 10-15 miles between two days of skiing, so I was getting 3+ extra hours of “time on legs”, albeit differently than running. Instead of just keeping one longer run, a medium run, and two shorter runs (my original plan), I shifted to one long run, one medium long run (originally 8 and then jumping to 13 miles because it matched my favorite route), and the big difference was making my third run about 8 miles, too. This meant that I carried my vest and fueled for all three runs, rather than just one or two runs per week. I think the extra time training with the weight of my vest paid off, and the miles I didn’t do or the days I didn’t run didn’t seem to make a difference in regard to recovering during the weeks of training or for the big run itself. Plus, I practiced fueling every week for every run.

I also tapered differently. Once I switched to three runs a week, my shin felt a lot better. However, in addition to cross country skiing, Scott and I also have access now to an outdoor rock climbing wall (so fun!) and have been doing that. It’s a different type of workout and also helps with full body and upper body strength, while being fun and not feeling like a workout. I bring it up mostly because three weeks ago, I think I hurt the inside of my hip socket somehow by pressing off a foothold at a weird angle, and my hip started to be painful. It was mostly ok running, but I backed off my running schedule and did fewer miles for a week. The following week I was supposed to do my last longest long run – but I felt like it wouldn’t be ideal to do with my hip still feeling intermittently sore. Sometimes it felt uncomfortable running, other times it didn’t, but it didn’t feel fully back to normal. I decided to skip the last long run and stick with a week of my medium run length (I did 13, 13, and 8). That felt mostly good, and it occurred to me that two shorter weeks in a row were essentially a taper. If I didn’t feel like one more super long run (originally somewhere just under a 50k) was necessary to prepare, then I might as well consider moving my ‘race’ up. This is a big benefit of DIY’ing it, being able to adjust to injury or schedule – or the weather! The weather was also forecasted to be REALLY nice – no rain, high 50s F, and so I tentatively aimed to do a few short runs the following week with my 100k on the best weather day of the weekend. Or if the weather didn’t work out, I could push it out another week and stick with my original plan.

My taper continued to evolve, with me running 4 easy miles on Monday (without my vest) to see how my hip felt. Mostly better, but it still occasionally niggled when walking or running, which made me nervous. I discussed this endlessly with Scott, who as usual thought I was overcomplicating it and that I didn’t need to run more that week before my 100k. I didn’t like the idea of running Monday, then not running again until (Friday-Sunday, whenever it ended up being), but a friend unexpectedly was in town and free on Wednesday morning, so I went for a walk outside with her and that made it easy to choose not to run! It was going to be what it was going to be, and my hip would either let me run 100k or it would let me know to make it a regular long run day and I could stop at any time.

So – my training wasn’t ideal (shifting down to 3 runs a week) and my taper was very unexpected and evolved differently than it usually does, but listening to my body avoided major injury and I woke up feeling excited and with a good weather forecast for Friday morning, so I set off at 6am for my 100k.

(Why 6am start, if I was DIYing? My goal was to finish by 11:45pm, to beat the goal time of 11:46pm, which would have been 17 hours and 46 minutes. I could start later but that would involve more hours of running at night and keeping Scott awake longer, so I traded for an hour of running before it got light and finishing around midnight for a closer to normal bedtime for us both.)

*One other major thing I did to prep was that as soon as I identified that I wanted to shift my race up a week, I went in and started scheduling my bedtimes, beginning with the night before the race. If I raced at 6 from home, I would wake up at 5 to get ready, so I wanted to be sleeping by 9pm at the latest in order to get close to a normal night of sleep. Ideally it would be closer to 8-8:30. I set my bed time and each night prior, marked the bedtime 15 minutes later, so that when I started I was trying to push my bedtime from ~11pm to 10:45 pm then the next night 10:30pm etc. It wasn’t always super precise – I’ve done a better job achieving the goal bedtimes previously, but given that I did an early morning cross country ski race on the morning of daylight saving time the week before (ouch), it went pretty ok, and I woke up at 5am on race morning feeling rested and better than I usually do on race days. 7 hours and 45 minutes of sleep is an hour to an hour and a half less than usual, but it’s a LOT better than the 4-5 hours of sleep I might have otherwise gotten without shifting my schedule.

THE START (MILES 0-17)

My ultra running experience checklist, to highlight the good and the less good as I run. This shows that I saw stars, bunnies, and a loon and a pheasant, but did not see my usual eagles, heron, or heard any ducks splashing in the river at night.I set out at 6am, It was 33 degrees (F), so I wore shorts and a short sleeve shirt, with a pair of fleece lined pants over my shorts and a long sleeve shirt, rain jacket, ear cover, and gloves on my hand. It was dry, which helped. I was the only one out on the trail in the dark, and I had a really bright waist lamp and was running on a paved trail, so I didn’t have issues seeing or running. I felt a bit chilly but within 3 minutes could tell I would be fine temperature wise. As I got on the trail, I glanced up and grinned – the stars were out! That meant I could “check” something off my experience list at the very start. (I make a list of positive and less great experiences to ‘check off’ mentally, everything from seeing the stars or seeing bunnies or other wildlife to things like blisters, chafing, or being cold or tired or having out of whack glucose levels – to help me process and “check them off” my list and move on after problem solving, rather than dwelling on them and getting myself into a negative mood). The other thing I chuckled about at the start was passing the point where, about a half mile in to my 82 miles, I had popped the bite valve off of my hydration hose and gotten water everywhere and couldn’t find the bite valve for 3 minutes. That didn’t happen this time, phew! So this run was already off to a great start, just by nothing wild like that happening within the first few minutes. I peeled off my ear cover at 0.75 miles and my gloves at a mile. My jacket then peeled off to tie around my waist by the second mile, and I was surprised when my alarm went off at 6:30am reminding me to take in my first fuel. My plan calls for fuel every 30 minutes, which is why I like starting at the top of the hour (e.g. 6:00am) so I can use the alarm function on my phone to have alarms pre-set for the clock times when I need to fuel. Morning-sunrise-during-100kAs I continued my run/walk, just like I do in all my training runs, I pulled my enzymes out of my left pocket, swallowed them, put them away, grabbed my fuel out of my right pocket (starting with chili cheese Fritos), then also entered it into my fuel tracking spreadsheet so I could keep an eye on rolling calorie and sodium consumption throughout my run. (Plus, Scott can also see it and keep an eye on it as an extra data point that I’m doing well and following all planned activities, as well as having live GPS tracking and glucose tracking capabilities). I carried on, and as the sky began to lighten, I could see frost covering the ground beside the trail – brrr! It actually felt a little bit colder as the sun rose, and I could see wafts of fog rolling along the river. I started to see more people out for early morning runs, and I checked my usual irritation at people who were likely only out for (3? 5? 10? Psh!) short morning runs while I was just beginning an all day slog.

PheasantI was running well and a little ahead of my expected pace, closer to my usual long run/walk paces (which have been around 14:30-14:50 min/mi lately). I was concerned it was too fast and I would burn out as so many people do, but I did have wiggle room in my paces and had planned for an eventual slow down regardless. I made it to the first turnaround, used the trail bathroom there, and continued on, noting that even with the bathroom stop factored in, I was still on or ahead of schedule. I texted Scott to let him know to check my paces earlier than he might otherwise, and also stopped in my tracks to take a picture of a quail-like bird (which Scott thinks was a pheasant) that I’d never seen before. Lap 1 continued well, and I was feeling good and maintaining an overall sub-15 pace while I had been planning for a 15:10/ish average pace, so although Scott told me he didn’t need me to warn him about being particular miles away for aid station stops, I saw he was still at home by the time I was less than a mile out, and texted him. He was finishing a work call and had to rush to finish packing and come meet me. It wouldn’t have been a big deal if he had “missed” me at the expected turnaround spot, because there’s other benches and places where we could have met after that, but I think he was still stressed out (sorry!) about it, although I wasn’t. However, he biked up to me right at the turnaround spot, grabbed my vest and headed back to our normal table for refueling, while I used the bathroom and then headed out to meet him.

The other thing that might have stressed him out a little – and did stress me out a little bit – was my glucose levels. They were running normal levels for me during a run, around ~150mg/dL in the first 2-3 hours of my run. This is higher than I normally like to be for non-running times but is reasonable for long runs. I usually run a bit higher at the start and then settle in around 120-130mg/dL, because the risk of having too much insulin at the start from breakfast is prone to causing lows in the first hour; therefore I let myself reduce insulin prior to the run so that the first hour or so runs higher. However, instead of coming down as usual from the start of my run, I started a steady rise from 150 to 180. That was weird, but maybe it was a physiological response to the stress? I issued a correction, but I kept rising. I crossed 200 when I should have been beginning to flatten, and it kept going. What on earth? I idly passed my hand over my abdomen to check my pump site, and couldn’t feel my pump site. It had come unclipped!!! This was super frustrating, because it means I didn’t know how much insulin was in my body or when it had come unclipped. (Noteworthy that in 20+ years of using an insulin pump, this has NEVER happened before until this month, and it has now happened twice, so I need to record the batch/lot numbers and report it – this batch of sites is easily coming unclipped with a tug on the tubing, which is clearly dangerous because you can’t feel it come unclipped and don’t know until you see rising glucose levels.) “Luckily” though, this was when I was within 30 minutes or so of being back to Scott, so I texted him and told him to grab the inhaled insulin baggie I had set out, and I would use that at the aid station to more quickly get my body back into a good state (both in terms of feeling the insulin action as well as normalizing glucose levels more quickly. For those who don’t know, injected/pump insulin takes ~45 minutes to peak activity in the body, whereas inhaled insulin is much faster in the ballpark of ~15-20 minutes peak action, so in situations like this I prefer to, when possible, use inhaled insulin to normalize how my body is feeling while also resuming/fixing the pump site for normal insulin from then on).

As planned, at every aid station stop he brought water and ice to refill my camelback, which he did while I was at the bathroom. When I came up to the table where he was, I quickly did some inhaled insulin. Then I sat down and took off my socks and shoes and inspected my feet. My right foot felt like it had been rubbing on the outside slightly, so I added a piece of kinesiology tape to the outer edge of my foot. I already had pieces on the bottom of my feet to help prevent blisters like I got during my 82, and those seemed to be working, and it was quick and easy to add a straight piece of tape, re-stick pieces of lamb’s wool next to each big toe (to prevent blisters there), put fresh socks on, and put a fresh pair of shoes on. I also changed my shirts. It was now 44 F and it was supposed to warm up to 61 F by the end of this next lap. I stood up to put my pack on again and realized I had forgotten to peel off my pants! Argh. I had to unlace my shoes again, which was the most annoying part of my stop. I peeled off the pants (still wearing my shorts under), put my shoes back on and laced them again, then put my vest back on. I removed the remaining trash from my vest pockets, pulled out the old enzyme and electrolyte baggies, and began to put the new fuel supply and enzyme and electrolyte supply in the front vest pockets. Last time for my 82, I had Scott do the refilling of my vest, but this time I just had him set out my gallon bag that contained all of these, so that I could place the snacks how I like best and also have an idea of what I had for that lap. I would need to double check that I had enzymes and electrolytes, anyway, so it ended up being easier for me to do this and I think I’ll keep doing this moving forward. Oh, and at each aid station stop we popped my (non-ultra) Apple Watch on a watch charger to top off the charge, too. I also swapped in a new mini battery to my pack to help keep my phone battery up, and then took off. All this, including the bathroom time, took about 15 minutes! I had budgeted 20 minutes for each stop, and I was pleased that this first stop was ahead of schedule in addition to my running slightly ahead of schedule, because that gave me extra buffer if I slowed down later.

A 24 hour view of my CGM graph to show my glucose levels before (overnight), during the run including marks where my pump site likely unclipped, where I reclipped it, and how my glucose was in range for the remainder of the run.
A 24 hour view of my CGM graph to show my glucose levels before (overnight), during the run including marks where my pump site likely unclipped, where I reclipped it, and how my glucose was in range for the remainder of the run.

LAP 2 (MILES 18-34)

The next lap was the same route as the first, and felt like a normal long run day. It was mid 40s and gradually warmed up to 63 F and actually felt hot for the second half! It hadn’t been 60+ degrees in Seattle since October (!) so my body wasn’t used to the “heat”. I was still feeling good physically and running well – in fact, I was running only ~10s slower than my average pace from lap 1! If I kept this up and didn’t fall off the pace much in the second lap, I would have a very nice buffer for the end of the race. I focused on this lap and only thought about these 16-17 miles. I did begin to squirt water from my camelback on to the ‘cooling’ visor I have, which evaporates and helps your head feel cooler – especially since I wasn’t used to the heat and was sweating more, that felt good. The end of the second lap, I started to feel like I was slightly under my ideal sodium levels. I’m pretty sensitive to sodium; I also drink a lot (I was carrying 3-3.5L for every 17 mile lap!); and I’m a salty sweater. Add increased heat, and even though I was right on track with my goal of about ~500mg/hour of sodium intake between my fuel and additional electrolyte pills, I felt a bit under, and so the next while I added an extra electrolyte pill to increase my sodium intake, and the feeling went away as expected.

(My glucose levels had come back down nicely within the first few miles of this lap, dipped down but as I was fueling every 30 minutes, came nicely into range and stayed 100% in range with no issues for the next ~12 hours of the run!)

This time, Scott was aware that I was ahead of expected paces and had been mapping my paces. He told me that if I stayed at that pace for the lap, I would be able to slow down to a 16 min/mi pace for lap 3 (16 miles) and down further to a 17 min/mi pace for the last (almost 13 miles) lap and still beat my goal time. That sounded good to me! He ended up biking out early to meet me so he could start charging my watch a few minutes early, and I ended up taking one of my next snacks – a warmed up frozen waffle – for my ‘last’ snack of the lap because it was time for a snack and there was no reason to wait even though it was part of the ‘next’ lap’s fuel plan. So I got to eat a warm waffle, which was nice!

Once we got almost there, Scott took my vest and biked ahead to begin the camelback process. I hit the turnaround, made another quick bathroom stop, and ran over to the table. This time, since it was 60s and I would finish my next lap while it was still above 50 degrees and light, I left my clothing layers as-is, other than a quick shirt switch to get rid of my sweaty shirt. I decided not to undo my shoes and check my feet for blisters; they felt fine and good. Because I didn’t need a shoe change or have anything going on to troubleshoot, I was in and out in 5 minutes! Hooray, that gave me another 10 minute buffer (in addition to 5 before, plus all my running ahead of schedule). I took off for lap 3, but warned Scott I would probably be slowing down.

LAP 3 (MILES 35-50)

The third lap was almost the same route, but shorter by a little less than a mile. I was originally concerned, depending on how much I had slowed down, that I would finish either right around sunset or after sunset, so that Scott might need to bring me out a long sleeve shirt and my waist lamp. However, I was ahead of schedule, so I didn’t worry about it, and again set out trying to not fall off my paces too much. I slowed down only a tiny bit on the way out, and was surprised at the turnaround point that I was now only slightly above a 15 min/mi pace! The last few miles I felt like slowing down more, but I was motivated by two thoughts: one was that I would finish this lap and essentially be at 50 miles. This meant, given my excellent pacing, that I would be “PR”ing my 50 mile pace. I’ve not run a standalone 50 miles before, just as part of my 82 mile when I wasn’t paying attention to pace at all (and ran 2-3 min/mi slower as a result), so I was focused on holding my effort level to be close to the same. Plus, after this lap, I “only” had a ~13 mile single lap left. That was my usual route, so it would be mentally easier, and it’s my last lap, so I knew I would get a mental boost from that. Psychologically, having the 50 mile mark to PR here really helped me hold my pace! I ended up only slowing down ~13s average pace compared to the ~10s deterioration between laps 1 and 2. I was pretty pleased with that, especially with hitting 50 miles then!

At this aid station stop, I was pretty cheerful even though I kept telling Scott I would be slowing down. I took ~10 minutes at this stop because I had to put my jacket back on around my waist and put my double headlamp on (which I wear around my waist) for when it got dark, plus do the normal refueling. I changed my short sleeve shirt again so I had a dry shirt, and debated but went ahead and put my fresh long sleeve shirt on and rolled up the sleeves. I figured I’d be putting it on as soon as it got dark, and I didn’t want to have to hassle with getting my vest on and off (while moving) in order to get the shirt on, especially because I’d also have to do that with my jacket later, so I went with the long sleeve shirt on and rolled up the sleeves for now. I had originally planned to put my long pants back on over my shorts, but it was still 63 degrees and the forecast was only going to get down to 45 degrees by midnight, and I seemed ahead of schedule and should finish by then. If I did get really cold, Scott could always bike out early and bring me more layers, but even 45 degrees in the dark with long sleeves, jacket, ear cover, and two pairs of gloves should be fine, so I went without the pants.

Speaking of ahead of schedule, I was! I had 5 minutes from the first aid station, 15 minutes from the second aid station, 5 minutes from this last aid station…plus another ~15 minutes ahead of what I thought my running time would have been at this point. Woohoo!

LAP 4 (MILES 51-63)

However, as soon as I walked off with my restocked vest, I immediately felt incredibly sore thighs. Ouch! My feet also started complaining suddenly. I did an extra walk interval and resumed my run/walking and my first mile out of the aid station stop was possibly my slowest mile (barring any with a bathroom stop) for the entire race, which is funny, because it was only about a 16:30 pace. But I figured it would be downhill from there and I’d be lucky to hold a sub 17 pace for these last 13 miles, especially because most of them would be in the dark and I naturally move a bit slower in the dark. Luckily, I was so far ahead that I knew that even a 17 min/mi average pace (or even slower) would be fine. However, I had joked to Scott coming into the end of lap 3 that I was tempted to just walk lap 4 (because I was finally starting to be tired) but then I’d have to eat more snacks, because I’d be out there longer. Sounds funny, but it was true – I was eating ok but occasionally I was having trouble swallowing my enzyme pills. Which is completely reasonable, I had been swallowing dozens of those (and electrolyte pills) all day and putting food down my throat for ~12+ hours consistently. It wasn’t the action of swallowing that was a problem, but I seemed to be occasionally mistiming how I would get the pills washed to the back of my mouth at the top of my throat to be able to swallow them down. Once or twice I had to take in some extra water, so it really wasn’t a big deal, but it was a slight concern that if I stopped being able to enzyme, I couldn’t fuel (because I have EPI) and I’d either have to tough it out without fueling (bad idea) or stop (not a fun idea). So I had that little extra motivation to try to keep run/walking!

Luckily, that first mile of the last lap was the worst. My thighs were still sore but less so and my feet stopped yelling at me and were back to normal. I resumed a reasonable run/walk pace, albeit at closer to a 15:30+ pace, which was a bigger jump from my previous lap average pace. I didn’t let it stress me out, but I was wishing I felt like fighting harder. But I didn’t, and focused on holding that effort level. I texted Scott, telling him I was averaging sub-16 pace (barely) at miles 4 and 5, then asking him to check my assumption that if I didn’t completely walk it in, I could maybe be an hour ahead of schedule? He confirmed that I “only” needed 16:53 average pace for the lap to come in at 10:30pm (75 minutes ahead of goal) and that if I kept sub-16 I could come in around 10:19pm. Hmmm, that was nice to hear! I didn’t think I would keep sub-16 because it was getting dark and I was tired, ~55 miles into the run, but I was pretty sure I’d be able to be sub 17 and likely sub 16:53! I carried on, turning my light on as it got dark. I was happily distracted by checking happy experiences off my mental list, mostly seeing bunnies beside and darting across the trail in the dark!

I hit the almost-halfway mileage point of the last lap, but even though it wasn’t halfway in mileage it felt like the last big milestone – it was the last mini-hill I had to climb to cross a bridge to loop around back to finish the lap. Hooray! I texted Scott and told him I coudn’t believe that, with ~7 miles left, I would be done in <2 hours. It was starting to sink in that I’d probably beat my goal of 11:45 and not doubt that it was real, and that I’d beat it by more than a few minutes. I then couldn’t resist – and was also worried Scott wouldn’t realize how well I was moving and be prone to coming out too late – and texted him again when I was <5 miles out and then 4 miles out. But by the time I was at 3 miles, he replied to ask if I needed anything else other than the bag I had planned for him to bring to the finish. Nope, I said.

At that point, I was back on my home turf, as I think about the last 2-3 miles that I run or walk on most days of the week. And I had run these miles 3 times already (in each direction, too), but it was pretty joyful getting to the point where I know not only every half mile marker but every tenth of a mile. And when I came up under the last bridge and saw a bright light biking toward me, it was Scott! He made it out to the 1.75 mile mark and rode in with me, which was fun. I was still holding just under sub-16 pace, too. I naturally pick up the pace when he’s biking with me – even when I’ve run 60+ miles! – and I was thinking that I’d be close but a few minutes under an hour and a half of schedule. It didn’t really matter exactly, but I like even numbers, yet I didn’t feel like I had tons of energy to push hard to the end – I was pleased enough to still be moving at a reasonable speed at this point!

Finally, about a half mile out, Scott biked ahead to set up the finish for me. (Purple painter’s tape and a sign I had made!) I glanced at my watch as I rounded the last corner, about .1 mile away, and though “oh, I was so close to beating the goal by over an hour and a half, too bad I didn’t push harder a few minutes ago so I could come in by 10:16 and be an hour and a half ahead”. I ran a tiny bit more but didn’t have much speed, walked a few last steps, then ran the rest of the way so Scott could video me coming into the finish. I could see the light from his bike’s light glowing on the trail, and as I turned the corner to the finish I was almost blinded by his waist light and his head lamp. I ran through the finish tape and grinned. I did it! He stopped videoing and told me to stop my trackers. I did but told him it didn’t matter, because I was somewhere under an hour and a half. We took a still picture, then picked up my tape and got ready to head home. I had done it! I had run 100k, beat my goal time…and it turns out I DID beat it by over an hour and a half! We checked the timestamp on the video Scott took of the finish and it has me crossing at 10:16pm, so that makes it a 16 hour and 16 minute finish – woohoo!

A picture at night in the dark with me running, light at my waist, toward the purple painter tape stretched out as my finish line.

My last lap ended up being ~37 seconds average pace slower, so I had :10, :13, and :37 differences between the laps. Not too bad for that distance! I think I could’ve pushed a little harder, but I honestly didn’t feel like it psychologically, since I was already exceeding all of my goals, and I was enjoying focusing on the process meta-goals of trying to keep steady efforts and paces. Overall, my average pace was 15:36 min/mi which included ~30 min of aid station stops; and my average moving pace (excluding those 30 minutes of aid station time but did include probably another ~8-10 min of bathroom stops) was 15:17 min/mi. I’m pleased with that!

FUN STATS

A pivot table with conditional formatting showing when my sodium, calories, and carbs per hour met my hourly goal amounts.One of the things I do for all training runs but also races is input my fueling as I go, because it helps me make sure I’m actually fueling and spot any problems as they start to develop. As I mentioned, at one point I felt a tiny bit low on sodium and sure enough, I had dipped slightly below 500mg/hr in the two hottest hours of the day when I had also been sweating more and drinking more than I had been previously. Plus, it means I have cool post-run data to see how much I consumed and figure out if I want to adjust my strategy. This time, though? I wouldn’t change a thing. I nailed it! I averaged 585 mg/hour of sodium across all ~16 hours of my run. I also averaged ~264 calories/hour, which is above my ~250/hr goal. I did skip – intentionally – the very last snack at the top of the 16th hour, and it still meant that I was above goal in all my metrics. I don’t set goals for carb intake, but in case you were wondering, I ended up averaging 29.9 grams of carbs/hour (min 12, max 50, and the average snack is 15.4 carbs), but that’s totally coincidental. Overall, I consumed 3,663 calories, which was 419 carbs, 195 g of fat, and 69 grams of protein.

With EPI, as I mentioned that means I have to swallow enzyme pills with every snack, which was every 30 minutes. I swallowed 71 OTC enzyme pills (!) to match all that fuel, plus 26 electrolyte pills…meaning I swallowed 97 pills in 16 hours. You can see why I get tired of swallowing!

A graph showing the rates of sodium/hr for each 16 hours of the run (averaging above 500mg/hr); calories per hour (averaging above 250/hour), and carbs per hour.

Here’s a visual where you can see my consumption of calories, sodium, (and carbs) over the course of my race. The dip at the end is because I intentionally skipped the second snack of the hour 16 because I was almost done. Up to 15 hours (excluding the last hour), I had a slightly rolling increase in sodium/hr and a very slight decrease in calories/hr, with carbs/hr slightly increasing. Including the 16th hour (with a skipped snack intentionally), this changed the trends to slight rolling decrease in sodium/hr; the slight decrease trend in calories/hr continued; but it flattened the carbs/hr trend line to be neutral.

In contrast to my 82 mile where I had more significant fluctuations in sodium (and really felt it), I’m glad I was able to keep my sodium consumption at goal levels and also more easily respond when the conditions changed (hotter weather causing more sweat and more water intake than previous hours) so I could keep myself from getting into a hole sodium-wise. Overall, I feel like I get an A+ for executing my fueling and sodium strategy as planned. GI-wise, I get an A+++ because I had ZERO GI symptoms during and after the run! That’s really rare for any ultrarunners, let alone those of us with GI conditions (in my case, exocrine pancreatic insufficiency). Plus, despite the unclipped pump site and BG rise that resulted, I resumed back to typical running glucose levels for me and achieved 100% TIR 70-180 after that and I think likely 100% TIR for a more narrow range like 70-140, too, although I haven’t bothered to run those stats because I don’t care exactly what the numbers are. More importantly, I never went low, I never had any big drops or rises, and other than the brief 30 minutes of annoyance due to an unclipped pump site, diabetes did not factor any more into my thinking than blister management or EPI pill swallowing or sodium did – which is great!

Here’s a view of what I had leftover after my run. I had intentionally planned for an extra snack for every lap, plus I ran faster so I needed fewer overall. I also had packed extra enzymes and electrolytes for every lap, hoping I would never need to stress about running out on any individual lap – and I didn’t, so those amounts worked well.

A view of the enzymes and electrolyte baggies after my run, with a few left in each baggie as I planned for extras. I also had some snacks I didn't eat, both because I planned one extra per lap but I also ran faster than I expected, so I needed fewer overall

POST-RUN RECOVERY

As soon as I stopped running and took a picture at the finish line, we got ready to head home. My muscles froze up as soon as I stopped, just like always, so I moved like a tin person for a few steps before I loosened back up and was able to walk normally. I got home, and was able to climb into the shower (and out!) without too much hardship. I climbed into bed, hydrated, and was able to go to sleep pretty normally for about 5 hours. I woke up at 5am pretty awake, which possibly was also due to the fact that I had been sleep shifting my sleep schedule, but I also felt really stiff and used the opportunity to point and flex my ankles. I slept every 20-30 minutes off and on for another few hours before I finally got up at 8am and THEN felt really sore and stiff! My right lower shin was sore and had felt sore just a tiny bit in the last few miles of my run, so it wasn’t surprising that it was sore. My right hip, which is the one I had been watching prior to the race, was sore again. I hobbled around the house and started to loosen up, enough that I decided that I would put shoes on and try to go for a short easy walk. Usually, I can’t psychologically fathom putting shoes on my feet after an ultra, but my feet felt really decent! I had some blisters, sure, but I hadn’t even noticed them running and they didn’t hurt to walk on. My hip and ankle were more noticeable. I didn’t try to take the stairs and used the elevator, then began hobbling down the sidewalk. Ouch. My hip was hurting so much that I stopped at the first bench and laid down on it to stretch my hip out. Then I walked .3 miles to the next bench and again stretched my hip. A little better, so we went out a bit farther with the plan to turn around, but my hip finally loosened up after a half mile where I could mostly walk normally! Hooray. In total, I managed 1.5 miles or so of a walk, which is pretty big for me the day after an ultra run.

Meaningfully, overnight, I still had 100% time in range (ideal glucose levels). I did not have to do any extra work, thanks to OpenAPS and autosensitivity which adjusts automatically to any increases and later return to normal insulin sensitivity from so much activity!

A 12 hour view of glucose levels after my 100k. This was 100% TIR between 70-180 and probably a tighter range, although I did not bother to calculate what the tighter range is.

The next night, I slept even better, and didn’t notice any in-bed stiffness, although again on the second morning I felt stiff getting out of bed, but was able to do my full 5k+ walk route with my hip loosening up completely by a mile so that I didn’t even think about it!

On day 3, I feel 90% back to normal physically. I’m mostly fatigued,which Scott keeps reminding me is “as one should be” after runnning 100k! The nice change is that with previous ultras or long runs, I’ve felt brain fog for days or sometimes weeks – likely due to not fueling enough. But with my A+ fueling, my brain feels great – and good enough that it’s annoyed with my body still being a little bit tired. Interestingly, my body is both tired but also itching for more activity and new adventures. My friend compared it to “sea legs” where the brain has learned that the body should always be in motion, which is a decent analogy.

WHAT I HAVE LEARNED

I wouldn’t change anything in terms of my race pacing, execution, aid station stops, fueling, etc. for this run.

What I want to make sure I do next time includes continuing to adapt my training to listen to my body, rather than sticking to my pre-decided plan of how much to run. I feel like I can do that both because I now have 3000+ miles on my body of lifetime running (that I didn’t have for my first ultra); and I now have two ultras (last year’s 82 miles post-broken toe and this year’s 100k with minor hiccups like a sore shin and a hip at different times) where I was forced to or chose to adapt training, and it turned out just as good as I would have expected. For my 100k, I think the adaptation to 3 runs per week, all with my vest, ended up working well. This is the first run where I didn’t have noticeable shoulder soreness from my pack!

Same goes for taper: I don’t think, at my speed/skill level, that exact taper strategy makes a difference, and this experience confirmed it, doing DIY ultras and being able to flex a week forward or back based on how I’m physically feeling and when the best weather will be is now my preferred strategy for sure.

—-

If you’re new to ultras and haven’t read any of my other posts, consider reading some of the following, which I’ve alluded to in my post and directly contribute to the above situation being so positive:

Feel free to leave questions if you have any, either about slow ultra running in general or any other aspects of ultra running! I’m a places-from-last kind of ultra runner, but I’m happy to share my thinking process if it helps anyone else plan their own adventures.

How to Pick Food (Fuel) For Ultramarathon Running

I’ve previously written about ultrarunning preparation and a little bit about how I approach fueling. But it occurred to me there might be others out there wondering exactly HOW to find fuel that works for them, because it’s an iterative process.

The way I approach fueling is based on a couple of variables.

First and foremost, everything has to be gluten free (because I have celiac). So that limits a lot of the common ultrarunning fuel options. Things like bars (some are GF, most are not), Uncrustables, PopTarts, and many other common recommendations in the ultra community just aren’t an option for me. Some, I can find or make alternatives to, but it’s worth noting that being gluten free for celiac (where cross-contamination is also an issue, not just the ingredients) or having a food allergy and being an ultrarunner can make things more challenging.

Then, I also have exocrine pancreatic insufficiency. This doesn’t limit what I eat, but it factors in to how I approach ideal fueling options, because I have to match the enzyme amounts to the amount of food I’m eating. So naturally, the pill size options I have of OTC enzymes (one is lipase only and covers ~6g of fat for me, the other is a multi-enzyme option that includes protease to cover protein, and only enough lipase to cover ~4g of fat for me; I also have one much larger that covers ~15g of fat but I don’t typically use this one while running) influence the portion sizes of what I choose.

That being said, I probably – despite EPI – still tend toward higher fat options than most people. This is in part because I have had type 1 diabetes for 20+ years. While I by no means consume a low c-a-r-b diet, I typically consume less than the people with insulin-producing pancreases in my life, and lean slightly toward higher fat options because a) my taste buds like them and b) they’ve historically had less impact on my glucose levels. Reason A is probably the main reason now, thanks to automated insulin delivery, but regardless of reason, 20+ years of a higher level than most people’s fat consumption means I’m also probably better fat-adapted for exercise than most people.

Plus, ultrarunning tends to be slower than shorter runs (like marathons and shorter for most people), so that’s also more amenable to fat and other nutrient digestion. So, ultrarunners in general tend to have more options in terms of not just needing “gu” and “gel” and “blocks” and calorie-sugar drinks as fuel options (although if that is what you prefer and works well for you, great!).

All of these reasons lead me toward generally preferring fuel portions that are:

  1. Gluten free with no cross-contamination risk
  2. ~20g of carbs
  3. ~10g of fat or less
  4. ~5-10g of protein or less

Overall, I shoot for consuming ~250 calories per hour. Some people like to measure hourly fuel consumption by calories. Others prefer carb consumption. But given that I have a higher tolerance for fat and protein consumption – thanks to the enzymes I need for EPI plus decades of practice – calories as a metric for hourly consumption makes sense for me. If I went for the level of carb intake many recommend for ultrarunners, I’d find it harder to consistently manage glucose levels while running for a zillion hours. I by no means think any of my above numbers are necessarily what’s best for anyone else, but that’s what I use based on my experiences to date as a rough outline of what to shoot for.

After I’ve thought through my requirements: gluten free, 250 calories per hour, and preferably no single serving portion size that is greater than 20ish grams of carbs or 10g of fat or 5-10g or protein, I can move on to making a list of foods I like and that I think would “work” for ultrarunning.

“Work” by my definition is not too messy to carry or eat (won’t melt easily, won’t require holding in my hands to eat and get them messy).

My initial list has included (everything here gluten free):

  • Oreos or similar sandwich type cookies
  • Yogurt/chocolate covered pretzels
  • PB or other filled pretzel nuggets
  • Chili cheese Fritos
  • Beef sticks
  • PB M&M’s
  • Reese’s Pieces
  • Snickers
  • Mini PayDays
  • Macaroons
  • Muffins
  • Fruit snacks
  • Fruit/date bars
  • GF (only specific flavors are GF which is why I’m noting this) of Honey Stinger Stroopwaffles

I wish I could include more chip/savory options on my lists, and that’s something I’ve been working on. Fritos are easy enough to eat from a snack size baggie without having to touch them with my hands or pull individual chips out to eat; I can just pour portions into my mouth. Most other chips, though, are too big and too ‘sharp’ feeling for my mouth to eat this way, so chili cheese Fritos are my primary savory option, other than beef sticks (that are surprisingly moist and easy to swallow on the run!).

Some of the foods I’ve tried from the above list and have eventually taken OFF my list include:

  • PB pretzel nuggets, because they get stale in baggies pretty fast and then they feel dry and obnoxious to chew and swallow.
  • Muffins – I tried both banana muffin halves and chocolate chip muffin halves. While they’re moist and delicious straight out of the oven, I found they are challenging to swallow while running (probably because they’re more dry).
  • Gluten free Oreos – actual Oreo brand GF Oreos, which I got burnt out on about the time I realized I had EPI, but also they too have a pretty dry mouthfeel. I’ve tried other brand chocolate sandwich cookies and also for some reason find them challenging to swallow. I did try a vanilla sandwich cookie (Glutino brand) recently and that is working better – the cookie is harder but doesn’t taste as dry – so that’s tentatively on my list as a replacement.

Other than “do I like this food” and “does it work for carrying on runs”, I then move on to “optimizing” my intake in terms of macronutrients.  Ideally, each portion size and item has SOME fat, protein, and carbs, but not TOO MUCH fat, protein and carbs.

Most of my snacks are some fat, a little more carb, and a tiny bit of protein. The outlier is my beef sticks, which are the highest protein option out of my shelf-stable running fuel options (7g of fat, 8g of protein). Most of the others are typically 1-3g of protein, 5-10g of fat (perfect, because that is 1-2 enzyme OTC pills), and 10-20g of carb (ideal, because it’s a manageable amount for glucose levels at any one time).

Sometimes, I add things to my list based on the above criteria (gluten free with no cross-contamination list; I like to eat it; not messy to carry) and work out a possible serving size. For example, the other day I was brainstorming more fuel options and it occurred to me that I like brownies and a piece of brownie in a baggie would probably be moist and nice tasting and would be fine in a baggie. I planned to make a batch of brownies and calculated how I would cut them to get consistent portion sizes (so I would know the macronutrients for enzymes).

However, once I made my brownies, and started to cut them, I immediately went “nope” and scratched them off my list for using on runs. Mainly because, I hate cutting them and they crumbled. The idea of having to perfect how to cook them to be able to cut them without them crumbling just seems like too much work. So I scratched them off my list, and am just enjoying eating the brownies as brownies at home, not during runs!

I first started taking these snacks on runs and testing each one, making sure that they tasted good and also worked well for me (digestion-wise) during exercise, not just when I was sitting around. All of them, other than the ones listed above for ‘dry’ reasons or things like brownies (crossed off because of the hassle to prepare), have stayed on the list.

I also started looking at the total amount of calories I was consuming during training runs, to see how close I was to my goal of ~250 calories per hour. It’s not an exact number and a hard and fast “must have”, but given that I’m a slower runner (who run/walks, so I have lower calorie burn than most ultrarunners), I typically burn in the ballpark of ~300-400 calories per hour. I generally assume ~350 calories for a reasonable average. (Note, again, this is much lower than most people’s burn, but it’s roughly my burn rate and I’m trying to show the process itself of how I make decisions about fuel).

Aiming for ~250 calories per hour means that I only have a deficit of 100 calories per hour. Over the course of a ~100 mile race that might take 30 hours, this means I’ll “only” have an estimated deficit of 3,000 calories. Which is a lot less than most people’s estimated deficit, both because I have a lower burn rate (I’m slower) and because, as described above and below, I am trying to be very strategic about fueling for a number of reasons, including not ending up under fueling for energy purposes. For shorter runs, like a 6 hour run, that means I only end up ~600 calories in deficit – which is relatively easy to make up with consumption before and after the run, to make sure that I’m staying on top of my energy needs.

It turns out, some of my preferred snacks are a lot lower and higher calories than each other! And this can add up.

For example, fruit snacks – super easy to chew (or swallow without much chewing). 20g of carb, 0g of fat or protein, and only 80 calories. Another easy to quickly chew and swallow option: a mini date (fruit) bar. 13g carb, 5g fat, 2 protein. And…90 calories. My beef stick? 7g of fat, 8g of protein, and only 100 calories!

My approach that works for me has been to eat every 30 minutes, which means twice per hour. Those are three of my favorite (because they’re easy to consume) fuel options. If I eat two of those in the same hour, say fruit snacks and the date bar, that’s only 170 calories. Well below the goal of 250 for the hour! Combining either with my beef stick (so 180 or 190 calories, depending), is still well below goal.

This is why I have my macronutrient fuel library with carbs, fat, protein, *and* calories (and sodium, more on that below) filled out, so I can keep an eye on patterns of what I tend to prefer by default – which is often more of these smaller, fewer calorie options as I get tired at the end of the runs, when it’s even more important to make sure I’m at (or near) my calorie goals.

Tracking this for each training run has been really helpful, so I can see my default tendency to choose “smaller” and “easier to swallow” – but that also means likely fewer calories – options. This is also teaching me that I need to pair larger calorie options with them or follow on with a larger calorie option. For example, I have certain items on my list like Snickers. I get the “share size” bars that are actually 2 individual bars, and open them up and put one in each baggie. ½ of the share size package (aka 1 bar) is 220 calories! That’s a lot (relative to other options), so if I eat a <100 calorie option like fruit snacks or a date bar, I try to make it in the same hour as the above average option, like the ½ snickers. 220+80 is 300 calories, which means it’s above goal for the hour.

And that works well for me. Sometimes I do have hours where I am slightly below goal – say 240 calories. That’s fine! It’s not precise. But 250 calories per hour as a goal seems to work well as a general baseline, and I know that if I have several hours of at or greater than 250 calories, one smaller hour (200-250) is not a big deal. But this tracking and reviewing my data during the run via my tracking spreadsheet helps make sure I don’t get on a slippery slope to not consuming enough fuel to match the demands I’m putting on my body.

And the same goes for sodium. I have read a lot of literature on sodium consumption and/or supplementation in ultrarunning. Most of the science suggests it may not matter in terms of sodium concentration in the blood and/or muscle cramps, which is why a lot of people choose sodium supplementation. But for me, I have a very clear, distinct feeling when I get not enough sodium. It is almost like a chemical feeling in my chest, and is a cousin (but distinct) feeling to feeling ketones. I’ve had it happen before on long hikes where I drank tons to stay hydrated and kept my glucose levels in range but didn’t eat snacks with sodium nor supplement my water. I’ve also had it happen on runs. So for me, I do typically need sodium supplementation because that chemical-like feeling builds up and starts to make me feel like I’m wheezing in my chest (although my lungs are fine and have no issues during this). And what I found works for me is targeting around 500mg/hour of sodium consumption, through a combination of electrolyte pills and food.

(Side note, most ultrarunning blogs I’ve read suggest you’ll be just fine based on food you graze at the aid station. Well, I do most of my ultras as solo endeavors – no grazing, everything is pre-planned – and even if I did do an organized race, because of celiac I can’t eat 95% of the food (due to ingredients, lack of labeling, and/or cross contamination)…so that just doesn’t work for me to rely on aid station food to supplement me sodium-wise. But maybe it would work for other people, it just doesn’t for me given the celiac situation.)

I used to just target 500mg/hour of sodium through electrolyte pills. However, as I switched to actually fueling my runs and tracking carbs, fat, protein, and calories (as described above), I realized it’d be just as easy to track sodium intake in the food, and maybe that would enable me to have a different strategy on electrolyte pill consumption – and it did!

I went back to my spreadsheet and re-added information for sodium to all of my food items in my fuel library, and added it to the template that I duplicate for every run. Some of my food items, just like they can be outliers on calories or protein or fat or carbs, are also outliers on sodium. Biggest example? My beef stick, the protein outlier, is also a sodium outlier: 370mg of sodium! Yay! Same for my chili cheese Fritos – 210mg of sodium – which is actually the same amount of sodium that’s in the type of electrolyte pills I’m currently using.

I originally had a timer set and every 45 minutes, I’d take an electrolyte pill. However, in the last year I gradually realized that sometimes that made me over by quite a bit on certain hours and in some cases, I ended up WAY under my 500mg sodium goal. I actually noticed this in the latter portion of my 82 mile run – I started to feel the low-sodium chest feeling that I get, glanced at my sheet (that I hadn’t been paying close attention to because of So. Much. Rain) and realized – oops – that I had an hour of 323mg of sodium followed by a 495mg hour. I took another electrolyte pill to catch up and chose some higher sodium snacks for my next few fuels. There were a couple hours earlier in the run (hours 4 and 7) where I had happened to – based on some of my fresh fuel options like mashed potatoes – to end up with over 1000mg of sodium. I probably didn’t need that much, and so in subsequent hours I learned I could skip the electrolyte pill when I had had mashed potatoes in the last hour. Eventually, after my 82-mile run when I started training long runs again, I realized that keeping an eye on my rolling sodium tallies and tracking it like I tracked calories, taking an electrolyte pill when my hourly average dropped <500mg and not based on a pre-set time when it was >500mg, began to work well for me.

And that’s what I’ve been experimenting with for my last half dozen runs, which has worked – all of those runs have ended up with a total average slightly above 500mg of sodium and slightly above 250 calories for all hours of the run!

An example chart that automatically updates (as a pivot table) summarizing each hour's intake of sodium and calories during a run. At the bottom, an average is calculated, showing this 6 hour run example achieved 569 mg/hr of sodium and 262 calories per hour, reaching both goals.

Now, you may be wondering – she tracks calories and sodium, what about fat and protein and carbs?

I don’t actually care about or use these in real-time for an hourly average; I use these solely as real-time decision in points as 1) for carbs, to know how much insulin I might need dependent on my glucose levels at the time (because I have Type 1 diabetes); and 2) the fat and protein is to make sure I take the right amount of enzymes so I can actually digest the fuel (because I have exocrine pancreatic insufficiency and can’t digest fuel without enzyme pills). I do occasionally look back at these numbers cumulatively, but for the most part, they’re solely there for real-time decision making at the moment I decide what to eat. Which is 95% of the time based on my taste buds after I’ve decided whether I need to factor in a higher calorie or sodium option!

For me, my higher sodium options are chili cheese Fritos, beef stick, yogurt covered pretzels.

For me, my higher calorie options are the ½ share size Snickers; chili cheese Fritos; Reese’s pieces; yogurt covered pretzels; GF honey stinger stroopwaffle; and 2 mini PayDay bars.

Those are all shelf-stable options that I keep in snack size baggies and ready to throw into my running vest.

Most of my ‘fresh’ food options, that I’d have my husband bring out to the ‘aid station’/turnaround point of my runs for refueling, tend to be higher calorie options. This includes ¼ of a GF PB&J sandwich (which I keep frozen so it lasts longer in my vest without getting squishy); ¼ of a GF ham and cheese quesadilla; a mashed potato cup prepared in the microwave and stuck in another baggie (a jillion, I mean, 690mg of sodium if you consume the whole thing but it’s occasionally hard to eat allll those mashed potatoes out of a baggie in one go when you’re not actually very hungry); sweet potato tots; etc.

So again, my recommendation is to find foods you like in general and then figure out your guiding principles. For example:

  • Do you have any dietary restrictions, food allergies or intolerances, or have already learned foods that your body Does Not Like while running?
  • Are you aiming to do carbs/hr, calories/hr, or something else? What amounts are those?
  • Do you need to track your fuel consumption to help you figure out how you’re not hitting your fuel goals? If so, how? Is it by wrappers? Do you want to start with a list of fuel and cross it off or tear it off as you go? Or like me, use a note on your phone or a drop down list in your spreadsheet to log it (my blog post here has a template if you’d like to use it)?

My guiding principles are:

  • Gluten free with no cross contamination risk (because celiac)
  • ~250 calories per hour, eating twice per hour to achieve this
  • Each fuel (every 30 min) should be less than ~20g of carb, ~10g of fat, and ~5-10g of protein
  • I also want ~500mg of sodium each hour through the 2x fuel and when needed, electrolyte pills that have 210mg of sodium each
  • Dry food is harder to swallow; mouthfeel (ability to chew and swallow it) is something to factor in.
  • I prefer to eat my food on the go while I’m run/walking, so it should be all foods that can go in a snack or sandwich size baggie in my vest. Other options (like chicken broth, soup, and messy food items) can be on my backup list to be consumed at the aid station but unless I have a craving for them, they are secondary options.
  • Not a hassle to make/prepare/measure out into individual serving sizes.

Find foods that you like, figure out your guiding principles, and keep revising your list as you find what options work well for you in different situations and based on your running needs!

Food (fuel) for ultramarathon running by Dana Lewis at DIYPS.org

Ultramarathon Races Are Exclusionary

Recently, I’ve been thinking about the feeling I have that ultrarunning races (ultramarathons) are exclusionary.

Running is theoretically very accessible: you go out and do it. No special equipment or clothes needed. Same for ultrarunning: go run a distance longer than a marathon (26.2 miles or ~42 kilometers). You don’t even have to do it in an organized “race”, as many of us run DIY or solo ultramarathons for training or in lieu of races (like I did for my 82 miler). Run 26.3 miles? Technically you’re an ultrarunner (although it’s more common for a 50k/31 mile race to be the first distance most people consider ‘ultra’).

For many people, though, an organized ‘race’ or event is important for a number of reasons. It provides a commitment device and a firm and hard deadline for which to train. It might be the only safe way to achieve a distance, with aid stations and volunteers to support achieving the endeavor, if they don’t have family or friends able to crew runs otherwise or lack safe places to run these distances. It also provides motivation and camaraderie of setting out to achieve the same goal as a group of other people at the same time. And of course, it provides competition – not only with one’s self to achieve their best that day, but also against other people.

Most of us, though, statistically aren’t racing in an ultramarathon for a podium place or top-whatever finish.

So why do the rules work to exclude so many people from participating in ultramarathons?

I’m talking about rules like those often found listed in the 200 mile ultramarathon race descriptions and rule handbooks that say that aid cannot be administered outside of the aid station. Crew may not hand anything to racers outside of the aid station:

  • Cowboy 200, runner manual last updated 8/16/22: “Crew is only allowed to assist runners at FULL/MANNED aid stations. No exceptions. Crew cannot give anything to or take anything from runners anywhere except at manned aid stations.”
  • Bigfoot 200, 2022 runner manual: “Pacers are not allowed to mule (carry items) for their runner. Pacers may not give their runner any aid, food or water unless it is an emergency situation, in which case the runner may be disqualified. Pacers are for safety, not for giving aid or gaining an advantage over fellow participants.” and “Crew may not meet their runner between aid”
  • Tahoe 200, 2022 runner manual: A full disqualification may be given if “Contacts crew anywhere between aid stations; Has crew leave items left for the runner anywhere along the course; Takes outside aid between aid stations”
  • Moab 240, 2022 runner manual – same as above Tahoe 2022
  • Cocodona 250, accessed January 2023: “Crew may not meet their runner at any point on the course other than designated crew access aid stations. Runners will be automatically disqualified for receiving aid from crew outside of crew access aid stations.”

It’s a thing in 100 miles races, too.

  • Western States 100, 2023 participant guide: “Runners may not accept aid or assistance from their crew or other spectators in between crew-accessible aid stations.” and “Pacers may not carry water, food, flashlights, shoes, clothing, or other supplies for their runner or provide any other type of mechanical or physical assistance to their runner on the course.”
  • Hardrock 100, 2022 guide: “No stashing of supplies along the course and no accepting aid except within 400 yards of a designated aid station.” and “Pacers may not carry water, food, flashlights, shoes, clothing, or other supplies for their runner or provide any other type of mechanical or physical assistance to their runner on the course.”

Why is this a problem?

Well, say that an ultrarunner has type 1 diabetes and uses an insulin pump and the insulin pump breaks. (Battery dies; the pump itself smashes against a rock and breaks the screen; or like in my 82 miler last year, the water busts the button panel and it is no longer operable.) If you have a backup pump and a crew member, in a non-race setting they’d simply bike or run or drive out to you (whatever was feasible and safe for them) and hand you the pump. You’d replace it, and continue on your way.

But according to the ‘rules’ of these ultramarathon ‘races’, you’d be immediately disqualified and stopped from continuing the ultramarathon. In order to not be disqualified, you’d have to wait until you got to the aid station to swap to a backup insulin pump. Sure, you’d likely have a back up insulin delivery method (syringe or insulin pen), but those are stop gaps and not a strategy to get you to the end of the race, most likely. Knowing those rules, it incentivizes non-optimal decision making of participants to choose to continue for miles (in some cases, could be hours to the next crew-accessible aid station), all the while racking up high blood sugar and low insulin levels that can be really, really, physically unpleasant and further put ultrarunners at risk of physical injury due to the altered state of unnaturally high blood sugar levels.

My guess is these rules are there to limit cheating and a non-fair playing field for those competing for podium. (In some cases, it might be to limit traffic on narrow parts of trail, etc. so for safety reasons, but for the most part the reasons cited seem to be about ‘a fair playing field’.)

But you know what? It’s already an unfair playing field between them and people with diabetes: because those runners without diabetes have a fully functioning insulin production system inbuilt to their body! People with diabetes are already at a disadvantage. Allowing someone to switch to their backup insulin pump outside of an aid station isn’t an unfair advantage or “cheating”, nor does it even “level the playing field” with the other runners.

Instead, the ability to get medical supplies for a chronic disease outside of an aid station reduces medical and physical injury risk to the participant.

Maybe you think I’m being dramatic about the rules of these races and feeling excluded from participating. Because in fact, I do feel excluded. I know things can happen and there’s no point in paying hundreds or thousands of dollars to participate in an event where if I need to switch medical equipment mid-race and outside of an aid station, that I’ll be disqualified and receive an automatic DNF (did not finish) on my race record.

Further, there are other races with even more stringent rules that point blank exclude people with diabetes from participating at all in their races.

Yes, really.

In 2021, UTMB (one of the world’s top ultrarunning race series) announced a new medical policy (based on the Quartz Program) that forbids use of any substance on the WADA (World Anti-Doping Agency) Prohibited List that would require a TUE (therapeutic use exemption) within 7 days prior to competition or during competition.

Guess what’s on the WADA Prohibited List? Insulin.

So if you use insulin and are an athlete in another sport, you get a TUE approved and you’re allowed to participate in your sport despite using insulin for insulin-requiring diabetes.

But as a person with diabetes, you’re banned from participating in UTMB’s races! People with insulin-requiring diabetes can’t go 7 days prior to an event without insulin, nor can we go the entire race (hello, 105 miles takes a long time) without insulin. So this means we cannot participate.

This is dumb and outright exclusionary. There’s other people with healthcare conditions who are now outright banned from participating in UTMB races, too. The same exclusionary ‘health’ “program” has also been used by the Golden Trail Running Series.

This makes ultrarunning exclusionary for people with most chronic illnesses.

Think I’m being dramatic again? Check out this quote from an interview with the organizer of the health ‘program’ that UTMB used to generate this list of requirements:

“Whether the athlete is under the influence of drugs or sick, our role consists of protecting them and therefore stop them from starting the race.”

They outright say they’re trying to stop athletes from starting the race, under the guise of policing what is healthy and safe for trail and ultrarunning. It doesn’t allow for individual evaluation.

Point blank: I’m excluded, and so are many other people with chronic illnesses, despite the fact that we are likely in better health than many other prospective participants of the race, regardless of chronic illness.

Personally, I think having a chronic illness, as hard as it makes ultrarunning, makes me better prepared and a better ultrarunner: I am very experienced with listening to my body and adjusting to challenging situations and dealing with physical and medical adversity. I do ultramarathons in part because they are hard and challenging. They’re hard and challenging for everyone! That’s why so few (relatively speaking) people run ultramarathons. If it was easy, everyone would have done it.

But no one should be prevented from entering a race because of living with a chronic illness.

If you’re willing to put in the training and cover the miles and plan what you need to do in order to achieve this with your medical devices and life-critical medications? You should do so. You should not be discouraged from taking the best possible care of your body before, during, and after an ultramarathon. That is what these policies do at best: at worst they exclude you outright from entering the race.

Race directors and race organizers, your ultramarathon policies are exclusionary. You should fix them.

Fellow ultrarunners, I encourage you to ask race directors to update their policies, too.

How?

Take a leaf out of Tunnel Hill 100’s book. They say (bold emphasis mine):

“USATF SPECIAL NOTICE: No American, or World Record, including age group records, will be recognized for any athlete who:

1) receives aid outside of a designated Aid Station area, OR

2) uses a pacer who is not entered in the race. These rules fall under the “unfair advantage” rules.

NOTE: Don’t worry about these rules if you aren’t going to set any records other than your own personal records.

This is how it should be done: make it clear what rules apply to elite/pro runners (aka podium/top 10/whatever places get rank or $$$) and which ones do NOT apply to the rest of us.

Don’t make people with chronic diseases pay yet another time tax to have to contact the race director and (in the US) ask for an accommodation under the Americans with Disabilities Act. Or point out, if declined, that it’s illegal to exclude people with disabilities (which includes people with most chronic diseases). We do enough work and already pay a lot of “time tax” for acquiring health supplies and managing our chronic diseases; don’t put MORE hoops in front of us to be able to participate and run.

That’s not equitable, nor fun, and it’s yet another barrier to keep more people out of running these races and events.

Functional Self-Tracking is The Only Self-Tracking I Do

“I could never do that,” you say.

And I’ve heard it before.

Eating gluten free for the rest of your life, because you were diagnosed with celiac disease? Heard that response (I could never do that) for going on 14 years.

Inject yourself with insulin or fingerstick test your blood glucose 14 times a day? Wear an insulin pump on your body 24/7/365? Wear a CGM on your body 24/7/365?

Yeah, I’ve heard you can’t do that, either. (For 20 years and counting.) Which means I and the other people living with the situations that necessitate these behaviors are…doing this for fun?

We’re not.

More recently, I’ve heard this type of comment come up about tracking what I’m eating, and in particular, tracking what I’m eating when I’m running. I definitely don’t do that for fun.

I have a 20+ year strong history of hating tracking things, actually. When I was diagnosed with type 1 diabetes, I was given a physical log book and asked to write down my blood glucose numbers.

“Why?” I asked. They’re stored in the meter.

The answer was because supposedly the medical team was going to review them.

And they did.

And it was useless.

“Why were you high on February 22, 2003?”

Whether we were asking this question in March of 2003 or January of 2023 (almost 20 years later), the answer would be the same: I have no idea.

BG data, by itself, is like a single data point for a pilot. It’s useless without the contextual stream of data as well as other metrics (in the diabetes case, things like what was eaten, what activity happened, what my schedule was before this point, and all insulin dosed potentially in the last 12-24h).

So you wouldn’t be surprised to find out that I stopped tracking. I didn’t stop testing my blood glucose levels – in fact, I tested upwards of 14 times a day when I was in high school, because the real-time information was helpful. Retrospectively? Nope.

I didn’t start “tracking” things again (for diabetes) until late 2013, when we realized that I could get my CGM data off the device and into the laptop beside my bed, dragging the CGM data into a CSV file in Dropbox and sending it to the cloud so an app called “Pushover” would make a louder and different alarm on my phone to wake me up to overnight hypoglycemia. The only reason I added any manual “tracking” to this system was because we realized we could create an algorithm to USE the information I gave it (about what I was eating and the insulin I was taking) combined with the real-time CGM data to usefully predict glucose levels in the future. Predictions meant we could make *predictive* alarms, instead of solely having *reactive* alarms, which is what the status quo in diabetes has been for decades.

So sure, I started tracking what I was eating and dosing, but not really. I was hitting buttons to enter this information into the system because it was useful, again, in real time. I didn’t bother doing much with the data retrospectively. I did occasional do things like reflect on my changes in sensitivity after I got the norovirus, for example, but again this was mostly looking in awe at how the real-time functionality of autosensitivity, an algorithm feature we designed to adjust to real-time changes in sensitivity to insulin, dealt throughout the course of being sick.

At the beginning of 2020, my life changed. Not because of the pandemic (although also because of that), but because I began to have serious, very bothersome GI symptoms that dragged on throughout 2020 and 2021. I’ve written here about my experiences in eventually self-diagnosing (and confirming) that I have exocrine pancreatic insufficiency, and began taking pancreatic enzyme replacement therapy in January 2022.

What I haven’t yet done, though, is explain all my failed attempts at tracking things in 2020 and 2021. Or, not failed attempts, but where I started and stopped and why those tracking attempts weren’t useful.

Once I realized I had GI symptoms that weren’t going away, I tried writing down everything I ate. I tried writing in a list on my phone in spring of 2020. I couldn’t see any patterns. So I stopped.

A few months later, in summer of 2020, I tried again, this time using a digital spreadsheet so I could enter data from my phone or my computer. Again, after a few days, I still couldn’t see any patterns. So I stopped.

I made a third attempt to try to look at ingredients, rather than categories of food or individual food items. I came up with a short list of potential contenders, but repeated testing of consuming those ingredients didn’t do me any good. I stopped, again.

When I first went to the GI doctor in fall of 2020, one of the questions he asked was whether there was any pattern between my symptoms and what I was eating. “No,” I breathed out in a frustrated sigh. “I can’t find any patterns in what I’m eating and the symptoms.”

So we didn’t go down that rabbit hole.

At the start of 2021, though, I was sick and tired (of being sick and tired with GI symptoms for going on a year) and tried again. I decided that some of my “worst” symptoms happened after I consumed onions, so I tried removing obvious sources of onion from my diet. That evolved to onion and garlic, but I realized almost everything I ate also had onion powder or garlic powder, so I tried avoiding those. It helped, some. That then led me to research more, learn about the categorization of FODMAPs, and try a low-FODMAP diet in mid/fall 2021. That helped some.

Then I found out I actually had exocrine pancreatic insufficiency and it all made sense: what my symptoms were, why they were happening, and why the numerous previous tracking attempts were not successful.

You wouldn’t think I’d start tracking again, but I did. Although this time, finally, was different.

When I realized I had EPI, I learned that my body was no longer producing enough digestive enzymes to help my body digest fat, protein, and carbs. Because I’m a person with type 1 diabetes and have been correlating my insulin doses to my carbohydrate consumption for 20+ years, it seemed logical to me to track the amount of fat and protein in what I was eating, track my enzyme (PERT) dosing, and see if there were any correlations that indicated my doses needed to be more or less.

My spreadsheet involved recording the outcome of the previous day’s symptoms, and I had a section for entering multiple things that I ate throughout the day and the number of enzymes. I wrote a short description of my meal (“butter chicken” or “frozen pizza” or “chicken nuggets and veggies”), the estimate of fat and protein counts for the meal, and the number of enzymes I took for that meal. I had columns on the left that added up the total amount of fat and protein for the day, and the total number of enzymes.

It became very apparent to me – within two days – that the dose of the enzymes relative to the quantity of fat and protein I was eating mattered. I used this information to titrate (adjust) my enzyme dose and better match the enzymes to the amount of fat or protein I was eating. It was successful.

I kept writing down what I was eating, though.

In part, because it became a quick reference library to find the “counts” of a previous meal that I was duplicating, without having to re-do the burdensome math of adding up all the ingredients and counting them out for a typical portion size.

It also helped me see that within the first month, I was definitely improving, but not all the way – in terms of fully reducing and eliminating all of my symptoms. So I continued to use it to titrate my enzyme doses.

Then it helped me carefully work my way through re-adding food items and ingredients that I had been avoiding (like onions, apples, and pears) and proving to my brain that those were the result of enzyme insufficiency, not food intolerances. Once I had a working system for determining how to dose enzymes, it became a lot easier to see when I had slight symptoms from slightly getting my dosing wrong or majorly mis-estimating the fat and protein in what I was eating.

It provided me with a feedback loop that doesn’t really exist in EPI and GI conditions, and it was a daily, informative, real-time feedback loop.

As I reached the end of my first year of dosing with PERT, though, I was still using my spreadsheet. It surprised me, actually. Did I need to be using it? Not all the time. But the biggest reason I kept using it relates to how I often eat. I often look at an ‘entree’ for protein and then ‘build’ the rest of my meal around that, to help make sure I’m getting enough protein to fuel my ultrarunning endeavors. So I pick my entree/main thing I’m eating and put it in my spreadsheet under the fat and protein columns (=17 g of fat, =20 g of protein), for example, then decide what I’m going to eat to go with it. Say I add a bag of cheddar popcorn, so that becomes (=17+9 g of fat) and (=20+2 g of protein), and when I hit enter, those cells now tell me it’s 26 g of fat and 22 g of protein for the meal, which tells my brain (and I also tell the spreadsheet) that I’ll take 1 PERT pill for that. So I use the spreadsheet functionally to “build” what I’m eating and calculate the total grams of protein and fat; which helps me ‘calculate’ how much PERT to take (based on my previous titration efforts I know I can do up to 30g of fat and protein each in one PERT pill of the size of my prescription)

Example in my spreadsheet showing a meal and the in-progress data entry of entering the formula to add up two meal items' worth of fat and protein

Essentially, this has become a real-time calculator to add up the numbers every time I eat. Sure, I could do this in my head, but I’m usually multitasking and deciding what I want to eat and writing it down, doing something else, doing yet something else, then going to make my food and eat it. This helps me remember, between the time I decided – sometimes minutes, sometimes hours in advance of when I start eating and need to actually take the enzymes – what the counts are and what the PERT dosing needs to be.

I have done some neat retrospective analysis, of course – last year I had estimated that I took thousands of PERT pills (more on that here). I was able to do that not because it’s “fun” to track every pill that I swallow, but because I had, as a result of functional self-tracking of what I was eating to determine my PERT dosing for everything I ate, had a record of 99% of the enzyme pills that I took last year.

I do have some things that I’m no longer entering in my spreadsheet, which is why it’s only 99% of what I eat. There are some things like a quick snack where I grab it and the OTC enzymes to match without thought, and swallow the pills and eat the snack and don’t write it down. That maybe happens once a week. Generally, though, if I’m eating multiple things (like for a meal), then it’s incredibly useful in that moment to use my spreadsheet to add up all the counts to get my dosing right. If I don’t do that, my dosing is often off, and even a little bit “off” can cause uncomfortable and annoying symptoms the rest of the day, overnight, and into the next morning.

So, I have quite the incentive to use this spreadsheet to make sure that I get my dosing right. It’s functional: not for the perceived “fun” of writing things down.

It’s the same thing that happens when I run long runs. I need to fuel my runs, and fuel (food) means enzymes. Figuring out how many enzymes to dose as I’m running 6, 9, or 25 hours into a run gets increasingly harder. I found that what works for me is having a pre-built list of the fuel options; and a spreadsheet where I quickly on my phone open it and tap a drop down list to mark what I’m eating, and it pulls in the counts from the library and tells me how many enzymes to take for that fuel (which I’ve already pre-calculated).

It’s useful in real-time for helping me dose the right amount of enzymes for the fuel that I need and am taking every 30 minutes throughout my run. It’s also useful for helping me stay on top of my goal amounts of calories and sodium to make sure I’m fueling enough of the right things (for running in general), which is something that can be hard to do the longer I run. (More about this method and a template for anyone who wants to track similarly here.)

The TL;DR point of this is: I don’t track things for fun. I track things if and when they’re functionally useful, and primarily that is in real-time medical decision making.

These methods may not make sense to you, and don’t have to.

It may not be a method that works for you, or you may not have the situation that I’m in (T1D, Graves, celiac, and EPI – fun!) that necessitates these, or you may not have the goals that I have (ultrarunning). That’s ok!

But don’t say that you “couldn’t” do something. You ‘couldn’t’ track what you consumed when you ran or you ‘couldn’t’ write down what you were eating or you ‘couldn’t’ take that many pills or you ‘couldn’t’ inject insulin or…

You could, if you needed to, and if you decided it was the way that you could and would be able to achieve your goals.

Looking Back Through 2022 (What You May Have Missed)

I ended up writing a post last year recapping 2021, in part because I felt like I did hardly anything – which wasn’t true. In part, that was based on my body having a number of things going on that I didn’t know at the time. I figured those out in 2022 which made 2022 hard and also provided me with a sense of accomplishment as I tackled some of these new challenges.

For 2022, I have a very different feeling looking back on the entire year, which makes me so happy because it was night and day (different) compared to this time last year.

One major example? Exocrine Pancreatic Insufficiency.

I started taking enzymes (pancreatic enzyme replacement therapy, known as PERT) in early January. And they clearly worked, hooray!

I quickly realized that like insulin, PERT dosing needed to be based on the contents of my meals. I figured out how to effectively titrate for each meal and within a month or two was reliably dosing effectively with everything I was eating and drinking. And, I was writing and sharing my knowledge with others – you can see many of the posts I wrote collected at DIYPS.org/EPI.

I also designed and built an open source web calculator to help others figure out their ratios of lipase and fat and protease and protein to help them improve their dosing.

I even published a peer-reviewed journal article about EPI – submitted within 4 months of confirming that I had it! You can read that paper here with an analysis of glucose data from both before and after starting PERT. It’s a really neat example that I hope will pave the way for answering many questions we all have about how particular medications possibly affect glucose levels (instead of simply being warned that they “may cause hypoglycemia or hyperglycemia” which is vague and unhelpful.)

I also had my eyes opened to having another chronic disease that has very, very expensive medication with no generic medication option available (and OTCs may or may not work well). Here’s some of the math I did on the cost of living with EPI and diabetes (and celiac and Graves) for a year, in case you missed it.

Another other challenge+success was running (again), but with a 6 week forced break (ha) because I massively broke a toe in July 2022.

That was physically painful and frustrating for delaying my ultramarathon training.

I had been successfully figuring out how to run and fuel with enzymes for EPI; I even built a DIY macronutrient tracker and shared a template so others can use it. I ran a 50k with a river crossing in early June and was on track to target my 100 mile run in early fall.

However with the broken toe, I took the time off needed and carefully built back up, put a lot of planning into it, and made my attempt in late October instead.

I succeeded in running ~82 miles in ~25 hours, all in one go!

I am immensely proud of that run for so many reasons, some of which are general pride at the accomplishment and others are specific, including:

  • Doing something I didn’t think I could do which is running all day and all night without stopping
  • Doing this as a solo or “DIY” self-organized ultra
  • Eating every 30 minutes like clockwork, consuming enzymes (more than 92 pills!), which means 50 snacks consumed. No GI issues, either, which is remarkable even for an ultrarunner without EPI!
  • Generally figuring out all the plans and logistics needed to be able to handle such a run, especially when dealing with type 1 diabetes, celiac, EPI, and Graves
  • Not causing any injuries, and in fact recovering remarkably fast which shows how effective my training and ‘race’ strategy were.

On top of this all, I achieved my biggest-ever running year, with more than 1,333 miles run this year. This is 300+ more than my previous best from last year which was the first time I crossed 1,000 miles in a year.

Professionally, I did quite a lot of miscellaneous writing, research, and other activities.

I spent a lot of time doing research. I also peer reviewed more than 24 papers for academic journals. I was asked to join an editorial board for a journal. I served on 2 grant review committees/programs.

I also wrote a lot.

*by ton, I mean way more than the past couple of years combined. Some of that has been due to getting some energy back once I’ve fixed missing enzyme and mis-adjusted hormone levels in my body! I’m up to 40+ blog posts this year.

And personally, the punches felt like they kept coming, because this year we also found out that I have Graves’ disease, taking my chronic disease count up to 4. Argh. (T1D, celiac, EPI, and now Graves’, for those curious about my list.)

My experience with Graves’ has included symptoms of subclinical hyperthyroidism (although my T3 and T4 are in range), and I have chosen to try thyroid medication in order to manage the really bothersome Graves’-related eye symptoms. That’s been an ongoing process and the symptoms of this have been up and down a number of times as I went on medication, reduced medication levels, etc.

What I’ve learned from my experience with both EPI and Graves’ in the same year is that there are some huge gaps in medical knowledge around how these things actually work and how to use real-world data (whether patient-recorded data or wearable-tracked data) to help with diagnosis, treatment (including medication titration), etc. So the upside to this is I have quite a few new projects and articles coming to fruition to help tackle some of the gaps that I fell into or spotted this year.

And that’s why I’m feeling optimistic, and like I accomplished quite a bit more in 2022 than in 2021. Some of it is the satisfaction of knowing the core two reasons why the previous year felt so physically bad; hopefully no more unsolved mysteries or additional chronic diseases will pop up in the next few years. Yet some of it is also the satisfaction of solving problems and creating solutions that I’m uniquely poised, due to my past experiences and skillsets, to solve. That feels good, and it feels good as always to get to channel my experiences and expertise to try to create solutions with words or code or research to help other people.

There IS Something You Can Do For Diabetes Month

I have a favor to ask of you, especially you as a person who is not living with diabetes.

On day 1 of diabetes awareness month 2022 (also known as today), I saw a tweet. Someone posted a picture of some snacks and asked what people thought it was.

Like clockwork, one of the replies was “Diabetes”.

The original tweet’s author replied with a laughing emoji.

I saw it, sighed, and clicked away.

Then I clicked back to it. And typed: Diabetes “jokes” aren’t funny.

Later, I checked and the author deleted their laughing emoji tweet. The original “Diabetes” tweet still stands.

I’ve lived with type 1 diabetes now for more than 20 years.

It’s not because of what I ate as a kid. It has nothing to do with what I ate before or what I eat now.

Most cases of diabetes, in fact, are not the direct result of individual behavior (such as what we choose to eat), and result from a complicated combination of genetics, immune system shenanigans, and numerous factors outside of people’s control (such as the environment in which they live). Diet changes can sometimes delay the onset of type 2 diabetes, but diet is never the sole cause of it, and usually not even the dominant factor.

Diabetes is no one’s fault, just like getting cancer is no one’s fault.

But unlike cancer or asthma or numerous other life-altering chronic diseases, diabetes is a punchline in society.

It’s treated as something you can judge and shame other people for. It was 20 years ago and it is today.

Literally, today.

Probably hundreds if not thousands of times, people are out there making diabetes jokes.

So here’s where the favor comes in that I’d like you to do for me, especially those of you reading this who don’t have diabetes, when you see someone making a diabetes “joke”.

Speak up. Say something. Anything. Don’t look away.

Say, “please stop” or “Diabetes “jokes” aren’t funny” or “Why are you stigmatizing people?”

Because these are in fact stigmatizing comments. It impacts us in ways you can’t imagine, from our day to day lives (people trying to restrict our food or tell us what we can eat) all the way to the fact that these pervasive, stigmatizing attitudes are so internalized, even by healthcare professionals, that they actively cause harm when we seek healthcare in the healthcare system.

So please, say something. Advocate for and with us. Be our allies. Speak up, and give us a break. We don’t get a break from diabetes. We sometimes get burnt out from advocating for ourselves and keeping ourselves alive. That is a lot of work, as is advocating. But it would be great if we got a break from the “jokes” that aren’t jokes.

That’s something you can do for diabetes awareness month, and every month, that will make a meaningful difference for people living with all types of diabetes.

(Thanks.)


(PS – For what it’s worth, those snacks being tweeted about were actually for running an ultramarathon, which takes a lot of snacks. And people with diabetes, like me, can eat snacks and run an 82 mile ultramarathon.)

Speak up. Say something. Don't look away. These are things you can do for diabetes awareness month.

What It Feels Like To Run 100 Miles Or Similar Long Ultramarathons

Sometime in the last year, I decided I wanted to run 100 miles. In part, because I wanted to tackle the complex challenge and problem-solving that is even figuring out how to do it.

My situation as an ultrarunner is slightly atypical: I have type 1 diabetes and need to closely manage insulin levels and glucose levels while running; I have celiac disease so I can only eat 100% gluten free things; and I have exocrine pancreatic insufficiency (EPI) so I need to swallow enzymes with everything that I eat, including when I run. It’s a logistical cornucopia of challenges…which is in part why I wanted to do it. It wouldn’t be half as rewarding if it were easy? Or something like that.

But mainly, I wanted to prove to myself that I can do hard things, even things that most people think I can’t do. No, I can’t produce my own insulin, but I can locomote for 100 miles at one time despite this and the other challenges I have to deal with along the way.

Plus, there’s the “normal” ultrarunning challenges of fueling, hydrating, managing electrolytes, keeping your feet from becoming a ball of blisters, etc.

Ultrarunning is a sport where it generally doesn’t matter how fast you go, and the farther the distance the more of an equalizer it is. I’m a slow runner, and I had trained at an easy slow pace that I planned to run during my race (self-organized). Not having the pressure of time cutoffs would help. I was also curious whether running so slow at the start would possibly help me maintain a more even pace split across the entire run, and whether I could ultimately achieve a reasonable time by keeping consistent slow paces, compared to many I’ve read about who go a bit too fast at the start and end up with wildly different paces at the end. Everyone hurts running an ultra no matter how much you run or walk or both and no matter how fast or slow you go, but I was hoping that more consistent pacing and effort would minimize how terrible everything felt if I could pull that off.

Background

I trained, ran a 50k in June, and resumed training and worked back up to 24 mile long runs and all was going well, until I massively broke a toe and had 6 weeks off. Then I resumed training and re-built back up to running 29 miles, ending around midnight for night-run training. At that point, I had one more long run scheduled (32-ish miles), but decided I would rather skip the last long run and push my 100 mile run up a few weeks to try to beat the impending rainy season that Seattle would eventually get.

The joke was on me. We had 6+ weeks of terrible air quality, which peaked into a two-day stretch of downright “hazardous” (ugh) air quality the two days before my run. Air quality was finally improving overnight before and the morning of my run, thanks in part to the most rain we had gotten in 128 days. Woohoo! So I got to add some wet and cold running challenges to my list of problem-solving that I’d tackle during my run.

Overall, though, my training had gone well, and I had spent enough time planning and prepping that I felt relatively confident. Mostly, confident that no matter how well or long I trained, it was going to hurt. All over. For what felt like forever, and then I still wouldn’t be anywhere near done. And confident that I had planned and prepped to the best of my ability, and that I could figure out how to tackle whatever situations I faced as they came.

How I felt before the race

Aside from having cabin fever from being inside (AQI was too hazardous to go out even with a mask), I felt fairly good in terms of running fitness. I had been tapering, my legs felt fresh, I was fueling and hydrating and everything felt fine. Unfortunately, though, while I managed to escape many taper niggles, I experienced a round of ovulation pain that I don’t get every month but was lucky enough to get this month, for the 3 days prior to my race. (I’m not sure why, but in the last few years after never experiencing ovulation pain, I have started to get ovulation pain similar to period pain and cramps and general icky feelings. My doctor isn’t concerned about it, but it’s unfun, and in this case poorly timed.) So I was a bit grumpy about going into my race in a less-than-perfect state, even though “perfect” state is an ideal and usually there is something wrong, whether it’s a taper niggle or something else.

The thing I was most pleased about was my feet. My broken toe had healed well and hadn’t been giving me any issues. However, after I broke my toe it changed my foot strike or how my feet move in my shoes in a way that caused epic blisters and then I kept getting blisters on top of blisters for several runs. I finally figured out that I needed to try something different, stopped causing new blisters, and the existing blisters healed, peeled off, and went away. So my feet were in great shape, and despite being nervous about the effect of the rain on my feet during my 100 miles, I at least was starting from a “clean slate” with healthy, non-blistered feet.

The start

I set my alarm and woke up and checked air quality. The winds and the start of the rain had blown it absolutely clear, so I was able to head out without a mask for the first time in weeks! (Last time I ran with it for all 8 hours of my long run, which is annoying when you need to fuel every 30 min.)

I wasn’t even a mile in when I had my first problem. I started with a long sleeve shirt and my rain jacket, knowing I’d warm up and want to take it off soon after I started. As I removed my arms from my rain jacket (keeping it zipped around my waist) and shuffled my arms in and out of my running vest, I suddenly felt water hit my feet and looked down. Water was gushing out of my hydration hose! I grabbed it and stuck my finger over the end: the bite valve had flown off somehow while I was getting out of my jacket. Ugh.

Luckily, though, this is where all of my planning and reading of others’ experiences had come in handy. While this had never happened to me, I had read in someone’s blog that this had happened and it took them 20 minutes to find the valve. I had a bright waistlamp and it was getting increasingly lighter outside as the sun rose, so I hoped mine would be easier to spot. I figured it was stuck in my rain jacket sleeve so I worked to check my sleeve and vest for the valve. No go. I looked around and didn’t see it. I turned and walked back a bit, looking for it on and off the trail. No luck. I finally pulled out my phone and called Scott, while still holding my finger over the hydration hose to keep it from leaking out 3 liters of water. While I talked to him and told him I probably needed him to get dressed and bike out a replacement valved to me, I turned around and walked forward again one more time. Aha! Found it. It had flown way to the left side of the trail. I replaced it and breathed a sigh of relief. It had added only 4 minutes to my first mile time.

Well, I thought: that’s one way to keep my early paces slow! I hung up with Scott, and carried on.

The first lap I was very focused on making sure my socks and shoes were in good shape. I am pretty good at gutting it out if I have blisters or foot issues, but that’s not a good strategy when you’re going to cover 99 more miles. So 6 miles into my first lap, I stopped at a bench, took my socks off, and re-lubricated my feet. Later on the way back (this first lap was an out-and-back), I stopped at mile 16 and similarly sat on a rock to re-lubricate and add lamb’s wool to reduce rubbing on the side of my foot.

A picture of Dana Lewis running down the rainy paved trail, with resupply gear (dry shoes, water, fuel) in the foreground of the picture. She's wearing shorts, a rain jacket, and a rain hat. She is smiling and around 12 miles into her eventual 82 mile run).

Yet overall, lap 1 went well. It started raining after about 20 minutes so I ran with my rain hat and rain jacket on (I put it on after my bite valve escapades at mile 1), and intermittently put my hood over my hat and took it off when the rain picked up or lessened, respectively. But it pretty much rained the whole time. Scott met me as planned after my turnaround spot (about 12 miles in) and refilled my hydration pack and I re-packed my vest with snacks, enzymes, and electrolytes and carried on.

At the end of lap 1 (almost 24 miles), I physically felt pretty decent. I had been working to focus on the lap I was in and what I needed to do for the next lap. Nothing else. No thoughts of how many miles I would run or hours it would take. My watch had stopped itself in the rain and canceled the run (argh), so I wasn’t going to have a running total of time throughout the entire run like I wanted. But this might have been a feature, as it kept me from using my watch for that and I set a new lap/run each time I headed out so I could keep an eye on the segment pace, even though I had no idea what the overall pace time really was.

A paved trail picture taken from on the trail. Trees and a river are to the left; more trees line the trail to the right. It is very cloudy, the trail is visibly wet.I went slow the first lap (part of why I was feeling so strong), and I took my time in between laps. I pulled off my socks and shoes. I used hand sanitizer on them to draw some of the water out, then re-lubricated and added Desitin (to continue to help draw water out of my feet and aid in preventing blisters). Then I put on a fresh pair of toe socks and added more lamb’s wool in between key toes that typically are blister-prone. At this stage I had no blisters, and other than wet soggy feet was in good shape! Sitting for 10 minutes for my sock and foot care change chilled me, though, and I was happy to start moving again and warm back up.

The middle

I headed out on lap 2, which similarly went well. This was my “triangle” shaped loop/lap. The only issue I had this lap was that it was the only section of my route where the trail crossed 3 small intersections. Two had lights but one did not. At the intersection without a light, there were no cars so I continued running across the pedestrian crossing. As I stepped out I saw a car whipping around the corner with their head turned looking for cars in the opposite direction. Not sure if they would turn in time to see me, I slammed on my physical brakes. They did turn and see me and stopped in plenty of time, so I continued across the crossing and on the trail. However, that had tweaked my right ankle and it felt sore and weak. Argh. It felt better after a few more minutes, but it intermittently (once every hour or so) would feel weak and sore throughout the rest of my run as a result.

After lap 2, I again sat to remove my socks and shoes, dry my feet, put hand sanitizer on them, re-lubricate, etc. My feet were definitely wet and wrinkly, so I added even more Desitin to my feet. It wasn’t raining super hard but it was a constant hard drizzle that was soaking through to my socks and feet even though there weren’t many puddles (yet). This time, though, I used some reusable hot packs while I sat to change shoes, so I wasn’t as chilled when I left.

Lap 3 (back to an out-and-back route) also went well, and I was starting to realize that I was in surprisingly good physical shape. My feet were intermittently a little bit sore from pounding the ground for hours, but they weren’t constantly annoying like I’ve had on some training runs. I had long surpassed my longest running distance (previously 32 miles; at the end of lap 3 I would reach 52 miles) and longest ever running time. I did develop one or two small blisters, but they didn’t bother me. Usually, I build up huge blisters and they’re a constant annoyance. During my race, maybe thanks to the Desitin etc, I only noticed the blisters (which were fairly tiny) when they popped themselves. I had one on each foot pop and sting for a minute and then not bother me again, which was pleasant! Lap 3 was also when it got dark, so I’d headed out with my double waist lamp. I have two sets of two waist lamps that we strapped to each other; I turn one on and run it out (somewhere around ~3 hours) and then turn the belt around and turn the other lamp on. This lasts me the longest laps I have, even if I was going at walking speed. It’s plenty of light for the paved trail even on the darkest nights, but because it was raining it was cloudy and the city’s light pollution reflected off the clouds so that trail itself was easy to see! So while I only saw a few stars at the end of the night in between patches of cloud, for most of the night the night-running aspects were pretty easy. Dana sits on a bench at a picnic table in a public park. It is dark. She is wearing long rain pants, a rain jacket, and a rain hat and is bent over her bare feet, applying lubrication. It is dark and nighttime, so she has an extra waistlamp on the table illuminating her feet. Other ultrarunning supplies are strewn across the table.

Interestingly regarding my feet, after lap 3 they were still white and wrinkly a bit, but they were definitely drying out. They were much drier than they had been after lap 2, so the combination of hand sanitizer and Desitin was working. I was pleased, and again slathered with more lubricant and Desitin before putting on fresh socks and heading back out for lap 4, which would be a repeat of my “triangle” lap.

Physically, I was mostly ok. My feet weren’t hurting. I had expected my IT bands to get tight and bother my right knee and for my hips and back to start getting sore: my left knee did intermittently hurt some, but it was like a 3/10 annoyance and came and went. Stretching my hip flexors didn’t change the tightness of my IT band, but it was also the least amount of knee pain I’ve ever had when things got tight, so it was very manageable and I didn’t stress about it. It was hard to believe that with the completion of this lap (lap 4) that I’d have finished a 100k (62 miles) and added a few miles to it!

It seemed like the triangle loop wanted to keep things interesting, though. On Lap 4, after I had turned off into the section that has the intersections and the “triangle” part of the loop, my hydration hose made a gurgling noise. I felt the back of my hydration pack, which was rock solid with ice…but no water left. Oops, I thought. I was at mile 6 out of 13. If I kept going forward on my route, it would take me an estimated 4+ miles to get back to the next water fountain. Or I could call and wake up Scott, who had just fallen asleep for his first 2 hour nap overnight (it was around 1am by now), to bring me water, but that would take him 20-30 minutes before reaching me.

It mattered that I didn’t have water. Not just in terms of thirst and hydration, but I also needed water to be able to swallow my electrolyte pills (every 45 minutes) and my fuel (every 30 minutes when I ate a snack) and the digestive enzymes I absolutely require to digest my food since I have EPI. I definitely needed water so that my hydration, fueling, electrolytes, etc. wouldn’t suffer.

I could go back, but I hated to backtrack. It would be a mile back to the previous water fountain, although I wasn’t even sure it would be turned on and working. Mentally, though, I groaned at the thought of “turning around” and finishing the loop in reverse and trying to figure out how many miles I would cut off that loop and how many I’d have to added to my very last loop to make up for it.

Luckily, I realized a better idea. Because I was on the section of the triangle running alongside a road (hence the annoying intersection crossings), the intersections are where the road turned off into various parking lots. Across the road at one of the two intersections with lights was a gas station! I could see it glowing from a quarter of a mile away. I crossed my fingers hoping it would still be open, because I could go inside and buy a bottle of water to hold me over. It was open! I crossed the intersection and went in, grabbed a liter of water, bought it, went outside, and refilled my hydration bladder under the bright lights of the gas station.

A 1-liter wattle bottle held in a hand covered with a blue nitrile gloves.
I’m wearing nitrile gloves to help keep my hands drier and warmer given the cold, endless rain.

I was pretty proud of that solution, especially because it was ~1am and I had been running for 17 hours and was able to troubleshoot and solve that problem on the fly! Without sending it, I also drafted a text to send to Scott near the end of that loop when he’d be awake, to list out which foods and gear I wanted at the next refuel, and to specify what happened and how I solved it and request that I get more water and less ice for the next loop.

(Running out of water was on my list of things I planned for in all of my preparation, so while I had low expectations of my mental capacity as the miles piled up, that likely helped because I had mentally listed out where all the available water fountains were, so I could run my loop mentally forward and backward to figure out where the closest one was. In this case it was a mile behind me; going forward it would have been 4+ miles or more than an hour away. The gas station ended up being 15 minutes from where I realized I was out of water).

Finishing lap 4 was exciting, because I only had 3 laps left to go! I had one more out and back loop, and my father-in-law was driving down in the wee hours of the morning to run part of it with me to keep me company. We hadn’t planned on that all along, but he and Scott had been texting and working it out, so Scott just told me that was the plan and I was thrilled. I was a little bit tired overall, but more energetic than I thought.

The sock change before lap 5 was disappointing, though. After lap 3, my feet had been drying out a little bit. Now after lap 4 they were wet and soft again, like they were after lap 2. The rain had been more constant. I took the time (15-20 min) I needed to dry and treat them with hand sanitizer, lubricant, Desitin, replace fresh toe socks and lambs wool and dry shoes. They weren’t hurting, so I was hoping the light rain would taper off and my feet would dry out again.

The (beginning of the) end

I headed out on to lap 5, buoyed by the thought that I only had ~4 miles ‘til I had company. The rain picked up again (argh) and as my father-in-law met me on the trail with his headlamp and rain gear, he asked if it had been raining this much the whole time. No, I said, and pointed out that it had only been raining hard in 10-20 minute chunks and this one had been going since before I met him so it should lighten up soon. He commented on how energetic and chatty I was. “You’re pretty chatty,” he said, “for 5am!” (I am well-known in both our families for NOT being a morning person). I joked about how impressive it was for me being this chatty not only at 5am but also for it being 22 hours into my run!

Unfortunately, 3 miles into the section he ran with me, it went from annoying hard drizzle to an epic mega downpour. My shoes went from damp from constant hard drizzle to super soaked from top all the way down to the insoles squishing with every step. I was frustrated, because this much rain was also making it hard to use my phone. My phone had an alarm going off every 30 minutes to remind me to fuel; I needed to pull out my phone each time and turn off the very loud alarm (it was effective!) and then open up my spreadsheet and enter what I ate and what electrolytes I took. Then I also had to pull the baggie out of my vest pocket, select out the number of enzyme pills I needed with wet and cold gloved fingers, re-seal the baggie and put it back in my vest, and get out the fuel from the other pocket of my vest and eat it. Even tired, I was managing to fuel successfully and stay on top of my schedule. I was increasingly proud of this.

But the rain and the inability to use my phone when I wanted to was starting to irritate me, in part likely because I was trying not to stress about what the volume of water was doing to my feet. They weren’t actively hurting, but I knew this much water for this long of time could be dangerous and I needed to be careful. It was still downpouring when we reached the turnaround and headed back to his car. I dropped him off at his car and carried on. I was tired, soaked, cold, but physically in great shape otherwise in terms of legs, knees, hips, back etc all holding up and not feeling like i had run ~78+ miles at that point!

I had just eaten another snack and went to press buttons on my pump to give myself some insulin for the snack. It didn’t seem to work. I have a vibration pattern so I can use the pump without seeing it; but the “enter” button was not working. I had been concerned about the volume of water my pump was going to be exposed to and mentally prepared for that, but it was SO disheartening to suddenly feel the pattern of 6+ vibrations followed by an audio beep indicating an error state had been reached on the pump. I cursed to myself, out in the rain after 24 hours of running, knowing what I would find when I pulled my pump out from under my jacket. Sure enough, “button error”, because water had gotten under the buttons and to protect itself, the pump went into a “I won’t do anything” state. That meant that the insulin I needed for my latest snack wasn’t going to happen and any future insulin wasn’t going to happen.

I pulled out my phone and started a text to Scott, explaining that I had a button error and needed him to pull out my backup pump. I told him where it was, told him to put in a new battery and program it with the basal rate that I wanted. I then sent a text saying it was raining a lot and it would be easier if he called me if he needed to talk, because it was so hard to use my phone in the rain. He read the text so I knew he was awake, so I called him and talked to him while I trudged on and he was getting dressed and packing up my replacement pump and the gear I needed for lap 6. Then we hung up and I carried on, grumbling along the way and starting to feel the physical effects of not having enough insulin for the past hour or so.

A picture of a glucose graph from a CGM. The dots are flat in the first hour of the screenshot, then slowly and almost exactly lineary head up and to the right.

My blood glucose levels were rising, but I wasn’t worried about that. I knew once I had replacement insulin my blood sugars would come down nicely. I had prepared for this; there was a “high BG” baggie with supplies ready to go! But the combination of the 25+ hours of rain, the extra hard rain and cold temps from the last several hours, my feet starting to be bothered from the wet soaking, and then on top of it all the chemical feeling of not having insulin going in my body: it was a lot. I really focused on the physical state I was in, evaluating what I wanted to do. I knew that I could fix the cold state (switch to dry clothes; use hot packs) and my blood sugars (new replacement pump, take some inhalable insulin for a faster fix while the new pump insulin would be kicking in within an hour and fixed from there). But my feet were starting to bother me in a way that I wasn’t sure could be fixed with a 20 minute sock change.

Scott biked up to me right as I passed my favorite trail bathroom, the stalwart of my ultra, and had me turn around and head in there to be out of the rain. It was clean, big, had toilet paper, and was well lit and had the door open (wasn’t locked) all night long. I stepped inside the bathroom while Scott parked his bike by the building and whipped out the baggie with the replacement pump. I checked that no one else was in the women’s bathroom and he stepped inside, and impressively (to me) pulled out the baggie that held a garbage bag. I had packed it so I could more easily change clothes in public bathrooms by standing on it and placing my clothes on it so they wouldn’t be on the ground. He instead laid the garbage bag on top of the garbage can lid and set out my dry clothes, helped me out of my wet soaked rain jacket, hat, and shirts, and handed me my dry shirts followed by some hot packs. He gave me a giant one and told me to stuff it down my shirt, which I did. I took some inhalable insulin (which hits in about 15 minutes), then held the smaller hot packs in my hands while he was pulling out the bag with my replacement pump. I rewound and primed the pump with my existing reservoir and tubing, then reconnected it to my pump site and primed it. That problem (lack of insulin) was now solved, and I knew that my blood glucose would come back down to target over the next hour.

Next up, I could walk/run (or walk) the remaining 1.5 miles back to my normal turn around point, which was a table under a park awning that was relatively dry. I knew that I needed to be warmer and stay dry, and although I had dry clothes on now, I wasn’t sure that sitting outside even with hot packs while I tried to address my feet would warm me up. I told Scott that I wanted to go back to the house (thinking I’d walk the ~1.5 miles to the house). Then I could dry out my feet, get warm, and go back out if I wanted to continue. But I had a hunch I didn’t want to continue. My feet were feeling like they were getting to be in a not-good state from the level of water they had retained after 25 hours, despite all the excellent foot care.

I thought about it and realized that I was satisfied with running 82 miles. I was in otherwise decent physical shape and energy, I had been nailing my electrolytes and fueling and blood sugars the entire run. I had successfully run overnight; more than 24 hours; and by far (2.6x) the longest distance I had ever run. I could keep running to 100 miles (about 18 more miles), but no one cared if I did. I didn’t have to prove anything to anyone, including myself. I had planned, strategized, and executed above and beyond what I had thought was possible, both in terms of physical and mental performance. I had no major injuries, and I wanted to keep it that way. I knew I had the willpower and persistence to keep going; I was stubborn enough to do it; but as the last bit of icing on top of my ultramarathon cake, I wanted to have the mental strength to decide to stop where I was so I wouldn’t create a long-lasting injury in the last 18 miles from sheer stubbornness.

So I stopped. I told Scott I would decide for sure after I got home and dried off and warmed up, but that I was pretty sure this would be a stop and not just a pause. Rather than let me walk home in the rain, he insisted I stay in the warm dry bathroom while he biked home and got the car and brought it to the nearest trail entrance, which was about a quarter of a mile away (more good planning on my part!). Once he had gotten in the car and called me, I slowly walked out to meet him at the parking lot, reaching it right as he pulled in. The walk on my feet confirmed to me that they were done. They weren’t exceptionally blistered or injured, but I knew the cumulative water effect and soggy skin would likely lead to some damage if I continued on them. We headed home. I sat down and took off my socks and shoes and sure enough, my feet were wet, white, and very wrinkly and starting to crease. I took a hot shower then dried off, put hand sanitizer on my feet to help dry them out, and laid down with them sticking out of the covers to help them air out. Within a few hours, they had dried out, and showed me some blisters on the bottom of my right foot that were not really bad, but if I had kept going on them, the wet wrinkly tissue would’ve been very prone to more extreme damage. I reflected on the choice to stop and was still happy with my decision.

The 24 hours after I ran 82 miles

After my shower and laying down, I realized that I was (still) in great physical shape. Some parts of me were starting to stiffen up now that I had stopped, but they hadn’t bothered me at all during running. That was my hips that now hurt if I tried to lay on my side but not on my front or my back; and my thighs felt sore when I straightened and bent my legs. I had never even been tempted during my run to take pain meds because I was never overly sore and didn’t have any injuries.

(Note: you shouldn’t take NSAIDs during extreme events due to the risks of overworked kidneys having problems. I had packed Tylenol, which is acetaminophen, in case I needed it for pain management, but specifically did not pack any oral NSAIDs and warned Scott about offering me any. I did pack topical NSAID *gel* which is an extremely low quantity of NSAID compared to even one oral NSAID pill, and I used that once on my shoulder blades during the run. After my run, I waited several hours and made sure my kidneys were fine via hydration before I took any NSAID.)

It is very surprising to me that despite my longest training runs being almost a third of the distance I did, that I ended up in better physical shape at the end than I did during some training runs! This is probably in part due to going even slower (as planned) during my ultra, but I was really pleased. It might have also been due to the fact that I mentally trained for it to hurt really bad and to continue anyway. Again, lots of mental training and prep.

I ended up napping 2 hours after I got home and showered, and then was awake a few more hours and took another one hour nap. I ate several small meals throughout the day and stayed in bed to rest and not stress my feet further, then went to sleep at a normal bedtime and managed to sleep 9.5 hours through the night. Woohoo! I really wasn’t expecting that. I did wake up many times and find myself bending and flexing my knees or my ankles to help me roll over and could feel them being sore, but it wasn’t painful enough to fully wake me up or keep me from falling back to asleep within seconds, so it felt like a fully rested un-broken night of sleep.

The bottoms of my feet felt weird as they dried out, but progressively felt better and felt close to normal (normal meaning as normal as you are with a routine blister on the bottom of your forefoot) by the time I woke up the next morning (24 hours after ending my run). Everything that stiffened up in the first few hours after I stop has been gradually loosening up, so other than my forefeet still being sensitive with blisters, I’m walking around normally again.

The good, the bad, the ugly, and what I wish I had done differently

I had prepared for so much to go wrong, both those things in my control and things out of my control. And I think that’s why it actually didn’t hurt as much or go as wrong as it could have, despite all the variables in play. I nailed my pacing plan, energy levels, hydration levels, fueling intake, electrolyte intake, and enzyme intake.

I had estimated that I would need to take up to ~160 enzymes to cover my fueling. Remember that I stopped at ~25 hours (82 miles) instead of ~32 hours (100 miles) so I took less than that, but still a lot.

I consumed 50 (fifty!!!) snacks, one every 30 minutes, and swallowed multiple enzyme pills each time. I consumed at least 98 enzyme pills (!!!) in this 25 hour time period. I was concerned that my body wouldn’t be able to digest the pills or have some other issue with them, because I have never taken anywhere near this number of pills in a single day. But, it worked, and flawlessly: I had ZERO EPI-related issues and ZERO other gastrointestinal (GI) symptoms. GI symptoms are super common in ultras, even for people without things like EPI, so I’m incredibly thrilled with how well my planning and practicing paid off so I could execute my fueling plan and not have any issues.

My goal had been to take in ~250 calories per hour and ~500 mg of sodium per hour (from both the snacks every 30 min and electrolyte pills every 45 min). I use calories as my rolling metric because while most ultrarunners prioritize carbs, I’m running slower and likely more fat adapted than most people, and also need digestive enzymes no matter what I’m eating so taking small amounts of fat and protein are fine for me. Plus it makes for more interesting running snacks. So using calories as the global running metric of consumption rather than just carbs or fat etc. works for me. I nailed it, and across all 25 hours of my run I averaged 671 mg of sodium per hour and 279 calories per hour. I did have one hour where I somehow dropped low on sodium and felt it, and took an extra electrolyte pill to help catch up. It fixed the “low on sodium” feeling and I didn’t have any issues again. I had slightly more variability toward the end of the run, but that’s just due to the timing of when I logged it into my spreadsheet (due to the wet-phone issues I described earlier) and the auto-calculation on which hour it falls into; overall I still was maintaining the goal levels every hour.

A graph of calorie consumption, sodium consumption, and carb consumption per hour for all 25 hours of the 82 mile run.

(The purple dotted line is carbs, because I was curious about how that level fluctuated given that I didn’t prioritize my run snacks based on carbs at all. I generally seek <20 grams of carbs per snack but have a few that are closer to 30 grams; otherwise <10 or so grams of fat and however many grams of protein I don’t care).

How do I have all this data? I used my macronutrient spreadsheet as I went, selecting the snack I was going to eat from the drop-down list that then pre-populated the rest of the data in the sheet and updated a pivot table that summarized my rolling totals per hour. It was getting increasingly hard to use my phone in the mega downpour rain in the last few hours, which is why the timing of logging them was a little variable and the numbers look a little more bouncy each hour toward the end, but my consumption was still on time thanks to my every 30 minute phone alarms and so the logging was the only thing that varied and I was still above-goal overall although trending downward slightly.

This spreadsheet means I can also summarize my total consumption across 25 hours: I consumed an eye-popping 817 grams of carbs; 365 grams of fat; 136 grams of protein; 16,775 mg of sodium; and 6,979 total calories. That matched the 98+ enzyme pills (and 33 electrolyte pills, which are 210 mg of sodium each and reflected in the overall sodium counts), so I also swallowed >131 pills in the 25 hour time period running. Wow.

It’s common to end up in a calorie deficit due to the hours and miles that an ultra demand of your body, but my watch estimates I burned around 8,000+ calories (maybe an undercount since it stopped itself a few times), so I didn’t have as big of a deficit as I had originally predicted.

There were so many (50!) opportunities to mess up my digestion, and I didn’t mess up once. I’m really proud of that! I also had such a variety of snack types and textures that even though I was never really hungry, I ate my snacks like clock work and didn’t get major palate fatigue or get to the point that I wanted to stop chewing and needed to switch to my backup list of liquid fuel. The only time I slightly felt off was when I did a Snickers for one snack at the end of my lap and then my next snack was hot mashed potatoes – combined, that was 390 calories (one of my top two hours of calorie consumption) and felt like a little too much food, either because of the calories or the volume of mashed potatoes. It was only a minor annoyance, though, and the feeling passed within another 15 minutes and I didn’t have issues with any other combination of snacks. I did get tired of peanut butter pretzel nuggets, because they’re drier than many of my other snacks and took a lot of water to swallow. So I stopped choosing those in lieu of my other snacks and left those as emergency backups.

Looking back, I wish I could have done something differently about my feet, but I don’t think there’s anything else I could have done. I changed socks and into dry shoes at every single lap. I dried them and tried to draw out water with hand sanitizer and Desitin. I lubricated with Squirrel Nut Butter and Desitin, and overall came out with very few blisters compared to my typical shorter long runs (e.g. 25-30 miles). But we did get 0.72 inches of rain in that 24 hour period, and a lot of it was dumped onto my feet in the 4-7am time period. If I’d had a way of knowing 24 hours in advance exactly when the rain was going to let up with enough confidence to delay the run for a day, it turns out it would’ve been drier, but the forecast before I started running was for similar chances of rain all weekend. The laws of feet physics and the timing was just not good, and that was out of my control. I’ll keep researching other strategies for wet feet management, but I think I had done everything I could, did it well, and it just was what it was.

Overall, I can’t think of anything else I would have changed (other than my training, it would have been swell not to have broken my toe and been not weight bearing for 6 weeks!). Fueling, electrolytes, enzymes, blood sugars, pacing, mental game: flawless. I was even picking up the pace and still running and walking 30:90 second intervals, and I think I would have continued to pick up the pace and pushed it to the finish, estimating that I would have come in under 32 hours overall for 100 miles (around a 19 min/mi average pace overall, or a bit under that).

But I chose to stop at 82 miles, and being willing to do that was a huge mental PR, too.

So I’m pleased, proud, and thrilled to have run an 82 mile ultramarathon, and physically and mentally feel better than I would have predicted would be possible after 24 hours.

What it feels like to run (almost) a 100 mile ultramarathon, by Dana M. Lewis on DIYPS.org

How I Organized Supplies For a 100 Mile Ultramarathon Run

One of the things I read trying to learn about best approaches for running 100 miles (an ultramarathon) is that it’s mostly mental and logistical challenges rather than physical, because after a certain point everyone is running much farther than they’ve ever trained and what makes the difference is how well you deal with the mental and logistical challenges and problem solving when you reach those points. I took that to heart and did a lot of pre-planning for my 100 mile run attempt. You can read more about the other types of prep and decision making that went into this, but the below is a more tactical “here’s how I organized” the different things I had been thinking about for months.

Route Planning and Pace Chart

First, you either need to plan your route (self-organized) or get the course map (organized race). This enables you to start to build out a pace chart. I did this first, because it then informed fueling strategy, planning, etc.

I laid out my route (7 laps, which later turned into 8 planned laps based on re-designing my routes). I had a column for the distance of each lap/segment, then a total distance column. This was mostly to make sure I had my distance add up to > 100 miles; otherwise I don’t care about the rolling distance total. I then built out a pace sheet with what I thought my paces would be. I’m very slow and run/walk, and planned to go as slow as possible at the start to be able to finish the entire distance. So while normally my running might be 14:00-15:30 min/mile pacing, I expected to want to start around 16:00-16:30 min/mi pace and that I’d likely slow over time. As a result, I started my pace chart with a 16min/mi pace and did a 17, 18, 19, 20, and 21 min/mi pace chart for each of my segments. This enabled me to estimate the time it would take to run each lap (segment) at each given pace, and also a clock time that I would be expected to roughly finish that lap.

Example of a 100 mile pace chart, with rows for each segment/lap run and then columns estimating a different minute per mile pace and how that changed the total segment time and clock time for each lap.

I also created a dynamic pacing chart that I could use to simulate different paces throughout my run. This enabled me to estimate what happens if I start fast and slow down a little or a lot and how that influences my overall time and pacing. During my run, my husband as crew updated the actual time to help estimate what my next segment time would be based on both the last segment time and overall pace. This helped him determine when he needed to set an alarm to come back out and meet me, as well as remind him where he was meeting me each time based on the route.

You’ll notice I’ve highlighted to make sure I remember to change the date when I cross over midnight, to make sure the pace chart updates accurately.

(Again, note these are simulated/fake times. The dark shading suggests when it’ll be dark, due to the time of year I’m running.)

Example of a dynamic pacing chart with the ability to enter the date and time I completed each segment or lap, and the right columns updated the segment pace and the overall run pace based on this input.

Fuel, Enzyme, and Electrolyte Estimates

These pace charts were useful for then estimating what I’d need when. Namely, how much fuel I’d need to prepare in bags for my husband to give me for each lap. I used the slower paces for each segment and my plan of fueling every 30 min to determine how much I needed. For example, if I’m fueling every 30 minutes, my second segment is 13.06 miles and I’d probably be running around or below a 17 min/mi pace at that point, which means it’ll be 3.7 hours or so. This is 7 snacks (one every 30 minutes, and I’ll be back before the next snack time for my refill). But, if I run slower, I want to round up slightly and add a snack to that estimate, so I put in 8 needed for that lap. I did that for all laps, rounding to the next hour and/or adding 1 to the estimate.

I also estimated my electrolytes similarly. I drink water and get my sodium and electrolytes via a combination of my fuel and electrolyte pills, with taking electrolyte pills every 45 minutes. Again, I used the slower pace times and the segment time to determine how many electrolyte pills I needed for the segment and listed those out.

Then, you’ll notice I also estimated “enzyme” needs. I have exocrine pancreatic insufficiency, known as EPI, which means I have to swallow enzymes anytime I eat anything to help my body digest it. Fun, right? Especially when I’m eating every 30 minutes across a 100 mile run and how many enzymes I need to take depends on what I’m eating! I typically take two (one each of two types) over the counter enzymes for a snack; although some bigger snacks I can take 2-3. Therefore, I estimated one per snack plus a few snacks where I’d take the 2-3, and also factored in dropping a few (it happens). It adds up to ~118 enzymes but again, that’s a lot of extra added in so I don’t have to worry about running out if I drop some or eat bigger snacks.  I calculated I’d probably end up consuming closer to ~80 of each type (so 160-ish total) across the 100 miles.

Another chart with the lap segment numbers and in columns to the right, estimates for the number of snacks, enzyme pills, and electrolyte pills for each segment. Totals of each type (snack, electrolyte, enzyme pills) are at the bottom of the chart.

Deciding What I Want to Eat, When

Next, I took these snack per segment estimates and decided what I actually wanted to eat. Based on my training, I ruled out some foods and perfected my list of what I wanted to eat and had practiced.

I listed all my preferred snacks down a column, then listed out the laps/segments in the row at the top. I then started playing around with what I wanted to eat at different times. Knowing I’d probably get tired of chewing crunchy things (for me it’s not the chewing but the texture of the harder things in my mouth), I put things like my chili cheese Fritos and peanut butter pretzel nuggets toward the first few laps. Later laps got easier to chew/swallow items like peanut butter M&M, fruit snacks, etc.

At the bottom you’ll notice I have a few different columns. A lot of the snacks indicated with numbers are ones that are shelf-stable and pre-packed. Others are snacks that are at home in the fridge or freezer or require prep (like mashed potatoes). I have a variety of quantities of those prepared (see right side of table) so I can choose any combination of 2 of those for my husband to bring out each lap, in addition to the pre-packed shelf-stable snacks. The bottom combinations make sure I have enough snacks between the pre-packed snacks and 2 fresh snacks every time, based on the above chart I had made to estimate how many snacks I needed for each segment.

A chart listing snack types in a row on the left; then the headers of the columns to the right list each lap number. Down the chart are numbers representing that snack and how many for each lap. A section at the bottom totals up the pre-packaged snacks per lap, as well as a row indicating that two extra home/hot snacks will be added, to estimate the total number of snacks I'll have for each segment or lap.

The other reason this chart is helpful is that I know how many extras of everything I have at home, too. So while I have certain amounts prepped and packed per column Z; column AA notes the extras I have pre-packaged and sitting at home, so if I get tired in lap 3 of beef sticks and want to not eat those, I can figure out what other 4 snacks I want that I have prepped and have my husband bring those alternatives.

One other note for nutrition and macronutrients: I use a macronutrient fueling tracking spreadsheet to help me track my calorie intake as well as sodium intake, to make sure I’m getting enough on a rolling basis. It also helps me figure out how many enzymes to take for each snack, if I don’t know it off hand or my brain forgets (as it might after running for 20+ hours!). You can read more about how I built and use this fueling spreadsheet here.

Planning Supplies

Over the last few months and especially the last training runs, I built a list/library of likely common issues I experienced or had learned about by reading other people’s race recaps and reports that I wanted to be prepared for. I organized it by type of problem, then listed potential supplies and solutions. For example, I had a blisters/feet section; low sodium; high or low blood glucose (because I have type 1 diabetes); etc.

The solutions list here is unique to me/how I solve things, but here’s an example of what I would include:

  • Sodium
    • More electrolyte pills more frequently than 45 min
    • Short term fix: Chicken broth (¼ is 530mg sodium. Entire thing is 2120mg)
    • Less sodium but variety: GZero (no carb) gatorade sips – whole bottle 270mg

I then also started a separate document for 100M Prep. This included a long checklist of all the items I had brainstormed as solutions – so in the above sodium example, it included extra electrolyte pills; chicken broth; Gatorade Zero; etc.

A screenshot of my 100 mile prep document showing the sodium section with chicken broth, electrolyte pills, and gatorade zero checked off the list, as I had already packed them.

This became helpful for me to a) make sure I had these things at home and to get them if I didn’t have them yet and b) to make sure I had set them out/organized them prior to my run so they’d be easily accessible for my husband to find.

The 100M Prep document also helped me break down larger tasks, too. Instead of “blister kit”, I started a sub-list that described everything I wanted in that baggie.

A contact case with a strip of purple painter tape that has "vaseline" written on it in sharpie; and three lip gloss tubes filled and marked with "NSAID", "salt", and "desitin".

This also helped me realize when I needed to add a task for splitting supplies. For example, if I had a big tube of cream or ointment that I possibly wanted to be in two places (such as a certain type of foot lubricant). I had previously bought a bag of empty lip gloss tubes for making travel size toiletries (shampoo, face wash, etc.). I realized that they also worked great for liquid, gel, cream supplies for ultra running, too. And so I added tasks for splitting those into smaller tubes once I decided and listed where they should go and thus how many I needed.

I also had a checklist for each lap bag, which is a combination of which snacks (planned above) and other supplies (like eye drops) that I wanted to have each time. I made a checklist for each lap, then laid out all my supplies and checked them off the list for each lap. Once I had all the supplies laid out, I then compiled them into one bag for each lap and added a label. This way my husband has one bag to bring for each lap, and there is a sticky note on top of each bag that has anything else (e.g. 2 fresh food items from home) he needs to add and bring that lap.

Laid out on the floor are baggies with enzymes and electrolyte pills for each lap; snacks surround the baggies. There are also individual pre-pasted toothbrushes and individual eye drop containers.

(Again, this is planned food, electrolytes, and enzymes for each lap. See the above section to see how I estimated the food/snacks, electrolytes, and enzyme needs.)

A gallon bag containing the enzymes, electrolytes, and snacks for each lap of my ultramarathon. Atop the bag is a printed sticky note with reminders of other fresh supplies my husband will bring each time.

I had started a list in a PDF for each lap, then printed the list for each lap on a sticky note so I could easily tape it to the bag and it would be easy for my husband to read.

Editor/Husband/Crew note from Scott: “These pre-prepped lap bags and printed sticky notes turned out to be most useful for making sure I got everything prepped each time. When I got home after each pit stop, I would pull out the next lap bag and make sure I had everything charging/washing/drying that I’d need at the next pit stop. Then when it got close to time to go, I’d work down the checklist, collecting each thing and putting it in my bike’s saddlebags, and then put the lap bag on top when I had everything packed.”

Crew Checklist

The same document as the overall solutions list became my Crew Checklist document. I added a checklist for what we should be doing at each lap. Again, this is unique to me, but it included things like putting my watch on the charger; removing trash from my vest; replacing water and ice in my hydration pack; replacing my battery for charging my phone; putting my fuel/enzymes/electrolytes into my vest and using eye drops; swapping socks; seeing if I need replacement supplies for low blood glucose; and after midnight considering whether I wanted to drink a Diet Mtn Dew for joy and caffeine.

A checklist in a Google Doc listing what my husband should make sure we do in between every lap, such as removed trash, replace water and ice and fuel, and make sure I have enzymes and electrolytes before I head out. It also reminds him to update the pacing spreadsheet with my latest lap time, and links to all spreadsheets he needs.

You’ll also spot the section I added for my husband for after he gets home to remember to charge batteries on various things, use the pacing spreadsheet to help him figure out when to come back out, etc.

At the bottom of my crew document (the lap checklist is at the top, followed by the comprehensive solutions list), I also included an example pep talk section with constructive things to say. If there’s things you don’t want your crew to say (e.g. “you’re almost there!” or “only X hours left” are on my ‘please no’ list), you can also list those out. I also have my list of run-ending situations that my husband and I agreed upon, which includes things like having a broken bone; severe dehydration or peeing blood; hypothermia; etc.

And finally in the document at the very bottom, I created a checklist for post-race care so when I get home and everything feels terrible and I don’t know what to do, my husband has my pre-thought-of checklist of things in the best order (shower then compression sleeves; making sure I eat something within an hour of finishing; etc) to help me do all the self-care things I’m probably going to forget about.

Editor/Husband/Crew note from Scott: “Peace-time plans are of no particular value, but peace-time planning is indispensable” and “No plan of operations extends with any certainty beyond the first encounter with the main enemy forces.”

– This particular document ended most useful for pre-race planning purposes, including our night-before review of all the plans. I glanced at it a couple times during the race, but mostly relied on the lap-bag checklist and the physical presence of items in my saddlebags at the pit stops.

DanaWatch

The other thing I had prepared was a document with instructions for friends who had agreed to help out during the overnight hours for me. My husband was “on call” and crewing the whole time, but overnight there were sections where I was out running 3-4 hours and he needed those times to sleep. For those hours, we set up “DanaWatch” (as I call it), with a friend who will text me every half hour or so to check on me. If they don’t get a text back (a simple emoji or other text from my watch), they were to call me, and if they couldn’t reach me, they’d call Scott. So, the document has these instructions, an outline of my safety plan, Scott’s number, etc. so everyone knows what the plan is. I had friends staggered over different times. For example, a friend in the UK was to text me starting around 8am his time, which is midnight for me. When another friend wakes up on the east coast (three hours ahead of me), she’d starting texting me, and so on. This way I wouldn’t feel “alone” and would have extra folks watching out to make sure I’m still on track.

I think that’s everything I did to prep in advance! Mainly, having those documents built to add ideas to (especially problems and troubleshooting solutions) and building out my pace chart so I could progressively make my fuel, electrolyte, enzyme and supply plans in advance was really helpful. Then I blocked off time the week before my run to make sure I had everything prepped and ready to go well before the day before my race, so I wasn’t stressed about getting ready. As I described in my other preparation for ultra post, anything I could do to limit stress and mitigate decision-making fatigue, I did. And it definitely helped!

How I Organized Supplies for a 100 mile (or similarly long) ultramarathon

How To Prepare Or Plan For A 100 Mile Ultramarathon (Or Similarly Long Ultra Run)

As I prepared for months for my first-ever 100 mile run, I did a lot of research to figure out how I should be prepared. There’s no one way to “prepare” for an ultramarathon of any distance, and much of the stuff online is about your training plan and physical preparations. Which is definitely important, but not the only thing that needs preparation.

After a lot of reading, thinking about my own plans and preparation, I’ve realized there are 4 general types of preparation for an ultramarathon that I’ve been doing: mental preparation and training; nutrition preparation and training; race day strategy preparation; and the actual physical training and running to prepare for an ultramarathon.

Usually, blog posts either cover the last category (training plans and physical training philosophies) or one of the other categories. This blog post summarizes everything I’ve done in all of these categories together in one place – in part to help me if I ever run another ultra following my first 100 mile attempt!

Almost everything I thought about and planned for a 100 mile ultramarathon, by Dana M. Lewis on DIYPS.org
  1. Mental preparation and training

It’s commonly said online that running 100 miles (or most ultra distances) is 80% mental and only 20% physical. (Or similar splits like 90/10). This is in part because it is not feasible to physically train to run the distance prior to your race (usually); and the first time you tackle a new distance, you always have many (often dozens!) of miles of distance that you’ve never covered before. It’s going to be uncomfortable, and you have to plan for that. Thus, mental preparation and training as much as possible to be prepared to deal with these challenges.

The first major aspect of this, for me, is practicing and reminding my brain how to process and work through discomfort. Discomfort is distinct from pain and being injured. (Pain and an injury should include evaluating whether you should cease your activity.) I’ve fortunately (and unfortunately) had recent experiences of pain when I broke my toe. Returning to walking and then running involved some discomfort as my body got used to covering miles again. It was a very distinct feeling that was not easily confused with pain from a broken bone, which to me feels like an “electrical” type of feeling.

This recent experience with pain is easy to differentiate from the discomfort of running long distances and being tired and sore. I’m working to capture these thoughts when I have them, and transition from “I’m tired and this hurts and this is terrible” during training runs and convert these thought patterns to “I’m tired and uncomfortable. But this is not pain; this is discomfort. This is how I’m going to feel at mile 34 or 57 or the back half of my 100M, and I’m going to keep running then and I’m going to keep running now to practice this feeling.” I want to register and save this feeling and mental state for what it’ll feel like during my 100M, so it’s easier to pull that out when I’m exhausted and uncomfortable at 3am and still likely have another 40-50 miles to go.

Similarly, I also try to envision different scenarios that I will experience in my “race” or 100 mile experience. In my case, I plan to run on a paved trail for a solo endeavor (DIY or self-organized, rather than an organized race with other people). Some of the scenarios I am expecting to experience and deal with include:

  • I will be running a course with 7 “laps” or loops of various lengths. This involves me coming back to the same point seven times so that I can get re-fueled by my crew (my husband), change clothes if needed, etc. I envision coming in for my second or third lap, having to turn around to head back out for another (but not my last) lap and not wanting to leave.
    • How I planned to deal with this scenario: I’ve written down crew instructions for my husband, which include how to refuel and replenish my supplies; a list of troubleshooting scenarios and supplies; but also specific things that would be constructive to say to me. In this instance, any of the following:
      • You are strong and you can do this.
      • You only have to do the current lap.
      • Walk as much as you need to.
  • This 100M will be one of the first times (other than a training run where I practice the transition) running all day and into the the night. I’m a little apprehensive about this idea of running for 14 hours in the dark (due to the time of year). Partially, this is because I’ve never run 14 hours before, and I’ll be doing it after already having run for 10 or so hours! And because I’m not as experienced running in the dark.
    • How I planned to deal with this scenario: I have a clear set of “day to night” transition supplies and instructions to gear up for the night. I will be equipped with reflective components on my vest; a bright colored shirt; a waist lamp; a head lamp; a blinky red light on the back of my vest. I will focus on getting geared up and recognizing that it’s a mental transition as well as a physical gear transition. I will also try to think about the novelty and adventure aspects of running through the night. It’ll probably be wet and cloudy – but it might clear up in patches enough to see some stars! And – the running through the night is something I didn’t think I could do, which is actually why I’m doing a 100M, to prove to myself that I can do anything I want to set my mind to. This is the purpose of being out here, and it’s a necessary part of achieving 100M.
  • At some point, most people do a lot of walking. I’m fairly unique in my “running” approach – I run/walk from the start, and also not like many people run/walk. In ultras, most folks walk every X minutes or when they reach hills. I consistently run/walk with 30s of running, then 60s or 90s of walking – from the very start. These are short intervals, but it’s what works well for me. But like everyone else, regardless of initial strategy, I expect there will be a time where it might be more efficient to try a brisk, consistent walk for a few minutes (or miles!), or a slow slog (inefficient walk) because that’s all I can convince myself to do.
    • How I planned to deal with this scenario: The goal is forward motion, however I can move. Walking is ok, and expected – and I will remind myself of that. I know there is a crossover point when running speed slows down to a certain degree and running becomes as efficient at a certain point. I also know these points, speeds, and effort levels will change throughout my 100M. It helps that I’m already a proactive walker; I have no shame, guilt, or hangups related to walking because it’s ½ or ⅔ of my forward motion strategy from the start! But I will remind myself that my plans for intervals can change and I can experiment to see what feels good throughout.
  • It’s possible that I could trip and fall, especially as I get tired and scuffle my feet on the trail, even though I’m on the paved trail. I also might get swooped by an owl or startled by something which causes me to trip and fall unexpectedly.
    • How I planned to deal with this scenario: I’ve got my safety plan in place (more on that below) and know I will first while on the ground disable the alarm on my watch so it does not call 911 (assuming this doesn’t appear to be needed). I will move my body to see if I’m just sore or if there are any scrapes or injuries that need addressing. I will stand up if possible, continuing to check myself out. I will slowly walk, if possible, and see how I feel. I’ll also probably call and let my husband know, and either ask him to come meet me earlier than expected that lap or just let him know so he can check on me when we meet up as planned. I will let myself walk any soreness off for a while (and turn off my interval alerts) before resuming a planned run/walk strategy.

So these are some of the scenarios I’m envisioning dealing with and my plans for them, with the hope and expectation that my brain will be better equipped to deal with them as a result of thinking about them in advance.

Depending on your race/route/plans, you might need to add other types of scenarios – such as leaving the aid station with warmth and light before heading into the night; or what to do if your crew doesn’t show up as planned; or your drop bag gets soaked with water; or the aid station is out of supplies or there is no one where you expect an aid station.

The other part of my mental preparation is a lot of pre-problem solving. Similar to the above scenarios, I have thought through what I need to do for the following:

  • I drop my fuel, enzymes, or electrolytes and can’t find them.
    • How I planned to deal with this scenario: I will call or text my husband and adjust plans for where he meets me. I will use the backup fuel supplies in my pack as needed to tide me over. (For my race, I have fuel in individual baggies and separated out for each “lap” or segment, plus extras and backups, so my husband can grab the backup bag or the next lap bag and bring it to me.)
  • I run out of water.
    • How I planned to deal with this scenario: There are 3-4 water fountains along or nearby my planned run route, and I can re-fill my hydration bladder within ~3 miles from any spot on the trail. I can also again call my husband and have him meet me sooner to re-fill my hydration pack.
  • My stomach gets upset.
    • How I planned to deal with this scenario: I have supplies (such as Immodium, GasX, Tums, etc) in my running pack that I can use. I also have more supplies laid out at home that I can ask my husband to bring.
  • I don’t feel like eating.
    • How I planned to deal with this scenario: I included this on the list because I read that it happens to a lot of people. But, as a person with type 1 diabetes…I have 20 years of practice of consuming sugar or food when my blood sugar is dropping or low, even when I’m not hungry. I have also practiced consistently fueling throughout my long runs, and I am used to eating when not hungry. I expect it is more likely that I will get tired of certain textures, so I have planned out my fuel so that “harder to chew” or crunchy foods that might hurt my mouth are the snacks I eat earlier, and then eat softer snacks or snacks that require less chewing later in the run. I also have a variety of backups that include different textures and some liquid options that I can substitute for my planned fuel.
  • Other scenarios I’ve pre-problem-solved are getting blisters or sore spots on my feet; chafing; getting low on sodium/electrolytes; muscles hurting on other parts of my body other than my feet; having feet that swell; getting itchy or having other types of allergic reactions; having trouble breathing; my eyes hurting; being really tired; being hot or cold or wet; my blood sugar staying higher or lower for a longer period of time; and mentally feeling “low” and unmotivated and wavering in the pursuit of my goal.
    • How I planned to deal with this scenario: As part of the ‘crew instruction’ list I’ve made for my husband, I have listed out all the supplies I have to address these categories. I will also have all of these supplies grouped and set out at home. My husband is awesome at troubleshooting problems in general, but he’ll also be tired at 2 am after only sleeping for 2 hours (plus I will be tired), so I created this to help me prep all the gear but also when I tell him “I’m ____”, he can offer the requisite supplies to address the problem without me having to try to figure out what my options are and decide what to do. All of this is to help mitigate the decision fatigue I will have and the overall fatigue he will have.
    • Note: I’ve also previously read a really good tip about managing decision fatigue. Tell your crew – in my case I’ve told my husband and written it onto the crew sheet – not to ask open-ended question, but to offer specific suggestions or options. For example, say “Do you want 2 or 2.5 liters of water in your hydration pack?” instead of “How much water do you want?”. For refilling my snacks, I’ve told my husband to refill my snack pack from the pre-filled bags, but the bag also has a sticky note about grabbing fresh prepared food. I told him to specifically ask “Do you want your waffle; sweet potato tots; mashed potatoes; or” (whatever is on my list of pre-prepared food for him to make and bring), instead of “What do you want?”

A lot of these I put on my list to think about based on race reports I’ve read from other people, that covers what they experienced (e.g. feet swelling and finding it helpful to have a half size bigger shoe to change into) and how they troubleshot things during the race while in between or at aid stations.

Some of my favorite race reports/blogs that I’ve learned a lot from include Rebecca Walker’s race reports; Wes Plate’s race recaps; Debbie Norman’s race reports (check out her sample crew sheet in that linked post); Bob Hearn’s thoughtfulness around pacing and walk strategy; and Sarah Lavender Smith’s race reports.

I have learned quite a bit and improved my planning and preparation by reading race reports of DNFs and also of finished races of different lengths. The longer the race, the more challenges there are and the more time to learn and sort them out. So that’s why I appreciate reading Wes’s multi day (eg 240 mile) recaps as well as 100 mile race reports, even though my focus has been on 50ks previously and now “just” a 100M.

One other thing I’ve thought about is the importance of knowing what your criteria for quitting/stopping/DNFing. For me this links back to discomfort versus pain. An injury should involve stopping temporarily and maybe permanently. But being tired, sore, uncomfortable – for me those should not qualify as reasons to stop. My goal is not to stop before 100 miles unless I have an actual injury (eg broken toe level pain).

2. Nutrition preparation and training

Yes, it’s worth “training” your nutrition. This means training your body by practicing fueling with the same foods and strategies as you want to use on your race. There’s a mantra of “nothing new on race day” that is both useful and not applicable to ultrarunning. In general, a lot of ultrarunners seem to do well (per my above search through many race reports) with eating small portions of “whatever looks good” at aid stations. If it looks good, their body is probably going to deal with it ok. But not always. And a lot of time people will bring fuel and rely on things they haven’t tested on their long runs prior to race day. Don’t be that person!

  • Test your fueling options and strategy (e.g. timing of fueling) on most runs, not just your very longest runs. For me, I do fuel for any runs of 2 hours or longer, because that correlates with when I bother to bring hydration and therefore also bring fuel. (That’s 8 miles for me at an average 15min/mile pace). Some folks use 1 hour or an hour and a half as their cutoff. But the point is – don’t just test your fuel on 6 hour runs. Fueling on shorter runs helps those runs feel better; you’ll likely recover from those runs more quickly; and it helps your body practice with those fueling options. You don’t want to find out at hour 8 of your 36 hour race that your body doesn’t do well with ___. It’s better to find that out at hour 3 of a 4 hour run, or similar.
  • Create your list of fuel that works for you. This should be based on your preferences but also how it helps you meet your fueling goals. When you have an idea for a new fuel, make sure you take it on your next run and try it. If you’re like me, you might want to try it near the end of your run, just in case your body doesn’t like it while running. If your body doesn’t like it, cross it off your list. You don’t want to be hauling or trying to eat food you know your body doesn’t like during a 100 mile run! I’ve found some things that I like to eat and found tasty fresh out of the oven – like ½ of a GF banana bread muffin – felt terrible in my mouth during runs. Some combination of the dry muffin (vs. freshly moist out of the oven) and the taste was not ideal for me. I ate it, and didn’t have GI distress, but I got home and promptly moved the remaining half portioned muffin baggies to my husband’s section of the fridge/freezer where my snack rejects go, and crossed it off my list. If it doesn’t bring you joy, or if it makes your brain cranky, it’s probably not a food you want for your ultra.
  • Don’t feel like there is a “wrong” food, as long as it’s something that’s not going to spoil easy or melt or be too hard to eat on the go. Look at snacks and meals you like to eat; is there a serving size or a variation that you like to eat? If so, try it! People eat all sorts of things in ultras, from puréed fruits and vegetables like applesauce or baby food pouches, to candy and chips to hamburgers and soup. Walk the store aisles (physically or virtually) and get ideas for food to try. But don’t limit yourself to sports “products” like blocks, gels, gu, drink mix, and similar. You’d be surprised about the variety of food that is portable, and in individual portions is close to the same macronutrients (calories, carbs, fat or protein, sodium, etc) as more expensive sports products. A lot of time you are paying for convenience and a certain texture/delivery method. But you can achieve the same intake of macronutrients through a variety of foods and beverages.
  • Some people stick with 1-2 foods or fuel sources (like liquid calorie/electrolyte solutions or gels/gu/blocks), but get tired of the sweet taste or the taste/texture of what they’re eating. Having a variety can help with this. Make your list, and for each run make sure you’re working through trying out and approving or removing the foods that you want to use during your race. Ideally, try them 1-2 times before your big run.
  • If you can, practice with some of the aid station type food including warm food (eg quesadilla or burger or whatever). Have someone meet you on longest runs with this freshly prepared, or take it with you and eat it for your first fuel. (Watch out for food spoiling/going bad – I always eat the hot/fresh prepared stuff first out of my set of fuel options when I get my pack refueled, to reduce the chance of bacteria growing or the food otherwise spoiling.) This is harder to do and may not be possible, but it could help expand your options for what you’re willing to take at aid stations if you’ve tested a version of a similar food before during a training run.
  • More planning ahead on nutrition for race day and training runs: figure out your timing of nutrition strategy and how many snacks or how much fuel (liquid or otherwise) you need to consume each hour or segment or between aid station. Pre-portion your fuel/snacks and if possible, label them. Plans can change and you can adapt on the fly, but having everything pre-portioned and ready to go means you can more easily start your training runs, fill your drop bags, or prep bags for your crew by having everything portioned out.
  • Planning ahead also means you get to the store or order however much you need so you’re not adding stress the last few days before you race or run in order to have your fuel set up and ready to go.
  • Don’t be afraid to use a timer. Some people wear running GPS watches that have alert/alarm features for fueling. You can use regular phone alarms, too, or apps like “Timer+” or “Intervals Pro” – both are ios apps that have free versions that allow one alarm each. You can choose whether it pushes a notification to your phone or watch or provides a verbal audio alert. I use both these apps and have one alarm that’s verbal audio reminding me to take electrolytes every 45 minutes; and the other one is a push-notification only that helps me remember to fuel roughly every 30 minutes. I generally am checking my watch so it’s easier to remember to fuel every :30 and 1:00 from when I start running, which is why I choose that one to be a push notification just in case. That works for me, but figure out your ideal timing and alert/alarm strategy to help you remember to fuel and electrolyte as you need to.

If anyone is curious about my individual approach to nutrition, I’ve written a bit more about it here, including how and why I actually use a spreadsheet to track nutrition and fueling during ultras and training runs. I separate my hydration (water only) and electrolytes (electrolyte pills; plus tracking the sodium in what I’m eating), so tracking my fueling serves many goals both during a run and after a run when I can look back and see if I need to tweak anything (such as not putting two smaller/lower-calorie, lower-sodium snacks back to back).

Since I’m running my ultra solo/DIY, I’m taking advantage of some fresh/heated fuel options, like mashed potatoes, ¼ of a ham and cheese (gluten-free) quesadilla, etc. For these, I am leaving a pre-printed sticky note on the baggie of shelf-stable fuel with a reminder for my husband to bring 2 of my fresh/hot options each time as well as anything else I need him to bring for that lap. To aid the bringing of the fresh/home food, I made a printed set of instructions that lists what these are, broken down by location (freezer, fridge, or on the counter) and instructions on how to make them. This is a critical step because what he predicts I want or how I want something to be cooked or prepped for a run doesn’t always match what I was wanting or expecting. Having clear instructions he can follow (eg heat ¼ quesadilla in microwave for 30s) works well for both of us and further helps with limiting his decision/processing fatigue since he’ll be responsible for grabbing and making 2 things; getting the lap bag of refuel; packing up ice and water; and getting all that and any other requested supplies out to the trail on time to refuel me as I pass by again.

If you have crew, think similarly about what food you want to have; how they’ll make it and serve it to you; how you’ll consume it at the aid station or as you move along on the trail. All of this planning will pay off.

(Another benefit of my macronutrient/fuel tracking spreadsheet is that my husband has access to it and can check it to see if I’m sticking to my fueling and electrolyte strategy, so he can troubleshoot and recommend things if I need support in fixing a problem. I don’t think he’ll use it much, but this secondary use of the spreadsheet was inspired by one of Heather Hart’s many excellent ultra posts talking about showing her empty fuel wrappers to her crew to prove that she was fueling. In my case, instead of counting wrappers, my husband can check my spreadsheet.)

3. Race day strategy (and pre-race and post-race strategy)

Continuing on the theme of pre-planning and laying out your strategy, I also think about strategy related to race day and leading up to race day as well as after race day.

My goal is to eliminate stress; pre-do as much work as I can physically and mentally to reduce the load when I will be physically and cognitively fatigued and overloaded.

Pre-race

For example, I look at my schedule prior to the race and try to clear out stressful activities (or prevent scheduling them, if possible). I know I’ll need to spend hours physically prepping (per above, making fuel and organizing supplies), so I put that on a to-do list and make a block of time on my calendar for it. I think about tasks that I will have before and after the race, such as changing my continuous glucose monitor (CGM) and pump sites to be in optimal locations on my body for the race; but also changing them early enough prior to the race so that they are settled in and I know they are working well. I also do things like pre-fill my reservoirs with insulin, and do enough reservoirs for a few days before and a week or so after the race. Like during the race, anything I can do to help reduce cognitive fatigue or pre-do steps of tasks that I know I will find harder to do is the goal.

This includes also blocking off my schedule with reminders to go to bed earlier. I think about when I’ll be waking up on race day and the night before, set my bedtime reminder for about 8 hours prior. Then every day before that I set it 15 minutes later, working back about a week and a half. I don’t always hit these sleep times, but progressively slightly shifting my sleep like this has been effective prior to international trips with a lot of time zone changes and also has paid off for getting a better night’s sleep the night or two before a race that involves waking up early.

I also specifically think through all the steps from waking up to starting my race, and how to optimize those. I eat a particular breakfast prior to the race, time it so that I can best get some macronutrients in, and time the insulin so I don’t have much of a BG spike but also then don’t have much insulin activity happening when I start my run. I don’t always get this right, but I attempt to line up my schedule so that I wake up and immediately eat what I have laid out on my bedside table and start hydrating, so that I can sleep as long as possible and don’t have to spend extra minutes convincing myself to get out of bed to go make breakfast. Some of these strategies are unique to me being a person with insulin-requiring (in my case, type 1) diabetes; but it’s pretty common for other ultrarunners to have strategies around what to eat the morning before a race; how many hours prior to the race; etc. I’d suggest you decide based on first principles and your own knowledge what to do for you.

Pro tip/personal vent: most people who blog or write about “avoiding insulin spikes” prior to the race or during the race – if they don’t actually administer exogenous insulin (aka inject or pump it, their pancreas makes it) – they also don’t usually actually know anything about the insulin response to food in their body. They are mostly repeating that from hearing it from others who repeat it from a long chain of people. You are SUPPOSED to spike insulin in response to what you’re eating: that’s good because it manages your blood glucose levels and helps your body process and store what it needs to be storing. It is also very normal for your blood sugar to rise in response to eating. The only people who need to think about “insulin spikes” are people who don’t think about it as insulin “spikes” but as insulin activity or more commonly “insulin on board” (IOB), which are people with insulin-requiring diabetes. This is different for us because we have to inject/pump insulin separately (our pancreases don’t make it on demand in response to sensing food in our bodies) AND because the insulin we use takes longer to act – 45-60 minutes instead of mere minutes – as well as has an hours-long “tail” effect. So it’s a lot of work to match the peak timing of insulin to the impact of different types of food in our bodies as well as watching out for insulin “stacking” over the many-hour activity curve for each dose. Your body, if you don’t have insulin-requiring diabetes? It does this, on its own, like magic. Yay, you! So ignore the stuff about “avoiding insulin spikes” and focus instead on things like whether the food feels heavy in your stomach when you run or gives you GI distress or otherwise doesn’t make you feel good. If it doesn’t, try different food and try different timing.

4. Race start and race strategy

You should definitely have a plan for how you run your race. In my case, because I’m a run/walker, I think about which set of intervals I will start at (likely 30:90, meaning 30s run and 90s walk, because that’s also how I train and helps me achieve my easy effort and easy paces). My goal is to start easy and limit excitement. Since I’m solo running, I don’t get swept up in other people running and racing. But, I always find the start and the first mile to be hard. So my strategy instead is to start, make sure all my intervals and run trackers are turned on; my electrolyte and fuel timers are set; and that I get my audiobook or podcast going. I troubleshoot any of these as needed on the walk intervals as I get going. I specifically try not to think about pace, especially the first half mile, nor how it’s feeling so I don’t catastrophize. I know the first 0.75 miles or so always feels pretty rough, so I aim to do no foreshadowing of how anything else is going to feel.

For most people running organized races, it helps to have studied the course maps and elevation profiles. Learn the course by heart, in terms of knowing how many miles to each aid station and what the elevation profile is like, and what your strategy is for each section. This means having a pace plan from the start and if you are going way too fast (due to excitement and other people around you), switching to walk breaks to help moderate your pace if you can’t slow your run pace down on its own. It also might help to not only have a pace plan but to also put time estimates on aid stations or check points. Use any extra time – especially if you are far ahead – to address any issues popping up (chafing, blisters or hot spots on your feet, etc.). Don’t start foreshadowing and forecasting that you can hold this too-fast pace through the whole race. You likely can’t (physically), and skipping the plan to stop and address issues will also doubly backfire later.

Even though I’m not running an organized race, this is still something I struggle with. I’m setting the goal to stop for bathroom breaks or shoe re-lacing or hotspot fixing in the first out and back “lap”, recognizing that it will help get my average time here to slow down a bit and keep me from powering through it too hard based on initial excitement. My goal is to make sure I don’t skimp on self-support (e.g. foot care or re-applying anti-chafe) by folding that it in to my goal pacing.

In general, though, because I’m running a 7 “lap” course, I focus on each lap. And only that lap. I’m running known out-and-back or triangle shaped “loops” that I know and love, so I can treat the first out-and-back like a long extra-easy run and settle in to watch landmarks while I listen to my audiobook and focus solely on managing effort. When I get back after the first loop and refill my vest, I then can think about the lap that I’m on (13 miles next, a much shorter loop). When I’m back, then I think about the next out and back (about 16 miles). And so on. My goal is to never think about how much time or distance is left. I’m not good at “running the mile I’m in”, as people often advise, but I am fairly good at focusing on a sub-component and the process overall. So focusing on each lap, and knowing there are 7 laps of varying lengths, helps me compartmentalize the experience. I’ll run ¼ of the first out and back in the dark and transition into the daylight; the second lap should also be during the day; then I’ll transition to my night gear for the third lap and be in the dark on the 4th, 5th, and 6th lap. I don’t have aid stations or elevation changes to really break up the course, but since I know the course and all the landmarks well, even with the variable distance “laps”, that aids me in knowing what to watch for and keep moving toward, even if I transition to a walk or get off track pace-wise from problem solving and am trying to re-orient myself again afterward.

It’s good to think about what supplies you’ll carry versus what you will have access to at aid stations, what you have in drop bags, and what your crew will have. I generally carry most of my needed first-aid/don’t feel good supplies on me: anti-chafing, kinesio tape for blisters or muscles, anti-nausea medication, etc. But I have a set of supplies prepped and ready for my husband (who is my crew) to bring to me if needed. I won’t have aid stations, so I think about my planned re-fuel stops as aid stations where he’ll primarily be. If something gets really bad, though, he can bike out to meet me. In some races you may have crew access to the trails wherever you need them; in other races, they are not allowed or able to access you outside designated points. Plan and carry supplies accordingly.

And, plan for your crew how to help you and how you’ll communicate with them. I will have cell service on my run, so I plan to text my husband to give him updates (in addition, he can geo-track my phone’s location) of when I’m on or off the last predicted pace to a refuel stop; what I want him to bring (e.g. the 2 hot/fresh food items, or any extra supplies from my laid-out stash); and how it’s going. We have practiced on training runs for him to grab my vest and refill ice and water, fuel, electrolytes/enzymes/eye drops, then bring it back to me (biking) or when I re-pass him after I’ve turned around and come back to the spot where he is per my course plan. But I also expect him, as crew, to also get tired and mentally fatigued, so I’ve made a checklist that he will use to make sure he completes the steps every lap. There’s also a checklist for day to night transition and night to day transition. This is in the same online document as my expert list of supplies and strategies to troubleshoot every issues, so he doesn’t have to guess what the good options are for fixing blisters or low sodium or whatever the issue may be. He runs, but he doesn’t do ultra runs, and regardless everyone is different in terms of what works for them and especially what works for them at different stages of an ultra; thus, having this crew guide or checklist or supply/strategy “cheatsheet” is a benefit, especially as both he and I get more and more tired through the night.

My strategy also includes making sure my devices stay powered. I always carry a small battery and a charging cord for my phone, and will keep my phone power topped off. This is because I use it for run tracking; geolocation for my crew (husband); fuel/electrolyte reminders; fuel tracking via my spreadsheet; and it is the “receiver” for my CGM so I know what my blood sugars are. Thus, it’s a mission-critical device and I always like to keep it charged. I will also grab a watch charger from my husband after a certain number of laps to top off the charge on my watch 1-2x, based on how it’s battery is doing. He’ll replace the battery in my vest each time after I’ve used it (we’ve got 2-3 small batteries for this purpose so he can take one home and re-charge it while I’m using the other, plus another backup). My phone then also serves as an emergency back-up light if my other two lights fail at night.

Speaking of lights and night gear, have a plan for when and how you’ll transition to night gear. Because I’m running a solo/DIY race and I’m not experienced at running at night (although I’ll do a run or two in training to practice the transition and my gear), I’m actually choosing to start my run at 6am so I run about 1.5-2 hours in the dark at the start of my race. Why? My husband doesn’t believe it’s necessary and is still arguing with me about it, but my strategy is intentional. I want to start the run in my lights and night gear and practice running in the dark again so that I can see if I need to tweak or adjust it for later that night around 6pm when I need to run in the dark again. This gives me one more practice round and mentally will help me – or at least, that’s the goal – know what it’s like to run in the dark. Given that I’ll run in the dark for 14h overnight, I don’t want to pick up my lights and take off and be 6-8 miles down trail from my husband and my backup gear if I realize something isn’t working well. I know I’ll be prone to just sticking it out for the entire lap; this way, I get a mini, 1.5h test of the gear on the same day and that way when I do a 3-5 hour first lap in the dark that evening, it’ll be slightly more likely to go smoothly and I’ll take all the smoothing I can get for my first 100M and my first all night and overnight run!

My other strategy involves self-care in the sense of regular medications that I need. Of course, I’ll be managing my blood sugars and insulin very carefully all day throughout (often thinking about it every 10-15 minutes to make sure everything is on track). But I also take allergy medication twice a day at morning and night, as well as a thyroid medication at night. So I have set reminders on my husband’s calendar to make sure he brings out my bags of night medication (e.g. allergy and thyroid) and in the morning (allergy) medication to make it less likely that I’ll forget to take them. Thankfully if I mess this up and am super delayed or forget to take them, it won’t derail my race/run much, but I definitely will feel not taking my allergy medication within hours so that will also help me remember to take my thyroid evening medication, too.

Another self-care strategy is around keeping my eyes hydrated with eye drops on a regular basis. In October 2021 I started to have really dry, gritty eyes and went to my eye doctor and was diagnosed with…dry, gritty eyes. Helpful! But, sarcasm aside (I love my eye doctor), I got eye gel to use before bedtime and eye drops to use throughout the day. Then in August 2022 I realized I had subclinical hyperthyroidism from Graves’ disease, which is an autoimmune disease (to go with type 1 diabetes, celiac disease, and exocrine pancreatic insufficiency) that causes eye issues. So! My dry gritty eyes were a precursor to my thyroid level changes. At any rate, learning how and when to use eye drops has become routine and I know how helpful it is to keep my eyes lubricated. I use preservative-free eye drops, not because the preservatives bother my eyes but because they come in miniature vials that are very easy to put in your pocket. Supposedly they are designed to be single use, but they usually contain enough lubrication for 2-3 rounds of drops for both eyes. So I twist off the lid, drop in both eyes, put the lid back on, and stuff it back in my pocket. I have set reminders on my calendar during the run to do this every few hours in case I forget, but I have also put vials in each lap bag (along with electrolytes and enzymes) and this presence of new eye drop mini-vials will help remind me (hopefully) to stay on top of eye lubrication.

Keeping my eyes from getting dry will hopefully help me be able to wear my contacts longer, because I usually take them out at night. But, I also will have my husband ready with my contact case and contact solution to take them out; then I will switch to my glasses or run without them (because I don’t need to see far or read signs off in the distance) for some period of hours, while still using the eye drops to keep them happy.

I’m fairly nervous about my eyes being an issue, since I’ve never run this long or all night. This was exacerbated by reading race recaps where folks talked about losing their vision! Yikes! I read a little bit more and realized they’re talking about corneal edema, where there is temporary swelling in the edema that makes your retinas visually look cloudy (if someone else looks at your eye). It usually goes away when people stop running after a few hours or day. But given my eye issues, before I had realized I was dealing with eye stuff related to Graves’ disease and thyroid stuff, I was concerned that my tendency to dry/gritty eyes would make me at higher risk of this, even though it seems like only 1-2% of 100M finishers ever deal with this. But, like everything else, I decided to have a strategy for this. I’ll seek to prevent it with regular lubrication and if it’s cold and windy, using my glasses (in lieu of contacts) or clear biker glasses or sunglasses to help protect my eyes from irritation and drying out further. But if it does happen, I’m using the advice from this post and bought a small vial of 5% hypertonic eye drops to use and try. (I had a regular annual eye doctor appointment a month prior, so I checked with my eye doctor about this. She had never heard of it and consulted a cornea specialist who had also not heard of it, which helps confirm that it’s pretty rare! Although they admitted they don’t get a lot of endurance athletes, looked it up on PubMed like I had, and agreed that if it happens to try the 5% hypertonic eye drops. Note that contact wearers want to take the contacts out before using these drops.) If I start to have vision issues; and I have the clear visual symptoms of this (according to Scott’s assessment of looking at my eyeballs); I’ll try the eye drops and ideally they’ll help. Since this is a known issue, if I still have some vision and can run safely (given my 6 foot wide paved trail in a safe location with no navigation required); I will likely try to continue – again based on discussion and advice with my doctor. But having a plan for this is much better than suddenly having vision issues in the ultra and feeling like I need to abort, when it might be ok to continue running (again on advice from my doctor).

Another strategy is thinking about how I’ll use caffeine. I usually drink caffeine up until noon, then switch to caffeine-free diet soda (and more water) in the afternoon and evening. I’ll drink a diet Mtn Dew when I wake up with my breakfast, but only one, and I will aim not to drink any throughout the day and save them for after midnight, when I’ll have been running for 18+ hours and have spent 6 hours in the dark. That way I have a “pick me up” to look forward to, both in terms of the taste/flavor of diet Mtn Dew, which I love, and some caffeine. There’s some suggestion that weaning off caffeine in the weeks prior to the race would make this a more effective strategy; but for me I think removing the joy of diet Mtn Dew would not be a net benefit. I’m also not convinced that I know what amount of caffeine is needed for an overnight boost, nor that I can test this reliably enough to have a solid evidence-based strategy here. So instead, I’m likely going for the mental boost of the taste change and the placebo effect of thinking the caffeine is helping. I have, however, tested drinking a diet Mtn Dew during a long run in the morning; so I do know that my body is ok taking it in.

This is yet another example of how I’m trying to remove decision-making during the race by pre-planning wherever possible for decisions like when to take caffeine or not; what to eat when; etc. I have laid out pacing sheets for a wide variety of run paces – so wide that the fastest pace (if all goes amazingly well) would have me finishing 8 hours faster than the slowest pace I have charted out. But the reason this matters is because I’m using the slowest time to estimate how much fuel I need to have prepared, then preparing more as backups (see more detail in the nutrition section). I created my overall fuel list then started putting in estimates of how many of each I would be willing to consume, also factoring in palate fatigue and texture fatigue and not wanting to chew or put ‘hard’ things (like Fritos) into my mouth in the later hours of my run. I balanced all of these variables and came up with 6 max servings of my chili cheese Fritos, most of which will be consumed in the earlier hours; 6 max servings of a few other routine things I can eat in most situations, then smaller counts (eg 1-4) of other things like the hot/home food that my husband will bring out in addition to the shelf-stable food. Once I had my overall counts totaling enough fuel for the slowest hour estimate and the number of servings; I then made a lap-by-lap list of what I wanted to eat when. I’m going to prepare these bags with the numbers I need per lap based on the timing (e.g. 10 snacks for the slowest pace estimated for my longest lap in between refuels, of which 8 are shelf stable and 2 will be added based on the sticky note reminder for the fresh/home options). Each of these lap bags will also include the requisite number of electrolyte pills I need, based on similar estimates from my “slow” paces, and the enzymes I need (because I have exocrine pancreatic insufficiency and need these to actually digest the fuel I consume), plus new eye drops. The point of this strategy is to remove decision making for both me and my husband: we don’t need to figure out how many enzymes or electrolytes I have “left” from the last lap (because I am off my fueling plan or more likely because I packed extra for each); instead, he can simply pull out all the trash, old enzyme/electrolyte bags, and replace with the new fuel, electrolyte, and enzymes along with my water/ice refill.

You may not have the complexity of my situation (type 1 diabetes, celiac, exocrine pancreatic insufficiency) influencing your fueling strategy and choices and how you’ll deal with fuel on the run. But, you might want to consider similarly planning your fuel. You may need to adapt your strategy based on how you’re feeling and what options you have in your pack, drop bag, with crew, or at an aid station, but you can plan for options to address issues of fatigue, palate/texture fatigue, etc. That, essentially, is what I have done.

Finally, I also consider a safety strategy part of my important race planning. I wear a watch that will generate an SOS alert and call emergency services if I fall during a run. I have the ability to press and hold a button on my watch or my phone to similarly generate an emergency services call. My location is tracked by my husband (and my mom from afar); and my husband also has access to my CGM for blood glucose tracking. He’ll have extra alerts and alarms set at different thresholds than we typically do for glucose levels. Finally, we’ve also created what I call the “DanaWatch” plan/squad, which is 3 people who will be texting me periodically from midnight to 9am my time, which is the overnight hours when Scott will be intermittently sleeping for 1-2 hour snatches in between refueling me. The plan is for my friend in the UK to text me every half hour and watch for a response that I’ll generate from my watch – probably a simple thumbs up emoji or tapping one of the auto-generated responses like “thanks” or “hi” or “I’m good”. After a few hours, a friend on the east coast will take over. Then my mom in central time zone after she wakes up will start texting. Nothing fancy, but the point is that they have ensured I’m still moving and ok. If I don’t respond within 5 minutes, they’ll call me; if I don’t pick up the phone, they’ll call Scott. This means that there wouldn’t be more than about 30 minutes where I’m not actively being “watched” virtually in case I get swooped by an owl, fall down and hit my head and am too disoriented to call for help (or some other very rare situation). I don’t expect that will happen; but I also think I’ll appreciate the “company” since I’m again, running a solo, DIY race where there aren’t aid stations, other runners, and other crew out and about to cheer me on. It’ll also help my husband sleep better/feel better, so any of those reasons are worth this strategy!

Post-race strategy

Like pre-race strategy, post-race strategy and planning is also critical for me. Once I cross the finish “line” and stop, I get cold and start to feel being wet (from sweat or rain) very quickly. My feet and everything hurt even more. I am absolutely not hungry despite knowing I need to re-fuel. But later I am ravenously hungry like a switch has shifted. So I plan accordingly.

First up, gear change. I want to change into dry clothes. I remind my husband to remind me that yes, despite the pain/hassle of getting out of a wet sports bra and changing it, I’ll regret not changing out of it in addition to changing my shirt. Sometimes, if we are getting in the car to drive home, I quickly swap to a dry shirt and then take the sports bra off under my shirt and just leave it off. No need for gymnastics to put another one on if I am just riding in the car. Same with shoes: once I take my sneakers off, my feet will not want to go back in sneakers. Definitely not the same sweaty, dirty shoes I was running  in, but also not cleaner and even bigger shoes. Instead, I prefer sandals/arch support flip flops. I have those, compression sleeves, and my clean dry clothes ready to go. I learned after my first trail marathon how good a washcloth feels for rubbing off sweat and dirt, so I also have a washcloth. It works for removing masses of mud before you get in the car, too. Or if you’re not muddy and hot and sweaty, pouring some cool water on it and washing your face feels heavenly.

Next up is fueling. When running an organized race, I don’t want to eat any of the race food, even if I can have it. (By “can have it” I mean that it’s safely gluten free with no cross-contamination risk, since I have celiac disease.) Usually I can’t have it, and I plan accordingly to bring food that is not the same food I’ve been eating throughout my ultra (because I have palate fatigue). I don’t want to eat as soon as I stop running, but usually after changing in the car and driving off, my body switches into “you’re safe” mode and wants to start refueling. Make sure you have all your food in the seat with you so you don’t have to stop and dig it out; or worse, have to try to twist around or reach for it (because you won’t want to do that most likely).

And again, you may have palate fatigue or similar (or it may disappear as soon as you are done), so having a few good options will be useful.

I also try to get enough groceries and prepare food for the following several days, too, when I’ll still be hungrier and making up for burned energy. My motivation to cook/prepare/put together food will be low, so having a stocked fridge and freezer with easy to prepare food is important.

Also, you may not be driving home from your race (or being driven home), so make sure to plan your logistics accordingly. Can you get to the airport that same day? Should you? Do you want to? And the next day? Is it safe to fly in your physical state? What different supplies do you need for flying that might be different (due to security regulations around liquid etc) than you would if you were driving home? Do you have enough snacks/food for the travel days following your run?

Training strategy

Oh, and yes, you have to physically train for your ultra. I am by no means a coach or an expert ultra runner. I am a solid, places-from-last back-of-the-pack runner who is a consistent run/walker. So get or make a training plan (Heather Hart has some great free ones for various distances). And stick to it. Except for when you don’t stick to it.

Wait, what?

You set your training strategy for “if all goes well”, but also build in flexibility and extra time for when things don’t go well. Like wildfire smoke season making it unsafe to run outside for a few days or weeks. Or you break your toe and spend 4 weeks not weight bearing. Or you have a lot of life stress, child or parental care, job stress, or any number of things. All this stress impacts training. Give yourself grace and be prepared to be flexible.

I have a hard time with this; I like my spreadsheets and my plans. But wildfire smoke and a broken toe were part of my 2022 ultra training experience this year, and I had to adjust training (and race plans) accordingly. At some point, you have to make the go/no-go decision about whether you’re going to run your race.

Think about what the “ideal training” is. Think about what is the “minimum training” to complete your event safety. If you’re somewhere in between, it’s going to be mental training and planning that can make the difference. At some point, if you’re above ‘minimum’ training you can decide to run even if your training isn’t ideal. Remember, it probably won’t be ideal and it isn’t for a lot of people. But per the mental training section and the wisdom I’ve gained from a lot of ultra runners…the most important factor might be deciding to do it. If you decide to, barring injury during the race or an accident, you will. If you decide mid-race you can’t or don’t want to, likely you won’t.

I think one thing I observe people not training is their walking strategy. Mine is baked in, because all my training short and long runs are intervals of run/walk. Many folks talk about walking hills or walking X minutes per Y minutes or Z miles. If that’s the plan for your race, train it during long runs. Walk hills or powerwalk or hike hills during runs or at the ends of runs. Practice a slow walk mixed in or a faster more efficient power walk. This will help build different muscles and help you maintain more efficient form (and speed) when you shift to it during the race, and help you go longer.

Similarly, practice with your vest/pack/handheld and other hydration gear. Practice with a similar stuffed and weighted pack. Practice with your head lamp. Do a run early in the morning as it transitions from dark to light; do a run into the evening as it transitions from light to dark to get used to your gear; practice troubleshooting it; and to improve your strategy for these transitions. If it’s wildfiresmoke season where you live, practice running masked as well. (On my last long run, I wore my mask for the full 8 hour run because air quality was so yucky.)

Also train and practice with your crew, if possible. Especially things like helping them tape or lubricate, tying your shoes, helping you put your pack on, them packing your pack/vest with supplies, etc. Any of these steps can be practiced during a training run so you and they can figure out what questions and assumptions you each have, and to build the crew checklist and instructions.

In my case, I’ve trained with my husband on refilling my ice and water in my pack during several training runs and previous races. We haven’t trained yet on him re-packing my (new) vest, though, so that’s on our list to practice on runs heading into my 100M. We did practice one run where I needed him to pick me up at a trail construction closure and drive me to the other side, with him bringing me a fresh/hot home-prepared fuel option. It worked well to a degree; I had a ¼ ham and cheese quesadilla slice in the microwave and had told him how to microwave it, which I had factored in cooling time for when he would be driving it to me before I would eat it. But he also tried to optimize and then put it in our car-based portable food warmer, which doesn’t do well with plastic bags (it needs a tupperware container) in general and was way too much heat. So it was scalding hot when I got in the car! Oops. Lesson learned. That was maybe unique to the car scenario but we will also test and practice the other food warming up options to make sure he doesn’t accidentally re-optimize where I’ve already optimized the food process; and make sure I have in fact optimally optimized the food strategy for each item.

Conclusion

Wow, that’s a lot of planning and strategy now that I’ve written it all out. Which makes sense, because I’ve been thinking about all these things for months and iterating on my strategies and plans. Hopefully, it’ll pay off and help immensely with making my 100M experience more smooth (note that I doubt any 100M would be easy/easier but I hope for “smoother”!) than it otherwise would be.

In summary, I pre-plan mentally for how it’ll feel running; I attempt to solve as many problems in advance as I can and prep supplies for fixing problems; I test, plan, and practice my fueling as much as possible; I aim to carefully pace effort as well as speed during my run; I break my run up into mental chunks so I am not dwelling on what’s to come but focusing on running the current segment; I try to minimize decision fatigue during and after the race by pre-doing anything I can and pre-supplying myself to make it easier; and of course, I train for months to prepare physically as best as possible while realizing that my training might not ever be ideal but that I can still safely attempt to run 100 miles.

PS – if there are any strategies, tips, or approaches you take to ultrarunning, especially 100 miles or more distance-wise, I’d love to hear them! Please share them in the comments or link to any posts you’ve written. I’m still learning and likely will always be evolving my strategies!

Note: I wrote this post before my 100 mile attempt. I ended up completing 82 miles and happily choosing to stop, knowing that I could physically keep going. Looking back at the above and reflecting on my experiences, I didn’t have a single challenge or experience that I wasn’t prepared to deal with or couldn’t deal with, thanks to all of the above work. So I’m thrilled and proud of my 82 mile experience!

If you found this post useful, you might also be interested to read this post with more details on how I developed my pacing, enzyme, and electrolyte estimates and more tactical specifics of how I prepped myself and my crew for my ultramarathon.

Reasons to “DIY” or Self-Organize Your Own Solo Ultramarathon or Ultra Run

I’ve now run two ultramarathons (both happened to be 50k races, with a race report for the second race here), and was planning my third ultrarace. I had my eye on the 50 mile (50M) version of the 50k I ran last year. It’s on a course I adore – a 6 foot wide crushed gravel trail that’s slightly uphill (about 1,000 feet) for the first 30 miles and then downhill at 2% grade for the remaining 20 miles. It happens to be close to home (hour and a half drive to the start), which helps for logistics.

I started training for the 50M weeks after my 50k this year, including talking my husband into taking me out to run some of the segments along the first 25 miles of the course. I’ve done the back half of the course several times through training and racing the 50k, and I wanted to check out each of the earlier segments to get a sense of what trail bathrooms existed on the course, make notes about milestones to watch for at various distances, etc.

After the first training run out there, when I started talking goal paces to get through the first and main cutoff at mile 30 (cutoffs got progressively easier from there, and even walking very slowly you could finish if you wanted to), my husband started to suggest that I should just run the course some other time on my own, so I didn’t have to worry about the cutoffs. I told him I didn’t want to do that. The cutoffs are a good incentive to help me push myself, and it’s worth the stress it causes in order to try to perform my best. (My target pace would get me through a comfortable 15 minutes before cutoff, and I could dial up the effort if needed to achieve cutoff). However, he suggested it another time and pointed out that even when running an organized race, I tend to run self-supported, so I don’t really don’t benefit as much from running in a race. I protested and talked again about the camaraderie of running when everyone else did, the fact that there were aid stations, the excellent search and rescue support, the t-shirt, the medal, the pictures! Then out loud I realized that I would be running at the back of the pack that I would miss the pictures at 25 miles because the photographer heads to the finish before I would get there. And they stop finish line pictures 3 hours before the end of the race. (Why, I don’t know!) And so I’d miss those photos too. And last year, I didn’t partake in the 50k staffed aid stations because I couldn’t eat any of their food and didn’t want any extra COVID exposure. Instead, my husband crewed me and refilled my hydration at two points on the course. The un-staffed aid stations didn’t have the plethora of supplies promised, and one race report from someone near the front of the pack said they were low on water! So it was a good thing I didn’t rely on the aid stations. I didn’t wear the tshirt last year, because it wasn’t a tech tee. Medals aren’t that exciting. So…why was I running the organized race?

My only remaining reasons were good search and rescue (still true) and the motivation of signing up for and committing to running on that date. It’s a commitment device. And my husband then smashed that reason, too, by reminding me that the only commitment device I typically need is a spreadsheet. If I decide I’m going to work toward a goal, I do. Signing up doesn’t make a difference.

And to be fair, he crews me whether it’s an organized race or not! So to him, it makes no difference whether I’m running an organized race or a self-organized long ultra.

And so I decided to give it some thought. Where would I run, if I could run anywhere in an hour’s distance from home? Do the same 50 mile course? Was that course worth it? Or was there somewhere closer to home where I could run that would be easier for my husband to crew?

He suggested running on our “home” trails, which is a network of hundreds of miles of paved trail that’s a short walk away. I immediately scoffed, then took the suggestion seriously. If I ran “from home”, he could crew from home and either drive out or e-bike out or walk out to bring me supplies along my route. If the park trail bathrooms ended up getting locked, I could always use the bathroom at home (although not ideal in terms of motivating myself to move quickly and get back out on the trail). I’d have a bigger variety of fueling options, since he could microwave and bring me out more options than if it had to be shelf-stable.

The list of benefits of potentially doing my own DIY or self-organized ultra grew.

(And then, I broke my toe. Argh. This further solidified my willingness to do a DIY ultra, because I could train up until when I was ready, and then run my distance, without having to choose between a non-refundable signup and not running or risking injury from running before I was ready.)

Eventually, my plans evolved (in part due to my broken toe). I was originally going to DIY a 50M or 100k (62M) over Labor Day weekend, recover, then re-train up and run a DIY 100 mile (100M) in late October or early November. When I broke my toe, I decided to scratch the “test” 50M/100k and just train and run the 100M, since that was my ultimate goal distance for the year.

Here are the pros of running a DIY ultra or a “self-organized” ultra, rather than an organized race with other people:

  • For me specifically, I have better trail options and route options. I can run a 95% flat course on paved, wide, safe trails through my local community.
  • These are so local that they are only a few minutes walk from my door.
  • The location means it’s easy for Scott to reach me at any point. He can walk out and bring me water and fuel and any needed supplies when I complete a loop every 4 or so hours. If needed, he could also e-bike out to bring me anything I need if I ran out or had a more urgent need for supplies. He can also drive out and access the course every half mile or mile for most of my planned route.

    This also means I have more fuel options that I can prepare and have for Scott to bring out. This is awesome because I can have him warm up ¼ of a ham and cheese quesadilla, or a corn dog, or sweet potato tots, or any other fuel options that I wouldn’t be able to use if I had to rely on pre-packed shelf stable options for a 30 hour race.

    (Note that even if I did an organized race, I most likely still wouldn’t benefit from aid station food. In part, because I have celiac and have to have everything gluten free. I also have to watch cross contamination, so a bowl of any kind of food that’s not individually packaged is something that’s likely contaminated by gluten. COVID has helped reduce this but not completely. Plus, I have diabetes so I need to be roughly aware of the amount of carbs I’m eating to decide whether or not to dose insulin for them, given what is happening to my blood sugar at the time. And, I have exocrine pancreatic insufficiency (EPI) which means I have to dose enzymes for everything I eat. Grazing is hard with EPI; it’s easier to dose and eat the amount that matches my enzymes, so pre-packaged snacks that I know the carb and fat and protein count means I know what insulin I need and what enzymes I need for each set of “fuel”. Guessing carb counts or enzyme counts in the middle of the night while running long distance is likely not going to be very effective or fun. So as a result of all that – pre-planned food is the way to go for me. Related, you can read about my approach for tracking fuel on the go with a spreadsheet and pre-planned fuel library here.)

  • There is regular public bathroom access along my chosen route.
  • I’ve designed out and back laps and loops that have me coming back by my start (remember, only a few minutes walk from home) and that make it so I am passing the bathrooms multiple times on a regular basis in case I need them.

    These laps and loops also make for mentally smaller chunks to tackle. Instead of 100 miles, I’ve got a ~24 mile out and back, a 13 mile loop, a 16 mile out and back, a repeat of the 13 mile loop, repeating again the 16 mile out and back followed by the 13 mile loop one more time, and then a quick 5 mile total out and back (so 2.5 out and back). These are also all routes I know well, so mentally finding waypoints to focus on and know how far I’ve gone are a huge benefit for mentally breaking down the distance into something my brain and body “know”.

  • There are no cutoffs or pace requirements. If I slow down to a 20 minute mile (or slower)…well hey, it’s faster than I was walking with my hands-free knee crutch a few months ago! (I rocked anywhere from a 45 minute mile to a 25 minute mile).

    There’s no pressure to go faster, which means I won’t have pressure to push my effort, especially at the start. Hopefully, that means I can maintain an “easy”, even effort throughout and maybe cause less stress to my body’s hormone systems than I would otherwise.

    The only pressure I have will be the pressure I put on myself to finish (eventually), which could be 26 hours or could be 30 hours or could be 36 hours or even slower… basically I have to finish before my husband gives up on coming out to refuel me!

  • And, once I finish, it’ll be ‘fast’ to get home, shower, refuel, and be done. This is in comparison to a race where I’d have an hour+ drive to get home. I’ll need to walk home which might actually take me much longer than that after I’ve ambulated for 100 miles…but it should hopefully be shorter than an hour!
  • Finally, the major benefit is flexibility. I can set my race date for a weekend when I’ve trained enough to do it. I can move it around a week or two based on the weather (if it’s too cold or too rainy). I can even decide to move it to the spring (although I’d really love to do it this year).

Here are some of the cons of running a DIY ultra or a “self-organized” ultra, rather than an organized race with other people:

  • Theoretically, it would be easier to stop because I am so close to home. I haven’t committed money or drive time or dragged my husband to far away places to wait for me to finish my run. (However, I’m pretty stubborn so in my case I think this is less of an issue than it might be for others?)
  • Yet, out and back loops and the route I’ve chosen could get monotonous. I chose these loops and the route because I know the distance and almost every tenth mile of the route super well. The first 6 miles of all the laps/loops are the same, so I’ll run those same 6 miles repeated 7 times over the course of the run.
  • I won’t have the camaraderie and knowledge that other people are out here tackling the same distance. I’m a back of the pack runner (and celebrate being places from last the way most people celebrate places from first!) and often don’t see anyone running after the start…yet there’s comfort in knowing I’m one of dozens or hundreds out here covering the same course on the same day with the same goal. I do think I’ll miss this part.
  • There is no one to cheer for me. There’s no aid station volunteers, fellow runners, or anyone (other than my amazing husband who will crew me) to cheer for me and encourage me and tell me I’m moving well.
  • There’s no medal (not a big deal), t-shirt (not a big deal), or official finishing time (also not a big deal for me).
  • There’s no cutoffs or pace requirements to motivate me to keep pushing when things get hard.

All in all, the benefits pretty clearly outweigh the downsides – for me. Again, I’m a back of the pack super slow runner (in fact, I typically run 30 seconds and walk 60 seconds throughout my whole race consistently) who can’t eat aid station food (because celiac/EPI makes it complicated) coming off of a broken toe injury (which messed up my training and racing plans), so my pros/cons lean pretty heavily toward making a DIY/self-organized solo ultra run an obvious choice. Others might have different pro/con list based on the above variables and their situations, but hopefully this helps someone else think through some of the ways they might decide between organized and un-organized ultramarathon efforts!

Reasons to "DIY" or self-organize your own ultramarathon run