Client Portal Check-in System: Six Practical Workflows
Nour
Founder, Coachful
A client portal check-in system gives clients a reliable place to prepare, report something relevant and receive the response their service actually includes. It works only when the whole exchange is clear: who answers, who reads, when review happens and what the client can do next.
Coachful is our #1 recommendation for coordinating that workflow through configured coaching flows, submitted reflections, individual conversations and linked actions. This is our editorial recommendation about those supported functions, without a market-ranking, treatment or coaching-outcome guarantee. A completed flow is not proof that a coach replied or that the client's situation improved.
This guide develops six possible purposes, an original three-question check-in and a complete fictional rollout. Its example includes a genuine visibility failure, a late coach reply and a decision to stop a weekly requirement that has become repetitive.
Define the service before adding questions
Decide whether the answer prepares a later session, requests an included reply or exists only for the client's own reflection. These arrangements can all be legitimate, but they create different expectations. Do not invite a support request through a channel that nobody has agreed to monitor.
State the review clock with a time zone and a rule for submissions outside the cutoff. Availability, reminders and human review are separate. A portal that opens at midnight does not establish overnight support, while a reminder sent on Tuesday does not prove that the client read or completed anything.
Explain the actual audience, including authorized team members and any agreed sponsor reporting. Request only information needed for the purpose. The ICO's UK data-minimisation guidance concerns adequate, relevant information limited to that purpose. The page is under review following the Data (Use and Access) Act; it is not a universal legal checklist or proof that a particular coaching setup complies with every applicable law.
A useful design may omit health histories, employer details or lifestyle scores entirely. Let the client explain a changed priority and agree a suitable alternative when written portal responses are inaccessible or unhelpful.
Choose among six distinct check-in purposes
1. Weekly alignment
Ask which current priority deserves attention and what decision or support would help. This is planning information. It need not require a report of success in the preceding week.
A client may need to clarify a role before pursuing it, rather than add another productivity target. Decide whether alignment and the previous period's review can share one short flow. Requiring both to repeat the same context adds work without necessarily adding understanding.
2. Habit reflection
Use this when a specific practice has relevant opportunities. Separate what was planned, attempted, completed and unknown. A missing mark does not explain whether the client forgot, lacked an opportunity, declined the practice or could not use the interface.
Keep the purpose connected to the client's goal. Four completed actions out of six planned opportunities is a different statement from four completed actions out of four recorded entries. Neither establishes a change in personal character or coaching effectiveness.
3. Mid-cycle pulse
A short pulse can identify a changed circumstance before the next larger review. Use it only if the service can do something useful with the answer. Explain what a status choice means and whether a response follows.
A color or low rating is not a crisis diagnosis. A routine coaching portal should not be presented as emergency monitoring. If an ordinary work decision is needed before the coach's next review, the client's actual workplace or administrative route may be the appropriate one.
4. End-of-period reflection
Ask what occurred, what remains difficult and what the client would change. Permit no change, disappointment or an ending. A compulsory gratitude or wins list can conceal the information the service most needs to hear.
Distinguish the client's contribution from other factors, including extra help, a canceled obligation or lighter demand. A useful exception may depend on resources that are unavailable next time. Do not turn it immediately into a recurring assignment.
5. Pre-session preparation
Invite the client to identify a question and necessary context before a live session. State how much document review is included and the notice required. A submitted answer is a proposed starting point; confirm the agenda together when the session begins.
Give an honest late-preparation rule. If the coach cannot read a long document before the call, explain that limit rather than pretending receipt guarantees adequate preparation. The session may use a shorter summary or another agreed focus.
6. Milestone review
Use a meaningful point to reconsider the goal, evidence, service and reporting burden. The result can be continuation, a changed purpose, reduced tracking or completion. A renewal decision is separate from a rising chart.
Where comparison matters, preserve definitions and note changes. A confidence rating based on a new understanding of the task cannot automatically be compared with an earlier number as though nothing changed. Our habit dashboard guide develops related counting distinctions.
Write clear questions and a usable return route
AAPOR's research guidance recommends specific, understandable questions addressing one concept, attention to response burden and pretesting. It also distinguishes nonresponse from substantive answers. These principles can inform a coaching form; they do not make one client's responses a representative survey or validate a new assessment.
W3C's form-instruction guidance stresses clear instructions, required versus optional information and usable labels. Placeholder examples are not substitutes for labels. Test the actual client experience and meaning, rather than infer accessibility from a short question count.
A deliberately small original check-in could use:
- What would you like to use coaching for in the next period?
- What happened since our last exchange that is relevant to that choice? Include no change or uncertainty if that is your account.
- What question would you like me to respond to at the next agreed review?
Explain that an answer can be left unresolved or declined. Set the actual response requirements accordingly. The third question only belongs in a service that includes the corresponding coach response. A self-reflection-only version should say so and use different wording.
Follow a complete fictional rollout
Cleo coaches Anya, who wants to prepare a useful personal introduction before deciding whether to approach a local history group. Kit helps test a synthetic setup. Every person, date, message, observation and figure is fictional. The measured workflow runs from 2 to 16 June 2064, using Amsterdam time.
Complete the service agreement and first test
Anya already keeps personal project notes. She declines daily scores and a mid-cycle pulse. They choose one private custom flow with the three questions above, used for two weekly reviews before a twenty-minute design review. The purpose is to select useful coaching questions, without copying her entire diary into another system. Cleo configures the private flow for Anya, with Available all day and Show once a day enabled; that availability does not require daily completion.
The completed instructions say:
This check-in is optional preparation for our agreed coaching exchange. Each Tuesday at 12:00 Amsterdam time, Cleo takes the review cutoff. Unreviewed responses received by that cutoff get a written response by Wednesday at 17:00 the next day. Anything later joins the following Tuesday cutoff and Wednesday response. The portal is available at other times, but it is not continuously monitored. Do not use it for emergencies or a decision needed before that next review. Use the relevant person's normal contact route for time-sensitive administrative matters. You may leave a question unanswered or tell us the form is not useful.
This rule covers Monday, weekend and after-cutoff submissions as well as Tuesday morning. There is no same-week entitlement for a Tuesday afternoon answer. Anya's material is visible to Cleo's authorized coaching audience, not Kit or a history-group organizer. Kit uses only a separate synthetic test configuration.
On 2 June, Kit first cannot find the test flow on Home. The flow was placed in Reflection while that optional homepage section was off. Cleo keeps the intended audience intact and moves the flow to the already enabled Dynamic section, with App on. He does not solve visibility by granting access to everyone.
Kit then finds the test entry, submits synthetic answers and locates Cleo's returned test message in the individual client conversation. The test distinguishes opening the flow, completing it, finding the saved response and receiving a usable reply. Anya separately spends ten minutes checking her real private entry and reading the instructions before she submits personal material. This is a fictional rehearsal, not a claim that we inspected a customer's account.
Use the first full answer and own the late return
On Tuesday 3 June at 10:00, Anya spends eight minutes submitting these answers:
| Question | Anya's actual fictional answer |
|---|---|
| Purpose for the next period | Write a personal introduction for a local history group. I want to learn about attending before offering to lead anything. |
| Relevant events | I already had a group listing before this setup, but the next meeting arrangements are unclear. I have not contacted an organizer. My existing project notes already cover what I researched. |
| Question for the coach | How can I make the introduction specific without sounding as though I am volunteering to organize the group? |
The promised response is due Wednesday 4 June at 17:00. Cleo misses it and sends the actual return on Thursday 5 June at 09:00, sixteen hours late. Anya had left a fifteen-minute writing opportunity at 18:00 on Wednesday; she waited for the promised response and did not use that opportunity. Those fifteen minutes are a lost planned opportunity, not fifteen minutes of completed writing or active message handling.
Cleo's full return says: “I missed the response time we agreed. I am sorry; your planned writing opportunity passed without the reply. For the introduction, distinguish attending from organizing in the opening, name your actual interest and ask one practical question about joining a meeting. Avoid offering leadership work you have not chosen. If useful, draft that limited introduction; you do not owe a catch-up task because I replied late. We can review whether this schedule still serves you.”
Anya spends five minutes reading it. She chooses a separate twenty-minute block on 7 June: twelve writing, five checking that she has not invented meeting details and three saving the draft. Her complete output is:
Hello, I am Anya. I am interested in attending a local history discussion and learning how your group works before deciding whether to join. My current interest is how residents describe changes in the places they use every day. I would enjoy listening to other people's accounts and contributing to a discussion as a participant. I am not currently offering to organize meetings or lead a project. Could you tell me how someone can find the next meeting arrangements and whether a new participant needs to contact an organizer first? I have not made a meeting commitment yet.
The draft is complete, but it has not been sent to an organizer and no meeting place or membership is secured. Anya decides to identify the correct contact before using it. The portal check-in did not verify those outside arrangements.
Let the second cycle reveal unnecessary repetition
On Tuesday 10 June at 11:00, Anya spends six minutes on the same flow. Her complete answer says: “I have the introduction draft. Identifying the group's normal contact route is still pending. There is no new coaching question. This repeats my own notes, and I do not want to invent another update just to complete a weekly form.” She leaves the reply-question field unanswered.
Cleo reads the saved submission instead of coding the blank field as a request, a failed flow or a motivation problem. He sends the second actual response on Wednesday 11 June at 16:00, before its 17:00 deadline: “You have reported a completed draft, an unresolved contact route and no new coaching question. I will not add a task to fill the gap. Let us use the design review on 13 June to decide whether to stop the weekly expectation and keep preparation only when a session needs it.” Anya spends five minutes reading.
On 13 June Anya spends five minutes preparing and both use the agreed twenty-minute review: five on usefulness, five on the late reply, five on repetition and five on the new arrangement. Anya chooses to end weekly check-ins. She wants a short preparation entry only when they have agreed a live session and a useful question exists.
Cleo accepts that choice. They do not promise that leaving a flow visible creates a new response entitlement. Any future preparation deadline and review allowance will be agreed for the actual session; the two-cycle weekly reply arrangement is finished.
Make the ending concrete
Cleo spends eight minutes checking the private flow and communication settings and replacing its original response-clock instructions. The new opening says: “This entry is optional preparation only. The two-cycle weekly response arrangement is finished. Any future session preparation and review must be separately agreed.” Push, Email, WhatsApp and Coach completion alerts are off. App stays on, preserving the Home entry and existing app behavior. This is not a claim of complete notification silence: independent automations and manual sends are separate, and the entry remains available. No new weekly completion is required.
His final five-minute written status, sent on 16 June, says: “The weekly reporting requirement and its reply arrangement have ended after the two agreed cycles. Your private preparation entry remains available, with no expectation that you fill it each week. The listed outgoing reminder channels and shared coach completion alerts are off; App remains on. We will agree any preparation and review for an actual future session separately. Your saved replies are not a financial-impact measure or proof of membership in the history group.” Anya spends five minutes reading it.
The observed ending is a changed service arrangement and a completed introduction draft. The outside contact and future coaching sessions remain unresolved. There is no claim that a lighter system improved her confidence, secured membership or produced financial ROI.
Count response performance and the whole workload
Both real submissions were reviewed and both received a written return. Only one return met its promised deadline: one of two, 50%. Reporting two successful exchanges without that timing qualification would conceal the service failure. Kit's synthetic submission is excluded from the two-client-response denominator.
| Person | Actual active minutes, 2–16 June | Total against allowance |
|---|---|---|
| Cleo | Setup, synthetic failure, repair and test return 30; first real review and late return including accountability 17; second review and return 12; design-review preparation 10; live review 20; notes 5; ending settings check 8; final written status 5. | 107 of 115; 8 unallocated. |
| Anya | Orientation and private-entry check 10; first submission 8; read late return 5; write, verify and save introduction 20; second submission 6; read second return 5; review preparation 5; live review 20; read final status 5. | 84 of 95; 11 unallocated. |
| Kit | Read test instructions 5; first visibility test 5; retest, synthetic submission and returned-message check 5. | 15 of 20; 5 unallocated. |
The complete defined workflow uses 206 of 230 available person-minutes, leaving twenty-four across three separate allowances. Cleo's first response uses the normal twelve-minute review-and-return allocation plus five addressing the missed promise. Anya's draft block contains twelve writing minutes and eight checking or saving. Her lost fifteen-minute opportunity is recorded separately. No external organizer read, reply or membership decision is claimed, and no later contact search is represented as completed work in this portal workflow.
Configure the Coachful system in a deliberate order
- Choose the purpose and audience. Use Create > Coaching flows, selecting the suitable weekly or custom flow. A custom flow can collect answers or provide information. Completing an informational flow is not automatically a written feedback request.
- Write and test the questions. Use labels and visible instructions. Set optional fields as optional. Test a blank answer, an actual saved answer and what the client understands a response promise to mean.
- Separate display from reminders. Custom flows have separate controls. Available all day concerns availability, not when human review happens or which reminder days and times are configured. Show once a day is a daily completion limit, not a weekly service inclusion or automatic-opening rule.
- Check Home placement. Choose Dynamic section, Reflection widget or Both. The selected surface must be enabled. Both displays the same flow and completion state; it does not create two assignments. Placement does not expand the audience, enable access or reset completion rules.
- Check notifications separately. Client reminder channels differ from Coach completion alerts. App also affects Home visibility, so do not turn it off simply to seek a quiet outbound-email setup. Independent automations and explicit Send actions require their own review.
- Complete the feedback loop. Find the client's submitted flow response in Reflections, then send the actual return through the individual's profile message icon and client conversation with the agreed authorized audience. A saved answer or internal preparation is not delivered feedback.
Where an eligible Voice Text Input question offers Type, Voice-to-text and Voice note, explain the difference. Dictation produces editable text; a voice-note answer retains audio. Only the selected answer is submitted. Program-completion forms have a separate renderer and do not offer that voice-note setting.
Keep submitted flow responses distinct from questionnaire worksheets. A worksheet's Coach review is private to the authorized coach team and excluded from its response PDF; do not imply every flow answer has that same private review panel. Goals can organize chosen actions, without proving an outside outcome.
Unshared journal pages differ from pages the client explicitly shares through supported specialty workflows. Session recaps are automatic by default; approval can hold new unsent recaps, session-type overrides matter and a settings change does not recall messages already sent. See Coachful features and our client accountability system guide for the wider service arrangement.
Troubleshoot the whole service
The entry is missing. Check the actual flow, audience, access, enabled Home surface and App setting before sending another invitation. An inaccessible flow does not establish client disengagement.
A reminder was sent but no answer exists. Distinguish dispatch, receipt, opening and final submission. Do not invent a completed response or assume a refusal. Ask about usefulness and access through an agreed route.
The answer exists but no coach reply arrived. Review the service promise and actual return channel. Own a missed deadline. A private note or completion alert does not replace the response the client was promised.
The client has nothing new to report. Accept the answer. Stop or simplify duplication rather than adding compulsory prompts to maintain a completion rate.
Frequently asked questions
Should every client have all six check-ins?
No. They serve different purposes. Choose only those whose answers are useful and whose review work fits the service.
Does a portal being available mean immediate support?
No. State the actual cutoff, response time, time zone and outside-window rule. Keep urgent and time-sensitive needs on appropriate routes.
Can I compare scores after changing the question?
Document the changed definition or wording and interpret cautiously. A different answer may reflect a different question, not a real change in the client's situation.
Does turning off reminders remove the client entry?
The controls differ. In the described setup, outgoing reminder channels and coach completion alerts are off while App stays on. Check the actual selected flow and Home surface rather than assume every toggle has the same effect.
Do completed check-ins prove coaching ROI?
No. They document submitted accounts and service activity. Financial effects require separate evidence, costs and attribution; completion and reply counts do not establish them.
