Client Check-Ins Without Google Forms: A Complete Workflow
Nour
Founder, Coachful
You can manage client check-ins without Google Forms by connecting a short, purposeful reflection with the coaching relationship and a response the client can actually use. The important work starts before choosing the form: agree what the check-in is for, when someone will read it and what happens after submission.
Coachful is our #1 recommendation for this connected coaching check-in workflow. Original forms or worksheets can sit alongside the client's preparation, tasks and coaching record. The coach still needs to read the answer, choose the appropriate response and send any promised feedback through an agreed channel.
This guide develops a small manual workflow before adding recurrence or automation. Its completed fictional pilot includes a coach-private review mistaken for client feedback, an actual repair, a useful personal practice change and a missing response that remains unknown. A completion rate alone would hide much of that story.
Compare a complete process, not just two form builders
Google's current Forms documentation supports viewing summaries and individual responses, linking responses to Sheets, downloading CSV data and receiving notifications of new submissions. Those are useful capabilities. A practice that already uses them responsibly may have a process worth retaining.
The relevant question is how the whole check-in works for this service. Where does the client find it? Who reads it? Does the person know whether a reply is included? How are questions, missed submissions and changes handled? Which record is authoritative when a response is corrected?
Compare the actual requirements and administration, including any existing templates, records, permissions and integrations. Do not present a new interface as a complete migration or assume an export preserves the meaning of every field and historical response.
Keep a clear boundary between old and new collection. The example below starts a new, agreed two-date pilot for four existing clients. It does not import Google Forms response history, delete an old spreadsheet or claim that every use of Google Forms should stop.
For the wider service agreement, the client onboarding guide can help connect preparation, delivery and follow-up. A check-in should serve that agreement rather than silently add a new service promise.
Write a check-in brief before writing questions
Use a short operational brief. It should answer the same practical questions a client would ask before spending time on the form.
| Decision | What to make explicit |
|---|---|
| Purpose | The chosen action or question the reflection will help review. |
| Period | The dates or activity being described, not an ambiguous “recently”. |
| Effort | A realistic expected response length and an alternative if needed. |
| Audience | Who can read the submitted answer and any later feedback. |
| Response | Whether feedback is included, where it arrives and the actual deadline. |
| Missing answer | Whether a reminder is agreed and what the coach will avoid assuming. |
| End | When this check-in arrangement ends and what remains separate. |
A promise such as “I will review it” can mean several things. The coach may intend to read and make a private note, while the client expects a written reply. Name the output instead: one short question, one agreed suggestion, preparation for the next session or no written response.
Choose a rhythm that fits the actual service and capacity. Two dated check-ins can establish whether the process is useful before a recurring flow is appropriate. Do not make daily disclosure the default simply because software can ask for it.
If the service does not offer continuous monitoring, say so plainly. Check-ins should not be presented as an urgent response channel. Give the appropriate administrative contact route for access problems and clarify the service's limits before collecting potentially sensitive reflections.
Match the questions to the kind of check-in
A short form can serve several different purposes. Select one primary purpose before combining questions. Otherwise the client may be preparing for a session while the coach believes they are reporting completed work.
| Purpose | Useful information | Mistake to avoid |
|---|---|---|
| Preparation for a session | The question or choice the client wants to bring. | Demanding an outcome from work that has not happened. |
| Review of an agreed action | What was attempted, under which conditions and with what result. | Treating intention as a completed attempt. |
| A decision still awaiting another person | The actual request, response and next permitted contact. | Counting an unresolved dependency as personal failure. |
| Administrative confirmation | The necessary scheduling or access detail. | Collecting personal reflections to answer a logistical question. |
The pilot here reviews chosen practice. A client can still report that nothing happened or that the plan changed. If the response identifies a different coaching question, agree that transition rather than forcing the answer back into the original template.
For example, someone waiting for a venue confirmation may need a clear request and owner, not a higher progress rating. Someone preparing for a conversation may want to practise a sentence rather than complete another retrospective survey. The follow-up should fit the actual need.
Use four questions that lead to a decision
These are original prompts for a bounded coaching reflection, not a validated progress or wellbeing instrument. Adapt them with the client and preserve the relevant meaning when the task changes.
- What did you choose to try, and for which period? Invite the client to name the action in their own words. This prevents the coach from assessing an earlier goal after the client has deliberately chosen a different one.
- What actually happened? Ask for enough detail to distinguish an attempt, a completed action, a refusal, a missed opportunity or an unknown result. A brief example is often more useful than a general claim of success.
- What helped, got in the way or needs checking? Leave room for resources, other people's choices and practical conditions. Do not assume every difficulty is a motivation problem.
- What would you like next from this check-in? The client can request a brief question, a suggestion, discussion in the next session or no written response. Only offer choices the service can actually provide.
Keep questions separate rather than putting several hidden tasks inside one required answer. Offer a brief response or an agreed alternative where appropriate. A client should not need to write an essay to explain that the planned activity did not happen.
Be precise with numbers. “How much progress?” has no stable unit. If the client wants to count practice, distinguish scheduled time, time actually spent and the activity performed. If they choose a personal rating, agree what it means and keep it separate from a capability score or a measure comparable across clients.
The ICO's data minimisation guidance connects adequate, relevant information with a specified purpose and periodic review. The guidance is under review following the Data (Use and Access) Act. Apply relevant requirements to the actual practice; collecting less is not useful if the remaining answer cannot support the agreed decision.
Configure a small manual workflow in Coachful
- Create the dated resources. Prepare the original form or worksheet and its clear instructions. For the two-date pilot here, use two separately named forms so the period and response remain distinguishable. This does not claim automatic weekly duplication.
- Assign the intended client's access. Use the normal Clients, client, Worksheets & resources assignment route. Verify that the correct client can open the correct resource. Copying a private URL does not itself assign access.
- Make the due arrangement visible. Tell the client the date, time zone and response commitment. A private coach reminder and a client notification are different things; inspect the actual saved delivery choices.
- Read the response in context. Open the client's Reflections, Forms & worksheets, then the actual submission. Check the relevant period and earlier answer rather than treating an aggregate chart as the whole account.
- Separate private review from communication. Save an appropriate coach review if useful. Then send promised feedback separately through the agreed client-facing route and check the actual recipient and content.
Coach review is private to the coach team; it is not automatically shown to the client or included in the response PDF. A “Reviewed” state can show that internal work was recorded while the client has received no answer. The case below makes that failure concrete.
For a repeatable future service, assess whether a coaching flow or Journey better fits the intended timing and review. Read the actual trigger, audience, completion and message rules first. Do not describe two manually assigned forms as a running automation or assume that a saved step delivers every promised response.
Worked pilot: four clients and two check-in dates
All people, responses, messages, dates and results here are fictional. Imani runs a solo coaching practice. Noor, Orin, Pia and Quinn are existing clients with separate goals and private records. They agree to try two short check-ins during November 2026. This pilot adds no employer or group audience.
The first form is due by 17:00 on 9 November and reviews 2–8 November. The second is due by 17:00 on 16 November and reviews 9–15 November, Europe/London. Each uses the four prompts above. Imani explains that a brief answer is sufficient and checks that each client can open their assigned form.
For answers received by those deadlines, the agreed short written feedback arrives in the existing one-to-one Coachful Messages conversation by 17:00 the following working day. Imani is the only coach in the practice. A response can ask for another permitted format, and the pilot includes an administrative question route in that same conversation.
If a form remains unanswered, the client has agreed to one individual reminder on the Wednesday after the due date. There is no repeated pursuit or assumption that silence authorises more messages. The pilot closes at 17:00 on 19 November after the promised feedback and closing confirmations. Later coaching and any new check-in rhythm remain separate agreements.
Imani creates “9 November practice check-in” and “16 November practice check-in” as distinct forms and assigns each to the four named clients. She checks the dates and access from the intended client route. This establishes the new pilot; it does not move or erase earlier Google Forms records.
All four first forms arrive by the deadline. Noor describes an attempted conversation and requests a clarification question. Orin asks for one suggestion about preparing a decision. Quinn wants a brief question about a delayed action. Pia wants help reconsidering a music-practice plan. All four choose the offered short written reply.
Imani reads each answer and records her private review. She sends Noor, Orin and Quinn their agreed replies by 17:00 on 10 November. For Pia, she saves a useful question in Coach review and marks the submission reviewed, then mistakenly treats that as having delivered feedback.
Repair a reviewed answer that received no feedback
At 10:00 on 12 November, Pia asks in Messages, “Did you receive my check-in? I cannot see a reply.” Imani opens the actual submission and conversation. The private note exists; a client-facing message does not.
Imani does not tell Pia to search harder or submit again. At 14:00 she replies:
I received and read your check-in. I saved my question privately and did not send the feedback I promised by Tuesday. That was my mistake. You do not need to repeat the form. If you still want a question about the practice plan, I can send it here now; you can also leave it for our next conversation.
Pia confirms she still wants the question. Imani asks which part of the plan is genuinely available to Pia and which depends on another person's agreement. The response is two days later than promised; the actual repair does not make it timely.
Pia's original wish was two twenty-minute periods of playing each week. She had tried to organise Tuesday and Thursday with her friend Ari, although Ari had said he was only available on Sunday. Her first check-in described the plan as a failure without distinguishing her preferred days from a commitment Ari had accepted.
Pia chooses a different plan herself: a 15-minute solo slot on Friday 13 November and a possible 20-minute shared slot on Sunday 15 November. The shared slot remains a proposal until Ari agrees. He confirms the Sunday time that evening; Imani does not treat the coach's suggestion or Pia's form as Ari's consent.
Imani records the actual late message and Pia's chosen next step. She adds a manual send check to her own review procedure: after recording a private note, inspect the actual conversation before marking the promised response complete. She does not claim that this changes the software's privacy rules.
Read the second answer without inflating progress
Pia completes the second check-in on 16 November. The Friday slot happened: six minutes tuning and nine playing. The Sunday slot with Ari also happened: five minutes setting up and fifteen playing. The two slots total 35 minutes, but actual playing totals 24.
Two appointments happened; the original forty minutes of playing did not. The difference is sixteen playing minutes. Imani avoids saying “You met the goal because you practised twice.” She asks whether the distinction is useful to Pia and what she would like to keep.
Pia says the shared practice was enjoyable, but she is frustrated that setup used more time than expected. She wants to consider a longer slot or simpler preparation later. That is a future choice to discuss, not an already completed improvement or a claim that setup is wasted time.
By 17:00 on 17 November, Imani sends the chosen short reply, with the actual numbers and an optional question about the next plan. Pia reads it and confirms that it matches her account. The coach does not overwrite the first answer or pretend the old Tuesday/Thursday arrangement had been workable all along.
Noor and Orin also submit the second form by the deadline and receive their chosen replies on time. Quinn does not submit it. Imani sends the single agreed reminder on 18 November and receives no answer by the pilot's closing time.
Quinn's missing second response stays unknown. It does not establish that the action failed, the client disengaged, the reminder was read or the earlier coaching was ineffective. The record shows what was due, what was sent and what remains unobserved.
Review delivery with the right denominators
| Pilot measure | Observed result | Limit |
|---|---|---|
| Forms originally due | Eight: two for each of four clients. | Different personal goals are not one common progress scale. |
| Forms submitted | Seven of eight, or 87.5%. | Submission is not goal completion or satisfaction. |
| Promised replies to submitted forms | Seven, all eventually delivered. | Delivery includes Pia's late first reply. |
| Replies within the agreed window | Six of seven, approximately 85.7%. | The late reply remains a provider miss. |
| Missing second response | Quinn: one reminder sent, no answer observed. | No reason or outcome is inferred. |
Do not divide six timely replies by eight forms due and call that the same service measure. One unanswered form produced no submitted answer to review. The two denominators answer different questions and should be labelled accordingly.
Imani records thirty minutes preparing the forms and brief, eight assigning and checking access, twenty-eight reviewing seven submissions, thirty-five preparing and sending the seven short replies, six additional minutes on the repair correspondence, four on the reminder and eight on closing confirmations. Total coach time is 119 minutes against a 120-minute allowance.
The extra six repair minutes are separate from Pia's ordinary five-minute feedback allocation. The reminder and all four closing confirmations are completed by 17:00 on 19 November, with no outstanding pilot response promise. A later unsolicited answer would need the appropriate ongoing-service decision rather than being counted as work already completed.
Pia spends three minutes on the first form and four on the second: seven minutes of check-in work, separate from her 35 minutes of practice slots. Other clients' response times were not measured. This is not a total cost for every person's activity or evidence of a saving against the previous form process.
Move existing collection carefully
If replacing a current Google Forms process, inventory what exists before changing it: form questions, response locations, collaborators, linked Sheets, notifications and any other workflow consuming the answers. Google's documentation distinguishes form data from the linked spreadsheet; permissions and deletion should not be treated as one global switch.
Decide the new collection date and tell clients where the next answer belongs. Check the correct destination using a permitted test or the intended client route. Preserve earlier records according to the actual policy and obligations. A new form does not need every historical answer copied into it to become useful.
If old collection must close, use the actual supported control and verify the resulting state. Do not infer that unlinking a spreadsheet removes the form, that deleting a form removes every separate copy, or that a client notification proves access. This article performs none of those actions on a real account.
Start with a controlled scope. Imani's pilot establishes new assignments, seven actual responses and replies, a repaired provider error and the current unanswered item. It does not establish a universal Google Forms importer, automatic historical trend conversion or a completed practice-wide migration.
Handle exceptions without turning them into scores
The answer is very brief: ask whether it provides enough information for the agreed purpose. “Nothing happened” may need a useful clarification, but brevity is not evidence of poor motivation.
The response contains another person's private details: avoid repeating them in feedback or a group summary. Review what is needed for the coaching purpose and handle the record appropriately. Do not promise that removing a later copy recalls information already seen elsewhere.
The client wants less frequent check-ins: discuss the actual service and choose an appropriate change. Keep past and new arrangements distinct. Do not treat a preference change as a failed completion streak.
The coach cannot meet the reply window: acknowledge the actual miss and agree a concrete repair. Revise future capacity before promising more. A new template or reminder cannot retroactively make a late response timely.
The coaching client-record guide develops the surrounding information workflow. Use Coachful's features to keep preparation and follow-up connected while checking what was actually delivered.
Frequently asked questions
Does a private coach review send feedback?
No. Coach review is internal to the coach team. Use the agreed client-facing route for a promised reply.
Do check-ins have to be automated?
No. A small manual process can clarify the service before recurrence is added. Describe the actual saved workflow accurately.
Can I compare progress percentages across clients?
Only if the measure and context justify that comparison. Different personal tasks and informal ratings do not become comparable merely because a chart displays them.
Does no response mean the action failed?
No. Record the missing answer and any agreed contact. Leave the underlying reason and result unknown until there is evidence.
Does this replace every Google Forms use?
No. Assess the actual requirements. This guide covers a connected coaching check-in process, not all surveys or a guaranteed full migration.
