Weekly Check-In Triage: The 4-Bucket Decision Rule

Weekly Check-In Triage: The 4-Bucket Decision Rule

AI coaching is only useful if the weekly review turns messy data into the next right action.

The most useful coach reply in the KB is not a motivational line; it is a triage move: when insulin sensitivity improved enough that the same dose pushed blood sugar lower, Justin cut the dose and brought meals closer together instead of waiting for a worse week. The mechanism is simple: decision quality depends on separating signal from noise fast enough to change the plan before the mistake compounds. That is the real job of a weekly check-in, and the falsifiable thesis is this: if your AI check-in cannot sort a client into the right bucket by next action, it is not coaching, it is reporting.

Why weekly check-ins fail

Most check-ins collect too much and decide too late. Weight, steps, pumps, hunger, blood sugar, training performance, sleep, adherence, photos, digestion, stress—none of that matters if the coach cannot answer the one question that actually moves the athlete forward this week: do we hold, push, reduce, or redirect?

The KB examples show that Justin’s best decisions are not based on a single metric in isolation. They are based on pattern recognition plus a practical threshold for action.

Take the insulin example. Joe Webb reported that on a high day, the same insulin dose that had been fine the week before now dropped blood sugar noticeably, forcing the next meal earlier than usual. Justin’s response was not “keep monitoring.” The response was to reduce the dose, keep the meal spacing tighter, and avoid overreacting to a single event. That is triage: identify a changed condition, name the likely cause, and make the smallest adjustment that restores control.

Now compare that with the retatrutide discussion. The coach noted that it lowered appetite and added fatigue, and that if the goal was to bring food up, he might pause or reduce it until prep. But he also said he was holding judgment on the “helpful in gaining” claim because he wanted more data. That is a useful distinction for AI coaching: do not confuse a new tool’s effect on appetite with proof that it improves the current phase objective. Appetite suppression can be a feature in prep and a liability in a gaining phase. The weekly check-in should force that phase-specific distinction.

The four buckets

If an AI coach is going to triage well, it needs a simple structure. I would use four buckets:

1. Hold — nothing in the data justifies a change.
2. Push — performance, compliance, or recovery is stable enough to add a small demand.
3. Reduce — a current lever is overshooting, causing friction, or creating risk of bad decisions.
4. Redirect — the problem is not dose, food, or workload; it is the frame itself.

The point is not the labels. The point is the decision gate.

Hold

Hold is the hardest bucket for impatient coaches because it looks like inaction. It is not. It is a deliberate refusal to make a change when the pattern is still within expected variance.

The KB nutrition guidance on fruit shows this same logic at a lower stakes level. Justin says he would be surprised if a client saw a noticeable difference over a year even if all carbs came from fruit, because the vast majority of results come from nailing macros. That means many weekly check-ins should end in hold, not because details never matter, but because the current issue is too small to justify interference.

Hold protects decision quality. If every small deviation triggers a change, the athlete never gets a clean read on what actually worked.

Push

Push is appropriate when the pattern is stable and the current load is no longer the limiting factor. In practice, this usually means compliance is consistent, recovery is acceptable, and the athlete is not showing signs that the current plan is stressing the wrong system.

Justin’s off-season framing in the podcast excerpt is blunt: the goal is to teach the body to digest and assimilate a massive amount of clean food, and improved food handling supports more muscle growth and a better metabolism later. Whether or not one agrees with every bodybuilding premise, the decision rule is clear: if the athlete is handling the current intake well, the next move is often to progress food or workload gradually, not to micromanage.

Push should be small. The KB repeatedly favors moderation over drama. The target is not a heroic leap; it is a controlled increase that preserves the ability to interpret the next check-in.

Reduce

Reduce is where AI coaching can add real value, because many athletes only notice a problem after the problem has already narrowed their options.

The retatrutide case is the cleanest example. Appetite dropped hard; fatigue increased; food intake became harder to justify in a gaining context. That is not a cue to “wait and see” for several more weeks. If the current lever is reducing appetite in a phase where food volume is the job, the lever may need to come down.

The insulin example is similar. If a high-day dose is now producing a lower-than-expected glucose response, the coach reduces the dose and tightens meal timing. The decision is not about being conservative. It is about preserving the quality of the day.

Reduce is also where too many AI systems go wrong by optimizing for one metric and ignoring downstream cost. Lower appetite is not automatically good. Lower glucose is not automatically bad. Lower body weight is not automatically progress. The check-in has to ask: what is this variable doing to the phase objective right now?

Redirect

Redirect is the bucket for cases where the issue is not the visible symptom.

This matters because weekly check-ins often become a loop of superficial fixes: adjust calories, tweak cardio, change meal timing, and hope the pattern resolves. But sometimes the wrong lever is being pulled. In the KB, Justin’s response to challenging situations is often to step back and evaluate whether the current tool belongs in this phase at all. With retatrutide, the key question was whether a strong appetite suppressant belongs in a gaining block. With growth hormone in the voice examples, the question was whether the bodybuilding upside was worth the blood sugar tradeoff, and the answer depended on whether the reduced sensitivity meant the current dose was too much.

That is redirect thinking. The right move may be to change the phase, the tool, or the priority rather than merely nudging a number.

What AI should actually do in check-ins

An AI coach should not try to sound profound. It should do four things well:

• Extract the dominant change since last week.
• Classify the change as hold, push, reduce, or redirect.
• Name the mechanism in one short phrase, not a paragraph.
• Recommend one next action that fits the phase.

That sounds obvious until you look at how many systems fail on it. They summarize instead of deciding. They list every number instead of identifying the one that changed the plan. They produce a paragraph of acceptable advice and still leave the coach with no action.

A weekly check-in is not an essay contest. It is a triage problem.

Decision quality beats detail volume

The KB keeps pointing to the same lesson: good coaching is not the accumulation of more data; it is the ability to make the smallest correct move at the right time.

• If blood sugar drifts lower on the same insulin dose, reduce the dose.
• If appetite collapses in a food-up phase, reconsider the appetite suppressant.
• If macros are on point and the issue is minor, hold.
• If the athlete is stable and ready, push gradually.
• If the symptom is not the real problem, redirect.

That is what AI should help with. Not endless personalization theater. Not a wall of metrics. Just a cleaner weekly decision.

My falsifiable claim is unchanged: the best AI fitness coaching will not be the system that predicts the most; it will be the system that reliably places the athlete into the right weekly bucket and takes one correct action before the next check-in.

Sources Used

• raw/_consumed/2026-05-26/troponiniq_kb.md
• raw/Justin_TT1.txt
• 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