A client opens the check-in with a screenshot of her watch. Seven days of sleep, a heart rate chart and a recovery score. She wants to know what it means.
You could spend an evening on that. You don’t need to. Wearables give clients a lot of numbers. You only need one of them and a good question.
Should you use wearable data in check-ins at all?
Yes, a little. A client’s watch notices things you can’t see between sessions, like a run of short nights. It can’t tell you why, or how the client feels about it. Use the watch for the “what”, and ask the client for the “why”.
What is the one-summary rule?
Ask each client to share one weekly summary, not a stream of data. Look for one trend you can act on: sleep running short, a drop in activity, a stretch of high stress. Then ask one question.
A good question is open and kind. “Your sleep looked short this week. How’s it been feeling?” is a coach’s question. “Your sleep score was 61” is a report.
One summary, one question
- ShareClient sends one weekly summary
- SpotYou pick one trend, not ten
- AskOne open question about how they feel
- AdjustYou change the week if it helps
What does it look like for one client?
Here is a made-up example. “Client B” is a client who usually trains three mornings a week and sends upbeat check-ins.
Her weekly summary shows her sleep was shorter than usual on four nights. That’s the one trend. Her check-in says the week was “fine, just busy”. You don’t open the heart rate chart. You write back: “Your sleep looked short this week. Busy how? Is it a one-off or the new normal?”
She replies that her team at work is short-staffed and she has been up late finishing things. Now you know the real story, which no chart could have told you. You move her hardest session later in the week and keep the other two lighter. That’s one number, one question and one change.
What if a client doesn’t wear a watch, or doesn’t want to share?
Then you don’t use one. A wearable is one way to start a conversation, not a requirement. Plenty of clients tell you the same thing in words: “I’ve slept badly all week.” Treat the data as optional. Never push a client to share something they’re not comfortable sharing.
What goes into an AI chat, and what stays out?
Nothing from the raw feed. Raw health data, such as heart rate readings, detailed sleep logs and anything tied to a name, is sensitive. It doesn’t belong in a general AI chat.
If you want help turning a trend into a question, write the trend yourself in one line. No name, no detail. For example: “A client’s sleep averaged under six hours this week and their usual mood is upbeat.”
Free download
Free: the Quiet Client Win-Back Pack
Six signs a client is drifting, three short messages for day 3, day 7 and day 14, and a way to draft each one from your own notes. Ten pages, sent by email after you confirm. You’ll also get the Less Admin letter: plain-English AI guides for personal trainers, no tech skills needed.
What is a prompt that keeps it safe?
Copy this and fill in your own one-line trend.
I'm a personal trainer. A client's wearable shows this trend:
[one line, no name, no raw data].
Write three friendly questions I can ask in a check-in to find out
how they feel and what might be behind it. Keep each under 20
words. Do not give medical advice and do not suggest a cause.
Pick the question that sounds most like you, or change it. The AI is only helping you find the words.
What do you do with what they tell you?
Adjust the week. If the sleep is short because of a new baby, drop the volume or move the hard session. If it’s short because of a worry, a quick call may help more than a tweak to the plan. If the answer mentions pain, dizziness or anything medical, that’s for the client’s doctor, not for the watch and not for a prompt.
What does this change about your week?
Less time scrolling through charts. More check-ins that start with a person instead of a report. Clients feel that. They came to you because someone paid attention, and one good question shows that.
The free Trainer Admin Audit shows how much of your week goes on check-ins and the jobs around them, with your own numbers. It’s a quick way to see where one hour could come back. For the full count, see how many admin hours hide in your training week, and for the weekly routine, check-in triage.
Common questions
Do I need to read my clients' wearable data?
No. A single weekly summary and one question is enough. You're not a data analyst, and more numbers rarely make a better check-in. The conversation is where the value is.
Can I paste a client's raw wearable data into an AI chat?
No. Raw health data is sensitive and doesn't belong in a general AI chat. Share a one-line trend you wrote yourself, such as 'sleep averaged under six hours this week', with no name and no detailed health information.
What if the data shows something worrying?
A worrying number is not a diagnosis, and neither of you should treat it as one. Ask how the client is feeling, and if it sounds like a health matter, suggest they speak to their doctor.
Which wearables does this work with?
Any of them. Fitbit, Apple Watch, Garmin, Whoop, Oura and the rest all produce a weekly summary. Ask the client to screenshot it or read you the headline numbers.
Get our new guides first on Google: add Less Admin HQ as a preferred source (opens in a new tab).
