Sports & Fitness AI agent · Training plans
Training-Plan Copilot AI Agent
Draft training blocks from the schedule, equipment and history already on file, bound progression to limits a coach configured, and hold the plan for the coach of record, who decides what is trained.
- Typical delivery
- 4–6 weeks
- Deployment
- Your stack
- Coach sign-off
- Pre-session
- After launch
- Agent Care
What this agent does
Personalised to the schedule, not to a predicted response
In
- 01
Ingest the athlete's schedule, equipment, training history and preferences from supported coaching or club systems.
- 02
Normalise exercise names, units and session formats, and keep each input tied to its source.
Reason
- 03
Draft the block — sessions, exercises, sets, load targets and the deload week.
- 04
Apply the progression, volume and substitution rules the club configured.
- 05
Personalise on schedule, equipment, history and preference — never on predicted response.
Decide
- 06
Flag anything in the intake that belongs to screening, not programming.
- 07
Route the drafted block to the coach of record for sign-off.
Out
- 08
Retain the inputs, the draft, the coach's edits and the sign-off against the athlete record.
- 09
Execute write actions only inside the approval boundaries agreed during implementation.
Product statement
The agent proposes the block; the coach of record decides what is trained. Progression is configured, bounded and reviewable — never silent.
Example workflow
One block, intake to sign-off
- 1Athlete intake receivedScreening form, coaching notes, training history or club-system record
- 2Inputs assembledSchedule, equipment, history, preferences and screening flags, each with its named source
- 3Block draftedSessions, exercises, progression, deload and confidence
- 4Controls appliedScreening-flag checks, progression and volume ceilings, substitution-library rules and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing reaches an athlete at any of them — the agent is drafting, and the coach's lane opens at the confidence gate.
Goes to the coach of record to sign.
Adds a senior-coach read first.
Coach sign-off
The block is held with its inputs, its flagged lines and the confidence.
Approve · Edit · Send to senior review
Signed — released to the athlete
- 6Coaching systems updatedOnly where write access and approval policy allow it
- 7Outcome evaluatedEdit distance, flagged-intake outcomes, completion and post-session corrections
Edits
Every coach edit is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required
8 items
- Deciding whether a member is fit to train.
- Progressing a plan past an open screening flag.
- Changing a return-from-injury or post-surgical plan.
- Programming for a member held for clearance.
Automation boundary
Agent acts unaided
- ✓Draft the block from the schedule, equipment and history on file.
- ✓Substitute an exercise inside the configured library.
- ✓Write the session notes back to the athlete record.
- ✓Flag intake that needs screening, and hold the block for the coach.
Any write happens inside the boundaries agreed at implementation, never ahead of sign-off.
- Return-to-play after a suspected concussion.
- Reading a reported symptom as a training input.
- Pregnancy, paediatric or cardiac-history programming.
- Changes to progression ceilings or approval rules.
Example output
One session, annotated
Whatever the agent drafts stays attached to the inputs behind it.
Training-plan output · single session
Illustrative example- Athlete
- Returning member
- Drafted session
- Lower-body strength, three compound lifts then accessory work
- Working load
- Last logged set
- Source of record
- Logged training history
- Confidence
- 93%
- Progression
- Within the configured ceiling
As received
Taken from the training history and the intake form on file — the agent wrote none of this side.
Inputs used
- Logged sessions
- Coach intake form
- Equipment and schedule
Why this progression
It moves inside the ceiling a coach set, not toward a predicted response.
What the score decides
Below the configured threshold the block picks up a senior-coach read before the coach signs.
Action
ApproveEditSend to senior reviewValue
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value lands
Value 01 – 04
Every block
From the intake record
Draft from what is on file
Draw on the schedule, equipment and history on file, inside the ceilings a coach configured.
Draft the block, not the verdict
Routine blocks, progressions and deloads arrive already written.
Send review to the risky plans
Screening flags and low-confidence blocks are marked, so the coach's read starts where the risk sits.
Build an evidence trail
The plan, the inputs behind it and the coach who signed it stay attached to the athlete.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Club management
- Mindbody
- ABC Glofox
- Xplor Recreation
- Perfect Gym
Coaching platforms
- TrainHeroic
- TeamBuildr
- TrueCoach
- Trainerize
Athlete records
- Intake
- screening
- Session logs
- notes
Agent
Training-plan copilot
- Reads the inputs
- Drafts the block
- Holds for sign-off
Scheduling and comms
- Calendars
- Member app
- portal
Observability & evaluation
- OpenTelemetry
- Langfuse
- Supported monitoring/evaluation sources
Integration availability depends on the client's existing systems and API access.
Agent controls
Six layers between the model and the athlete
The layers nest. What each one misses is named in the map below.
L6 · Outermost — last line of defence
Inward → L1 · closest to the model
- L1 – L2
- Test whether a block may stand
- L3
- Puts the release in a coach's hands
- L4 – L5
- Show what the session was built from
- L6
- Reverts to the standing template when signals degrade
How Nestack evaluates it
Evaluate the drafting workflow — not only the finished block.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the session the athlete trains
- E1Final-output evaluationDid the block hold inside the configured ceilings and equipment?
- E2Step-level evaluationDid the agent use the right history, screening record and rule set?
- E3Tool evaluationDid it read the right athlete record and write the correct field?
- E4Confidence calibrationDo low-confidence blocks actually attract more coach edits?
- E5Slice evaluationHow does performance change across specific training groups?
- E6Business outcomeHow many blocks needed a coach edit or a correction after the session?
Floor — the outcome the club answers for
Failure modes
Where each failure originates in the agent
Seven failure modes, placed at the stage each one originates.
Agent lifecycle
Direction of processing →
01 · Retrieval
1 mode
- TG-03
Stale training history
A layoff is missing, so the athlete reads as continuously trained.
Stage gathers
Schedule, equipment, history and screening flags
02 · Reasoning
2 modes
- TG-04
Response-based personalisation
The block is shaped around a predicted response rather than the record.
- TG-06
Ceiling breached on substitution
A swapped exercise carries more volume than the rule allows.
Stage proposes
The block, the progression applied and confidence
03 · Tool / write
2 modes
- TG-02
Flagged intake programmed anyway
A block is drafted past a screening flag no one cleared.
- TG-05
Symptom read as a training input
A reported symptom is answered with a deload instead of a person.
Stage writes
Only where write access and approval policy allow it
04 · Output
1 mode
- TG-01
Unfamiliar volume spike
A block adds unfamiliar work faster than the ceiling intends.
Stage returns
The block the coach signs and the athlete trains
05 · Change / Version
1 mode
- TG-07
Silent progression drift
A model or rule change widens what the agent will progress.
Stage tracks
Model, prompt, progression rules and library config
- Sev-1 · a block trains past a screening flag
- Sev-2 · a wrong progression reaches an athlete
- Sev-3 · input degrades, block routes to review
Affected slices
The average holds while one group carries it
Base rates differ by training group, so one aggregate rate describes none of them well. Nestack reports the coach-edit rate by slice, and names the groups that carry it.
Slice performance — reported separately, not only in aggregate
Illustrative example| Slice | Failure rate | Lift | Lift vs. threshold | Status |
|---|---|---|---|---|
| Returning after a layoff | 5.3% | 3.9× | Review | |
| First-block novices | 3.9% | 2.9× | Review | |
| Minimal-equipment setups | 2.2% | 1.6× | Watch | |
| Members in continuous training | 0.9% | 0.7× | Normal |
Bar: coach-edit-rate lift vs. continuous-training baseline · scale 0–4.0× · tick marks the 2.0× review threshold
2 of 4 slices over threshold
Evidence-linked improvement
The cycle closes on a test, not a note
A cycle is done when the miss has become a test the next release has to survive. That suite is what the next block written by the copilot is measured against.
Improvement cycle · five stages
Switchback — the path turns at Improve and returns at Learn
- 01
Detect
Coach-edit rate rises in one training group.
- 02
Diagnose
Within the week it went out, a coach reads the block and its inputs until one of them accounts for it.
- 03
Improve
Version-stamp the change and attach the plans that exposed it.
- 04
Verify
The affected cases run again, and a fail stops the release.
- 05
Learn
It becomes a standing test, and the progression guardrails change with it.
Learn → Detect
The return edge. The next detection runs against a suite that is one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, drafting workflow, evaluation, integration, then production validation and handover.
Workstream
Week 1Week 2Week 3Week 4Week 5Week 6
- 01Coaching workflow discovery and boundary definition.Week 1
- 02Club and coaching-platform assessment.Week 1, Week 2
- 03Progression, volume and substitution-library mapping.Week 1, Week 2
- 04Athlete-record ingestion and normalisation.Week 2
- 05Drafting logic and source-input binding.Week 2, Week 3
- 06Confidence scoring and flagged-intake routing.Week 3
- 07Coach sign-off workflow.Week 3, Week 4
- 08Coaching and club-system integration.Week 5
- 09Progression regression cases.Week 4, Week 5
- 10Guardrails and progression controls.Week 4
- 11Plan-trail instrumentation.Week 5, Week 6
- 12Deployment, documentation and Agent Care handover.Week 6
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel
Final scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
| Capability✓ in scope · — not at this tier | PilotOne club, one squad | ProductionProduction coaching systems | AdvancedMultiple sites / brands |
|---|---|---|---|
| Introduced at Pilot | |||
| Drafting to your rules and library | ✓ | ✓ | ✓ |
| Coach sign-off | ✓ | ✓ | ✓ |
| Plan-quality baseline | ✓ | ✓ | ✓ |
| Introduced at Production | |||
| Reporting by training group | — | ✓ | ✓ |
| Sign-off workflow in your systems | — | ✓ | ✓ |
| Approved write-back | — | ✓ | ✓ |
| Coaching-platform integration | — | ✓ | ✓ |
| Introduced at Advanced | |||
| Multi-sport progression rules | — | — | ✓ |
| Multi-stage coaching approvals | — | — | ✓ |
| High athlete volume | — | — | ✓ |
| Multi-squad programme controls | — | — | ✓ |
| Build price | From $5,000 | From $8,000 | Custom quote |
- Final build price
- Confirmed after discovery based on integrations, workflow complexity, athlete volume, approval controls and deployment requirements.
- Separate from build
- Build pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bring
We build with it
01Your intake and screening-form structure
→Athlete-record ingestion and input mapping
Week 102Representative programmes you already write
→Drafting baseline, template extraction and input binding
Week 203Your progression, volume and substitution rules
→Progression, volume and substitution-library mapping
Week 104Access to relevant APIs, feeds or exports
→Club and coaching-platform assessment, then integration setup
Week 205Plans that should not have gone out
→Progression cases and the evaluation suite
Week 406What must reach a coach before an athlete trains it
→Confidence scoring, flag routing, guardrails and progression controls
Week 307Named coaches of record to sign blocks
→Coach sign-off workflow, then pilot and production validation
Weeks 5–6
Nothing else is required
Deployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Phases are drawn over the weeks they actually occupy, which is why week 5 doubles up rather than padding.
Phase
W1
W2
W3
W4
W5
W6
- DiscoveryW1
- BuildW2 – W3
- EvaluateW4 – W5
- Pilot & LaunchW5 – W6
Week focus
W1Coaching workflow discovery, rule mapping and the automation boundary
W2Source integration and the drafting baseline
W3Drafting workflow, confidence logic and progression controls
W4Evaluation suite, screening-flag checks and failure-mode testing
W5Coaching-platform integration, pilot blocks and targeted corrections
W6One training block written under the coaching staff, then handover
- Reading the band
- A bar covers only the weeks its work is named in. Both bars in week 5 are real work running together.
- At the end of W6
- The last checks clear on real blocks and monitoring moves to Agent Care.
- Duration
- Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Sports & Fitness AI agent
Build a training-plan copilot around the coaches who sign the block.
Show us your intake form, your progression rules and who signs. Get it wrong and an athlete trains a block no coach cleared — so we set the boundary before we write anything.
- Typical delivery
- 4–6 weeks
- Deployment
- Your club and coaching stack
- Coach sign-off
- Pre-session
- After launch
- Agent Care available
Nestack Agents · Training-plan copilot
AGT-SF-02 · Agent Care available after launch