Source: https://docs.tracked.gg/concepts/coaching

# Coaching relationships

Coaching workflows act on a specific client under an authorized coaching relationship. Having a coach subscription does not by itself make every member's information available.

## Establish the client context

Resolve the client using the authorized roster or the client currently focused in the dashboard. A display name alone may be ambiguous. Do not guess identifiers or use a similarly named member as a substitute.

Read the data needed for the task in that client context. An unavailable field may reflect access limits, missing data, or a feature that is not exposed on that surface.

## Team and group context

A coaching team organizes people and roles. A training group organizes membership and shared training content. Neither should be treated as blanket access to every participant's nutrition, notes, messages, or progress photos.

See [training groups](/concepts/training-groups) for group-specific concepts.

## Check-ins and reviews

Check-in templates describe questions and scheduling. A submitted check-in is a response from a member. A template assignment, a scheduled instance, and a completed response are different states.

Numeric summaries and free-text responses are also different data categories. The external connector's numeric check-in summary does not imply access to coach notes or free-text answers.

## Dashboard proposals

For supported changes, the dashboard assistant can prepare a proposal for the focused client after the coach explicitly requests that change. The coach reviews a before-and-after confirmation card. The change is applied only after confirmation, subject to current access and state checks.

Do not report a proposal as completed, repeat a refused proposal with invented values, or infer that a general question authorizes a change.

See [change nutrition targets](/workflows/update-nutrition-targets) and [capabilities and access](/reference/capabilities).