Your workspace. Their training. One clearer conversation.

Two clear roles

Keep coaching work and client training connected.

Use Mako to prepare the plan and manage the service around it: the agreement, bookings, packs, payments and next follow-up. The planned Beta Training experience gives the client a place to review the offered program, log supported results and ask a question about the work.

Assigned-plan logging and coaching replies are intended to be included with the Mako coach plan, without a second paid Beta Training subscription for that experience. Any optional consumer features would have their own clearly disclosed access rules. Confirm the actual pilot scope before inviting clients.

First, an agreement

A plan becomes useful when both of you know what was agreed.

Prepare a specific program version, including supported exercises, instructions and recording fields. The client reviews and accepts or declines it in the planned connection. After acceptance, agree dates or recurring training days in the client's timezone.

Plan acceptance, scheduling and workout-sharing permission are separate choices. An offer that has not been accepted must not create missed-session counts. A new version should explain what changes and when, while the completed work keeps the instructions that applied when it was done.

Then, completed work

Review results after they sync.

The intended coach view receives completed, permission-shared workouts after a successful sync. It is not a live view of sets as a client performs them. A clear last-successful-sync time helps you decide how current the record is before you act.

A client can train without every record reaching the coach immediately. A device may not have synced, permission may have changed, or the period may not be fully covered. Keep observed completions visible, but leave consistency Unknown when the evidence is incomplete. Ask a useful question before assigning a reason.

Next, a conversation

Put the reply beside the work.

A client asks whether a set felt right. You open the relevant workout and answer with its instructions and recorded result in view. Another client shares a completed week; you write a short, specific acknowledgement. These examples illustrate the planned workflow.

Comments and encouragement should retain their context: the program, workout or result they concern. Your private notes are excluded from suggested client-message drafts. Drafts remain separate from client-visible discussion. You review and approve personal outreach. A saved draft, a sent message, a delivered message, a read, a reaction and a substantive answer describe different moments.

Their choice

Sharing training should be an informed decision.

The planned connection uses optional, revocable permission to share completed training with a coach. Before connecting, the client should be shown who can see the information and which records are in scope. Accepting a program or buying coaching must not quietly grant broader access.

Booking a service and making a payment remain independent of Beta Training sharing. Before pilot activation, Mako will need to explain the actual controls for stopping sharing and the treatment of information already shared. If you need those details for a client, ask us before connecting.

Back in Mako

Turn the context into the next useful step.

Shared results can support a coaching conversation, a future plan change or a session booking. Session packs, payments and renewals remain service records in Mako. A positive reply does not confirm a paid renewal, and booking attendance does not prove a workout was completed.

Dedicated Performance & Analytics is intended to bring these records together with their dates, counts and coverage. Use it to inspect what happened across the practice without turning an incomplete training window into a confident score.

Practical questions

A few things to know.