The 4-Week Check-In Triage Loop

The 4-Week Check-In Triage Loop

Weekly check-ins work when they convert noisy updates into one decision: hold, trim, or push.

The clearest coaching win in the Kahunas corpus is boring on purpose: Rory’s 2 mg retatrutide dose sharply lowered appetite within days, and Justin’s response was not to chase the sensation but to keep the decision tied to body-comp phase and food intake rather than hype. Mechanism-wise, that’s appetite suppression meeting decision gating. The falsifiable thesis is simple: in AI fitness coaching, weekly check-ins are only valuable if they force the right next move faster than the client’s own bias would; otherwise they just generate more status updates.

Weekly check-ins are not “how are we feeling?”

A lot of coaching systems treat the weekly check-in like a relationship tool: collect vibes, confirm compliance, move on. That is too weak for physique coaching and too weak for AI coaching. The useful version is a triage loop. Every check-in should answer three questions in order:

1. Is the current plan still safe and workable?
2. Is the trend moving the right way?
3. What is the smallest change that improves decision quality without creating noise?

That order matters. If you start by changing macros, adding cardio, or tweaking supplements before you know whether the issue is appetite, recovery, digestion, insulin sensitivity, or simple execution drift, you are not coaching. You are guessing with better branding.

The sources here show that good coaching decisions are usually not dramatic. They are conditional, phase-aware, and sometimes deliberately conservative.

The clearest signal is often appetite, not weight

Rory’s retatrutide note is useful because it shows what a check-in is actually for. The report was not “I feel different.” It was: 2 mg on Friday, appetite almost gone through Saturday and Sunday, and fatigue a bit higher than normal. Then came the practical question: if calories are going to rise, pause or reduce the dose; if prep is coming, maybe keep it; if smaller doses help gaining, maybe that has value, but the coach is not ready to accept that claim without better data.

That is what decision quality looks like. The first reading is not “this drug is magic.” The first reading is “appetite is now a stronger constraint than hunger.” Once that happens, the weekly check-in changes from general monitoring to triage. You ask whether the appetite drop is helping adherence or sabotaging food intake, and whether the current phase wants lower appetite or more intake.

For coaches, the lesson is not about retatrutide as a product. It is that appetite is a leading indicator. If appetite falls hard and the athlete’s phase still requires food loading, the check-in should trigger a phase call, not a motivational speech. If appetite suppression improves control during a cut, the same report can justify staying the course. Same signal, different decision, because the triage question is phase-specific.

The second signal is insulin sensitivity drift

Joe Webb’s check-in is even more instructive because it shows a small physiological shift creating a real program change. He reported that his high-day insulin sensitivity seemed improved: the same insulin dose as the prior week pushed blood sugar lower than expected, so he had to bring meal timing forward and later planned to reduce the dose further on the next high day.

That is a clean example of why weekly check-ins should be built around threshold changes, not generic compliance scores. The athlete did not say “everything is fine” or “everything is broken.” He noticed a timing change at the same dose. That is exactly the kind of detail a check-in should surface. It lets the coach distinguish between a true trend and a one-off problem.

The coach’s job here is not to celebrate the report or panic about it. It is to decide whether the new pattern is stable enough to act on. If the same dose now requires meals sooner, the plan is no longer matched to reality. That calls for a small correction, not a redesign. The smaller the correction, the easier it is to interpret the next check-in.

This is where AI tools can help if they are used properly. An AI system can sort the report into categories: appetite, timing, recovery, digestion, load tolerance, and trend direction. But it cannot be trusted to decide the answer unless it is anchored to the athlete’s phase and the coach’s thresholds. Without that, the model is just very fast at producing plausible confusion.

Justin’s actual coaching pattern: don’t move first, classify first

Across the knowledge base, Justin’s pattern is consistent: classify the situation before making the change. In the voice exemplars, he describes growth hormone as a real tradeoff when blood glucose worsens and explicitly frames the response as a response-curve problem with a point of diminishing returns. When sensitivity is reduced, the current dose is likely too much; the move is to drop it and watch blood glucose over a month or two. That is not hype. That is triage.

The same pattern appears in nutrition periodization. In the deep nutrition module, fruit is not treated as a moral issue. It is a small variable that matters mainly at the edges. Macros do most of the work; details matter in the last few percent. Pre- and post-workout fruit is fine up to about 50% of the carbs in those meals, and on high days sugar matters less because carb load and insulin are already high. Again, the decision is phase-aware and proportionate.

That is the standard weekly check-in should copy. The point is not to collect more data for its own sake. The point is to make the next action proportionate to the signal.

What a good check-in triage system asks

A useful weekly check-in for coaching, whether human-led or AI-assisted, should force the report into one of four buckets:

• Hold: The trend is acceptable and the client is executing. Do not create noise.
• Trim: A constraint is starting to bind, such as appetite suppression, recovery drag, or insulin sensitivity shifting. Make a small corrective move.
• Push: The athlete is absorbing the current workload and the trend supports escalation.
• Pause and reassess: The reported signal conflicts with the current phase or the data are too muddy to trust.

The win is not in the number of questions asked. It is in the number of decisions that become obvious after the questions are answered.

That also means the check-in needs a stable hierarchy. If weight is down but adherence is collapsing, the answer is not automatically “good progress.” If appetite is gone but intake needs to rise, the answer is not automatically “great tool.” If insulin sensitivity improved, the answer is not to keep the old dose because it worked last week. Weekly check-ins exist to catch when last week’s correct plan is no longer correct.

Why AI should help triage, not replace it

AI coaching is strongest when it compresses information, not when it impersonates certainty. A good model can flag patterns: appetite drop plus fatigue, insulin timing drift, worsening tolerance, stable execution with no trend change. It can sort the noise before the coach reads the message. That is useful.

But the decision still has to be anchored to the actual coaching logic visible in the sources: phase first, trend second, smallest effective change third. That logic is what keeps a weekly check-in from becoming a box-checking ritual.

If your AI system can surface the right bucket faster than a human can read 20 messages, great. If it cannot tell the difference between “keep running it” and “this no longer matches the phase,” then it is not improving decision quality. It is just improving throughput.

The best triage loops are not impressive. They are repeatable. They keep the coach from overreacting to every report, and they keep the athlete from waiting too long to make the one change that matters.

Sources Used

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