The notebook wins because the lifter built the schema.

Sunday night, the sheet is open again

Sunday night, and the spreadsheet is back open. Seventeen columns wide, a pivot table down the side, cells tinted by RPE.

The lifter refreshing it started three years ago in Strong. Moved to Hevy for the cleaner charts. Ran a block in Fitbod. And here they are anyway, hand-maintaining a Google Sheet that no product on the App Store can reproduce. Ask them why and the answer is flat: nothing else knows what a working set is versus a top set, nothing else shows a pressing family as one line, nothing else lets them park an RPE target and a percentage in the same cell. So they built it. Every advanced lifter you know is running some version of this sheet, and most of them are a little embarrassed about it.

The schema gap

Here is the pattern, named: the schema gap. A shipped tracker models a workout as a list of sessions, each session a list of exercises, each exercise a list of sets. Clean, generic, week-one friendly. The year-5 lifter models something else entirely. They think in exercise families, in mesocycle position, in top set versus back-off, in RPE that drifts against a percentage floor. That mental model is a schema. When the app's schema and the lifter's schema disagree, the lifter does not delete their mental model. They rebuild it by hand in the one tool where they own the columns. The sheet is not a downgrade from the app. It is the schema the app refused to ship.

It was never a features problem

The industry read on this is that the lifter needs more: more charts, more presets, a coaching layer that prescribes the next session. That diagnosis has it backwards. A lifter who maintains a 17-column sheet is not short on features. They have already built the exact structure they want and are maintaining it for free on their own time. What they lack is a product whose data shape matches the one they already trust. Bolting another prescription engine on top of the wrong schema does not close the gap. It widens it, because now the lifter has to reconcile the app's opinion with a model the app still cannot represent. The sheet has no opinions. That is a feature.

Ask r/weightroom and the answer is a notebook

This is not one writer's hunch. Walk into the serious-lifter forums with the question 'what's the best app' and watch what the top-voted replies actually say. On r/weightroom and r/powerlifting, the recurring consensus answer from people with long training histories is some version of: I tried the apps, I use a notebook now, or I use a spreadsheet. The people who log RPE by reflex and have run at least one full block of 5/3/1 or a hypertrophy mesocycle are the ones most likely to have left the apps behind. That convergence across two of the highest-signal strength communities, and across every major tracker, is the tell. When the advanced end of a market routes around every product in a category and lands on the same manual workaround, the category has a schema problem.

When the advanced end of a market routes around every product and lands on the same notebook, the category has a schema problem.

What the sheet actually models

Watch a real week move through the sheet and the gap gets concrete. The lifter is running block periodization with accessories that rotate every mesocycle, so they need a view that follows the pressing family across incline, close-grip, and overhead, not three unrelated logs. Their prescription is a hybrid: RPE 8 capped at a percentage of a training max, so both numbers have to live next to each other or the target is meaningless. Their top set and their back-off sets are different animals, and flattening them into one 'sets' list destroys the signal they read progression from. Then the confounds: a bad-sleep week that explains a stalled top set, and the quiet fact that the 45 in their garage is really 44.1 while the gym's calibrated plate is dead-on. The sheet holds all of it because the lifter cut a column for each. The generic app holds none of it, so the lifter cut the app.

If the schema is the tool, meet lifters at their schema

Take the thesis seriously and the whole build order flips. The winning move is not a cleverer prescription on top of a generic log. It is shipping the data shape the advanced lifter already reconstructs by hand, so they can stop being their own database admin on Sunday nights. That means exercise families as a first-class object, top set and working sets as distinct fields, a rolling block view instead of an endless session feed, and signals the lifter can verify by hand instead of trusting on faith. Get the schema right and the sheet has nothing left to do that the app cannot. Get it wrong and no amount of polish keeps a serious lifter from opening a blank spreadsheet.

Built to be handed the sheet, not to replace the lifter

That is the shape Platepusher was drawn to fit. Drop a CSV out of Strong or Hevy and every lift, every set, every date lands as native data, so the years you already logged are the starting line, not a fresh install. From there the model is the lifter's: pressing families as one progression line, top sets and back-offs kept apart, a rolling block view, and plateau flags that run on plain math you can check against your own numbers. It does not prescribe your next session and it does not grade your week. It records what your training has been recording and hands it back in the structure you would have built anyway. The lifter stays the one reading the block. The instrument just stops making them rebuild the columns.

What we're tracking next

The open question is how far schema-parity scales before it becomes its own kind of bloat. There is a version of this that keeps adding fields until the app is just a worse spreadsheet with a login. The line to hold is coverage of the common advanced schema without turning every screen into a config panel. We are watching which columns the forums keep rebuilding by hand, because those are the ones still missing from every product, ours included.