In most coaching apps, what you prescribed and what the client actually did sit on two different screens of the same workout. What they did last week lives somewhere else again, which means opening the whole workout a second time in another browser window and toggling that one too. To judge whether a lift is progressing, you end up holding three views in your head at once.
Why comparing the two matters
A logged number on its own tells you almost nothing. 60kg for 8 is a stall if it was 60kg for 8 last week, and a jump if it was 57.5kg for 6. Progression only shows up in the comparison: prescribed against actual, and this week against last. Miss it and you either push a lift that stalled or hold one that was ready to move.
The manual way, and why it drags
The usual routine is to open the workout, read the Logged tab, switch to Plan to see what you asked for, open last week in a new tab, switch its toggle too, and compare by eye. Per client, for a handful of lifts each. None of it is hard. It is just slow, and at scale the slowness is the whole problem.
Put all three in one row
The faster version is to stop toggling and line up prescribed, logged and last week side by side, one row per lift. Then a stall and a jump are simply visible: the lift that sat at the same weight two weeks running, and the one that moved.
The bench moved and the other two held, and you read that in a second rather than reconstructing it across tabs. This is the one thing PTToolBox was built around. It shows asked, did and last week in a single row, so the comparison you were doing in your head is just there on the screen.
What to do with it
Once you can see it, the call is quick: move the lifts that hit the top of the range, hold the ones that stalled, and note anything that dropped off so you can ask why in the check-in. The reading was the slow part. The coaching was never the problem.