How to run a weekly review for coaching clients

1. Block one batch slot, not scattered reactions

Reviews happen in one fixed weekly block, after check-ins close, not as each one lands through the week. Reacting in real time means every review starts cold; batching means you carry context from the last client straight into the next.

2. Open the trend before the single week

Pull up four to six weeks of adherence, weight, and energy before reading this week's numbers on their own. A week that looks fine in isolation can be the third week of a slide, and a week that looks bad can be normal noise around a trend that's still climbing.

3. Decide exactly one change

Pick the single biggest lever this week: volume, a macro target, a deload, or deliberately no change. Adjusting five variables at once is how a coach loses the ability to tell which change actually worked next week.

4. Write the plan update before the reply

Make the actual change in the program or plan first. Then write the client message describing it. A reply drafted before the change exists tends to describe an intention instead of something the client can act on today.

5. Match the channel to the size of the change

A routine tweak stays in the async check-in reply. Anything that reshapes the plan, or responds to a real setback, gets a short call or voice note instead. As a rule of thumb, if the message needs more than two paragraphs to explain, it needed a different channel.

6. Log the decision, dated, against the client record

One line is enough: what changed and why. Three weeks later this is the difference between reconstructing a plan shift from memory and just reading what you already wrote down.

7. Roll weekly decisions into a monthly pass

Once a month, compare the string of weekly decisions against the original goal, not just week over week. This is what catches a series of individually reasonable calls that have quietly drifted the plan off course.

What's the actual difference between a check-in and a weekly review?

The check-in is the client's structured input: a form, a set of numbers, a few sentences. The weekly review is the coach's output: reading that input, deciding what changes, and telling the client. See the client check-in system guide for the input side of this loop.

How long should a weekly review take per client?

With a fixed trend view and a one-change rule (steps 2 and 3), a reasonable target for a client who's on track is well under two minutes. Clients with a real flag or setback deserve more time; the batching in step 1 is what makes room for that without the whole roster sliding.

Does every client need a weekly review, or just the active ones?

Anyone on an active plan, yes. A client in a genuine maintenance phase with no plan changes expected can move to a lighter biweekly or monthly review, but that should be a stated decision, not a default a coach drifts into from being busy.

What if the check-in shows nothing changed?

That's still a decision: log "no change" with the date, same as any other outcome. A quiet week with no note looks identical, three months later, to a week nobody actually reviewed.

When does a weekly review need a call instead of an async message?

When the change is big enough that tone and questions matter: a real setback, an injury, a plan reset, or anything the client is likely to have follow-up questions about immediately. Step 5's two-paragraph rule of thumb is a decent trigger to check against.

Where does software actually help with the review itself?

Mainly steps 1, 2, and 6: holding the batch queue, surfacing the rolling trend without the coach rebuilding it by hand, and keeping the dated decision log attached to the client record. See "Where Amenti fits" below for exactly what that does and doesn't cover.