Event Information

This Timer Tip Tuesday is all about getting the most out of Segments in RaceDay Scoring—whether you’re timing a standard 5K or a multi-stage ultra.

Join us for a quick and informative refresher on setting up on-course segments for a variety of race types, including:

• Standard splits (like 5K/10K/Half splits)
• Triathlons and multi-sport events
• Rest segments and flexible timing windows for non-traditional formats
• Ultras and other multi-loop or extended races

We’ll walk through the setup process, cover key use cases, and share tips for managing complex timing needs with confidence.

View Slides

Summary of Webinar 

Overview

This Timer Tip Tuesday session serves as a foundational refresher on RaceDay Scoring segments, designed for timers ready to move beyond basic scoring setup. The webinar explains what segments are, how they work behind the scenes, and how they impact results, reports, RaceJoy integration, and data quality. It walks through standard segment configurations for road races, then expands into more complex use cases like triathlons, combo events, rest segments, and lap races. While advanced scenarios are introduced, a follow-up session is referenced for deeper dives.

What Are Segments?

Segments define how RaceDay Scoring calculates time, pace, and distance between timing points.

Key concepts:

• Every event has a default entire-race segment

• Additional segments create:

  • Splits

  • Laps

  • Discipline legs (triathlon)

  • Combo/challenge totals

• Segments are built using:

  • Start location + occurrence

  • End location + occurrence

Segments rely on timing locations and occurrences, so correct location setup is critical.

Segment Distance vs. Cumulative Distance

Understanding this distinction is essential.

• Segment distance: Distance of the individual segment itself

• Cumulative distance: Total distance completed from the start of the race up to that point

Examples:

• Road races typically show cumulative distance and pace

• Triathlons typically hide cumulative pace and only show segment-specific pace

• The same segment setup can support both styles depending on display settings

Where to Configure Segments

Segments are managed from the Segments page in the race dashboard.

Important notes:

• Segments are event-specific, not global across all events

• Always confirm which event is selected (e.g., 5K vs. 10K)

• Segments can be copied between events, then edited as needed

• Saving applies across all events, so error messages may reference a different event than the one currently selected

Common Segment Errors Explained

A frequent error:

“Cumulative distance must match other segments ending at the same location and occurrence”

What it means:

• Two segments cannot end at the same location/occurrence with different cumulative distances

• Usually caused by:

  • Incorrect occurrence number

  • Incorrect finish location selection

Carefully review:

• End locations

• Occurrence counts

• Cumulative distance values

Key Segment Settings

Pace Type

• Can differ from distance units

• Examples:

  • Triathlon bike leg → miles/hour

  • Swim → minutes per 100 yards/meters

  • Transitions → Do Not Display

• Distance units and pace units do not need to match

Minimum Allowed Time

• Prevents unrealistic segment times

• Useful for:

  • Multi-lap events

  • Shared courses (e.g., 5K + 10K)

  • Protecting against missed reads

Can be set:

• At the segment level

• In combination with gap factors (not always required)

“Once This Segment Is Completed” Setting

• Prevents earlier segments from completing after a later one finishes

• Especially useful for out-and-back courses

• Helps avoid negative or impossible split times caused by missed reads

Hide From Report Columns

• Allows segments to exist without appearing in default results

• Common for:

  • Supplemental data

  • Bike splits in triathlons

  • Internal or diagnostic segments

• Hidden segments can still be added to custom reports later

Standard Split Use Cases (Single Discipline)

Most common for running, cycling, or skiing events.

Considerations when placing splits:

• Is the data useful to participants?

• Does it enhance spectator experience?

• Does it help timers detect missed reads or course cuts?

• Is the timing location practical for hardware or mobile timing?

Segments typically run:

• From previous split → next split

• Cumulative distance automatically calculated

Multi-Sport & Triathlon Segments

Typical triathlon structure:

• Swim

• Transition 1

• Bike

• Transition 2

• Run

Best practices:

• Transitions:

  • Distance = 0

  • Pace = Do Not Display

  • Time is still shown

• Cumulative distance for transitions should match the prior segment

• USAT-style reporting expects this simplified structure

• Detailed splits (e.g., bike splits) can be hidden and shown via custom reports

Rest Segments (Combo & Challenge Events)

Rest segments represent time not spent racing and are subtracted from total time.

Common use cases:

• Combo events (e.g., 5K + 10K)

• Challenge weekends

• Certain ultra or staged events

Key rules:

• Segment distance = 0

• Cumulative distance = same as preceding segment

• Must be marked as Rest Segment

• Typically hidden from reports

Lap Segments

Lap events use segments combined into laps.

Important notes:

• Lap locations must be marked as lap locations

• Segments define lap components

• Laps are configured separately using Setup Laps

• Best for events with many repeated loops

• For small lap counts, simple segment occurrences may be sufficient

Segments & RaceJoy Integration

Segments are required for RaceJoy timing integration.

Why:

• RaceJoy needs segment distances to map timing data

• Locations alone are not enough

• Proper segment setup ensures accurate notifications and tracking

Troubleshooting & Best Practices

• Physical course control is always better than software-only fixes

• Not every race needs:

  • Gap factors

  • Minimum segment times

  • Advanced restrictions

• Reads that are ignored will show why (gap factor, min time, etc.)

• Test segment output:

  • Results pages

  • Reports

  • RaceJoy views

• When unsure, ask:

  • What do participants expect to see?

  • What does the organizer want reported?

Key Takeaways

• Segments are the backbone of RaceDay Scoring logic

• Cumulative vs. segment distance drives how results are displayed

• Proper segment setup improves:

  • Accuracy

  • Reporting

  • RaceJoy integration

• Start simple, then layer in complexity only as needed

• Advanced scenarios will be covered in a follow-up webinar