I’ve been tracking every race I’ve run in a spreadsheet since October 2017. Every single one. The good races. The terrible races. The DNFs. The races where I PR’d and the races where I wondered why I even showed up.<\/p>\n\n\n\n
For years, people looked at my spreadsheet and asked the same question: “Why?”<\/p>\n\n\n\n
Why track every race result? Why record the details\u2014times, distances, placements, weather conditions, how I felt? Why keep a running log that most people would consider obsessive?<\/p>\n\n\n\n
Because tracking every race didn’t just organize my results. It fundamentally changed how I approach running, set goals, and measure progress. And looking back at years of data, I can see patterns I never would have noticed otherwise.<\/p>\n\n\n\n
Here’s what I learned from being a spreadsheet runner\u2014and why I eventually realized spreadsheets weren’t enough.<\/p>\n\n\n\n
\n \ud83d\udcca Ready to move beyond spreadsheets?<\/strong>\n <\/p>\n \n RunningLog was built by a spreadsheet runner who wanted something better. Track your complete race history without the hassle of maintaining spreadsheets\u2014goals, results, and progress all organized in one place.\n <\/p>\n Start Your Race Log Free \u2192<\/a>\n <\/p><\/div>\n\n\n\n It started innocently enough. After running my first half marathon, I wanted to remember the details\u2014my finish time, how the race went, what I learned. I opened Excel and created a simple table:<\/p>\n\n\n\n One race became two. Two became five. Five became a dozen. Before I knew it, I had years of race history meticulously documented in rows and columns.<\/p>\n\n\n\n What started as simple record-keeping evolved into something more. I added columns for placement, weather conditions, how I felt during the race, what went wrong, what went right. I color-coded personal bests. I created formulas to calculate average pace. I built charts showing my progression over time.<\/p>\n\n\n\n My spreadsheet became my running diary, my performance tracker, and my source of motivation all in one.<\/p>\n\n\n\n Ask me about a race I ran three years ago without looking at my spreadsheet, and I’ll give you a vague answer. “It was okay, I think. Hot day, maybe?”<\/p>\n\n\n\n But check my spreadsheet, and there’s the full story: “Started too fast, hit the wall at mile 9, learned to respect the distance. Beautiful course but brutal heat\u201485\u00b0F at finish. Still PR’d by 2 minutes because of better pacing through mile 8.”<\/p>\n\n\n\n Memory fades. Data doesn’t. Every race I’ve run is documented with enough detail that I can relive it years later.<\/p>\n\n\n\n Looking at my spreadsheet chronologically, my progression looks messy. Some years I got faster. Some years I plateaued. Some years I got slower due to injury or life getting in the way.<\/p>\n\n\n\n But when I graph my personal bests over time, the trend is clear: gradual improvement with setbacks along the way. Without the complete data, I might have quit after a bad season thinking I wasn’t making progress. The spreadsheet showed me the bigger picture.<\/p>\n\n\n\n My half marathon times over the years:<\/p>\n\n\n\n <\/p>\n\n\n\n After tracking dozens of races, patterns became obvious:<\/p>\n\n\n\n These insights only became visible because I had years of complete data. One or two races don’t reveal patterns. Twenty or thirty do.<\/p>\n\n\n\n Early on, I was tempted to delete bad race results from my spreadsheet. That DNF? Delete. That race where I missed my goal by 15 minutes? Delete. Start fresh with only the good data.<\/p>\n\n\n\n But I didn’t. And I’m glad.<\/p>\n\n\n\n Looking back, my bad races taught me more than my PRs. That DNF at mile 18? Taught me not to race through injury. That race where I blew up at mile 20? Taught me to respect marathon distance and pace conservatively early.<\/p>\n\n\n\n Every “bad” race has a note explaining what went wrong and what I learned. Those lessons prevented me from repeating the same mistakes.<\/p>\n\n\n\n When I started running, I set arbitrary goals. “I want to run a 3:30 marathon.” Why 3:30? Because it sounded impressive.<\/p>\n\n\n\n Setting data-driven goals meant I hit them more often, which built confidence instead of constant disappointment from unrealistic targets.<\/p>\n\n\n\n As much as I loved my spreadsheet, it had serious limitations:<\/p>\n\n\n\n After every race, I had to manually:<\/p>\n\n\n\n It’s not hard, but it requires discipline. After a tough race, the last thing I wanted to do was open Excel and type. Sometimes I procrastinated, and details were lost.<\/p>\n\n\n\n My spreadsheet lived on my laptop. If I was on my phone and wanted to check a past race result? Out of luck. Traveling without my laptop? Can’t update race results until I get home.<\/p>\n\n\n\n I tried Google Sheets for cloud access, but it was still clunky on mobile. Entering data on a phone was frustrating.<\/p>\n\n\n\n Want to compare all my 10K times to see improvement? I’d have to filter the spreadsheet, sort by distance, manually review times. Want to see how I’ve performed on hilly courses vs flat? I’d need to add more columns, more manual categorization.<\/p>\n\n\n\n The data was there, but extracting insights required work.<\/p>\n\n\n\n I created charts in Excel showing my marathon progression over time. But every time I added a race, I had to manually update the chart range, fix the formatting, adjust the axes.<\/p>\n\n\n\n For casual review, I rarely bothered. My beautifully crafted charts were updated maybe twice a year.<\/p>\n\n\n\n My entire running history lived in one Excel file. If my laptop crashed and the backup failed? Years of data gone. I backed up religiously, but the anxiety was always there.<\/p>\n\n\n\n Sometimes I wanted to show my running progression to friends or compare notes with other runners. Sharing a spreadsheet is awkward. Exporting it, sending it, having them open Excel\u2014it’s a barrier to conversation.<\/p>\n\n\n\n And I couldn’t easily see how my progression compared to other runners at my level. Was I improving faster or slower than typical? No way to know.<\/p>\n\n\n\n After years of maintaining my spreadsheet, I realized I wasn’t alone. Lots of serious runners track their race history\u2014some in spreadsheets, some in notebooks, some in scattered Strava activities, some just in their heads.<\/p>\n\n\n\n But there wasn’t a simple tool designed specifically for tracking race results. Training run apps like Strava are great for daily runs, but race results get buried in your activity feed. You can’t easily sort by distance, compare performances, or track goals across races.<\/p>\n\n\n\n I wanted something that:<\/p>\n\n\n\n So I built it. RunningLog is essentially the spreadsheet I wish I’d had from the beginning\u2014simple, focused on races, easy to use, and built by someone who knows what spreadsheet runners need because I was one.<\/p>\n\n\n\n If I could go back to 2017 when I started tracking races, here’s what I’d say:<\/p>\n\n\n\n I wish I had recorded my very first 5K, not just races after I got “serious” about running. Those early races are part of the story. Start tracking now, even if you’re slow, even if you’re a beginner.<\/p>\n\n\n\n Some of my early race entries just have times. No notes. No context. I can’t remember what happened or what I learned. Write down how you felt, what went wrong, what went right\u2014while it’s fresh.<\/p>\n\n\n\n Every race\u2014good or bad\u2014is part of your journey. The DNF from Transylvania 50k in 2022 taught me more than the PR from 2023. Keep everything.<\/p>\n\n\n\n Don’t guess at goals. Use your actual race history to set realistic targets. You’ll hit them more often and build confidence.<\/p>\n\n\n\n I wish I’d recorded not just my finish time, but also what I was aiming for. Did I hit my goal? Miss it? Exceed it? That context matters when reviewing old races.<\/p>\n\n\n\n Here’s the real reason tracking every race changed my running: accountability<\/strong>.<\/p>\n\n\n\n When you know you’re going to log the race\u2014good or bad\u2014you show up differently. You take training more seriously because you know the result will be recorded. You don’t skip races because life got busy, because each race becomes a data point in your larger story.<\/p>\n\n\n\n My spreadsheet became a commitment device. Every blank row was a future race I needed to run. Every completed row was proof I’d shown up.<\/p>\n\n\n\n Over seven years, that accountability added up. I’ve run more races, trained more consistently, and improved more than I ever would have without tracking.<\/p>\n\n\n\n You don’t need to be as obsessive as me. You don’t need elaborate spreadsheets with formulas and color coding.<\/p>\n\n\n\n But I do believe every serious runner should track their race history somehow:<\/p>\n\n\n\n The method doesn’t matter as much as the consistency. Track every race. Record what you learned. Build a history you can look back on.<\/p>\n\n\n\n Because five years from now, you’ll want to remember where you started. Ten years from now, you’ll want proof of how far you’ve come. Twenty years from now, you’ll want to see the complete arc of your running journey.<\/p>\n\n\n\n And you can’t see any of that if you don’t track it.<\/p>\n\n\n\n I still love spreadsheets. I still have my original Excel file with years of race data (backed up in three places, because I’m paranoid).<\/p>\n\n\n\n But now I also have RunningLog, where I can add races from my phone minutes after crossing the finish line, see my PRs instantly, set goals for upcoming races, and review my complete history without opening Excel.<\/p>\n\n\n\n It’s everything I loved about my spreadsheet, without the friction.<\/p>\n\n\n\n For spreadsheet runners like me who appreciate organized data but want something easier to maintain, it’s the tool I wish existed in 2017.<\/p>\n\n\n\n And for runners who never would have touched a spreadsheet but still want to track their race progression? It makes that accessible too.<\/p>\n\n\n\n Whether you track in a spreadsheet, a notebook, an app, or carrier pigeons\u2014just track.<\/p>\n\n\n\n Your race history is more than a list of times. It’s a record of:<\/p>\n\n\n\n Don’t let that history live only in your memory. Memory fades. Times blur together. Details get lost.<\/p>\n\n\n\n Track it. All of it. The good races and the bad ones. The PRs and the DNFs. The breakthroughs and the learning experiences.<\/p>\n\n\n\n Because that’s not just data in a spreadsheet. That’s your running story. And it deserves to be preserved.<\/p>\n\n\n\n Ready to start tracking your complete race history? Built by a spreadsheet runner, for runners who want something better. Try RunningLog<\/a> free.<\/strong><\/p>\n\n\n\n Are you a spreadsheet runner? Or do you track races another way? Share your method on Instagram<\/a> or Threads<\/a>\u2014we’d love to hear how you keep your race history organized!<\/em><\/p>\n","protected":false},"excerpt":{"rendered":" I’ve been tracking every race I’ve run in a spreadsheet since October 2017. Every single one. The good races. The terrible races. The DNFs. The races where I PR’d and the races where I wondered why I even showed up. For years, people looked at my spreadsheet and asked the same question: “Why?” Why track […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-125","post","type-post","status-publish","format-standard","hentry","category-runninglog"],"_links":{"self":[{"href":"https:\/\/runninglog.app\/blog\/wp-json\/wp\/v2\/posts\/125","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/runninglog.app\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/runninglog.app\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/runninglog.app\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/runninglog.app\/blog\/wp-json\/wp\/v2\/comments?post=125"}],"version-history":[{"count":1,"href":"https:\/\/runninglog.app\/blog\/wp-json\/wp\/v2\/posts\/125\/revisions"}],"predecessor-version":[{"id":126,"href":"https:\/\/runninglog.app\/blog\/wp-json\/wp\/v2\/posts\/125\/revisions\/126"}],"wp:attachment":[{"href":"https:\/\/runninglog.app\/blog\/wp-json\/wp\/v2\/media?parent=125"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/runninglog.app\/blog\/wp-json\/wp\/v2\/categories?post=125"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/runninglog.app\/blog\/wp-json\/wp\/v2\/tags?post=125"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}How I Became a Spreadsheet Runner<\/h2>\n\n\n\n
\n
What Tracking Every Race Taught Me<\/h2>\n\n\n\n
1. You Remember Less Than You Think<\/h3>\n\n\n\n
2. Progress Isn’t Always Linear<\/h3>\n\n\n\n
\n
3. Patterns Emerge Over Time<\/h3>\n\n\n\n
\n
4. Bad Races Matter as Much as Good Ones<\/h3>\n\n\n\n
5. Goals Become More Realistic<\/h3>\n\n\n\n
The Limitations of Spreadsheets<\/h2>\n\n\n\n
1. It Takes Work to Maintain<\/h3>\n\n\n\n
\n
2. Spreadsheets Don’t Travel Well<\/h3>\n\n\n\n
3. No Easy Way to Compare<\/h3>\n\n\n\n
4. Hard to Visualize Progress<\/h3>\n\n\n\n
5. Risk of Data Loss<\/h3>\n\n\n\n
6. Impossible to Share or Get Insights from Others<\/h3>\n\n\n\n
Why I Built RunningLog<\/h2>\n\n\n\n
\n
What I’d Tell My Past Self<\/h2>\n\n\n\n
1. Start Tracking from Day One<\/h3>\n\n\n\n
2. Write More Notes<\/h3>\n\n\n\n
3. Don’t Delete Bad Races<\/h3>\n\n\n\n
4. Use the Data to Set Goals<\/h3>\n\n\n\n
5. Track Goals, Not Just Results<\/h3>\n\n\n\n
The Bigger Lesson: Tracking Builds Accountability<\/h2>\n\n\n\n
You Don’t Need a Spreadsheet (But You Should Track)<\/h2>\n\n\n\n
\n
From Spreadsheet to Tool: The Evolution Continues<\/h2>\n\n\n\n
The Bottom Line: Your Race History Matters<\/h2>\n\n\n\n
\n
\n\n\n\n