Executive coaching client portals: decide who can see what

A useful executive coaching client portal gives each participant the information needed for their role. The coach, client, practice administrator, and corporate sponsor may all belong to the same engagement, but that does not mean they should see the same records.

Before choosing features, write down what each person may read, change, approve, and export. This turns a broad request for a “private portal” into concrete requirements you can discuss with a software provider and test before launch.

Separate notes, actions, and sponsor updates

Start with three kinds of information rather than one session record that everyone shares:

• Private coach notes: working observations and preparation for the coach. Decide whether anyone else needs access, under what circumstances, and who approves it.
• Client-shared actions: commitments deliberately agreed with the client. Record the action, its owner, the target date, and the next review point. Give the client a way to correct a misunderstanding.
• Agreed sponsor reporting: information the practice has agreed to provide to an employer or program sponsor. Define specific fields, such as session usage or approved milestones, rather than granting access to the full coaching record.

Treat sharing as an explicit step. A private note should not automatically become a client action or a sponsor update just because the records concern the same session. Decide who prepares each shared item and who approves its release.

Write one permission rule at a time

For every record type, complete this sentence:

“Within this engagement, this role may take this action on these fields, when this condition is met.”

For example, a practice administrator might update session bookings without reading private coaching notes. A client might update progress on their own agreed actions without editing the coach’s preparation. A sponsor might read an approved engagement update without browsing session records.

Include engagement boundaries. “Coach” is not enough if a firm has several coaches: specify whether access covers assigned clients, an approved temporary handover, or a wider supervisory responsibility. Also identify who can change those assignments.

Our custom client portal development service starts with these working rules because they shape both the interface and the information behind it.

An illustrative engagement

The following example is fictional. It describes a proposed permission design, not a delivered coaching client project.

A leadership practice is coaching Jordan through an employer-funded program. After a session, the coach writes a private reflection about how the conversation unfolded. Separately, Jordan and the coach agree on an action: prepare an agenda for a forthcoming team discussion.

Jordan can see that action, add a progress update, and ask for a correction. The coach’s private reflection remains outside the shared action record. The practice administrator can see the next appointment and session balance, but not the reflection.

The sponsor receives an approved update showing sessions used and an agreed milestone status. It does not receive Jordan’s action notes or the coach’s reflection unless a separate, explicit sharing decision changes the agreed report.

If another coach takes over, the practice reviews what should transfer instead of automatically opening every historical record. That handover decision becomes part of the workflow.

Test the awkward moments

Use fictional accounts to test more than the normal session flow. Ask what each participant can see when an action is still a draft, a report has been rejected, a coach is reassigned, or an engagement has ended.

Check the same boundaries in searches, notifications, downloads, and reports. A page that shows the correct fields is only one part of the experience. A reminder email or exported document also needs to contain the intended information.

For practices working across countries, document the required time-zone behavior, hosting preferences, retention decisions, and account closure process during discovery. These are requirements to resolve for the engagement, not benefits to assume from a “global” product label.

A checklist for your portal discussion

Bring a blank form or fictional record and confirm:

• Which information is private, client-shared, or sponsor-approved?
• Who can create, edit, approve, export, and remove each record?
• How are access and responsibility limited to assigned engagements?
• How does a participant request a correction?
• What happens during reassignment, departure, or engagement closure?
• Do notifications and exports respect the same sharing decisions?
• Who verifies these scenarios before the practice starts using the portal?

An existing product may meet these requirements through configuration. Use our buy, connect, or build guide to compare options against the same scenarios.

The Recovery Residence project illustrates separate working views for different roles using fictional demonstration screens. It is a reference for discussing connected software, not a coaching deployment.

Explore custom software for executive coaches, or bring one engagement and its sharing boundaries to a project discussion.