Claude prompts for personal trainers who run a real training business

You are a personal trainer setting up a professional intake process for new clients. <context> You need a standard intake form to hand every new client before their first session, covering goals, training history, schedule, and preferences. </context> <inputs> - Business or trainer name: [PLACEHOLDER] - Session types offered: [PLACEHOLDER, e.g. 1:1, small group] - Typical client type: [PLACEHOLDER, e.g. busy professionals 30-55] </inputs> <task> Build a complete intake form with sections for contact info, goals, training history, schedule availability, equipment access, and communication preferences. </task> <constraints> - Do not include medical history or diagnosis questions; instead include one general readiness question directing clients with health concerns to consult a physician before starting. - Keep the form to questions a client can answer in under 10 minutes. - Use plain language, no jargon. </constraints> <format> A formatted document with numbered sections, each containing labeled fields ready to fill in or print. </format>

You are a personal trainer who runs a basic movement screen with every new client before programming. <context> You just finished a movement screen (squat, hinge, push, pull, single-leg balance) and have raw shorthand notes. You need a clean summary to keep in the client's file and reference in programming. </context> <inputs> - Client name: [PLACEHOLDER] - Raw screen notes: [PLACEHOLDER, e.g. squat: heels lift slightly, hinge: rounds low back, push: clean, pull: clean, single-leg: wobbles left side] </inputs> <task> Summarize the raw notes into a clear report: what was observed per movement, what it likely means for programming (mobility focus, stability focus, etc.), and 2-3 priority areas to build into the next program. </task> <constraints> - This is a movement quality observation, not a medical or orthopedic diagnosis; state that plainly at the top of the report. - Keep interpretation limited to training implications (what to program), not injury causes. - If any note suggests pain rather than just limited range, flag it for physician referral instead of interpreting it. </constraints> <format> A one-page report: Observations table (Movement, Note, Training Implication) followed by a 2-3 bullet Priority Areas section. </format>

You are a personal trainer documenting a client's baseline fitness assessment. <context> You just completed a baseline assessment with a new client covering body measurements, key lift numbers, and a cardio test. You need this saved as a clean baseline report to compare against in 90 days. </context> <inputs> - Client name: [PLACEHOLDER] - Date: [PLACEHOLDER] - Measurements (weight, waist, hips, body fat percent if taken): [PLACEHOLDER] - Key lift numbers (squat, bench, deadlift, or equivalents): [PLACEHOLDER] - Cardio test result and protocol: [PLACEHOLDER, e.g. 1-mile run, 9:45] </inputs> <task> Build a baseline report organized by category (body composition, strength, cardio) with the raw numbers, and add a short section on what a good 90-day target would look like for each category. </task> <constraints> - Keep 90-day targets realistic and tied to the client's actual starting numbers, not generic benchmarks. - Do not interpret body composition numbers as health risk categories; keep it strictly performance and training focused. - Note the exact protocol used for each test so it can be repeated identically at the 90-day mark. </constraints> <format> A report with 3 sections (Body Composition, Strength, Cardio), each a table with Metric, Baseline, 90-Day Target. </format>

You are a personal trainer who runs a goal-setting conversation with every client at the start of a new block. <context> A client stated their goal in their own words during a check-in. You need to turn that into a SMART goal worksheet they can refer back to. </context> <inputs> - Client name: [PLACEHOLDER] - Client's stated goal in their own words: [PLACEHOLDER, e.g. "I want to feel stronger and not be out of breath on hikes"] - Timeframe they mentioned: [PLACEHOLDER, e.g. before a trip in 4 months] - Any numbers already discussed: [PLACEHOLDER] </inputs> <task> Turn the client's stated goal into a SMART goal (specific, measurable, achievable, relevant, time-bound), with 2-3 milestone checkpoints between now and the deadline. </task> <constraints> - Keep the specific and measurable parts tied to things you can actually track in training (lifts, distance, session count), not subjective feelings alone. - Do not invent numbers the client did not mention; if a metric is missing, mark it [NEEDS CLIENT INPUT] instead of guessing. - Keep the tone matching the client's own words where possible. </constraints> <format> A one-page worksheet: SMART Goal statement, then a milestone table (Date, Checkpoint, How We'll Measure It). </format>

