Injury Management

Coachbase's injury system uses a three-level flag model to ensure every generated session is safe and appropriate for each athlete's current physical state. Flags are set by coaches and automatically applied by the generation engine.

Flag Types

Three levels of flags cover the full spectrum from acute injury to long-term monitoring:

FlagSeverityGeneration Behavior
Red Flag High — acute or serious injury All exercises targeting the affected body part are fully excluded from generated sessions
Yellow Flag Medium — managed or recovering injury Affected exercises are included but load is automatically reduced; a warning indicator is shown on the exercise row
Influence Factor Low — monitoring condition No generation restrictions applied; condition is tracked over time and visible in the athlete overview

How Flags Work

Red Flags

A red flag represents an injury that makes specific exercises unsafe to perform. When a red flag is active, the generation engine checks every candidate exercise's bodyParts field. Any exercise that targets the flagged body part is removed from the session entirely.

If a session would lose too many exercises due to a red flag, the engine substitutes corrective or alternative exercises that avoid the injured area. The coach is notified when substitutions occur.

🚨
Red flags apply to all sessions

Red flags affect every generation run for that athlete until the coach explicitly clears the flag. Changing the program settings or regenerating a session does not bypass active red flags.

Yellow Flags

Yellow flags indicate a managed or recovering condition where training can continue with modifications. The generation engine applies a load reduction of 20–40% to exercises targeting the flagged body part. The exact reduction depends on the athlete's load capacity setting.

Exercises modified by yellow flags display a warning indicator in the session view. Coaches can override the modified load manually in the edit sidebar if needed.

Influence Factors

Influence factors are non-restrictive monitoring entries. Use them for conditions that don't warrant training restrictions but should be tracked over time — such as chronic tightness, recurring soreness, post-surgical monitoring, or asymmetries flagged by a physio.

Influence factors appear in the athlete overview panel as a reminder to the coach during session review. They are logged with a date and can be annotated over time to track trends.

Creating a Flag

Navigate to the athlete profile and open the Influence Factors tab. Click Add Flag and fill in:

bodyPartstringrequired

The affected body part. Selected from the same body part taxonomy used in the exercise library — this ensures accurate cross-referencing during generation.

severity'red' | 'yellow' | 'influence'required

The flag severity level. Determines generation behavior as described above.

descriptionstringoptional

Coaching notes on the injury — mechanism, symptoms, treatment plan, or clinical notes. Displayed in the session view as a reminder.

onsetDatedateoptional

When the injury or condition began. Used for duration tracking and recovery timeline estimation.

expectedRecoverydateoptional

Target recovery date. Coachbase displays a reminder when this date passes and the flag has not been cleared.

Clearing Flags

Flags remain active until a coach explicitly clears them. This prevents accidental premature loading of recovering structures — no automatic expiry based on date.

To clear a flag, navigate to the athlete's Influence Factors tab, find the active flag, and click Mark as Cleared. The cleared flag is archived and remains visible in history with the date it was cleared.

⚠️
Clearing a red flag

Clearing a red flag immediately re-enables all previously excluded exercises for that body part. The next generation run will include those exercises again at normal load. Always confirm the athlete is fully medically cleared before removing a red flag.

Flag History

All flags — active, cleared, and archived — are visible in the athlete's Influence Factors tab under the History section. Each historical entry shows:

This history is valuable for identifying recurring issues or tracking recovery patterns over time.