Skip to main content

Set up your Soma workflow

A good workflow makes it easier to build training plans and stay informed about athlete progress. Start by creating reusable templates, then set up daily Slack updates and optional fatigue alerts.

1. Create and save your templates

Create your first template and name it 12 Sessions.

Add a session named Baseline:

  • Enable Minute on Minute (MoM) mode.

  • Add your chosen scale.

  • Enable Baseline Comparison.

When the athlete repeats the baseline, Soma automatically calculates the comparison and sends the results to them. The comparison also appears on your dashboard, making it easy to review changes in performance.

Next, add three core sessions named Session 1, Session 2, and Session 3. For the baseline and each core session, we suggest adding PFTT or PVT-B to both the Pre Session and Post Session sections to monitor fatigue.

Save your template, then repeat the process to create 16 Sessions and 20 Sessions templates using the structure below.

You now have three reusable templates with a baseline session, named core sessions, and your chosen fatigue checks. No other tasks are needed at this stage. You’ll add them when building each athlete’s plan

2. Load a template and build your athlete’s plan

Load the saved template for your chosen plan length and build the baseline session for your athlete.

If you prefer to review baseline data before finalising the plan, leave the core sessions blank, with their names and any chosen scales or MoM settings prepared. Once the athlete completes the baseline, review their results and use them to build the core sessions.

If you prefer to prepare the full plan in advance, build the baseline and core sessions together, then follow the copy-and-paste steps below before assigning the completed plan. Choose the approach that suits your workflow.

3. Copy your core sessions and adjust the plan

Once your core sessions are built:

  1. Tap Collapse Sessions.

  2. Tick the core sessions you want to copy.

  3. Tap Copy.

  4. Tap Paste as many times as needed to create your desired number of sessions.

Once all sessions are in place, update their names and make any adjustments for progression and periodisation.

MoM mode and scales are not copied over by default, giving you the flexibility to choose where to use them. Both are optional. Simply switch on MoM mode and apply your chosen scales to the sessions where you want them.

4. Connect Slack using a company account

Use a separate Slack member account for Claude so Soma Intelligence updates are easier to recognise. Give this account your company name and logo.

  1. Connect Slack through Claude using the company account.

  2. Invite the company account to the channel where you want updates.

  3. Continue using Slack from your personal account.

Soma Intelligence updates will appear under the company account instead of your own name. Check your channel notification settings to make sure they match how you want to receive alerts.

5. Schedule daily athlete progress updates

Once Slack is connected, create a scheduled task for the athlete you want to follow.

  1. Go to Scheduled Tasks.

  2. Click New Task.

  3. Select Create with Claude.

  4. Paste the prompt below and replace the placeholders with the athlete’s name, Slack channel, update time, and timezone.

Set up a scheduled task that posts [ATHLETE NAME]’s current plan progress to my [#CHANNEL] Slack channel every day at [TIME] [TIMEZONE]. Use the Soma connector. Look up the athlete by name first, then read their current plan and plan progress from their athlete status. Do not use the plan list for this, because it can flag an old, completed plan as active.

Keep the instruction to use athlete status in your prompt so the update uses the correct source for the athlete’s current plan and progress.

6. Set up optional fatigue alerts

Create a scheduled Slack alert to flag athletes whose task results show both slower and more variable responses.

  1. Go to Scheduled Tasks.

  2. Click New Task.

  3. Select Create with Claude.

  4. Paste the prompt below and replace the placeholders.

Set up a scheduled task that checks my athletes’ [TASK NAME] results every day at [TIME] [TIMEZONE] using the Soma connector.

Only check results from the last [NUMBER OF HOURS] hours. Flag a result only when both conditions are true for that same result: mean reaction time is above [REACTION TIME THRESHOLD] ms AND variation is above [VARIATION THRESHOLD] percent. Exceeding only one threshold must not trigger a flag.

Post flagged results to my [#CHANNEL] Slack channel under the heading “[HEADING]”. Include one line per flagged athlete, starting with 🚩, followed by their name, task name, session date and time, mean reaction time in ms, and variation as a percentage. If an athlete has multiple qualifying results, include their most recent qualifying result.

Do not alert on the same result again in a later scheduled run. If nobody meets both conditions, or there are no new qualifying results, post nothing.

Fill in the placeholders

  • [TASK NAME]: Use the exact task name shown in your plan builder, such as PFTT, RVIP, or Colour Shape Task.

  • [TIME] and [TIMEZONE]: Choose when the daily check should run.

  • [NUMBER OF HOURS]: Use 24 for a daily lookback, or 26 to provide some overlap between checks.

  • [REACTION TIME THRESHOLD]: Enter the mean reaction time threshold in milliseconds.

  • [VARIATION THRESHOLD]: Enter the variation threshold as a percentage.

  • [#CHANNEL]: Enter the Slack channel for alerts.

  • [HEADING]: Choose a message title, such as PFTT Fatigue Flag.

Review the task’s usual results in your dashboard before choosing thresholds. Set them to highlight changes that warrant your attention, then adjust if alerts are too frequent or miss changes you want to review.

Why require both conditions?

Requiring both thresholds means the alert identifies results that are slower and more variable, rather than flagging either measure alone. Use the flag as a prompt to review the athlete’s results and context; it does not confirm fatigue by itself.

Did this answer your question?