Coaching engine

Coaching should come from patterns people can actually repeat.

GlucoMove coaching is grounded in repeated datasets. It is designed to help users notice when a routine was associated with a smaller post-meal rise, not to invent generic advice or unsupported exact claims.

Pre-meal Medication Meal Activity Post-meal
Coaching evidence

Coaching is strongest when the data structure is repeatable.

The minimum useful coaching signals come from pre-meal glucose, activity, and post-meal glucose. Meal and medication improve context, but are not required for every meaningful daily pattern.

Required

Pre-meal · Activity · Post-meal

Context

Meal level and medication settings sharpen interpretation.

Result

Messages that feel more grounded and usable.

Medication reminders

Medication appears in coaching only when users enable it in settings.

GlucoMove supports oral medication, GLP-1, and insulin. Insulin is divided into basal, mealtime, and premixed types. Users select from common usage combinations so the coaching card can surface reminders at the right moment without forcing full drug entry every time.

Oral medication

Shown only if medication reminders are enabled.

GLP-1

Handled as part of the configured medication context.

Insulin types

Basal, mealtime, and premixed insulin are separated clearly.

Common combinations

Users pick simplified real-world combinations instead of entering complex logic repeatedly.

Meal levels

Meals are simplified into five carbohydrate levels for repeatable daily use.

The system does not depend on precise nutrient math. Users choose a level that matches their meal pattern. Photos can be saved, and the Records page can later show meal information with thumbnail images for easy review.

Level 1

Lighter carbohydrate load, selected quickly without overthinking.

Level 2

Moderate carbohydrate amount for common everyday meals.

Level 3

Higher carbohydrate load, useful when users want to compare heavier meals.

Message style

Good coaching should be useful, grounded, and honest.

Ordinary datasets should speak about smaller rises, reduced change, and repeatable routines. Exact reduction language belongs to controlled tests, not to ordinary daily logs.

Level 4

Very high carbohydrate load for larger or heavier meals.

Level 5

Highest carbohydrate load for meals that need stronger comparison over time.

Prefer
  • The rise was smaller.
  • This pattern looked more stable.
  • This routine may be worth repeating.
Avoid
  • Exact mg/dL reduction claims from ordinary daily datasets.
  • Generic advice with no connection to user behavior.
  • Overstating certainty from one isolated result.
PC FINAL v12 · Clean redirects + www thank-you