The measured burn engine

Standard TDEE calculators guess from stats, and two identical-looking people can burn hundreds of calories apart. Starting targets from a guess is fine; keeping them there is coaching malpractice once real data exists.

FuelPath measures instead: the client's own food log and weigh-ins tell you what their body actually does.

Over a rolling 28-day window: average logged intake, minus the weight trend converted to calories (a pound is about 3,500), equals measured daily burn. Eating 2,400 while losing half a pound a week means burning about 2,650.

Only credible days count (800 to 6,500 kcal logged), and the engine needs enough logged days and weigh-ins spread across the window before it trusts itself; until then it shows warming up. Consistent under-logging cancels out of the math, which is why the number beats any wearable's calorie guess. Wearable calories are deliberately ignored.

Each phase's anchor is measured burn times the phase multiplier. When a client's saved target drifts from their anchor, the gap shows on their page and the expenditure dashboard, with an apply button.

Applies move in steps capped at 250 calories so a thin data window can never crash someone's intake, and a red checkbox makes you acknowledge thin data before applying. Every change is audit-logged and reversible with Undo on the athlete's Macros page.

You do not have to watch for the moment their engine wakes up. FuelPath notifies you twice: once when a client's burn first becomes readable (roughly two weeks of logging and weigh-ins), and again when the window is solid enough to set targets from without the thin-data tick (roughly a month). Both land as a notification and a Needs Attention flag, and both link straight to their expenditure breakdown. The targets they started with came from a calculator; these are the two moments to replace them with measured ones.

Opening a client leads with the same read: a Macro review card with their target, the measured anchor, and the gap, louder past 250 calories. It also separates the two problems that look alike. Eating to plan with a big gap means the target is wrong; averaging well off their own number means the gap is adherence and a conversation beats a recalculation. Changing that phase's macros clears the card.

Cut stalled with a ready engine: trust the measured number over the calculator, apply the anchor step, and hold for two weeks before judging.

Build stalled: same move upward; the surplus only exists relative to measured burn. Engine warming forever: the client is not logging or weighing enough, which is a compliance conversation, not a math problem.

Client one-liner when they ask why targets moved: your own data showed your burn, so your plan now matches your body, not a formula.