The 7-Question Check-In Triages Better Than More Data

Justin Harris
7 min read
troponiniq
blog
coaching

Weekly coaching decisions improve when the check-in is built to sort signal from noise, not to produce a prettier dashboard.

The 7-Question Check-In Triages Better Than More Data

Weekly coaching decisions improve when the check-in is built to sort signal from noise, not to produce a prettier dashboard.

Justin Harris’s notes on prep show a recurring pattern: small changes in water intake, travel, and gut function can swing distension and perceived progress within days, which makes the weekly check-in a triage problem, not a data-collection problem. The underlying mechanism is simple: symptom triage beats raw volume of information when the goal is a better decision on a moving body. In practice, that means the best AI coaching check-ins are the ones that force a coach to decide what matters now, what can wait, and what is probably just noise.

The weekly check-in is not a report; it is a sorting task

Most coaches say they want “better check-ins.” What they usually mean is more complete check-ins: more photos, more bodyweight trends, more notes, more context. But completeness is not the same thing as decision quality.

A weekly check-in only matters if it answers three questions quickly:

  1. What changed since last week?
  2. What is the likely cause?
  3. What action should be taken before the next check-in?

That triage frame is especially useful in physique coaching because the variables are noisy. One coach note in the KB makes the point bluntly: a client can feel leaner, drop weight, and still be dealing with constipation and distension after travel; slightly less water on the drive back can leave him backed up for a couple days. The signal is real, but it is not always the thing the athlete first notices.

That’s the core problem with low-quality check-ins. They collapse distinct categories into one bucket called “how are things going?” A coach then has to reverse-engineer whether a scale jump is food volume, water, travel, digestion, sodium changes, or a genuine trend in tissue change. The more ambiguous the check-in, the more the coach is forced to guess.

Good triage separates outcome, cause, and urgency

The best weekly check-ins do not ask for everything. They ask for the minimum information needed to sort the case.

For a coach, the useful categories are:

  • Outcome: bodyweight trend, waist, photos, training performance
  • Process: compliance, appetite, sleep, digestion, stress, cardio completion
  • Urgency: anything that changes the next 48–72 hours

That structure matters because not all changes deserve the same response. A modest scale increase with stable visuals and normal digestion is not the same as a scale increase with bloat, constipation, and travel. A missed session is not the same as a persistent performance drop across several lifts. A client saying “I feel off” is not a plan.

If AI coaching is going to help, its first job is not interpretation theater. It is classification. The model should push the coach toward one of a few actions:

  • hold course
  • make a small adjustment
  • investigate a likely cause
  • escalate to direct human review

That is better than generating a long narrative that sounds helpful but doesn’t change the next decision.

A triage-first check-in reduces false alarms

One of the main failure modes in coaching is overreacting to temporary fluctuations. The KB examples point to why. Travel, slight water reduction, and prep-related gut slowdown can create a visual and scale problem that looks like fat gain, but isn’t. If a coach treats every fluctuation as a meaningful trend, the program becomes unstable.

Triage reduces that instability by asking first: is this likely a transient disturbance or a true directional change?

That distinction is practical, not philosophical. A coach who sees distension after travel should not immediately redesign the plan. A coach who sees the same pattern repeat across multiple weeks, across consistent conditions, may need to investigate the athlete’s digestion and routine more carefully. The check-in’s job is to surface repeatable patterns, not to amplify every temporary variance.

This is where AI can be useful if it is constrained properly. A system that summarizes a week into “weight down, physique improved, some constipation and distension after travel” is much more actionable than one that produces a polished paragraph about “overall positive momentum.” The first version helps the coach make a decision. The second version just sounds like one.

Decision quality depends on the question order

Weekly check-ins usually fail because the questions are ordered by convenience, not by decision relevance. Coaches often start with broad open-ended prompts and end up buried in details.

A better order is:

  1. Did the athlete do the plan?
  2. Did anything change that could distort interpretation?
  3. Did the main outputs move as expected?
  4. Is any issue urgent enough to override the normal process?

That sequence is the triage logic.

If the athlete complied and the expected outputs improved, the decision is usually to continue. If compliance was poor, you do not need a complex theory about stalled progress. If travel, poor sleep, or digestion issues were present, you discount some of the noise before changing the plan. If the athlete reports a persistent problem that affects execution, then the check-in should trigger human attention before the next week compounds the issue.

This is the same reason a good coach can look at a short update and know whether to press, hold, or back off. The point is not to build a bigger pile of data. The point is to sort the data into a decision.

What AI should do in the weekly check-in

If you are using AI in coaching, its best use case in weekly check-ins is not creative programming. It is triage support.

A useful AI layer should do four things:

  • Extract the few variables that matter
  • Flag inconsistencies or missing information
  • Cluster symptoms into likely buckets
  • Prioritize the next coaching action

For example, if a check-in says the athlete is leaner, down in weight, and has travel-related constipation, the system should not bury the lead. It should put the body comp trend first, note the confounder, and suggest a conservative interpretation.

If the check-in says energy is down, sleep is poor, training quality is slipping, and adherence is otherwise intact, the system should surface that as a likely recovery issue rather than a generic “monitor closely” note.

If the check-in is missing data that would change the interpretation, the AI should ask for that data rather than pretending the picture is complete.

That kind of support is valuable because coaches do not need more narrative. They need fewer bad decisions.

The falsifiable test

Here is the thesis in plain language: an AI coaching system that improves weekly check-in triage will produce faster, cleaner next-step decisions than one that merely increases the amount of information collected.

That claim is falsifiable. You can test it by comparing two workflows over several weeks:

  • Workflow A: broad, open-ended check-ins with long AI summaries
  • Workflow B: triage-first check-ins with a short decision prompt and explicit action categories

Measure which workflow produces:

  • fewer unnecessary plan changes
  • fewer missed confounders like travel or digestion issues
  • faster coach response times
  • clearer next-week action items

If the triage-first workflow doesn’t improve those metrics, it isn’t actually better. It’s just more structured.

What coaches should build instead

A practical weekly check-in should read like a decision brief, not a diary entry.

A strong template might include:

  • bodyweight trend
  • photos or key visual note
  • training performance summary
  • adherence estimate
  • sleep
  • digestion
  • stress/travel/confounders
  • one sentence: “What changed that matters most?”

Then the coach—or the AI assistant—should classify the week into one of four bins:

  • stable
  • improving
  • noisy but acceptable
  • needs action

That is enough to keep the process moving.

The real value of AI in coaching is not that it notices everything. It is that it helps a coach notice the right thing first. Weekly check-ins are where that advantage shows up most clearly, because the cost of bad interpretation is a week of wrong action. Triage is the difference between a coach who reacts to every fluctuation and one who makes decisions that hold up over time.

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-26/troponiniq_kb.md
  • raw/_consumed/2026-06-02/_GRAS/gras_strategy_training.md