π Your week now arrives on its own β and says more
The weekly total used to sit inside the daily report: two lines, calorie balance
and weight change. It showed up every morning but changed once a week β by the
seventh morning nobody read it.
Now the week arrives by itself, on Mondays, as its own message. And it covers more
than the balance.
π Week in review: 15β21 September
π Weight: 82.0 β 81.0 kg (β1.0 over the week)
βοΈ Balance: β500 kcal a day β 5 of 7 days with a diary
Why a week and not a day. Daily expenditure is an estimate, and it moves
around: "2,800 yesterday, 2,400 today" usually means ordinary spread, not a change
in how you live. Over seven days the spread of the average drops threefold. That is
why weekly numbers can be compared with each other and daily ones cannot.
A week also answers questions a day can't. How many sessions there actually were β
a number, not "I train regularly". How many nights sleep was recorded at all. What
the diet looked like, rather than one Tuesday.
How many days each number stands on. Every line says what it rests on: "the
whole week" or "5 of 7 nights". That is not fine print, it is part of the number
itself β an average over two nights and an average over seven are different claims
and should not look alike.
Expenditure appears once, next to what you ate. Food from five days against
expenditure from seven would invent a deficit that never happened, so both come from
the same days β the ones with a diary.
Your coach gets the same summary for each active client, with the name in the
header, at their own hour and time zone β the same settings as the daily report.
If a value is missing for more than four days out of seven, the line
is gone entirely β you won't see a zero in its place. An average over two days isn't
an average. And if nothing adds up over the week, no summary arrives: an empty
message is worse than none. During a rest period the summary stays quiet too.
π€ The AI coach commentary is gone from the report
Every report used to carry a short note from the AI coach: what went well, what to
watch, what to do tomorrow. We have removed it β for clients and for coaches alike.
If you noticed the block disappear, nothing is broken.
Why. The commentary sometimes pointed away from the real cause. A recent
example: a report had no sleep in it, and the coach suggested turning on sleep
tracking in the app β while the sleep was missing for a different reason entirely,
the phone's export had stopped halfway through the day. The advice sounded sensible
and sent the person to fix the wrong thing.
There is a second reason: the calorie target the coach reasoned from. Our own
methodology says plainly that this estimate is not yet stable β for one person
within one month it can differ several times over. Building advice on it means
stating confidently what we do not know.
What stayed. Everything else in the report β the numbers, the targets, the
notes about incomplete days. Exactly one thing changed: the commentary is gone.
It will come back when we can stand behind it. We are not naming a
date, because there isn't one. For now the rule is simple: silence beats advice that
leads you the wrong way.
β³ The report arrives when the data is ready
Yesterday's report used to go out at a fixed hour β and half the time it showed not
the day but the start of it. The app on your phone sends data whenever iOS gives it
a moment; if it hadn't managed by morning, the report carried two thousand steps
from before breakfast instead of yesterday's fourteen. A month of measurements:
53% of reports went out on an unfinished day.
The note about partial data at the bottom did not help. People read top to bottom:
the number comes first and the conclusion follows it β and the conclusion was "this
thing is lying". Coaches had it worst: they look at someone else's day with no way
to check it.
Now the report waits for data, not for the clock. It arrives once the day is
complete β that is, once the phone has sent the whole of it. If the data still
hasn't come by the following evening, the report goes out anyway, but the warning
stands on the first line, ahead of every number.
A report on an incomplete day
β οΈ Part of the day only: the device stopped sending at 13:00.
βοΈ Weight: 73.6 kg
π¦Ά Steps: 2,315
And when the data does arrive, the product sends a corrected report on its own β no
need to watch for it or ask.
βοΈ Also: the weekly balance
The report now has a line about the week: how much you ate and how much you burned
per day on average, the difference between them, and β right beside it β how your
weight actually changed over the same days.
What it looks like in the report
π THIS WEEK
βοΈ Balance: β400 kcal a day β 6 of 7 days with a diary
π Weight: 74.9 β 73.6 kg (β1.3 over the week)
Why a week and not a day. Expenditure is a calculated figure, accurate to
Β±10β15%. On a daily 2,500 kcal that is Β±250β350, and the usual "ate minus burned"
for a single day sits inside that margin: its sign isn't even certain. Over a week
the random part of the error drops threefold, and the number starts to mean
something.
The weight beside the balance isn't decoration. The model says what should
have happened; the scale says what did. Any gap between those two lines is visible
at once, and you don't have to take the first one on trust.
The balance appears once a week has at least three days where both
sides are known. If the balance is smaller than its own margin of error, the product
says so β "about zero" β instead of drawing a deficit out of noise.
π Missing days no longer disappear quietly
The app on your phone sends data on its own, whenever iOS gives it a moment.
Usually that happens several times a day and there is nothing to notice. But if
the phone goes quiet for a few days β it sat discharged, the app got dropped from
memory β those days stay empty: the app sends a window of the last day or two and
no longer reaches back that far.
The product used to mention this exactly once: βyour device is quietβ. And the
moment the connection came back, it went quiet too β even though the days lost to
that silence stayed empty for good, and the only way to find out was a strange
number in a report a week later.
Now the product watches the days themselves, not just the connection. Once a day
it looks a week back, and if some day did not arrive in full, it names the date
and spells out what to tap.
What the message looks like
π No data for 12.03 and 13.03.
These days won't fill in on their own: the app sends a
window of the last day or two and no longer reaches back that far.
To recover them β Health Auto Export β Automations β
your automation β Date Range: set these dates and tap Export Now.
One setting that makes missing days fix themselves. The app has an export
window β how many days go out at once. Set Date Range to
Previous 7 Days, and any single export closes the whole week: the
phone gets online once, and whatever was missing arrives without you doing
anything. The guide now asks for exactly this setting, and the product checks the
data itself to see which window you have β and says so once if it is too narrow,
before it costs you anything.
A vanished metric shows up too. Sometimes the connection is fine and data
keeps coming, but one line is gone from it: sleep, steps or HRV stopped arriving.
Most often that means the device simply did not record them β the watch spent the
night off your wrist. The product will say so, naming the day you last had that
value.
Why this way and not something simpler. Apple Health data cannot be pulled
from a server: there is no cloud to ask β everything lives on the phone and leaves
it only when the app decides to send it. So the product cannot go and fetch what
it missed. What it can do is notice in time and tell you what to do about it β and
with a week-wide window there is usually nothing left to fix.
Sleep the device never recorded will not come back with any setting:
if the watch was off your wrist, there is nothing to restore. The product will tell
you what is missing, but it will not fill the day in for the device.
π― Targets now count data from every device
Four parts of the product talk about the same day: the report, the targets, the
Traffic light and the daily summary from your coach. The report learned to read
every device a while ago; the other three did not β they only looked at the strap.
While the strap is on your wrist you never notice. Take it off, and a day with
twelve thousand steps from your watch looked empty: the coach said there was no
data, the step target counted as missed, and the Traffic light went red.
Now all four look at the same full day, whichever device it came from β watch,
strap, scale, or the phone in your pocket.
Targets are also broken down line by line now. The daily summary used to
say "0/4 done", and that zero mixed two different things: what you did not do,
and what we did not measure.
This is how the daily summary looks
π― Targets: 2/2 done
β steps β₯ 10,000 β 12,000 actual
β sleep β₯ 7 h β 7.5 actual
βͺ protein β₯ 160 g β no data
The count is out of what was measured: two out of two, not two out of four.
A target with no data behind it counts as neither done nor missed β it says so
on its own line.
Why this matters more than it looks. "No data" and "you did not do it" are
different things, and the product no longer gets to confuse them: you make
decisions from these lines, and your coach sees them in their list. A day when you
walked twelve thousand steps cannot be called a day with no report.
If there really is no data, the product will say exactly that.
An empty day stays empty: we do not fill the gaps in and we do not substitute
an average.
π₯ One screen per client: sessions, money, progress
Coaching someone is more than the training itself. It is also "when did we last
meet", "how many sessions are left", "what did we agree on" and "what shape are
they in". All of that used to live in two different places in the bot, and getting
the full picture meant walking between them.
Now there is one screen per person, with everything on it.
π€ Maria
π° balance: β¬60 Β· π· session price: β¬30
Last session: 14.08
πͺ Session β¬30
π¦ Status Β· ποΈ Exercises
π Notes Β· π§ What we did
πΈ Payment Β· Β± Fix balance
π History Β· βοΈ Settings
The buttons are ordered by how often you use them: what happens every session is
on top, what you open once a month is at the bottom. Record a session β the balance
recalculates itself and the client gets a message with the new figure.
Clients who stopped coming no longer clutter the list. There is an archive
now: the person leaves your day-to-day list but not your records β sessions,
payments and notes stay where they were, and one button brings them back. The list
opens with the people you work with now, answering "who am I seeing today" instead
of "who has ever come to me".
Progress lives on the same screen. A client's benchmark numbers β working
weights, reps, times β open from their card: you see where to start today and what
changed since last time.
Renamed. "Ledger" is now "My clients" β that button really does hold your
people and their balances. "Adjustment" became "Fix balance": a manual change with
a sign β a penalty, a discount, an extra payment, a correction to an earlier
amount. Old buttons still work if they are sitting on your keyboard from before.
Also: the report stopped passing partial data off as a full day. If a device
sent only part of the day, the report now says so β up to which hour the data goes
and what to do about the rest. And daily expenditure no longer vanishes for people
who have not weighed in for a while: it is calculated from the last known weight,
and the report says which weight that was.
Apple Health can now be connected from the bot on your own: "π Integrations β
π Apple Health" gives you the address, tells you what will appear once connected,
and checks whether the data arrived.
The product keeps track of money, it does not process payments: no
card processing, no receipts, no tax records. The balance is your own record of who
owes what β always at hand.
π₯ Daily energy expenditure is now in your report
The food diary only answered half the question. "Ate 2,100 kcal" β is that a lot?
It depends on how much you spent, and expenditure was not in the product at all.
Now it is β and not as a single number.
The breakdown matters more than the total. Resting expenditure is what the body
spends on itself, and it barely moves day to day. Walking, daily life and training
do move β and you can see by how much.
A watch is not required. The figure appears on days it stayed at home too β
the phone in your pocket sees the walking. The one thing the calculation cannot do
without is your weight: without it there is no resting expenditure.
Also: workouts are now seen from two sides. When a session is recorded by
both the band and the watch, your report still shows one workout β but with
the name that reads better: the band may call a session
functional-fitness while the watch calls it "Strength training" β you
will see the latter.
Why it does not say "you are in a deficit." Expenditure and intake sit side
by side, but the product does not subtract one from the other. Claiming a deficit
needs calibration against your weight and food over several weeks β that is the
next piece of work, and promising it now would be dishonest.
This is an estimate, not a measurement. Accuracy is around
Β±10β15%: no device knows your true daily expenditure β wearables are off by up to
28% on energy. So comparing yesterday with today means little; the signal shows up
over a week.
π Your recovery score is now part of your data
Every morning Whoop shows one headline number β recovery, in percent. Until now
it lived only on the band: it reached us every night and was dropped during
parsing. It is kept now, and you can see it over time β next to what it is built
from: resting heart rate, HRV and sleep.
Two sleep figures arrived with it: how much sleep the device considered
necessary for that particular night, and how much of it was paying back
accumulated debt. Whoop's sleep need is not a constant: it moves with
yesterday's strain and with how much you missed earlier, and on some nights it goes
well past eight hours. So "slept 6.5 hours" says nothing on its own β now there is
something to compare it against.
The full history is there β not just from today: everything Whoop has sent
over the tracked period was re-parsed. So the trend is visible right away, not after
a month of collecting.
Why the bot gives no advice based on this number. Recovery is a proprietary
Whoop composite: the formula is not published and has not been independently
validated. Worth looking at, not worth deciding by. Our signals and thresholds
still come from resting heart rate, HRV and sleep β things the device measures
rather than infers. For the same reason recovery has no personal baseline: we do
not show deviations "from your normal" for it.
Tip. These numbers read better together than alone: 63% recovery
on a night when the device asked for 8 hours and you slept them is about
yesterday's strain, not about your sleep.
π½ See what made up your day
Until now, food in the daily report was four numbers: calories, protein, fat,
carbs. Now there is a line under them β Β«π§Ύ 12 items across 4 mealsΒ» β and a
button next to the report: π½ Show foods.
One tap opens the day inside the same message: breakfast, lunch, dinner and
snacks, each with the foods and how much of them, and the calories for that
meal. Tap π½ Hide foods and the summary is back. Nothing new arrives in
the chat.
Why behind a button. The report has to stay short β it is read on a phone,
and a coach scrolls through several clients in a row. By default nothing looks
different; the day opens up only when you decide to look into it.
The numbers got more precise. Fractions of a gram used to be dropped from
every food item, so the daily protein and fat came out slightly low. They are
now summed without rounding down, and protein and fat in past reports may have
risen a little. Nothing broke β it is the same day, counted properly.
Vacation no longer leaves a gap. In vacation mode the bot still says
nothing: no messages, no questions. Your connected services keep collecting data
the whole time, so when you come back those days are there.
Manual edits stick. If you corrected calories or protein by hand, the
overnight FatSecret sync no longer puts the old number back.
π‘ The button shows up only on days that have entries in the food
diary β with nothing to open, there is no button. Once entries are there, the
breakdown is in the report for that same evening.
β° Coaches can now choose when the daily report arrives
Until now, the daily client report always landed at 11:00. Now you can pick
any hour that suits you β before your morning sessions, or in the evening
when you have time to review the day properly.
You can also set your own timezone: if you're in Vilnius, Dubai or New York,
"1:00 PM" means 1:00 PM in your local time, not the server's.
How to set it up:
Open βοΈ Coach settings in the bot.
Tap β° Report time.
Pick an hour from the grid (06:00β22:00).
If needed, tap π Timezone and choose region β city.
Each city shows its current offset (e.g. Los Angeles (UTCβ7)).
π‘ By default nothing changes β it stays 11:00 Madrid time.
Adjust it only if you want a different hour. The setting is one per coach:
all your clients' reports arrive together at the chosen time.
The change takes effect from the next report. If the new time has already passed today,
the report will arrive at your chosen hour starting tomorrow.