Friday is check-in day, but one client leaves the form blank. You send a reminder, wait and postpone reviewing their support. A week later, you still do not know whether the form is too long, the client is stuck or the message was never seen.
Start by restoring contact rather than enforcing form completion. You need information to tailor support. A blank form does not explain why that information is missing.
Check whether replying is possible
Verify the link and access, the expected reply time and whether the client understands how you use their answers. Ask a colleague to read the instructions. Do they explain the time needed and where to get help?
Check the contact agreement before messaging outside the usual channel. Sending the same question through several channels makes the conversation harder for both parties to follow.
Choose a small next step
| Observation | First question | Do not assume |
|---|---|---|
| One missed form | Could you open the check-in? | The client lacks motivation |
| Many repeatedly blank questions | Which question is hardest to answer? | Every field is essential |
| Replies through separate messages | Which feedback method is manageable? | More channels are needed |
| No reply after agreed follow-up | When and how will we try again? | The contract ends automatically |
A brief reply can bridge the gap to the next conversation. Do not silently change agreed services or payments because a form is missing.
Message 1: make replying easy
Hi [name], I have not received your check-in for [period]. Can you open the form? If it feels too much this week, you can briefly reply here: what went well, what got in the way, and what help would you like? Then we can agree a useful next step.
Ask only for information needed now. Do not require a sensitive personal account to explain an administrative delay. Follow appropriate professional routes for matters outside your expertise; a check-in is not a diagnosis.
Message 2: agree how to continue
Hi [name], I have not heard back about my message from [date]. I would like to check whether our current contact method works for you. Please let me know by [time] whether [specific contact option] suits you. I will then follow our agreement for [next step]. If you need a copy of that agreement, I can resend it.
Choose timing and follow-up from the existing arrangement, not a universal reminder frequency. Describe only a step you will actually take.
Shorten the check-in without losing its purpose
Start with three questions: what worked, what blocked progress, and what support is needed? Add a question only when its answer informs a specific coaching decision. Explain what you do with responses and when the client can expect yours.
Shortness is not the goal itself. If you repeatedly need to ask for essential context afterward, the questions still need work. Ask clients which wording is unclear and whether the timing is practical.
A four-week contact log
For each planned contact, record expected timing, reply received, channel, agreed next step and coaching time used. Avoid extra sensitive details when a process status is enough.
After four weeks, compare on-time replies with expected replies. Review repeated contact and coaching time per client too. A higher completion rate matters only if it makes support clearer or more workable.
Frequently asked questions
Should everyone receive the same form?
Not necessarily. Keep a comparable core where useful, while tailoring questions to the goal and agreed support.
How many reminders should I send?
Use an agreed contact rhythm and clear next step. No universal number solves every client problem.
Can I change the programme without feedback?
An absent reply does not establish that a change is appropriate. Determine what information your expertise and agreements require before deciding.
Test one contact cycle
Choose five clients and check that each question leads to a useful action. Review your organisation with FITsociety or book a demo with your current check-in. Discuss the workflow without assuming automated reminders or decisions.
