This webinar is ideal for Timers using RaceDay Scoring for team/relay events. We’ve enhanced RaceDay Scoring’s team scoring to make your job easier and more flexible. In this webinar, we’ll cover:
- Simplified result publishing – Faster, more efficient team scoring result sharing.
- Custom scoring algorithms – Greater flexibility to match your event’s unique team scoring rules.
- Aggregate team scoring improvements – More accurate and streamlined data handling.
Learn how to leverage these updates to save time and deliver better results.
If you are unable to attend, you can sign up for the webinar to automatically receive a recording of the session.
Summary of Webinar
What this webinar covered
Aggregate team scoring 101 (what it is, how it differs from relay team scoring)
Critical setup settings (where people commonly go wrong)
Workflow update: simplified RunSignup results publishing for aggregate team scoring (big change)
New feature: Custom Point Tables (generated formula or static import)
Best practices (setup order, report strategy, autosaves, testing)
Q&A
Aggregate team scoring basics
RDS has two team scoring types:
Relay: each member does a leg of the full race
Aggregate: each member completes the full distance, and the team score is derived from members’ placements/times
Aggregate scoring mechanics:
Each team member earns a point value or time value (depending on method)
The system sums (or averages) the top X members (X = scoring depth)
Typically: lowest total points/time wins
Scoring depth prevents “1-person team always wins” and defines minimum team size to be complete + how many members count.
Critical settings to get right
1) Team scoring must be enabled on the Scored Event
Common support issue: team results look wrong because team scoring wasn’t actually enabled.
Best quick check: go to Scored Events and look for the Team Scoring button/status.
2) Cross Country scoring vs Standard Aggregate
This is the #1 “pick the right mode” decision.
Cross country scoring adds displacement rules:
e.g., “score through 5, displace through 7”
runners in positions 6–7 affect other teams’ scoring (displacement)
Standard aggregate: anything beyond scoring depth does not affect other teams
Rule of thumb they gave:
Ask the organizer about displacement.
If they don’t know what that is → you probably want standard aggregate
If they want it → they’ll know it → use cross country
Cross country mode also disables age group functionality (fits typical XC meets).
3) “Separate report sections by gender”
Only use when teams should auto-split into male/female sections (common in XC school format).
Don’t check it unless you really mean it.
4) “Score teams by…”
Defines how members get points/times:
overall place, age group place, total time, age grade place, etc.
5) Scoring depth scope: by scored event vs by team type
Usually: by scored event (all team types share the same rules)
Use by team type only when different divisions have different depths (e.g., competitive scores 5, social scores 10)
Handling multiple team types (reports)
Team scoring relies on having teams in team types (divisions/categories like D1/D2/Social).
By default, RDS generates a report that may combine all team types in one section.
If you need separate results by team type:
Edit the report section’s team type selection
Rename report to reflect the type
Duplicate and repeat for other team types
They highlighted that when you add a team report section and multiple team types exist, RDS prompts:
“Which team types should be included in this report section?”
Selecting multiple = combined results.
Team standings reports (in RDS vs RunSignup)
Default report created is a Finish List style (looks like individual results listing).
Publishing that default report to RunSignup can still generate team standings online.
If you want team standings views inside RDS, you typically add supplemental reports like:
Team Summary (top teams summary)
Team Detail (team members listing per team)
Often combined in a “newspaper style” report (summary + detail)
These presets appear only if team scoring is enabled on the scored event.
Big update: simplified RunSignup results publishing (aggregate team scoring)
Old workflow (before recent change):
Needed two reports uploaded to RunSignup:
overall report (everyone)
team finisher list report (team members only) to generate the RunSignup Team Results tab
Result: two result sets online → confusing.
New workflow (now):
One default Finish List report is enough.
Publish one report → RunSignup generates:
age groups/divisions
team standings tab
from that same report.
Key detail:
A setting called “Allow unattached participants/runners” is on by default so non-team participants still show in the report.
Certain columns are required for RunSignup to generate the Team Results tab:
team place fields (e.g., team place / team age group place)
plus the age place field for divisions
Guidance: don’t delete these columns (you can hide them if you don’t want participants seeing them).
New feature: Custom Point Tables for aggregate scoring
Use case: when scoring wants higher points = better (inverted) or any nonstandard points system.
Two options:
1) Generated points (formula)
Inputs:
Start: points for 1st place (e.g., 1000)
Subtract: decrement per place (e.g., 1 → 1000, 999, 998…)
Minimum: floor points for places beyond the range (e.g., 1 participation point, or 0)
Formula concept:points = start - (place - 1) * subtract, floored at minimum.
2) Static point table (upload/import)
Import a spreadsheet mapping place → points (totally custom)
You can also add/edit rows inline after import (no need to reupload for small tweaks)
They explicitly asked users to share creative use cases—they expect interesting applications.
Best practices checklist (their “do this to avoid pain” list)
Get team scoring requirements early (rules, depth, divisions, displacement)
Review RunSignup groups/team types early (don’t discover a week before that you need male/female/co-ed divisions)
Configure team scoring first, before customizing reports
Changing team scoring rules can cause RDS to regenerate default reports and blow away customizations
Decide how to handle multiple team types
Separate reports? One report with multiple sections? Combined?
Add supplemental team reports (summary/detail) if you need team standings within RDS
Set up autosaves early and confirm the RunSignup Team Results tab appears as expected
If you edit reports after autosaves exist, re-save the autosaves
That “you made changes, update autosaves” message matters
Shorten/customize result set names (Manage Result Sets)
For RunSignup display: hide (don’t delete) team columns if they’re required but not useful to participants
Test your reports
Use report preview with:
show non-starters / show non-finishers / include without bib / push non-finishers to bottom
Helps validate filters and “who will appear” before race day
Note: multi-segment events often keep “show non-finishers” on to show split progress
If testing autosaves with fake times:
Disable results notifications during testing
Re-enable for race day
Q&A highlights
Can you add extra credit points to a team (e.g., donut run bonus)?
No—no per-team adjustment layer. You can only control points by placement via custom point tables.Can you give extra points to age group/overall winners (e.g., +10 bonus)?
No (same limitation—no dynamic bonuses on top of placement-based scoring).USAF club team scoring with individuals?
Answer was effectively no / no change (requires scoring same team across multiple filters; not supported in that way).Can you show average team time in results?
In RDS: yes (via team scoring fields/settings and adding the column).
For RunSignup display: likely via adding it as an additional column in the uploaded report (they weren’t 100% certain it appears as a native team-standings metric).If results notifications were disabled and you turn them on mid-event, do missed people get notified?
No—notifications only go out for results published after it’s enabled. Be careful.