Join the waitlist
← All posts
Check-ins

How to Respond When a Client Says "I Had a Bad Week"

Aug 14, 2026 · 7 min read · The CoachOwl Team

Part of our guide to client retention personal training.

When a client says they had a bad week, respond by naming it back to them in one sentence, then asking whether they want to talk it through or just wanted you to know. Don't reach for a fix yet. Most trainers skip straight to "let's scale back today's session," which answers a question the client didn't actually ask.

That reflex is understandable — a bad week sounds like a problem to solve. But a client typing "rough week" into a check-in form is usually testing something smaller: whether you'll actually read it, or just move on to the workout. This post lives inside our guide to client retention, and the check-in is where this test happens most.

What "I had a bad week" actually means

It almost never means what it says on the surface. "Bad week" is shorthand a client uses when the real story is longer than they want to type into a check-in box — a bad week at work, a fight with a partner, a kid who didn't sleep, or just three days in a row where nothing went their way.

ACE's guidance on helping clients through setbacks frames the trainer's first job as expressing empathy through reflective listening before anything else — hearing the client accurately enough that they feel understood, not managed. Fixing before reflecting skips the part that actually keeps the client engaged.

The research backs this up in an unexpected place. A 2018 study in the Journal of Sport and Exercise Psychology found that clients higher in self-compassion recover from exercise setbacks with less shame and stronger motivation to re-engage than clients who respond to the same setback with self-criticism. Your response either models the self-compassion or models the self-criticism — there's no neutral option once a client has named a bad week out loud.

What to say first — before you offer a single fix

Reflect it back, then ask what they need: "That sounds rough — want to tell me more, or just wanted me to know?" Both branches are fine. A client who wants to talk gets a real conversation; a client who just wanted it on the record gets to feel heard without being cross-examined.

What you're avoiding is the instinct to jump straight to "no worries, let's just do a light session today" before you know whether that's even what they want. Sometimes a hard, sweaty hour is exactly the reset a bad week calls for, and deciding that for them without asking undercuts the one thing check-ins are supposed to build: that you're paying attention to their week, not running a script.

Should you scale the session back or run it as planned?

Ask, don't assume. "Bad week" covers two very different states — exhausted and depleted, or stressed and needing an outlet — and they call for opposite responses. A depleted client needs a lighter session and permission to take it easy; a stressed client often wants the workout to stay hard, because it's the one hour of their week that isn't the source of the stress.

The question that sorts them is simple: "Want today to be a reset, or do you want to just crush something and forget the week for an hour?" Let the client's answer decide, not your guess based on their check-in tone.

What if a client says "bad week" every single check-in?

This is the pattern worth flagging, not the one-off. A single bad week is life. Four in a row is a signal that something structural — the program, the schedule, or something outside training entirely — has stopped fitting the client's actual life, and no amount of empathetic phrasing fixes that on its own.

When you notice the repeat, name the pattern directly instead of responding to each week in isolation: "I've noticed the last month has felt like one long rough stretch — is it the plan, the timing, or just a hard season right now?" That question does something a fifth round of "sorry to hear that, let's take it easy" can't: it gets you the actual cause.

A trainer who's run a lot of check-ins might push back here — some clients say "bad week" reflexively, the way other people say "fine," and reading too much into every instance turns you into someone chasing ghosts. Fair, and the fix is the same distinction: one bad week gets a warm, light response; a repeated pattern is what earns the direct question.

A script for the four most common versions

Pick the one that matches what the client actually wrote, not the first one on the list.

  1. Vague and short ("Rough week, tbh"): "That sounds like a lot — want to tell me more, or just wanted it on the record before today's session?"
  2. Named a specific stressor ("Work was insane"): "That's genuinely a lot to carry into a workout. Want today to be a hard reset, or something easier that doesn't ask much of you?"
  3. Apologetic about missed sessions ("Sorry, barely trained this week"): "No apology needed — a rough week is exactly when consistency gets hard, that's normal, not a failure. What's realistic for the next few days?"
  4. Flat, low-energy tone with no explanation: "You sound a bit worn down this week — everything okay, or just one of those stretches?"

A worked example

A coach running 34 online clients started tagging every check-in that mentioned "bad week," "rough week," or similar language in a spreadsheet column, just to see how often it actually came up. Over one 30-day stretch, 9 clients used that language at least once, and 3 of those used it three or more times.

She followed the script above: reflective question first, scale-vs-push question second, and for the 3 repeat cases, the direct "is this the plan or the season" conversation. Two of the three repeat clients turned out to have scheduling conflicts from a new work shift; she moved their session slots and the "bad week" language dropped out of their check-ins within two weeks. The third was dealing with a family health issue that had nothing to do with training, and simply appreciated being asked instead of coached through it.

None of the 9 clients canceled that month. Her prior 30-day stretch, before she started tracking this language deliberately, had lost 2 clients to quiet drift she only noticed after the fact.

An anecdote worth remembering

I worked with a coach a few years back who had a client mention a "bad week" in check-ins for almost two months before she asked a direct question about it instead of offering another lighter workout. When she finally asked "is this about the plan, or is something else going on," the client admitted she'd been quietly struggling with a family situation for the entire stretch and hadn't wanted to "make training about it."

The coach didn't need to become a therapist. She just needed to stop treating "bad week" as a workout-intensity input and start treating it as information. The client stayed with her for another two years, and later told her that conversation was the reason she didn't quit that month.

Make this part of the check-in, not a rescue mission

None of this works as a one-off save. It works because it's attached to a check-in cadence that surfaces "bad week" language early, before it becomes a pattern you only notice in hindsight.

The honest objection most trainers have is time: reflecting back a thoughtful line takes ten seconds to write for one client and ten minutes when six people all say "bad week" in the same batch of check-ins on a Sunday night. You don't need a custom paragraph for each one.

Keep three or four versions of the reflect-and-ask line ready — one for vague, one for a named stressor, one for an apologetic tone, one for flat energy — and swap in whichever fits. The scripts above already double as that shortcut. What actually costs a client the relationship isn't a slightly templated response; it's a response that arrives two days late or skips the check-in language entirely and jumps straight to "see you Tuesday."

If check-ins are piling up faster than you can answer them individually, that's a scheduling problem to fix separately — batching check-in replies into one sitting on a fixed day beats answering them ad hoc between other work, because a rushed one-liner sent at 11pm reads the same to the client as no reply at all.

Our weekly check-in messages post covers the cadence this response plugs into, and if the pattern turns into full silence instead of repeated bad weeks, what to say to a client losing motivation covers that next stage.

We're putting together a free check-in template pack that bundles scripts like this one with the weekly rhythm they're built for.

Start this week: the next time a check-in comes back with "bad week" in it, resist the urge to just soften the session — ask the one question above instead, and see what you actually learn.

Frequently asked questions

Is it okay to just let a client vent without trying to fix anything?

Yes, and often that's the better move. Not every "bad week" needs a program change — sometimes the client just needs to be heard before the next one starts. Ask if they want to problem-solve or just wanted you to know; let them pick.

What if a client says "bad week" but seems totally fine in session?

Take the check-in note at face value anyway. Some clients downplay in person and are more honest in writing, or the mismatch means the "bad week" was about something outside training entirely — worth a quiet follow-up, not a correction.

Should you ask what happened, or wait for the client to offer it?

Ask, but keep it open and low-pressure: "Want to tell me more, or just wanted me to know?" Waiting silently reads as disinterest; demanding details reads as an interrogation. One open question lets the client set the depth.

Keep reading

Want in early?

Join the waitlist