Most coaches do not run bad check-ins. They run check-ins that take too long, which turns into the same thing by about client twenty. A review that costs you twenty-five minutes is perfectly good coaching at eight clients and impossible at thirty-five, so the reviews start arriving late, then in a batch on Wednesday, then with a one-line reply that took ten seconds to write.
The fix is not to care less. It is to decide in advance what you are looking for, look at it in a fixed order, and stop looking once you have your answer. This covers the cadence, the questions worth asking, the order to review in, and what to do with a client who sends you nothing.
If you want the definition and what belongs in the form itself, start with what a client check-in is. This is the process around it.
Work out your time budget before anything else
Take the number of clients you carry and the number of hours a week you are willing to spend on review. Divide.
That is your budget per client, and every decision below has to fit inside it.
That is enough time to read a form, look at a trend, decide on a change and write three or four sentences — but only if the form is short, the history is in one place, and you are not reconstructing last week from memory. It is nowhere near enough if you are opening a spreadsheet, a photo album and a message thread for every person.
Seven minutes also sets a hard limit on how much you can collect. Every question you add is a question you have to read 35 times a week and a question a client can skip. A twelve-question form you review properly beats a thirty-question form you skim, because the skim is where you miss the sleep score that explains the stalled weight.
Coaches usually discover this the wrong way round: they design the check-in when they have six clients and time to spare, then carry that form to a full roster and wonder why Sundays disappeared. Design the form for the roster you want, not the one you have. What breaks first as you grow is almost always admin per client rather than coaching skill, which is the same reason a full roster caps out where it does.
Choose weekly or fortnightly per client, not per business
Weekly is the default because it matches the rate at which you would actually change anything. Calories, volume, step targets — none of these should move faster than that, and waiting a fortnight to catch a problem means two wasted weeks instead of one.
Weekly is right for anyone in an active phase: fat loss, a gaining block, contest prep, a new client in their first three months, or anyone who has told you they struggle with consistency. The deadline is doing as much work as the data. A client who reports adherence on Sunday makes different choices on Wednesday.
Fortnightly suits a narrower group than most coaches think:
- Maintenance clients who are stable and have been for months.
- Long-term clients past the two-year mark who need contact more than correction.
- Low-cost or low-touch packages where the price cannot support a weekly review, provided the client knows that is what they bought.
Monthly is usually too slow. By the time a problem shows up you have lost four weeks, and the client has had four weeks of deciding their answers do not matter much.
The mistake is running one cadence across the whole roster because it is simpler to administer. It is simpler, and it means your steadiest client gets the same attention as the one who is quietly about to quit. If you do split cadences, stagger the fortnightly clients so half report on one week and half on the next. Otherwise you get a quiet week followed by a week with two rosters' worth of reviews in it.
Ask only the questions that change a decision
Run every question through one test: if the answer came back at either extreme, would you do something different? If not, the question is data collection, and you are paying for it in review time every single week.
That test kills a lot of standard questions. "How was your week?" changes nothing on its own — you already ask for the specifics. "Rate your motivation out of ten" changes nothing unless you have decided what you do at a three. "Any questions for me?" is the one clients answer with "nope" 90% of the time and is better as an open comment box you have already got.
What survives is a small set:
- Weight and one or two measurements, taken the same way each week. Trend, not the reading.
- Adherence, as counts. Sessions completed out of sessions programmed. Days on target with nutrition out of seven. Numbers, so you can compare them; not "pretty good".
- Sleep and energy, on the same scale every week. These move before the scale does and they are how you catch a client who is grinding themselves down.
- Average daily steps, if steps are part of the plan. If they are not, do not ask.
- Progress photos, weekly or fortnightly. Same lighting, same time of day.
- One open question about obstacles. "What got in the way this week?" is the line that explains everything else, and it is the only free-text field most check-ins need.
That is enough to make every decision you make on a Sunday. The question-by-question build, including scales and wording, is in the client check-in template.
Read the objective data before you read their words
This is the single change that saves the most time and improves the most decisions. Open the numbers first, form a view, then read what the client wrote.
Do it the other way round and you get led. A client opens with "shocking week, so stressed, I've been terrible" — and you spend the review talking them down, only to notice afterwards that they hit five of five sessions and lost 400 grams. Or the reverse: a cheerful paragraph about how great they feel, and you nearly miss that the weight has not moved in four weeks. Clients are reporting a feeling. The feeling matters, but it is context for the data, not a substitute for it.
The other reason to look first is that it forces a decision before sympathy has a chance to make one for you. You will still adjust for the stressful week. You will just adjust from a position of knowing what actually happened.
Here is the order, and roughly what each step should cost you:
| Step | What you look at | What you are deciding | Time |
|---|---|---|---|
| 1 | Adherence counts — sessions done, days on target | Whether there is anything to adjust at all | 30 sec |
| 2 | Weight trend across the last three or four weeks | Is the current plan producing the intended rate of change | 1 min |
| 3 | Measurements and photos against the previous set | What the scale is hiding — recomp, water, a stalled weigh-in | 1–2 min |
| 4 | Sleep, energy, hunger, stress | Whether it is sustainable for another four weeks | 30 sec |
| 5 | Their open comment | Why the numbers look like that | 1 min |
| 6 | Your reply — the change and the reason | What they do differently starting tomorrow | 2–3 min |
If adherence is under about 70%, stop. There is nothing to adjust, because you are not looking at the result of your plan — you are looking at the result of a plan that was not run. The conversation is about the barrier, and steps two through four can wait a week. Coaches lose entire evenings redesigning programs that were never followed.
Batch reviews into fixed blocks
Handling check-ins as they land is the costliest way to do it. Every submission that arrives mid-Tuesday costs you the switch out of whatever you were doing and the switch back, and you pay that thirty-five times a week.
Pick the block instead. Check-ins due Sunday night, reviewed Monday morning in one sitting. If your roster is big enough that one block is unmanageable, split the roster rather than the day: half report Wednesday and get reviewed Thursday, half report Sunday and get reviewed Monday. Two predictable blocks beat a week of interruptions, and it spreads your own load.
Two rules make the block work. First, do not open the check-in queue outside it — turn the notifications off if they pull you in. Second, do the whole client in one pass and do not come back. Reading a submission, deciding to think about it, and returning on Wednesday means you read it twice and reply late.
Speed matters more than length here. A three-line reply on Monday is worth more than a page of analysis on Thursday, because on Monday the client is still in the week you are describing and can act on it. By Thursday half the week is gone.
The mechanics of this are what a purpose-built check-in form is for. You build the form once, put it on a weekly or monthly schedule, and assigned clients are reminded at the time you set in their own timezone. Submissions land in one queue rather than a message thread, you can put two side by side to see what moved, and your review comment goes into the client's chat so the reply is part of the same step.
Decide: change, hold, or ask
Every reviewed check-in ends in one of three outcomes. Naming which one you are choosing is what stops a review from expanding into a rethink.
Change when the trend disagrees with the goal for two or three consecutive weeks and adherence is good. One flat week is noise — water, sodium, a late meal, the time of the month. Three flat weeks at 90% adherence is information, and it is the point at which calories, steps or volume should move. Change one thing at a time, or you will not know which one worked.
Hold when the plan is working, when the client has been on a change for less than two weeks, or when a single reading looks odd against an otherwise clean trend. Holding is a decision and it should be said out loud: "nothing changes this week, here is why, here is what I want to see next week". Silence reads as no decision at all.
Ask when the numbers and the words disagree and you cannot tell why. Weight up, adherence reported at 100%. Energy at two out of ten with nothing in the comment box. One specific question beats a guessed adjustment, and it is quicker than the adjustment you would otherwise have to undo.
| What you see | Outcome |
|---|---|
| Adherence under 70% | Ask — about the barrier, not the plan |
| Trend on target, adherence good | Hold, and say so |
| Flat for one week | Hold |
| Flat for three weeks, adherence good | Change one variable |
| Sleep and energy dropping for two weeks | Change — reduce the demand before it becomes a churn risk |
| Numbers and comment disagree | Ask one specific question |
The wording of that reply is its own skill, and it decides whether next week's submission is honest or performative — how to write check-in messages clients reply to covers it.
Handle the client who sends nothing
A missed check-in is a coaching event, not an admin one. It is also the earliest churn signal you get, which makes it the one worth reacting to fastest.
One miss is a life event. Send a short personal message — not another automated reminder, which the client has already ignored once — and ask about the week rather than the form. Two in a row means something has changed: they are avoiding the report because the week was bad, they have decided the service is not worth the effort, or they are already half gone. Clients rarely cancel out of nowhere. They go quiet first, and the check-in is where the quiet shows up.
What not to do is let it slide because chasing feels like nagging. If the check-in is optional in practice, it is optional, and the clients who most need the structure are the first to work that out. Set the expectation at onboarding — this is when it is due, this is what happens if it is missed, this is what I do with it — and then hold it. That expectation is the backbone of keeping online clients accountable rather than hoping they self-manage.
A pattern of misses that survives two direct conversations is a different problem, and it is worth naming as one rather than absorbing it for another three months. There is a version of this that ends in a hard conversation, covered in how to handle difficult coaching clients.
Answer every check-in, even when nothing changes
A check-in you do not act on is worse than not running one at all. The client spent fifteen minutes weighing, measuring, photographing and writing, and got silence back. What they learn is that their answers do not matter, and the next submission is shorter, then vaguer, then absent — and it is absent for exactly the client whose data you needed most.
This is why "hold" has to be said rather than implied. Nothing changing is a legitimate outcome about half the time, and it takes one sentence to communicate. What cannot happen is a week where the form goes in and nothing at all comes back.
Two practical guards. Keep every submission in a queue until you have responded, so an unanswered one is visible rather than buried in a notification you already swiped away. And set a response window you can hold — 24 hours, or 48 if that is honest — then say it to the client and meet it. A shorter reply delivered when you promised is worth more than a considered one that arrives whenever you got to it.
