Feature · Progress
Pull the whole history
Progress in Cookrange isn't a single weekly summary. Months of record accumulate in one long column: a 94-day streak you held through the summer, how many days you logged in December, how much calorie and protein you took in — all of it sits side by side in the same record.
A bad month stays in the record too
You might have only logged nine days in February. Those nine days stay there; empty days aren't filled in with a guess. The point of progress analytics isn't to make you look good — it's to show what's actually true.
The prediction is a sentence, not a promise
Based on your log, a prediction gets written for 30, 60 and 90 days out — not a chart, a short piece of text. It's not a guarantee: change your logging habit (log more or less consistently, say) and the prediction changes too.
Which input moves the prediction
How consistently you log feeds the prediction. Skip a week of logging and the prediction doesn't get corrected for you — it just reflects that the week ran on thin data. Same rule as the nine-day February above: gaps don't get filled in with a guess, the prediction is written from whatever is actually there.
Same record, read forward
The prediction doesn't run a separate forecasting engine — it's an interpretation of the same column. With a 412-day record behind you, the prediction is written directly on top of those 412 days: how many you logged and which month ran thin is already known, and the same data just gets read forward.
You choose how much your gym or coach sees
By default, your gym or coach sees nothing about your progress beyond your check-in count and peak hours. If you want them to see more, there are three tiers, each adding to the one before: your check-in frequency, streak and last visit · plus how consistently you're logging · plus the direction your weight is moving (up or down) — your raw weight history is never shared through this path. You turn each tier on separately and off any time; the moment you turn one off, whatever summary existed is deleted immediately, not after the seven-day cache window.
At the platform level: nobody reads your data without permission
A coach or gym reads only what the tier you've granted allows — with no tier granted, they read nothing. To generate a report, your name and streak data are sent to our AI provider — a cross-border transfer. A gym always reads its own check-in count too — that's outside the tier system, part of the default access. Even though thousands of users' columns sit on the same infrastructure, nobody reads yours without permission — all three roles are relationships that already exist in real life, just running on infrastructure a single user couldn't build alone.
Your weight log is currently kept on your phone only — it doesn't carry over if you switch devices.
Read how this data accumulates on the nutrition & planning and gym ecosystem pages, and how the plan updates through the day on the Cookrange AI page.