Pre-Race Medical Preparation: The Foundation of Safety

The most effective medical support begins long before you set foot on the trail. Comprehensive preparation ensures that your support team has the information and resources to act decisively. This phase encompasses not only documenting your health profile but also training your crew to interpret data and respond to anomalies.

Document Your Complete Medical Profile

Create a detailed medical document that includes:

  • Chronic conditions (asthma, diabetes, heart conditions, epilepsy) with current management plans and triggers.
  • Allergies (food, drug, insect), including anaphylaxis triggers and prescribed epinephrine auto-injectors with expiration dates.
  • Current medications with dosages, schedules, and potential side effects that could affect performance (e.g., beta-blockers masking heart rate elevation).
  • Previous injuries (stress fractures, ligament damage, concussions) that may be aggravated by prolonged exertion, plus specific rehabilitation protocols.
  • Blood type, emergency contacts, insurance details, and primary care physician contact.

Share this document electronically with your support crew, your primary care physician, and the race medical director (if permitted). Printing a hardened copy and storing it in a waterproof bag in your drop bag provides offline backup. Consider using a secure cloud service like Google Drive or Dropbox with offline access enabled on your team’s devices.

Choose Your Medical Support Team Wisely

Your support team should include at least one person with formal medical training—an EMT, paramedic, nurse, or sports medicine doctor. If you cannot recruit a medical professional, partner with a family member or friend who completes a wilderness first-aid course (e.g., Wilderness Medicine Institute or NOLS) before the race. The team should also include a logistical coordinator who can manage communications and transportation for evacuations.

Define roles clearly: who monitors your GPS tracker, who answers your scheduled check-in calls, who drives to the nearest hospital if needed. Practice these roles during a pre-race simulation, such as a long training run where you intentionally send a distress signal. For example, have your crew respond to a mock “orange” scenario where they must meet you at a specific trailhead with medical supplies. This rehearsal reveals gaps in communication protocols and equipment reliability.

Create a Detailed Communication Plan

Map your race route with all checkpoints and expected arrival times. Identify cell service windows—most race organizers share mobile coverage data or you can use apps like CellMapper to estimate coverage. Agree on a primary and secondary communication method for each section. For example:

  • From start to first checkpoint (10 km): cellular text messaging.
  • From first to second checkpoint (25 km, no cell service): satellite SMS via Garmin inReach.
  • From second to third checkpoint (40 km, partial cell): cellular if available, else satellite.

Build buffer time into each arrival estimate to account for delays, and agree that your team will initiate a check-in call if you are more than 30 minutes late without communication. Also plan for weather delays: if thunderstorms are forecast, adjust the schedule so you check in earlier before the weather window closes.

Communication Technology and Tools: Your Lifeline

Choosing and preparing the right devices is critical. Redundancy is the key principle—never rely on a single tool. Your tech stack should include satellite messaging, GPS tracking, health monitoring, and backup power.

Satellite Communicators and GPS Trackers

Devices like the Garmin inReach Mini 2 or Spot X allow two-way messaging via satellite, independent of cellular networks. Their tracking features let your support team see your location in real-time on a web-based map, with automatic updates every 2–10 minutes. Program the SOS button to trigger an immediate call to a global rescue coordination center, which will alert local emergency services and your support team.

Test your device before race day: send test messages to your crew, verify tracking intervals, and ensure you know how to change batteries or recharge (most last 20–30 days in power-save mode). For races in deep canyons or dense forests, consider a device with Iridium satellite network (like inReach) rather than Globalstar, as Iridium has better coverage near the poles and in rugged terrain.

Wearable Health Monitors

Advanced wearables such as the WHOOP 4.0 or Garmin Enduro 2 track heart rate, blood oxygen saturation, skin temperature, and even stress scores. During a race, your support team can receive automated alerts if your heart rate exceeds a safe zone (e.g., prolonged time over 180 bpm while running slowly) or if your SpO₂ drops below 90%. These metrics provide early warning of heat exhaustion, altitude sickness, or cardiac strain, often before you feel symptoms.

Set up notifications so that your crew receives a summary after each scheduled check-in. For example, a Garmin LiveTrack session can share your heart rate data alongside your location. Some watches, like the Coros Apex 2 Pro, offer “Emergency Contact” features that automatically send your location if you take a hard fall—enable that setting before the race.

Backup Power and Connectivity

Pack at least two portable power banks (10,000–20,000 mAh each) in drop bags along the route. Use solar chargers like the GoalZero Nomad 10 for multi-day races. Carry a waterproof battery case and a short charging cable taped to your pack strap. Turn off non-essential features on your phone (Bluetooth, Wi-Fi, background apps) to conserve battery, and disable cellular data when you are out of range to prevent repeated network searches.

Consider a dedicated handheld two-way radio (e.g., a GMRS/FRS radio) for short-range communication at aid stations or between crew vehicles—this can be a secondary option if satellite or cellular fails. Many ultra races now provide radio frequencies for race officials; program those into your device. For very remote races, a Personal Locator Beacon (PLB) like the ACR ResQLink adds another layer of SOS-only redundancy without subscription fees.

Emergency Protocols: When Seconds Matter

Staying connected is only valuable if everyone knows what to do when a genuine emergency arises. Pre-agreed protocols reduce panic and speed response.

Define Emergency Levels and Signals

Create a three-tier system:

  • Level 1 (Yellow): Minor issue (blister, fatigue, low water). Resolved with support crew advice or supplies at next checkpoint. Signal: send a text saying “YELLOW – need advice.”
  • Level 2 (Orange): Moderate issue (vomiting, severe dehydration, possible mild hypothermia). May require crew to bring supplies or meet you at a defined road-accessible point. Signal: send “ORANGE – need meet at mile 22.” If you have a tracker, activate the “help” (not SOS) function.
  • Level 3 (Red): Life-threatening (chest pain, major bleeding, unconsciousness). Activate SOS on your satellite communicator immediately. Your support team should simultaneously call race medical and local emergency services.

