The spreadsheet never breaks. What fades is your memory of why you built it that way.
A spreadsheet is the most honest training tool there is. It costs nothing and it does exactly what you told it to do. The good ones took real thought to build: a tab per block, an e1RM formula in column H, conditional formatting that goes red when a set falls short. This is a respectful look at where that stops and training memory begins.
| Job | Spreadsheet | Fire Your Coach |
|---|---|---|
| Holds the numbers | Yes | Yes |
| Bends to any structure you invent | Yes | No |
| A whole block visible on one screen | Yes | No |
| Your data is yours to export | Yes | Not yet |
| Usable one-handed between sets | No | Yes |
| Holds the reasoning behind a change | No | Yes |
| Adapts the session to the day | No | Yes |
| Carries decisions into the next block | No | Yes |
| Reads balance drift across blocks | No | Yes |
It's Sunday night. The next block starts tomorrow and the file is open on the second monitor, the way it has been every eight weeks for years. You know how to train. That's not the problem. The problem is that you're sitting there trying to reconstruct a decision you made in April from a cell that says Belt squat 3x8.
None of that is the spreadsheet failing. It held every number you gave it, exactly, for as long as you kept the file. That's the whole job it agreed to. The arrangement was always that the grid holds the data and you hold the reasoning, and for one block that arrangement works fine.
It stops working quietly, which is why it takes years to notice. Nothing in the file degrades. You simply stop being able to answer, from the numbers alone, whether twenty sets for quads was productive or merely tolerable. So the next block is designed by a person with less information than the person who designed the last one. Nothing carries what one block taught you into the next, because carrying reasoning was never something a grid was built to do.
Nothing in the file degraded. The half that lived in your head did.
Fire Your Coach is not a better spreadsheet. It isn't trying to beat a grid at holding numbers, and it won't show you eight weeks at once the way your file does. What it holds is the column a grid cannot: the reason. Why the exercise changed. What you were actually chasing. Whether the last block worked.
That's one column with three consequences. A session adapts when you've slept four hours or the rack is taken, instead of staring back at you unchanged. A swap is recorded as a typed deviation with the reason attached, not lost as an unedited cell. And the next block opens with what the last one taught you already in it. What it deliberately does not do is take over the programming. You still make the calls. That sacrifice is the point, not a gap in a roadmap.
Keep the sheet if you want it. Plenty of people plan in a grid and execute somewhere else, and that's a reasonable way to work. If you'd rather run one thing, sets, splits and session notes are tracked faithfully here. One-handed, between sets, without a cell reference in sight.
The intake asks the questions your header row already answers: how you split the week, what you're training for, what you have to train with, how hard you've been pushing. It builds a structured plan from that in a few minutes, with the intent behind it recorded rather than implied. And if your actual log lives in Strong or Hevy alongside the sheet, drop that CSV in and the history comes with you. The memory starts from sessions you've already done, not from today.
A usable training spreadsheet template holds four things: the prescription, the load, what you actually did, and the date. Most templates stop there. The two columns that decide whether it still works in block three are why a prescription changed and what you learned from it. Those are the columns Fire Your Coach keeps, because a formula cannot compute a reason.
A spreadsheet is better at holding a structure you invented and at showing a lot of it at once. An app is better on the gym floor, where you have one hand free and no patience for a cell reference. Most self-programming lifters end up with both. The question worth asking is which one holds the reasoning, because neither a grid nor a set logger does.
Usually not because the file is badly built. A spreadsheet holds every number you put in it, permanently and accurately. What fades is the half you never wrote down: why you dropped an exercise, whether that volume was productive or just tolerable, what week six actually felt like. Copying the tab forward carries the numbers into the next block. It doesn't carry the reasoning.
Not as a file upload today. Fire Your Coach imports training history from Strong and Hevy CSV exports, so if your log lives in one of those alongside the sheet, that history comes with you. If everything lives in the sheet, the way in is the intake: it asks the same questions your header row already answers and builds a structured plan from them. Keep the sheet if you want it.