Aggregate team scoring is a type of Team Scoring (as opposed to Relay Team Scoring) where each team member completes the entire race distance individually, and their results are combined to create a team score. This is commonly used in cross country and road racing where:
  • Each athlete runs the full distance
  • Individual times/places are recorded for each runner
  • Team scores are calculated by combining individual results (typically using place or time)
  • Teams can be scored based on a set number of runners (e.g., top 5 count for score)
  • Additional runners may affect other teams' scores (displacement)
For example: In a typical cross country meet, each team might have 7 runners, with the top 5 finishers' places being added together for the team score. A team with places 1,4,6,7,10 (sum=28) would beat a team with places 2,3,5,8,11 (sum=29), even though both teams had 7 runners compete.

Setup Basics:

Go to Scored Event > Team Scoring


Then select Aggregate Team Scoring from the scoring type dropdown:




Then select and apply your scoring rules:


Aggregate Scoring Options:
  1. Score Teams By
  • Determines which participant field to use for total team scores
  1. Tie Breaker Rule
  • Multiple options for resolving ties between teams
  1. Team Scoring Depth
  • Controls how many team members per team are included in scoring
  • Can be set at Scored Event Level or vary by Team Type

Cross Country Scoring Features:
  1. Use Cross Country Scoring
  • Enables displacement rules where runners over a set number per team (usually through Position 7) won't count towards their team score but will count against other teams
  1. Ghosted Runners
  • Set minimum number for ghosted participants
  • Choose between "Last Overall Score" or "Last Team Member Score" for ghosted runner scoring
  • Option to "Allow Under Minimum To Displace" - lets team members score regardless if team meets scoring depth
Gender-Based Options:
  1. Separate Report Sections By Gender
  • Creates separate report sections for:
  • Male
  • Female
  • Non-Binary
  • Useful when running all genders together but wanting split reports
  • Creates separate result sets for each gender when publishing online
Tier-Two Scoring:
  1. Available for cross country scoring
  2. Creates multiple report sections based on two scoring tiers per team
  3. Useful when running all team participants together but wanting to split teams based on two scoring depths
Qualifier Event Features:
  1. Typically used for championship events
  2. Specify number of teams and individuals that qualify for next round
  3. Can set:
  • Team Qualifiers
  • Individual Qualifiers
  • Option to require individual qualifiers to be based on finish position
  1. Commonly used for State or Regional championships
Additional Features:
  1. Ability to set team time display options
  2. Option to create gender-specific report sections
  3. Customizable scoring depth settings for both regular and tier-two scoring
  4. Support for different tie-breaker rules
  5. Ability to handle ghosted runners in various ways
  6. Flexible configuration for qualifier events


Select Delete and Continue:

Next, apply the Team Type Scoring rules to your Team Types.

 

Applying Team Type Scoring Options:

This step determines how scoring rules are applied across different team categories (Male, Female, COED, etc.) in your event.

Options:

  1. Apply Scoring Rules to All Team Types

  • Updates all team types with the same scoring rules
  • Best for consistent scoring across all categories
  1. Add Scoring Rules to Team Types Without Scoring Rules
  • Only affects team types without existing rules
  • Preserves current settings while adding new ones
  1. Make No Changes to Team Types
  • Keeps all current settings as is

Important Note About Reports

Team types are combined in reports by default. To separate them, you can:
  • Filter the default report to show specific team types
  • Create separate reports for each team type
  • Add sections within one report for different team types
? Tip: Choose your reporting structure early in the setup process to avoid rework later. Customized reports are deleted and will need to be set up again!

See our guide on splitting Team Reports by Team Type for more info here


Finally, save scored events:


This will enable new Team Report Sections for this Scored Event. To add a new Team report go to Reports > Build Report. Then name the Report, select the Event you're going to add a Report Section for, then select the type of Report Section to add.


To post Team Scoring to RunSignup, you must have a "Team Finisher List" section in a Report which you will be able to auto-save to RunSignup. 


Recent Updates to Team Scoring Default Reports

Simplified Team Results Publishing

RaceDay Scoring has streamlined the process for publishing team results to RunSignup. You no longer need to create separate reports and result sets for team scoring - the default report now handles both individual and team results automatically.

Benefits

  • Single report handles both individual and team results
  • Automatic team standings on RunSignup
  • Simplified workflow with no duplicate result sets needed
  • Clearer, more consistent team results presentation

Legacy Setup vs New Setup

Before: Required separate result sets for individual results and team scoring
Now: Default "Team Finisher List" report includes everything needed for both individual and team results


Key Requirements

To ensure team standings appear correctly on RunSignup, your default report must include these fields:
  • Team Place: Required for overall team standings
  • Team Gender Place: Required for gender-specific team standings
? Tip: This works similarly to how Age Place must be included for Age Group results to appear on RunSignup.


Be sure that if you choose to customize your Default Team Aggregate Reports that you do not remove these fields, otherwise the Team Standings Tab will not populate at RSU!


Remember: If you need to separate results by team type, you can still do this through filtering, separate reports, or report sections while maintaining the simplified publishing process. That is explained more in depth here