AI prompts for personal trainers writing client programme notes

Most client programme notes are written in a shorthand that made sense in the session and means nothing three days later. “3×8 RDL @ RPE7, tempo 3-1-1” is precise, correct, and useless to a client standing in a busy gym trying to remember what RDL stood for.

The gap is not knowledge. The trainer knows exactly what they meant. The problem is that programme notes get written as a record of the session rather than as instructions for a person who will be alone when they use them. These five prompts close that gap: a translator for a single session, a full programme builder, a progression note, a review prompt that hunts for ambiguity, and a batch prompt for a full client roster.

Why do clients stop following client programme notes?

Rarely because they lack motivation, and usually because at some point the client programme notes stopped being actionable. A client who cannot remember whether the rest is sixty or ninety seconds will guess, then feel uncertain about whether the session counted, and the uncertainty is what erodes adherence — not the exercise itself.

The most common breakdowns are: an exercise name the client cannot map to a movement, a load prescription that assumes equipment the gym might not have free, an RPE target the client has never had explained, and no instruction for what to do when something is unavailable or hurts.

That last one is the biggest single cause of missed sessions. A client who finds the squat rack occupied and has no substitution rule does not improvise — they leave.

What makes client programme notes a client can follow?

Four things, and good client programme notes have all of them. The movement described in words a person could act on without the name, so “hinge at the hips with a barbell, back flat” sits alongside “Romanian deadlift”. A load anchor tied to something the client already knows rather than to a percentage they have never tested. A rest period as a number, not a feeling. And a stated fallback for each exercise.

Beyond that, the note should say what the session is for. A client who knows Tuesday is about hinge strength and Friday is about volume will make sensible decisions when reality interferes. A client who only has a list of exercises will not.

The core prompt: turning shorthand into client programme notes

You are turning a personal trainer's shorthand session notes into
instructions a client can follow alone in a gym.

Client experience level: {{beginner / returning / experienced}}
Terms this client already understands: {{list, e.g. RPE, tempo}}
Gym: {{commercial / home / limited kit — list what is available}}
Known limitations: {{injuries, restrictions, things to avoid}}
Session purpose in one line: {{what this session is for}}

Shorthand notes:
{{paste}}

For each exercise output:
- Name, then a plain-English description of the movement in one
  sentence, written so someone could do it without the name.
- Sets and reps as digits.
- Load, anchored to something the client knows. If the notes give
  a percentage and no tested max exists, convert it to an RPE or
  to a "last week's weight" reference instead.
- Rest, as a number in seconds.
- One cue: the single thing most likely to go wrong.
- A substitution if the equipment is taken, using only kit listed
  above as available.

Rules:
- Do not use any abbreviation not in the client's understood-terms
  list without defining it once, in brackets, on first use.
- Do not prescribe anything that conflicts with the stated
  limitations. If the shorthand does, flag it and stop.
- No motivational language.
- End with one line: what to do if something hurts.

A worked example

The trainer’s shorthand

The trainer’s shorthand:

A1 Back sq 4x5 @RPE8, 2min
A2 RDL 3x8 @RPE7, tempo 3-1-1, 90s
B1 Split sq 3x10ea, 60s
B2 Pallof 3x12ea
Client: Jo, 4 months training, commercial gym, right knee
  sensitive under load, understands RPE not tempo
Purpose: lower body strength, hinge emphasis

The client-facing result

What comes back is roughly this, for the first two exercises:

Back squat — bar across your upper back, sit down between your feet, stand up. 4 sets of 5. Load: the weight you used last Tuesday; it should feel like you had 2 reps left at the end of each set (RPE 8). Rest 120 seconds. Cue: knees track over your toes, don’t let them fall inward. If the rack is taken: goblet squat, 4 sets of 8. Knee note: stop the set if you feel anything sharp in the right knee rather than working through it.

Romanian deadlift — barbell in front of your thighs, push your hips back and let the bar travel down your legs with a flat back, then drive your hips forward. 3 sets of 8. Take 3 seconds to lower, pause 1 second at the bottom, 1 second to stand (this is what “tempo 3-1-1” means). Load: lighter than the squat; you should have 3 reps left (RPE 7). Rest 90 seconds. Cue: your back stays flat — when it rounds, the set is over. If the barbell area is busy: dumbbell RDL, same sets and reps.

The tempo definition appears in brackets on first use because it was not on Jo’s understood-terms list. The knee sensitivity produced an instruction rather than being silently ignored. And every exercise has a fallback, so a busy gym does not end the session.

The prompt for a full programme of client programme notes

You are writing a {{n}}-week training programme as client-facing
notes, not as a trainer's plan.

