Founding access is open for 2026.

Scoped team pilot

The strength staff view.

Authorized strength staff can create structured private assignments while medical and sensitive data remain outside the role.

The whole workload

Training week

Scoped team pilot

Program inside the whole training week

Calendar + rosterPermission-aware
Strength plansStructured authoring
Private copiesAssign · edit · withdraw

Access boundary

The strength role never implies access to injury, fueling, or clinical detail.

Designed for the job

The right context. Nothing extra.

Build strength work with the wider training week in view—not in a disconnected calendar.

01

Roster and programming calendar

02

Structured strength-plan authoring

03

Private assignment, edit, and withdrawal lifecycle

A real working sequence

How the strength staff view fits the day.

Availability follows the status shown above. Pilot and in-development workflows are confirmed before a program relies on them.

01Before programming

Read the whole training week.

Place strength sessions beside the athlete’s approved practice and calendar context.

02While building

Prescribe the work precisely.

Create exercises, sets, load, and either RPE or RIR targets without mixing prescribed targets with completed actuals.

03Across the pilot

Manage private assignments.

Create one private copy per athlete, then edit or withdraw the assignment without widening access to injury, fueling, or clinical detail.

Evaluate the boundary with the workflow

The right context only works when “nothing extra” is specific.

Use the Trust Center to review the permission model, then bring this role into a scoped team conversation.