You are a personal trainer who screens every new client for basic training readiness before writing a program. <context> A new client completed a standard pre-training readiness questionnaire covering activity history, current symptoms, and lifestyle factors. You need a clear summary before you write their first program. </context> <inputs> - Client name: [PLACEHOLDER] - Questionnaire answers: [PLACEHOLDER, e.g. no current pain, sedentary for 2 years, no chest pain or dizziness with exertion, cleared for general exercise] </inputs> <task> Summarize the answers into a short readiness note: clear to proceed with general programming, or flagged items that need a physician's clearance first. </task> <constraints> - This is a training readiness screen, not a medical clearance; state that explicitly. - Any answer suggesting cardiac symptoms, dizziness, chest pain, or a recent injury must be flagged as needing a physician referral before training, rather than interpreted further. - Keep the summary to one paragraph plus a clear status line (Clear or Flagged). </constraints> <format> A short memo: Status line (Clear to proceed / Flagged, see notes), followed by a 2-3 sentence summary of the relevant answers. </format>

You are a personal trainer who provides general habit-based nutrition education to clients, not personalized meal plans. <context> Several clients ask the same question about how to eat more protein day to day. You want a reusable one-page handout with general education and realistic food examples. </context> <inputs> - Client's typical meals (optional, for examples): [PLACEHOLDER, e.g. oatmeal breakfast, sandwich lunch, pasta dinner] - Dietary restrictions to account for: [PLACEHOLDER, e.g. none, or vegetarian] </inputs> <task> Write a one-page handout on general habits for adding protein throughout the day, using realistic food swaps and additions based on the example meals given. </task> <constraints> - Do not prescribe calorie or macro targets; this is general education, not an individualized nutrition plan. - Include a closing line recommending clients with specific medical or dietary needs consult a registered dietitian or physician. - Use everyday food names, not supplement brand names. </constraints> <format> A one-page handout: short intro paragraph, then a bulleted list of 6-8 practical swaps or additions. </format>

You are a personal trainer helping clients build consistent recovery habits alongside their training. <context> A client wants help staying consistent with hydration and recovery basics (water, sleep, stretching) between sessions. </context> <inputs> - Client name: [PLACEHOLDER] - Approximate body weight range: [PLACEHOLDER, e.g. 150-160 lbs] - Current recovery habits: [PLACEHOLDER, e.g. inconsistent water intake, 6 hours sleep average] </inputs> <task> Build a 7-day printable tracker with a daily water target (general guidance based on body weight range), a sleep hours box, and a checkbox for a 5-minute stretch or mobility routine. </task> <constraints> - Present the water target as a general guideline range, not a medical prescription. - Keep the tracker to one printable page. - Add a one-line note that clients with kidney, heart, or other medical conditions should get fluid guidance from their physician. </constraints> <format> A 7-column table (one column per day) with rows for Water, Sleep Hours, Stretch Completed, plus a header with the daily water target. </format>

You are a personal trainer who educates clients on general workout nutrition timing, not clinical meal planning. <context> Clients frequently ask what to eat before and after training. You want a simple, reusable education handout with general timing guidance and food examples. </context> <inputs> - Typical training time of day: [PLACEHOLDER, e.g. 6am before work] - Session length and intensity: [PLACEHOLDER, e.g. 45 min moderate strength] </inputs> <task> Write a one-page guide covering general timing (roughly how long before and after training to eat) with 3-4 realistic food examples for pre-workout and 3-4 for post-workout. </task> <constraints> - Keep guidance general (timing windows and food categories), not personalized macro or calorie numbers. - Use common grocery-store foods, not supplements or branded products. - Add a line noting clients with diabetes or other metabolic conditions should follow their physician's or dietitian's specific timing guidance instead. </constraints> <format> A one-page handout with two sections (Before Training, After Training), each with a short timing note and a bulleted list of food examples. </format>

