A Weekly Coaching Client Management Workflow

What belongs on the weekly client list?

Use one row per active engagement, not one row per email. Include the next session, the latest shared decision, client-owned work due, mentor-owned work due and any unresolved operational issue. A client with no session this week still needs a row when you owe feedback or have agreed a check-in.

Keep sensitive session content out of this overview. In guidance checked in 2026, the ICO's data-minimisation principle limits personal data to what the purpose needs. For this operational list, a neutral access problem is usually more useful than a detailed personal explanation.

The coaching workflow glossary describes the wider process. This weekly view is the control point that lets you see whether the process is actually moving. Give it a consistent review slot, but shorten or lengthen that slot according to the live workload rather than an arbitrary productivity target.

Every active client needs a next step, but not every next step belongs to the client.

How should you divide the week?

Use the start of the week to find delivery risk, session days to capture decisions, and the end of the week to reconcile the record. These are work windows, not promises to message clients on particular weekdays. A practice that runs weekend sessions should move the windows accordingly.

Define the boundaries before delegating. The 2025 ICF Code of Ethics addresses agreed roles, confidentiality and responsibilities for support personnel. An administrator can check whether a session is booked without needing access to the personal discussion that led to it.

Keep billing and coaching judgements separate. An overdue invoice belongs in an agreed payment process; it is not evidence that a client is disengaged. Follow the contract when deciding whether delivery pauses, and communicate that decision plainly instead of allowing a software access change to deliver the message for you.

A weekly rhythm works when every check has a clear completion condition.

How do you turn a session into owned work?

Close the session by separating an interesting idea from a commitment. Ask what the client wants to do, what evidence would show it happened and when it should be reviewed. Record your own obligations in the same way. If an action depends on someone outside the engagement, name that dependency without assigning that person work they have not accepted.

The 2025 ICF Core Competencies connect client growth with client-designed action and accountability. Applied operationally, that means suggested actions should remain proposals until accepted. The system should not turn a discussion into homework simply because someone typed it into a task field.

1. Write the commitment in observable language: draft the landing-page test brief, not improve the campaign.
2. Confirm who owns it and what is within that person's control.
3. Record the due date and the next review date separately when they differ.
4. Ask what could block the action and what support is agreed.
5. Read back the shared decisions and correct anything the client did not mean.

Use session notes for the discussion record and action item tracking for commitments. A summary can mention several possible approaches while the action list contains only one accepted next step. Preserving that distinction makes the next session easier to prepare without overstating agreement.

A suggestion becomes an action when the client accepts it, not when the software detects it.

What should happen when the normal workflow fails?

Create exception rules before the inbox fills. The rule should identify the next conversation or repair, not impose a judgement. Most problems need a proportionate response: confirm a booking, replace an impossible deadline or clarify who owes the next piece of information.

A reminder setting on your calendar does not prove the client received the same notification. Google Calendar's notification guidance, checked in 2026, says notification settings are personal to each account. Test the client's booking experience and agree how important changes will be communicated.

For an illustrative case, a client cannot complete a report because their analyst is away. Keep the original commitment visible, mark the dependency, and agree whether a smaller evidence sample is useful. Repeating the same reminder daily would add messages without changing the constraint.

An exception needs a decision, not an automatic increase in reminders.

How do you close the week without creating more administration?

Review only the records that can change next week's work. Check that shared summaries are accurate, promised materials are accessible and imminent deadlines are realistic. Move resolved exceptions out of the active queue while keeping their history. A small queue of genuine decisions is easier to trust than a long list of abandoned warnings.

Keep evidence review separate from task housekeeping. A completed action can be useful without moving the intended outcome yet. When a scheduled coaching progress report is due, compare the relevant evidence with the agreed starting point and include what remains uncertain. Do not manufacture a progress narrative because the weekly list needs closing.

For MentPass, use the client workspace for sessions, accepted actions and progress. Booking uses your TidyCal, Calendly or Cal.com link, with native Google Calendar sync, as described in the current plan information. Meeting imports require supported external services; do not assume the portal records the call or replaces the booking provider.

When comparing software, run this same week through both options. The MentPass and Simply.Coach comparison gives a starting point, but your exception cases determine fit. Ask which owner notices a failed hand-off and where the next decision is recorded. A feature exists operationally only when someone knows how to use its output.

A finished week leaves reliable commitments for the next one.