Client: {{age bracket, training history, current weekly sessions}}
Goal, stated as something measurable: {{goal}}
Sessions per week and length: {{n}} x {{minutes}}
Equipment available: {{list}}
Limitations: {{injuries, restrictions}}
Terms understood: {{list}}
What has failed before: {{previous programmes and why they stopped}}

Produce:
1. A one-paragraph explanation of how the programme works and why
   it is structured this way. Written for the client.
2. Each session, in the client-facing format: movement described
   in plain words, sets, reps, load anchor, rest in seconds, one
   cue, one substitution.
3. A progression rule per exercise, stated as a condition:
   "when you complete all sets at the top of the rep range, add
   {{x}} next session."
4. A deload week instruction.
5. A one-line "minimum viable session" for each day — what to do
   if the client only has 20 minutes.

Rules:
- No week may introduce more than two unfamiliar movements.
- Every session must be completable with the listed equipment
  alone.
- If the goal cannot be reached in the stated timeframe with the
  stated frequency, say so in one sentence before the programme
  and give the realistic version.

Point five earns its place. The most common reason a programme stops is a week where the client had no time, missed everything, and then felt too far behind to restart. A stated minimum session prevents the gap becoming a break.

The progression note prompt

You are writing the note that goes to a client after a session,
recording what happened and what changes next time.

What the client did today: {{loads, reps, anything missed}}
What went well: {{observation}}
What to change: {{your decision}}
Next session date: {{date}}

Write under 120 words, addressed to the client. Include:
- One specific thing they did better than last time, with the
  number that shows it.
- What changes next session and the reason in one clause.
- One thing to do between now and then, with a day attached.

Rules:
- Lead with the number, not with praise.
- No general encouragement. If there is nothing specific to
  point at, say the session was a maintenance session and why
  that was the right call.
- Do not describe soreness as progress.

The review prompt: hunting for ambiguity in client programme notes

Below are client-facing programme notes. Read them as a client
with {{experience level}} experience who is alone in a
{{gym type}} and cannot ask a question.

Output every point where you would have to guess, as:

LINE | WHAT IS AMBIGUOUS | WHAT YOU WOULD GUESS | RISK

Then list separately:
- Any abbreviation or term used without definition.
- Any exercise with no substitution.
- Any load prescription that depends on a number the client
  has not been given.
- Any instruction that conflicts with the stated limitations.
- Anything that could be read as a medical claim.

Do not improve the notes. Only find the gaps.

LIMITATIONS ON FILE: {{paste}}
NOTES: {{paste}}

Running a full client roster

You are converting this week's session plans for {{n}} clients
into client-facing notes.

Client profiles: {{table — name, level, gym, limitations,
  understood terms}}
This week's plans: {{table — client, session shorthand}}

For each client, produce their notes in the established format.

Rules for the batch:
- Never apply one client's limitations to another. Check each
  row against its own profile.
- If a plan conflicts with that client's limitations, output
  CONFLICT: {{client}} — {{what}} and write no notes for them.
- If a client's profile is missing limitations entirely, output
  NEEDS: {{client}} — limitations not on file. Do not assume
  there are none.

Output one block per client, and a summary list of conflicts and
missing profiles at the end.

The “do not assume there are none” rule exists because a blank limitations field is ambiguous between “no limitations” and “never asked”, and only one of those is safe to programme around.

Common mistakes with client programme notes

Listing every term the client has ever heard as understood. If a client nodded when you explained RPE four months ago, that is not the same as being able to use it under load in a busy gym. Keep the understood-terms list conservative and let the prompt define things.

Leaving the limitations field vague. “Bad back” produces generic caution; “disc issue, avoid loaded spinal flexion, fine with hinging under 60kg” produces usable substitutions. The prompt can only be as specific as the constraint you give it.

Asking for motivational framing. Clients following a programme alone need clarity, and encouragement in written notes reads as filler between the parts they actually need. Save it for the session.

Using client programme notes as your own record. They are the client’s copy. Keep your shorthand as the training log, because the plain-English version is longer and slower to scan when you are programming week five.

What to check before sending client programme notes

Read the notes as the client, in your head, standing in their gym. Every time you would have to make a decision, the note has a gap.

Check that no exercise assumes a piece of equipment you have not confirmed, that every load prescription references a number the client actually has, and that the limitations produced a visible instruction rather than silence. Silence means the model ignored them.

Finally, be clear with yourself about scope. These prompts write client programme notes; they do not assess injuries. The CIMSPA scope-of-practice guidance is the line to work to. Anything that reads as a diagnosis or a treatment plan needs to come out, and a client describing pain needs a referral rather than a substitution.