A coaching portal in Airtable can connect an adult client’s professional goals, upcoming session agenda and agreed follow-up actions. miniExtensions provides the client-facing forms and record views; the coach maintains the working structure and keeps preparation separate from completed-session notes.

The example here is fictional leadership coaching at Clear Path Practice. A client wants to run more focused project meetings, prepare a stakeholder presentation and delegate routine reporting. The workflow covers ordinary professional development, not healthcare, therapy records or emergency support. Appointments and video calls stay in the coach’s separate scheduling tools.

Organize the portal around the next useful conversation

Before a session, a coach needs more than a broad goal such as “improve communication.” Ask the client what happened since the last meeting, what they tried and which decision they want to discuss next. Preserve these answers against the relevant session so a later update does not erase the earlier context.

For fictional client Taylor, a useful agenda item is “How should I shorten the Monday project review without losing risk updates?” The coach can link this to a goal about meeting structure and an action to pilot a new agenda. A portal should help both people find that connection, rather than collect a long unstructured journal.

Use separate records for goals, sessions and actions

  • Clients: Client name as primary text, Email as an email field and Coach name as text.
  • Goals: Goal title as primary text, Client as a link, Desired outcome as long text, Target review date as date and Goal state as single select.
  • Sessions: Session reference as primary text, Client as a link, Planned date as date with time, Preparation deadline as date with time, Agenda as long text, Related goals as multiple links and Session state as single select.
  • Actions: Action title as primary text; Client, Originating session and Goal as links; Next action as long text; Due date as date; Client update as long text; Action state as single select.

Every displayed table has a direct Client link. Connecting an action only to a session is insufficient for the intended portal setup. Keep calendar location, call details and any sensitive credentials out of example records. If a working note should not be shared with the client, keep it outside the client-facing fields and review all record-expansion paths.

Create the client-facing workspace

Set up the Airtable relationships first, then choose a Portal data table and linked User Field using the Users Table guide. Add the other client-linked tables only after their relationships are correct.

Use a suitable verified login flow. miniExtensions recommends email verification in its login guide. Configure Personal records only for each client’s views, and check that linked goal choices do not reveal or permit selection of another client’s goals.

Keep the coach-controlled session date and status outside client editing. Let the client supply agenda notes and action updates where appropriate. Read-only presentation and record visibility are separate configuration concerns: inspect both the list preview and the expanded record rather than assuming a field omitted from a card is inaccessible everywhere.

A list works well for actions, while a calendar can make session dates easier to browse. The view-type documentation explains the required Calendar date field. A calendar view displays stored dates; it does not book a coaching appointment or check the coach’s external calendar for conflicts.

Run one session from preparation to follow-through

The coach creates the next Sessions record after agreeing an appointment through the normal scheduling process. Taylor sees the date and adds three agenda points, linking the meeting-structure goal. Preparation instructions ask for a specific example and a desired outcome, without uploading confidential employer documents or identifiable colleague information.

During the session, coach and client agree on one practical experiment: use a short risk-first agenda for the next two project reviews. The coach records an Action linked to the session and goal, with a review date. Taylor later adds an observation such as “The second meeting ended ten minutes earlier, but one dependency was missed.” This is the client’s report, not a measured product or coaching-success claim.

At the following session, the coach reviews that observation and records the next action. Keep a completed action available for context rather than repeatedly overwriting its description. A distinct new experiment deserves a new action record, even if it supports the same goal.

Handle rescheduling and unfinished preparation

If the appointment moves, update the agreed date deliberately and review the preparation deadline too. A change to a date field does not prove the client received a notification. Contact them through the normal channel or use a separately configured, tested notification process.

If Taylor has not completed preparation, the coach can still decide how to use the session. Keep “Preparation incomplete” distinct from “Session cancelled.” The portal should make missing material visible without inventing an automatic cancellation rule or suggesting that a blank agenda means the client has no useful topic.

When a goal changes, retain the earlier goal as Paused or Completed and explain the transition in ordinary professional terms. Do not turn the example into a psychological assessment or scoring system. The coach and client decide what the records mean.

Verify access and the actual workflow

Before using real information, create two fictional clients and test goal browsing, agenda edits, action updates and rescheduling. Check direct record access and every linked-record picker as well as the main views. Confirm that changing one client’s action cannot expose another client’s session or change coach-owned fields.

Publish the intended configuration before testing the end-user link, following the extension sharing guide. Reload the Airtable records after each fictional update and verify that completed actions remain available. These are recommended checks; this article does not report a runtime-tested implementation.

This approach suits a small professional-coaching practice that wants clear preparation and continuity. It does not provide a full scheduling, billing or clinical-record system. Its value is a readable trail from a practical goal to a session discussion and then to a specific next action.