Weekly Check-In Triage and the 1-Decision Rule

Weekly Check-In Triage and the 1-Decision Rule

AI coaching gets useful when it helps coaches decide what to change, what to watch, and what to leave alone.

Justin Harris’s coaching note on insulin sensitivity is blunt: when the same insulin dose started dipping blood sugar earlier than usual, he told the client to reduce the dose further on the next high day. The mechanism is simple feedback control: a weekly check-in is not a status report, it is a triage point. That matters because AI fitness coaching is only as good as its decision quality, and the sharpest thesis is easy to test: if a check-in does not force a concrete change, a concrete watch item, or a deliberate hold, it is not coaching—it is narration.

Why weekly check-ins exist at all

Coaches get tempted to treat check-ins like a ritual. Progress photos, scale weight, bloodwork, hunger, pumps, compliance, sleep, stress, and a paragraph of interpretation get bundled into a tidy summary. Useful, but incomplete. The real job is narrower: identify the one variable that now drives the next week.

The TroponinIQ knowledge base gives two useful examples of how this looks when done well. In one exchange, the client noticed that the same insulin dose used on a high day was now producing a noticeable drop in blood sugar sooner than expected. The response was not to add commentary or wait for more drama. The decision was to reduce the dose further on the next high day. That is triage: the signal changed, so the plan changed.

In another coaching example, appetite suppression from retatrutide was obvious enough that the coach did not pretend it was neutral. He noted the appetite drop, the added fatigue, and the tension between using it while food intake is going up versus using it when leaning out. His move was not to worship the tool. It was to hold judgment until more data and, given the athlete’s current body composition, lean out first while it was easy. Again, triage: decide what phase you are in, then decide whether the tool belongs there.

The check-in is a sorting problem

Most bad weekly reviews fail because the coach tries to answer too many questions at once. The better sequence is:

1. Is there a clear trend?
2. Is the trend behavior-linked, dosage-linked, or phase-linked?
3. Does the trend call for action now, observation, or no change?

That sequence keeps the coach from overreacting to noise. It also keeps AI from doing what AI is often good at: producing fluent summaries that feel decisive without actually being useful.

The KB examples point to a practical rule. If a variable is moving against the target and the relationship is clear, act. If the variable is changing but the direction or cause is not clean, watch and gather one more week of data. If the variable is stable, do not “optimize” it just because the check-in exists.

That rule sounds boring because boring is where decision quality lives.

What to change, what to watch, what to hold

A clean triage framework for weekly check-ins in physique coaching can be built around three buckets.

1) Change now

Use this when the signal is obvious and the plan is already telling you what the next lever is.

Example: a client reports that a previously tolerated insulin dose is now pushing blood sugar lower sooner. The plan changes immediately. There is no value in waiting for a prettier dashboard if the current dose is already behaving differently.

Another example from the KB: when appetite suppression is strong enough to interfere with current intake goals, the coach does not treat that as a feature to celebrate by default. If food is going up, a dose pause or reduction can be the right call. If the goal is to lean out and appetite suppression helps compliance, that same effect may be usable for a limited window. Same tool, different phase, different decision.

2) Watch one more week

Use this when the signal is real but not yet diagnostic.

The best example in the KB is the retatrutide discussion. The coach was not convinced by the blanket claim that it is “helpful in gaining” and did not accept the idea on slogan alone. He wanted more data. That is the correct posture for any new tool: short-term novelty is not proof of long-term value, especially when the observed effect is appetite suppression and fatigue. If a check-in produces an unclear tradeoff, the right answer is not a forced action. It is a better measurement window.

This matters for AI because models are prone to over-index on text confidence. A client can describe feeling flat, hungry, puffy, wired, depleted, or “off,” and the assistant can easily generate a plausible explanation. Triage forces discipline: unless the evidence points to a specific change, the answer is to watch the next data point you actually care about.

3) Hold steady

Use this when the plan is working and the check-in is just confirming it.

The KB’s nutrition examples are a reminder that not every interesting detail matters equally. Justin’s guidance on carbs makes the broader point: if the macros are nailed, the biggest results come from the basics, while the last few percent live in the details. Fruit can be fine around training, and on high days the exact carb source matters less because carbs are already high and insulin is elevated. In practice, that means many weekly check-ins should end with “no change” more often than coaches like to admit.

That is not laziness. It is restraint.

Why AI coaching rises or falls on this step

AI is good at pattern matching across many variables. That is helpful for flagging trends. But the failure mode is obvious: it can produce a tidy interpretation before the coach has decided whether the trend deserves action at all.

Weekly check-in triage is where a coach can use AI without becoming dependent on it. Let AI summarize the inputs, but make the human own the decision class:

• Change now
• Watch one more week
• Hold steady

That classification is better than a paragraph of generic advice because it creates accountability. If you change something, you know why. If you hold, you know what would have to happen to justify change. If you watch, you know which variable you are waiting on.

The Joe Webb exchange in the KB is another small but important example. The client noticed insulin sensitivity had improved enough that the usual high-day dose now dipped blood sugar earlier, so meals had to be pulled closer together. That kind of report is exactly what a good check-in should surface: the relevant operational change, not a narrative about the whole week. The coach’s job is to convert that report into the next clear action.

What good decision quality looks like in practice

A weekly check-in should be judged on whether it improves the next seven days.

If the check-in identifies an insulin dose that is now too aggressive, decision quality means the dose is adjusted and the next high day is safer and cleaner.

If the check-in identifies appetite suppression that may be incompatible with the current phase, decision quality means the coach chooses whether to lean out now, pause the tool, or wait for better information.

If the check-in shows nothing operationally important, decision quality means nothing changes.

That is the standard. Not more analysis. Not prettier language. Better decisions.

The bottom line

AI fitness coaching will not become valuable because it writes more polished summaries. It becomes valuable when it helps a coach triage weekly check-ins into the only three outcomes that matter: change, watch, or hold. The KB examples support a hard, testable claim: when the signal is clear, coaches should act immediately; when the signal is noisy, they should gather another week; when the plan is working, they should resist the urge to optimize for its own sake. In other words, weekly check-ins are not for explaining the week you had. They are for deciding the week you get.

Sources Used

• raw/_consumed/2026-05-31/kahunas-export/2026-05-31-w13-18m/clients/joe_webb___members-rksigkykimaxwmo_t4_e8nwvbtc2j0etleutkyysads.json
• raw/_consumed/2026-05-31/kahunas-export/2026-05-31-w13-18m/transcripts/rory_lazowski___members-c5balaovjbdoeefqmfuqdhh2tbpmfdu16lnf0tnrtmw.md
• modules/08-voice/kahunas-coaching-deep-voice.md
• modules/03-knowledge/kahunas-coaching-deep-nutrition.md