Check-In Triage and the 1-Week Insulin Response

Justin Harris
7 min read
troponiniq
blog
coaching

AI coaching is only useful if it helps you choose the right next action from a noisy weekly update: hold, reduce, or change course.

Check-In Triage and the 1-Week Insulin Response

AI coaching is only useful if it helps you choose the right next action from a noisy weekly update: hold, reduce, or change course.

Justin Harris’s check-in note on November 30, 2024 was blunt: the same insulin dose that worked the week before now dropped blood sugar enough to force an earlier meal, and the fix was a smaller dose on the next high day. That is a clean example of the mechanism that matters in coaching triage: changing insulin sensitivity across the week. The falsifiable thesis is simple: weekly check-ins are valuable when they catch dose-response drift early enough to change the next 7 days, and useless when they just produce commentary without a decision.

The real job of a weekly check-in

Most coaches talk about check-ins as if they are scorecards. They are not. A good check-in is a triage system. The question is not “How did the week go?” The question is “What needs to change now, what can wait, and what should stay the same?”

That distinction matters because bodybuilding prep and gaining phases are full of moving parts that do not fail all at once. Appetite changes. Meal timing shifts. Carb tolerance changes. Insulin sensitivity changes. Fatigue changes. The coach who sees those as separate decision points makes better calls than the coach who turns every update into a philosophy debate.

Joe Webb’s check-in is the clearest example in the KB. He reported that on his high day, the same insulin dose as the previous week dipped blood sugar noticeably, forcing him to move meal 2 up by about 30 minutes. He did not binge, did not blow the day, and did not need a dramatic reset. Justin’s response was practical: reduce the dose further on the next high day. That is triage done correctly. Notice the sequence:

  1. The body changed.
  2. The signal showed up in the check-in.
  3. The intervention matched the signal.
  4. The plan stayed narrow instead of becoming a larger rewrite.

That is what decision quality looks like in weekly coaching: respond to the actual failure mode, not the emotional noise around it.

Why AI fits check-in triage better than “full coaching”

AI gets overhyped when people pretend it replaces judgment. It does not. But check-in triage is exactly the sort of task where AI can be useful if it is trained to classify and route information instead of trying to be clever.

The reason is structural. Most weekly updates contain a few high-value signals buried under a lot of low-value text. Coaches need help with pattern recognition, not creative writing. If the athlete says:

  • appetite is lower after a new intervention,
  • fatigue is a bit higher,
  • meals are getting squeezed closer together,
  • insulin sensitivity looks better,

then the useful output is not a motivational paragraph. The useful output is a ranked list of actions:

  • hold steady if the signal is expected,
  • reduce the dose if the signal creates a safety or execution problem,
  • pause the change if it is working against the phase goal,
  • collect another week of data if the signal is ambiguous.

That is where AI coaching can earn its keep: extracting the actionable part of the check-in before the coach spends mental energy on the wrong problem.

Appetite changes are not always a win

Rory Lazowski’s retatrutide update shows why triage has to include phase context. He reported 2 mg on Friday and then essentially no appetite on Saturday and Sunday, even on low-carb days. He also reported more fatigue than normal. Justin’s reaction was not “great, more suppression.” It was more conditional: he didn’t love forcing appetite lower, noted that it was definitely lowering appetite, and then said to run with it while leaning out a bit while it was easy.

That matters because the same effect can be useful in one phase and annoying in another. A compound or tactic that makes food intake easier to control may be helpful when the goal is to get leaner. In a period where calories are supposed to come up, the same appetite suppression can become a bottleneck. The decision is not about whether the tool is “good” in the abstract. It is about whether it supports the current phase goal.

This is exactly why weekly check-ins should be triaged against phase, not against habit. If appetite is down and the athlete is trying to push food up, that is not a neutral update. It is a data point that changes the plan.

The off-season is where bad triage gets expensive

Justin’s recurring off-season theme in the KB is not “eat more” in the simplistic sense. It is teaching the body to digest and assimilate a massive amount of clean food so the athlete can handle more intake without runaway weight gain. He links that to two outcomes: better growth potential and a better metabolism heading into prep, which helps preserve more muscle during contest prep.

That framing is useful because it turns check-ins into a long-game audit. A weekly update is not just about whether bodyweight went up or down. It is about whether the athlete is becoming more or less capable of executing the next phase.

So the triage questions become:

  • Is appetite tolerance improving or collapsing?
  • Is the athlete handling the current food load without forcing substitutions or meal compression?
  • Are we collecting evidence that the current setup is building capacity, or just generating more stress?
  • Does the next decision preserve the athlete’s ability to execute the phase after this one?

This is where many coaching systems get sloppy. They chase scale weight or “look” changes and ignore whether the athlete is building the practical capacity to eat, recover, and adapt. Weekly check-ins should catch that drift early.

Decision quality beats intensity

The most common failure in coaching triage is overreacting to one variable and underreacting to the rest. A better system asks: what changed, what does it affect, and how fast does it need a response?

Examples from the KB line up neatly:

  • When insulin sensitivity changes and a meal lands too early, the response is a dose adjustment.
  • When appetite suppression is strong and calories may need to rise later, the response may be to pause or reduce the appetite-lowering tool.
  • When food tolerance is the bottleneck, the off-season priority is not novelty; it is digestion, assimilation, and consistency.

That is a decision tree, not a vibe.

The strongest AI coaching products will not be the ones that talk the most. They will be the ones that help coaches do three things faster and better:

  1. identify the dominant signal,
  2. ignore the irrelevant noise,
  3. choose the smallest effective change.

That last point matters. Weekly check-in triage is not about making the biggest move. It is about making the smallest change that addresses the actual problem without creating a new one.

What coaches should look for in a check-in

If you are using AI in coaching, the check-in template should not just collect data. It should force decision clarity. A useful weekly check-in asks:

  • What changed since last week?
  • What got better?
  • What got worse?
  • Did any intervention create a new bottleneck?
  • Is the athlete in a phase where we should push, hold, or back off?

The point is to make the next action obvious. If a tool cannot tell you whether to hold, adjust, or pause, it is not triage. It is trivia.

The KB examples support a straightforward conclusion: in bodybuilding coaching, weekly check-ins are only as good as the decisions they produce. The coach who can turn appetite shifts, blood sugar changes, and food tolerance into narrow next-step actions will outperform the coach who treats every update as a conversation. AI can help, but only if it is used as a triage engine, not a hype machine.

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