Print these definitions on a waterproof card and attach it to your pack or drop bag. Ensure your crew and the race medical director have the same card. Also pre-load your satellite device with custom messages that match these levels, so you can send them with a single button press.

Medical IDs and Documentation

Wear a medical ID bracelet or temporary tattoo that lists your name, key conditions (e.g., “Type 1 Diabetic,” “Allergic to Sulfa Drugs”), emergency contact phone number, and a link to your digital medical profile. Services like Road ID offer products optimized for endurance athletes. Carry a copy of your insurance card and a consent-to-treat form signed for your support team. In international races, also carry a translation card for key medical phrases in the local language.

On-Route Evacuation Planning

Review the race course map for evacuation points—places where a vehicle can reach the trail (fire roads, mountain passes, trailheads). For unsupported or self-supported races, pre-arrange with your support crew that they will drive to the nearest evacuation point based on your GPS location. If the race provides medical services, understand how to contact them via satellite phone numbers or radio frequencies posted at each aid station.

For severe weather or terrain that makes helicopter extraction necessary, program emergency service numbers for each region you cross into your device speed-dial. Confirm that your satellite communicator's SOS feature works in the country where the race is held (some devices require regional subscription plans). In mountainous areas, know the local air ambulance contact—some regions, like the Alps, have dedicated mountain rescue numbers that bypass 911/112 delays.

During the Race: Maintaining Communication Discipline

Execution during the race is where plans either succeed or collapse. Consistency and discipline are everything.

Scheduled Check-Ins

Agree on check-in intervals that align with your device's battery life and your crew's ability to monitor. For example:

  • Every two hours during daylight, every hour at night.
  • At each aid station (even if you don't stop) send a short message: “Arrived mile 40, feeling good, HR 145.”
  • Before and after each major climb or water crossing.

Use pre-written message templates so you can send them quickly: e.g., “OK” / “Tired but OK” / “Need supplies – bandage, electrolytes” / “Need meet at next road.” Your crew should acknowledge each message within 15 minutes. If you miss a check-in by 30 minutes and they cannot reach you via satellite, they should initiate the “orange” protocol (try phone, then contact race officials).

Communicating Health Metrics

Share brief updates that help your support team assess your status objectively:

  • Hydration: “Urine light yellow, had 500ml water since last check.”
  • Energy/food: “Ate one bar, feeling nauseous, will try broth at next aid.”
  • Pain/injury: “Left ankle tender but no swelling, slowing pace.”
  • Mental state: “Struggling, but staying positive. Talk me through next 10K.”

If you are using a wearable, share a screenshot or a short summary of key metrics. Your crew can then compare with your baseline data from training runs. For example, a resting heart rate that is 15 bpm higher than your normal while you are moving slowly could indicate early signs of overexertion or illness.

Managing Communication Fatigue

Constant messaging can drain mental energy and battery. Streamline the process:

  • Assign a single device as your primary messenger (e.g., satellite communicator) and keep your phone turned off or set to airplane mode except during aid station stops.
  • Use voice-to-text for longer messages to save typing time.
  • Pre-program inReach or Spot with a set of macros (e.g., “1 = All good,” “2 = Need call at next hour,” “3 = SOS scenario”).
  • Let your crew know you will check messages only at certain waypoints—do not feel obligated to respond to every location update ping.

If you feel overwhelmed, a simple “OK – talk at mile 50” is sufficient. Trust that your crew will continue monitoring your tracker and will act only if something seems wrong. For multi-day races, also schedule a longer phone or satellite call every 12 hours to discuss overall status and adjust pacing or nutrition.

Post-Race Medical Follow-Up

Crossing the finish line does not end the need for medical support. Many health issues emerge hours or days after the race, especially rhabdomyolysis, dehydration, kidney strain, and post-exercise immune suppression.

Immediate Post-Race Assessment

Arrange for your support team to meet you at the finish with a basic medical check: blood pressure, heart rhythm, urine color (dipstick for blood/protein if available), and mental status (confusion, memory gaps). If you have a wearable, download the race data and compare peak stress trends against your normal baseline. Report any symptoms—even transient ones—to your primary care provider within 48 hours. For ultra runners, a simple blood test for creatine kinase and creatinine can rule out rhabdomyolysis; discuss with your doctor if you have dark urine or muscle pain.

Debrief with Your Support Team

Schedule a formal debrief within three days of finishing. Discuss what worked in your communication plan and what broke down. Did the satellite device lose signal in canyons? Did your crew misinterpret a message? Use this feedback to refine protocols for your next race. Write down lessons learned and share them with the community—consider contributing to race medical research if appropriate. For example, many ultra races now collect data on communication failures to improve safety standards.

Adapting for Future Races

The data you collected—heart rate ranges, sleeping patterns, hydration logs—can inform your training and pacing for future events. For example, if your heart rate drifted upward late in the race despite consistent effort, that could indicate heat buildup or dehydration that may be prevented with better cooling strategies or earlier electrolyte intake. Use your crew's check-in notes to adjust your medical planning: if they noticed you were slow to respond to messages after 80km, schedule more frequent check-ins for those later stages next time.

Conclusion

Staying connected with medical support during a remote ultra race is not merely a safety measure—it's a performance enabler. When you know that a capable team has access to your location, health data, and a clear action plan, you can push harder, recover faster, and trust your instincts. Every minute spent preparing your communication infrastructure is an investment in peace of mind. Implement these strategies, test them in training, and refine them based on real-world feedback. The mountains will test your body, but they should never test your ability to call for help.