You are a personal trainer running a 30-day habit challenge for your client base. <context> You want to run a 30-day habit challenge to boost engagement and give clients a simple, visual way to track consistency on a few key habits. </context> <inputs> - 3 habits to track: [PLACEHOLDER, e.g. 8000 steps, 1 protein source per meal, 5-min mobility] - Challenge name: [PLACEHOLDER, e.g. "30-Day Consistency Challenge"] - Start date: [PLACEHOLDER] </inputs> <task> Build a 30-day grid tracker (day 1 to 30) with a checkbox row per habit, plus a short intro paragraph explaining the challenge and how to log it. </task> <constraints> - Keep habits general and non-medical (movement, protein, sleep, mobility), not calorie or weight targets. - Make the grid usable printed on one or two pages. - Include one line encouraging clients to adapt targets to their own baseline rather than treating them as a mandate. </constraints> <format> A 30-day table (Day 1-30 as columns, one row per habit) preceded by the intro paragraph. </format>

You are a personal trainer providing general grocery guidance to support clients' training goals. <context> Clients often ask what to actually buy to eat more protein without a full meal plan. You want a reusable grocery list template organized the way a store is laid out. </context> <inputs> - Dietary pattern to account for: [PLACEHOLDER, e.g. omnivore, vegetarian, pescatarian] - Budget level: [PLACEHOLDER, e.g. moderate] </inputs> <task> Build a grocery list template organized by store section (produce, protein, dairy, pantry, frozen) with 4-6 high-protein staple items per relevant section, matched to the stated dietary pattern. </task> <constraints> - Keep it a general staples list, not a prescribed weekly menu or calorie plan. - Respect the dietary pattern given (no meat items for a vegetarian client, etc.). - Add a note that clients with food allergies or medical dietary restrictions should have their list reviewed by a registered dietitian. </constraints> <format> A checklist grouped by store section, ready to print or copy into a notes app. </format>

You are a personal trainer who sends clients a monthly progress report to reinforce results and retention. <context> A month of training is complete for a client. You have this month's measurements and want a clean report comparing them to where the client started. </context> <inputs> - Client name: [PLACEHOLDER] - Baseline measurements (date, weight, key lifts): [PLACEHOLDER] - Current measurements: [PLACEHOLDER] - Sessions attended this month: [PLACEHOLDER, e.g. 7 of 8 scheduled] </inputs> <task> Build a monthly progress report comparing baseline to current numbers, noting the change for each metric, and add a short encouraging summary paragraph highlighting the biggest win. </task> <constraints> - Show the actual numeric change (plus or minus) for every metric, not just the raw numbers. - Keep the tone factual and encouraging, not exaggerated. - If a metric moved in an unwanted direction, note it plainly without blame and suggest one adjustment for next month. </constraints> <format> A report: comparison table (Metric, Baseline, Current, Change), followed by a 2-3 sentence summary paragraph. </format>

You are a personal trainer who runs small-group sessions and tracks personal records to keep clients motivated. <context> You want a running tracker of personal records (PRs) for your group clients across key lifts, formatted so it can be posted or shared as a friendly leaderboard. </context> <inputs> - Client names and their current PRs by lift: [PLACEHOLDER, e.g. Sam: squat 185 lbs, Alex: squat 205 lbs] - Lifts to track: [PLACEHOLDER, e.g. squat, deadlift, bench] </inputs> <task> Build a leaderboard table ranking clients by each tracked lift, plus a separate "most improved this month" line if improvement data is given. </task> <constraints> - Only use the numbers provided, do not invent PRs for anyone not listed. - Keep the framing friendly and non-competitive in tone (celebrate participation, not just first place). - Note that individual results vary based on training age and body weight, so rankings are for fun, not a judgment of effort. </constraints> <format> A leaderboard table per lift (Rank, Client, Weight) plus a short "most improved" callout line. </format>

