Notes for Coaching Scenarios

Notes are more than a scratch pad — they're the closest thing you have to a client CRM. Used well, they become a knowledge base that makes every coaching decision better, because the context behind past decisions is always accessible.

This page covers specific scenarios where notes add the most value to your coaching.

Tracking injury history

Injuries rarely appear in a single check-in and disappear. They evolve over weeks. Notes let you build a timeline.

When a client first reports pain:

Left knee pain during squats — started last week. No acute injury, came on gradually. Reduced squat depth today and will monitor.

Link this to the check-in where they reported it.

Follow-up notes over subsequent weeks:

Knee pain improving — no issues with box squats at parallel. Will try full depth next week.

Knee back to 100% — returned to full depth squats, no pain. Keep monitoring for the next 2-3 weeks.

Why this matters: Three months from now when you're programming their next phase, you can search their notes for "knee" and see the full history — what aggravated it, what helped, and how long recovery took. That's information you'd otherwise have to remember or ask the client to repeat.

Pro tip: Make a to-do when an injury is first reported:

Check-in on knee pain status — set due date for next week's check-in day

This ensures you actively follow up rather than hoping the client mentions it again.

Recording exercise preferences

Some clients love certain exercises. Others dread them. Some have equipment limitations you need to remember.

Examples:

Hates barbell back squats — feels uncomfortable even with good form. Responds much better to leg press and goblet squats. Don't programme back squats unless specifically discussed.

Only has dumbbells up to 25kg at home gym. Travels to a full gym on weekends. Weekday sessions need to be dumbbell-only.

Loves pull-ups — personal favourite exercise. Good for motivation when programming is feeling stale. Keep at least one pull-up variation in every plan.

These notes save you from making the same programming mistake twice and help you build plans your client actually enjoys following.

Documenting programming rationale

When you change a plan, write down why. Your future self will thank you.

When changing a meal plan:

Dropped calories from 2,400 to 2,100. Weight has been flat for 3 weeks despite good adherence (check-in 12 March). Sleep and steps are fine, so this isn't a recovery issue — just time to create a larger deficit.

When changing a workout plan:

Moved from Phase 2 (strength) to Phase 3 (hypertrophy). Client's 1RM estimates have plateaued — switching to higher volume to build more muscle before the next strength block. Plan to return to strength in 6 weeks.

When keeping a plan unchanged:

Weight hasn't moved this week but measurements are down and photos look leaner. Holding macros steady — likely recomposition. Will reassess in 2 weeks if weight still hasn't moved.

This is especially valuable when you have 15+ clients and can't remember why you made a specific decision for a specific person six weeks ago.

Client lifestyle context

Context that doesn't live in check-in data but affects your coaching decisions.

Work and schedule:

Works night shifts (10pm-6am) Mon/Tue/Wed. Training happens in the afternoon before shifts. Check-in day is Thursday because that's when their "week" resets.

High-stress job in finance. Stress eating is the main adherence challenge, not knowledge. When work pressure spikes, focus responses on damage limitation rather than perfection.

Travel and access:

Travels for work 1 week per month (usually week 3). Needs a travel-friendly plan variation each month. Hotel gyms typically have dumbbells and a cable machine.

Summer holidays in August — 3 weeks, limited gym access. Plan to programme a bodyweight maintenance phase.

Social and dietary:

Vegetarian — no meat, no fish. Eggs and dairy are fine. Custom food library entries needed for most protein sources.

Goes out for dinner every Friday — don't stress about Friday macros, focus on weekly averages.

Tracking coaching milestones with to-dos

To-dos aren't just for "review this check-in." Use them for coaching milestones that need to happen at specific times.

Plan review reminders:

Review meal plan effectiveness — 4 weeks into current cut. Due: 15 April.

Deload scheduling:

Schedule deload week — client has been training hard for 5 weeks. Due: next Monday.

Goal check-ins:

Mid-point goal review — client's weight goal is 12 weeks, we're at week 6. Assess whether target is realistic. Due: 20 April.

Phase transitions:

Transition from cut to maintenance — client hits target weight or 12 weeks, whichever comes first. Due: 1 May.

Re-assessment points:

Reassess training split — client asked about switching to push/pull/legs. Review progress on current plan before deciding. Due: after next check-in.

Building context for AI responses

Notes linked to check-ins feed directly into AI response drafts. This means your observations become part of the AI's context when generating the next response.

Strategic notes for AI context:

Client is feeling demotivated — weight hasn't moved in 2 weeks. Next response should emphasise non-scale victories (measurements are improving, strength is up).

Client mentioned wanting to compete in a powerlifting meet next year. Start weaving competition prep language into responses to build excitement.

Sleep has been under 6 hours for 3 consecutive check-ins. Need to address this directly — it's affecting recovery and likely stalling progress.

These notes ensure the AI draft picks up on nuances you've identified, rather than just responding to the numbers.

Keeping notes useful over time

• Be specific. "Knee issue" is less useful than "Left knee pain during deep squats — gradual onset, no acute injury." Specific notes are searchable and actionable.
• Date-stamp context when it matters. Notes have timestamps, but if you're referencing a future event ("holiday in August"), include the date so it's clear when reading the note months later.
• Link to check-ins when relevant. A note about a client's sleep problems is more useful when you can jump to the check-in that prompted it and see the actual data.
• Use to-dos for anything time-sensitive. If a note implies a future action, make it a to-do with a due date. Notes without to-dos are observations; notes with to-dos are commitments.
• Don't duplicate what's in the data. You don't need to note "weight was 82.3kg this week" — that's in the check-in. Note the interpretation: "Weight spike likely water retention from high sodium weekend — expect it to drop back next week."