Tools & Software
Should AI Write Your Clients' Training Programs?

AI should draft your clients’ programs; it should never finish them. Used as a first-pass generator that you feed with assessment data and then edit ruthlessly, AI saves real programming time. Sent to a client unedited, an AI program is generic at best and a liability at worst: the model has never seen your client move, and you remain professionally responsible for every set on the page. The tool is fine. Skipping the expert pass is the failure.
Trainers have clearly voted on the tool half: recent industry surveys put AI use somewhere around 64 percent of the profession. So the useful question is not whether, but how. Here is where AI drafting genuinely helps, where it fails clients, and the workflow that keeps you on the right side of the line.
What AI drafts well
Give a capable model tight inputs and it produces a competent skeleton fast:
- Sound structure: sensible weekly splits, movement-pattern balance, push-pull symmetry.
- Variety within patterns: ten hinge variations when you are bored of your usual three.
- Rough progression logic: workable week-over-week loading schemes for a general-population block.
- Speed: a first draft in minutes instead of an evening, which changes the economics of programming for a full roster.
For a deconditioned adult with general goals and no complications, an AI skeleton edited by a competent coach is honestly hard to distinguish from a manually written one. That is the true part of the hype. The catch in every case is the same, though: competence is not the bar. Your rate is.
Where it fails clients
The failures cluster in everything the model cannot know:
- The individual in front of you. Assessment findings, movement quirks, the shoulder that grumbles at certain angles, what the client fears and what they love. Programming around a person is the job; AI programs around a description.
- Anything medical-adjacent. Pain, injuries, conditions, medications: the model will generate confident programming for all of it, and none of that confidence transfers responsibility away from you. Those constraints come from the client’s physician or physical therapist, and your program lives inside them.
- Judgment across months. Real progression is a feedback loop: what actually happened last block decides the next one. A drafting tool sees no logs, no reassessment data, no bad month at work.
- Context, physical and personal. A program written for a generic gym floor wastes the specific room you coach in; an editing pass tunes it to the actual rack, cable system, and dumbbell run in front of you. (What’s in a FlexSpace is a concrete example of why equipment-aware editing matters: a Standard suite supports 850 or more exercises, which is a very different canvas than a hotel gym.)
- Specificity that looks like expertise but isn’t. Ask for a program for a high school pitcher and you get plausible athlete content, not the positional, seasonal judgment that an actual coach brings. Around here, with the Grand Park youth-sports pipeline sending travel-ball athletes through Hamilton County every weekend, that gap is exactly where a real coach earns the rate.
The responsible workflow
Five steps, in order, no skipping:
- Assess first. The human work happens before the prompt: movement screen, history, goals, constraints, equipment.
- Prompt with everything. Feed the model your assessment summary and hard constraints. Thin prompts produce generic drafts; the draft quality is set by your inputs.
- Edit as the expert. Cut what is wrong, swap what does not fit this body, set loads from real numbers. If the edit takes zero minutes, you did not read it.
- Deliver as yours. Your name, your standard, your responsibility. Be transparent about your methods if asked; never bill machine minutes as bespoke hours.
- Coach the loop. Watch it in the room, adjust from logs and check-ins, and let the next block be written by what actually happened.
Follow that and AI is simply a faster pencil. Skip steps three through five and you are reselling free output at professional prices, which clients eventually notice.
Keep the prompts themselves as an asset, too. A saved, refined prompt that encodes your assessment format, exercise preferences, and programming standards is a real piece of intellectual property, and it improves every time you notice what a draft got wrong. Coaches who treat prompting as part of the craft find their first drafts need lighter edits every month, which is where the time savings actually compound.
The business line under all of it
Clients are not paying for a document; they are paying for the judgment behind it and the accountability after it. Roughly half of clients now seek out specialists rather than generalists, which means the market is moving toward exactly what AI cannot supply: depth, context, and a coach who owns the outcome. Where that leaves the profession long-term is covered in will AI replace personal trainers, and the short version is: draft-writers are replaceable, coaches are not. The adjacent time-money question, when a template backbone beats bespoke work entirely, gets its own honest math in program templates vs custom.
The practical move: pick one straightforward client this week, run the five-step workflow once, and time it. Most coaches land somewhere that recovers hours every month without the product getting one percent more generic. Spend those hours where no model can follow you, in the room, and if you want a better room to spend them in, the first hour in a private suite is free.
Related questions
Is it unethical to use AI for client programs?
Using AI for a first draft you then edit against real assessment data is a workflow choice, like using templates. Delivering unedited AI output while charging for custom programming is the ethical problem, because the expertise being billed never happened.
Do I have to tell clients I use AI?
Be transparent if asked, and never claim a machine's draft as hours of bespoke work. Most clients care that the program fits them and that you stand behind it, not which tool produced the first skeleton.
Can AI handle injuries or medical conditions in programming?
No. Anything involving pain, injuries, medications, or conditions belongs with the client's physician or physical therapist, with your programming built inside the limits they set. AI will confidently generate advice here, which is exactly why it cannot be trusted with it.