You are a personal trainer building trend reports so clients understand direction, not just single-day numbers. <context> A client has been checking in every 2 weeks for measurements over a 12-week block. You want a report showing the trend across all check-ins, not just the start and end. </context> <inputs> - Client name: [PLACEHOLDER] - Biweekly check-ins (date, weight, waist measurement): [PLACEHOLDER, e.g. Week 0: 178 lbs / 36 in, Week 2: 176 / 35.5, Week 4: 175 / 35, Week 6: 174 / 34.5, Week 8: 173 / 34, Week 10: 172 / 34, Week 12: 171 / 33.5] </inputs> <task> Build a trend report showing all check-in points in a table, describe the overall trend direction in words, and note any plateau weeks. </task> <constraints> - Use only the data points given, do not smooth or estimate missing weeks. - Describe trend direction and rate of change (per week average), not just start-to-end difference. - Frame this as a body composition and performance trend, not a health or medical assessment. </constraints> <format> A data table (Week, Weight, Waist) followed by a short trend narrative paragraph. </format>

You are a personal trainer managing session packages and renewal timing for your client base. <context> Each client buys a block of sessions. You want a simple report per client showing sessions used, sessions remaining, and whether it is time to reach out about renewal. </context> <inputs> - Client name: [PLACEHOLDER] - Package size purchased: [PLACEHOLDER, e.g. 20 sessions] - Sessions used to date: [PLACEHOLDER, e.g. 16] - Average sessions per week: [PLACEHOLDER, e.g. 2] </inputs> <task> Calculate sessions remaining and estimated weeks until the package runs out, then flag whether it is time to send a renewal offer (flag if 3 or fewer sessions remain). </task> <constraints> - Show the math (sessions remaining, weeks remaining) plainly, not just a conclusion. - Use the exact renewal threshold given (3 or fewer sessions) rather than a different number. - Keep the output short enough to scan across a full client list. </constraints> <format> A single-row summary: Client, Sessions Remaining, Est. Weeks Remaining, Renewal Status (Flag / OK). </format>

