Weekly Check-In Triage: 3 Decisions That Beat Noise

Justin Harris
7 min read
troponiniq
blog
coaching

AI coaching gets useful when it turns messy check-ins into faster, better calls on water, gut function, and photo confidence.

Weekly Check-In Triage: 3 Decisions That Beat Noise

AI coaching gets useful when it turns messy check-ins into faster, better calls on water, gut function, and photo confidence.

The most actionable pattern in the corpus is blunt: on prep, small changes in water intake, travel, and gut regularity showed up as visible distension fast, while the coach’s response was to triage the check-in around what was changing, not around a theory. The mechanism is simple hydrodynamics plus GI backup. That makes weekly check-ins a decision-quality problem, not a “more data” problem: if you cannot separate signal from noise, you will overreact to the wrong variable and miss the one that matters.

A useful AI coach should therefore do three things in sequence every week: identify the highest-probability cause, decide whether the issue is stable or moving, and pick the smallest intervention that matches the risk. That is the actual job. Anything else is commentary.

1) Start with the variable most likely to move distension

Justin Harris’s note to a client after a week with travel is a clean example of the logic. The client reported constipation and distension earlier than usual in prep, and the coach immediately tied the problem to water intake and travel: “On the drive back from KC over Memorial Day weekend I drank slightly less water than I usually would - still a lot - and I end up backed up for a couple days.” The earlier message went even further: “Guys get big, the gut dries out faster in prep, shit gets backed up (literally) and distention builds.”

That is a triage model, not a diagnosis. The coach is not treating every mid-prep distension complaint as a new food intolerance, a magical new supplement problem, or a need to overhaul the whole plan. He is ranking the likely causes. When the check-in contains travel, reduced water, lower bowel regularity, or any other obvious interruption, those get moved to the top of the list before you start changing carbs, training, or sodium.

For coaches, the decision rule is practical:

  • If the athlete just traveled, ask about water first.
  • If water changed, ask about bowel regularity next.
  • If both changed, do not pretend the photos are telling you a pure body-composition story.

This is why AI coaching can be helpful when it is used correctly. A model is good at pattern matching across many check-ins, but only if you feed it the right hierarchy. The weekly prompt should force the system to answer: what changed since the last check-in that could plausibly explain the photos? If the answer is “nothing obvious,” then you can move to the next layer. If the answer is “travel plus less water plus constipation,” you already have a working hypothesis.

2) Separate transient noise from trend

The best check-in triage does not confuse a one-week fluctuation with a real plan failure. In the same exchange, the coach describes the client as leaner overall and notes a “big weight drop,” while also acknowledging the distension. That matters. A week can contain both progress and noise. If you only look at the noisy part, you will make bad adjustments.

This is where weekly check-ins often fail in practice. Coaches see a bloated photo and reach for a bigger change. Or they see a good scale trend and ignore an obvious GI issue that will keep contaminating the next few check-ins. The better move is to ask whether the problem is transient, repeatable, or worsening.

A simple triage stack works:

  1. Trend: Is bodyweight, look, or performance moving in the intended direction?
  2. Interruption: Did travel, low water, meal timing, or a routine change happen?
  3. Symptom persistence: Has the issue lasted more than one check-in?

If the trend is good and the interruption is obvious, the rational move is usually to hold course and clean up the interruption. If the trend is bad and the interruption is absent, then you look harder at the plan itself. The point is not to be passive. The point is to avoid mistaking a short-term input problem for a program failure.

The Skip Hill thread gives another useful clue about decision quality under uncertainty: “I really don’t like prepping hard for longer than 16 weeks, so I wouldn’t push too much on my end at this point either way… I’d have zero concern about being in shape on time.” That is a coach deciding with incomplete information but a clear time horizon. He is not reacting to every photo by making the prep harder. He is using the broader arc of the prep and the known timeline to avoid unnecessary escalation.

AI can help here by summarizing the weekly arc instead of just the latest image. But it should do that in a boring way: what is the trend over the last 2–4 weeks, what changed this week, and what action follows from that combination?

3) Pick the smallest intervention that matches the issue

Once the triage identifies the likely cause, the intervention should be minimal and specific. In the David LaMartina example, the coach did not immediately respond with a sweeping diet revision. The language is more tactical: if the gut is backing up and distension is building, the immediate problem is function, not a grand new macro strategy. Even the joke about “avoid vicodin lol” is doing real coaching work: it points to a known constipation risk without dressing it up as mystery physiology.

That is the part AI coaching often gets wrong. It loves broad fixes because broad fixes sound decisive. Coaches, however, need the smallest change that improves decision quality. If the issue is travel-related water disruption, you restore routine. If the issue is bowel regularity, you stabilize that. If the issue is a true trend break, then you consider actual plan changes. But you do not escalate just because the check-in is emotionally loud.

For weekly triage, the intervention ladder should look like this:

  • First: normalize the obvious disruption.
  • Second: re-check the same variable next week.
  • Third: only then modify the broader plan.

That sequence protects against overfitting to one bad photo. It also makes the coach look smarter than the average “more cardio, less food” reflex, because the action is tied to a cause rather than to panic.

What AI should actually do in a weekly check-in

If you are using AI in a coaching workflow, the most valuable output is not a fancy summary. It is a triage note that answers four questions:

  • What changed?
  • Is it likely temporary or trend-level?
  • What is the most plausible cause?
  • What is the smallest action that tests that cause?

That forces the model to behave like a disciplined assistant instead of a confidence machine. It also gives the human coach the last word where it matters most: judgment. The machine can sort inputs; it cannot know whether this athlete is the kind who bloats from a day of low water, whether the issue repeats every travel week, or whether the photos are distorted by constipation rather than actual condition loss.

The falsifiable thesis is straightforward: weekly check-ins improve when coaches use AI to triage causes before they react, and they get worse when AI is used to generate more commentary than decision structure. The corpus examples point the same way every time—water, travel, and gut function first; big plan changes only when the trend demands it.

A practical weekly triage template

Use this on every check-in:

  1. Trend check: Weight, look, performance, adherence.
  2. Disruption check: Travel, water, routine, meal timing.
  3. GI check: Bowel regularity, distension, constipation.
  4. Decision: Hold, clean up routine, or adjust the plan.
  5. Next-week test: What would confirm or disconfirm the call?

If you do that consistently, AI becomes a better filter for signal. If you don’t, it becomes a faster way to make the same sloppy mistakes.

Sources Used

  • raw/_consumed/2026-05-31/kahunas-export/2026-05-31-w19-24m/clients/david_lamartina___members-tlssnsjthkmnhfqcscszce25acz_vhdm_x2_xdlpx_i.json
  • raw/_consumed/2026-05-31/kahunas-export/2026-05-31-w13-18m/clients/skip_hill___members-b7s-_d0oqqz4a1tadlvuztb0y_vzfqlr9c29tpakweg.json
  • raw/_consumed/2026-05-26/troponiniq_kb.md