You are a personal trainer building social proof content from real client results. <context> A client has hit a meaningful milestone and agreed to be featured. You want a short script highlighting the specific numbers, not a generic "great job" post. </context> <inputs> - Client first name (or initial, if they prefer): [PLACEHOLDER] - Starting point: [PLACEHOLDER, e.g. couldn't do a push-up, 0 sessions per week history] - Result and timeframe: [PLACEHOLDER, e.g. 10 clean push-ups, 12 weeks] - What they said in their own words (if available): [PLACEHOLDER] </inputs> <task> Write a 60-90 second script (for video or a written post) that leads with the specific before/after numbers, includes the client's own words if given, and ends with a soft call to action to book a consult. </task> <constraints> - Use only the numbers and quotes provided, do not invent details. - Keep it specific (real numbers, real timeframe), not vague praise. - Do not make any claim that this result is typical or guaranteed for other clients. </constraints> <format> A short script with 3 labeled beats (Hook, Story, Call to Action), each 1-3 sentences. </format>

You are a personal trainer writing follow-up emails to keep clients engaged after a missed session. <context> A client has missed their last 2 scheduled sessions without rescheduling. You want a short, friendly email that re-engages them without guilt-tripping. </context> <inputs> - Client name: [PLACEHOLDER] - Sessions missed: [PLACEHOLDER, e.g. 2] - Last topic discussed with them: [PLACEHOLDER, e.g. their upcoming 5k] </inputs> <task> Write a short email checking in, referencing the last topic discussed to show it is personal, and offering 2 concrete times to reschedule. </task> <constraints> - Keep it under 120 words. - No guilt or pressure language; tone should be genuinely helpful, not salesy. - End with a clear, low-friction next step (pick a time, reply yes). </constraints> <format> A ready-to-send email with subject line and body. </format>

You are a personal trainer writing a renewal email for a client near the end of their current package. <context> A client has 2 sessions left in their current package. You want to prompt renewal by connecting it to the progress they have made, not just asking for money. </context> <inputs> - Client name: [PLACEHOLDER] - Sessions remaining: [PLACEHOLDER, e.g. 2] - Key result this cycle: [PLACEHOLDER, e.g. added 30 lbs to deadlift] - Next package options: [PLACEHOLDER, e.g. 10-session or 20-session pack] </inputs> <task> Write a renewal email that references the specific result, frames the next package as continuing that momentum, and clearly lists the package options with a simple way to confirm. </task> <constraints> - Keep it under 150 words. - Reference the actual result given, not a generic compliment. - Present exactly the package options given, no invented pricing. </constraints> <format> A ready-to-send email with subject line and body. </format>

You are a personal trainer who sends brief accountability texts between sessions to keep clients on track. <context> You want a small library of short text templates to send clients between sessions, covering common situations (habit check-in, encouragement after a tough session, reminder before a session). </context> <inputs> - Common situations to cover: [PLACEHOLDER, e.g. mid-week habit check-in, day-before session reminder, post-tough-session encouragement] - Tone: [PLACEHOLDER, e.g. friendly and direct] </inputs> <task> Write one short text template for each situation listed, with a placeholder for the client's name and one specific detail to personalize. </task> <constraints> - Each text must be 2 sentences or fewer. - Include a clear placeholder (e.g. [CLIENT NAME], [SPECIFIC HABIT]) so it can be personalized fast. - Avoid guilt or pressure language throughout. </constraints> <format> A labeled list, one template per situation, ready to copy into a phone. </format>

You are a personal trainer building a referral request to use with satisfied clients. <context> A client just hit a strong result and seems happy with their progress. This is a good moment to ask for a referral without it feeling transactional. </context> <inputs> - Client name: [PLACEHOLDER] - Recent result: [PLACEHOLDER, e.g. lost 15 lbs and hit a new deadlift PR] - Preferred referral channel: [PLACEHOLDER, e.g. text a friend, post on social media] </inputs> <task> Write a short script (spoken version for in-session, plus a written version for text or email) asking for a referral, tied to the specific result and the stated channel. </task> <constraints> - Keep both versions short (spoken under 30 seconds read aloud, written under 80 words). - Reference the specific result, not a generic "if you know anyone" ask. - Make the actual ask (what to say or do) concrete, not vague. </constraints> <format> Two labeled sections: Spoken Version, Written Version. </format>

You are a personal trainer running a win-back campaign for clients who have gone quiet. <context> A group of former clients has not booked a session in over 60 days. You want a 3-touch sequence to try to bring them back before writing them off. </context> <inputs> - Client segment description: [PLACEHOLDER, e.g. clients who stopped after 3-6 months, previously training for general fitness] - Days since last session: [PLACEHOLDER, e.g. 60+] - Any known reason they stopped (if known): [PLACEHOLDER, e.g. schedule got busy] </inputs> <task> Build a 3-touch sequence (email, text, final email) spaced roughly a week apart, each with a different angle: check-in, a specific offer or easy re-entry point, and a final low-pressure close. </task> <constraints> - Each touch must have a distinct angle, not a repeat of the same message. - Keep every message short (under 100 words for emails, under 2 sentences for the text). - The final message should make it easy to say no without guilt, not just repeat the ask. </constraints> <format> Three labeled touches (Touch 1: Email, Touch 2: Text, Touch 3: Email) each with subject line where relevant and body. </format>

You are a personal trainer building a month of social media content to bring in new clients. <context> You post on 2 platforms and want a full month planned in advance instead of scrambling daily for ideas. </context> <inputs> - Platforms: [PLACEHOLDER, e.g. Instagram, TikTok] - Posting frequency: [PLACEHOLDER, e.g. 4x per week] - Real client wins or topics this month: [PLACEHOLDER, e.g. client hit first pull-up, new small-group class launching] - Target client type: [PLACEHOLDER, e.g. busy parents 35-50] </inputs> <task> Build a 30-day calendar at the stated frequency, mixing education content, the given client wins, and one soft offer post per week, each with a content idea and a one-line caption angle. </task> <constraints> - Use the actual client wins and topics given rather than generic fitness content. - Keep caption angles specific to the target client type, not generic motivational language. - No more than 1 direct sales post per week; the rest should be education or story-driven. </constraints> <format> A calendar table (Date, Platform, Content Type, Idea, Caption Angle). </format>

You are a personal trainer creating a welcome packet to professionalize the new client experience. <context> You want every new client to receive a single document covering what to expect, logistics, and policies, so nothing gets explained inconsistently in person. </context> <inputs> - Business or trainer name: [PLACEHOLDER] - Location or session format: [PLACEHOLDER, e.g. in-studio, home visits] - Cancellation and late policy: [PLACEHOLDER, e.g. 24-hour cancellation, sessions late more than 15 min are forfeited] - What to bring to first session: [PLACEHOLDER, e.g. water, sneakers, comfortable clothes] </inputs> <task> Build a welcome packet with sections: Welcome message, What to Expect in Session 1, Policies (using the exact policy text given), and Contact/Scheduling info. </task> <constraints> - Use the exact policy wording provided, do not soften or change it. - Keep the whole packet to a length that fits on 1-2 pages. - Keep the tone warm but clear; this is a policy document as much as a welcome note. </constraints> <format> A formatted document with 4 labeled sections, ready to export as a PDF. </format>

You are a personal trainer formatting your pricing into a clean, sendable menu. <context> You have your session pricing worked out but only as rough notes. You want a polished pricing menu you can send to prospects without looking unfinished. </context> <inputs> - Session types and prices: [PLACEHOLDER, e.g. single session $85, 10-pack $750, 20-pack $1350] - Session length(s): [PLACEHOLDER, e.g. 60 min] - Any add-ons: [PLACEHOLDER, e.g. nutrition check-ins, at-home programming] </inputs> <task> Build a pricing menu listing each package with price, per-session cost, and savings versus single sessions, plus a short line on any add-ons. </task> <constraints> - Calculate per-session cost and savings accurately from the numbers given. - Use only the prices and packages provided, do not invent additional tiers. - Keep the layout simple enough to read in under 30 seconds. </constraints> <format> A pricing table (Package, Price, Per-Session Cost, Savings vs. Single) plus an Add-Ons line. </format>

You are a personal trainer building a system to systematically collect and reuse client testimonials. <context> You want a simple template to send clients after a milestone that captures enough detail to turn into a testimonial or a short case study, instead of a generic 5-star review. </context> <inputs> - Milestone types to trigger this: [PLACEHOLDER, e.g. 3-month mark, hitting a stated goal] - Questions you want answered: [PLACEHOLDER, e.g. what changed, what surprised them, would they recommend and why] </inputs> <task> Build a short client-facing questionnaire (5-6 questions) designed to surface specific, quotable details, plus a separate internal template for turning a strong response into a 100-150 word case study. </task> <constraints> - Keep the client-facing questionnaire under 6 questions so completion rate stays high. - Design questions to elicit specifics (numbers, before/after) rather than yes/no answers. - The case study template must include a placeholder to confirm the client's permission before publishing. </constraints> <format> Two sections: Client Questionnaire (numbered questions), Internal Case Study Template (fill-in-the-blank structure). </format>

You are a personal trainer formalizing how your business runs day to day into a standard operating procedures document. <context> You are either bringing on your first assistant trainer or just want your own process written down consistently. You need an SOP covering the core recurring operations. </context> <inputs> - Standard session structure: [PLACEHOLDER, e.g. 5-min check-in, warm-up, main work, cool-down] - Cancellation policy: [PLACEHOLDER] - Client communication norms: [PLACEHOLDER, e.g. respond to messages within 24 hours, no programming changes over text] - Booking or scheduling tool used: [PLACEHOLDER] </inputs> <task> Build an SOP document with sections: Session Structure, Scheduling & Cancellations, Client Communication, and a New Trainer Checklist summarizing the above as a quick-reference list. </task> <constraints> - Use the exact policies and structure given, do not invent new rules. - Keep the checklist section to items that are actually actionable day one. - Write it so a new hire could follow it without additional explanation. </constraints> <format> A formatted SOP document with 4 labeled sections. </format>