RaceDay Scoring v4.0.53

Feature Updates

Added quick navigation links from dashboard timing location panels to timing location settings.

Quick navigation from Dashboard to Timing Location configuration is supported if a time filter or configuration needs to be adjusted for a given location.

Data Check changes to participants will appear in the “Participant Edits” area of participant management and will be attributed to the data check that affected the change.

Bug Fixes

Fix for Start/FInish location with overlapped reads occurring.

Processing of reads has been updated for a common Start/Finish location accepting overlapped reads where the combination of gap factor and minimum finsh time configuration helps determine the correct overall start and finish reads to use.

Team Relay Group Names appear in Announcer Screen.

For both the “use same bib number” and the “use different bib number” use cases, the Team Relay Group Name will appear in name and team fields in the Announcer Kiosk screen.

Participant and Group Data Sync Fix.

We found that it was possible based on “real time” that a change at RunSignup due to check-in app changes were not seen in RaceDay Scoring. We have modified the sync timestamp logic to ensure this can not occur.

Tooltips for Main and Backup Streams on a Timing Location will always appear.


7/12/2024 – RaceDay Scoring v4.0.52 HOTFIX

Bug Fixes

Corrected an issue for RunSignup result publishing where places greater than 1000 were not being accepted due to formatting.


7/11/2024 – RaceDay Scoring v4.0.51

Feature Updates

Added the ability to change Giveaway Assignments for Participants.

We will detect when changing events whether or not the new event has the same Giveaway Options available. If so, we will map to the matching option from the original registration. If there are no matching Giveaway Options available, we will alert the user that their selection has been cleared and they may re-select a new one if they like.

Updated Failed to Sync errors directing the user to the notifications area where they can find details about why the sync failed.

Added the ability to use Raw Read filters in Data Check Reports.

You can now use Raw Read data to drive Data Check Reports, so that you can have more control over changing data based on raw reads. Before this, you could only use Data Actions with Raw Read filters that would run all the time automatically.

Now you could, for example, have a Data Check report that finds all participants with a raw read seen between 6am and 7am at your swim entrance mat (which is not used for scoring purposes) that are not in the 6:30am Corral, and decide which you would like to change over to the 6:30am Corral.

Added a Chip Difference Field to Reports and Data Checks.

This field will show the difference in time between each participant’s assigned start and their chip start. It will always be a positive number.

This can be used as a way to find runners that may have started in the wrong corral, if their chip difference is more than say 30 minutes.

Added an Occurrence Count to the Announcer Display.

This will be based on the number of occurrences the Announcer Screen has seen, not scoring. This means that if you clear the Annoucner, it will reset the Occurrence counts for all participants.

Made Fields in the Announcer Display Editable.

You can now edit column headers in the Annoucner Display to change the label and the text alignment to suit your needs.

Added helper text reminding users that duration inputs are not time of day inputs.

Fields that do not have an AM/PM selector are duration includes, but some users accidentally enter a time of day into them. Now there is a note telling the user that these fields are not time-of-day fields.

Added support in connector for additional precision in ISODATETIME.

Certain IMPINJ files would have extremely precise times included in their files which we were not supporting. We will now support out to 7 decimals, rounding to the first 3 hundredths.

Bug Fixes

Corrected an issue when publishing average lap results to RunSignup where too many decimal places would show.

We trim these values in RaceDay Scoring, but we were not when pushing the results to RunSignup.

Fixed a bug causing the Sync Disabled banner to always show for non-RunSignup/Local Races.

Corrected an issue that would allow users to add invalid columns in certain reports.

For example, including any results field in the “All” Scored Event Reports would not work for all but the first scored event in the list of included scored events, so those are no longer able to be included as a field.

Corrected an issue causing CSV import updates to not be applied.

Corrected an issue causing users to have to select a default event when importing updates from a CSV.

Fixed a bug with the duplicate bibs view when there were multiple participants with the same bib.

Corrected certain sync failed errors that would not tell the user why the sync had failed if they did not have proper access to the Race.

Corrected an issue causing imported Giveaway Options to be cleared on the next sync cycle.


6/26/2024 – RaceDay Scoring v4.0.50

Feature Updates

Added a way to view a list of all Participants that have the same bib as another Participant.

This is found under Participants > Actions > Show Duplicate Bibs.

Added a “Show Data Header” checkbox to CSV and TXT exports.

This determines whether or not the data headers are included (IE Name, Gender, Age, Clock Time, etc…). You can uncheck this if you would like to hide all data headers for all sections in this Report.

This is supported from the Reports > Actions > Export function as well as when setting up a CSV/TXT Auto-Save.

Added a Poor/No Network Banner.

We now will show a banner letting you know that we have detected that you have poor network, no network, or your sync is disabled. Additionally, if you have any stuck pending sync queue items, we will show a count of them, with a button that you can click that will bring you to the Pending Sync Queue where you can view/delete those changes if needed.

You can also dismiss the banner if you would not like to be shown it again.

Added support for BibTag readers with the Beta MyLaps Cloud Integration.

Bug Fixes

Corrected a bug that made the tooltip not show when hovering over the Participant sync error icon.

Corrected an issue that would allow you to delete Result Sets from the Result Set Management area that are in use by Reports.

This would cause an error on the next result push, so we have disabled the delete result set function if this result set is in use in a Report in this scoring file.

Corrected a bug causing results to be cleared and re-published for each and every result push to RunSignup.

Corrected a problem that would not let RACE RESULT timers enter in “-1” for the Gunshot Marker Identifier.


6/20/2024 – RaceDay Scoring v4.0.49

Feature Updates

Added Edits View to Participant Record.

This is an audit log for all Participants that allows you to view all changes that we have seen for this Participant, with the most recent at the top. We will show you the previous value of the changed field, what source changed it (RSU, which Data Action, etc…), and when the change occurred. This will help in troubleshooting situations where you are trying to find out what caused some data to change, or what the previous value was so you can revert the change.

You can find this on the Participant view, under the Scoring Data tab.

Data Action Changes are now stored for future reference.

Now when you make a change to a Data Action, the original one is deleted and a new one is added. The old Data Action is available to be viewed by checking the new box to show deleted Data Actions. This can be helpful in troubleshooting what may have caused problems by being able to go back to see what your previous settings were at the time you experienced an issue.

Added Name Field to Data Actions.

You can now name your Data Actions so they will be easier to recall what they were designed to do. The name is shown in the Data Issues > Log area so you can more easily tell what changes were caused by what Data Action.

Added Support for Data Actions to be run on entities in multiple events.

This mostly applies to Super/Sub Event Participants, and requires that either a Registration Event Participant Filter is set up or an Event Raw Read Filter is set up on the Data Action in order for the system to know which version of the participant to select.

Added Warning and Prevention of Issues with Data Actions with circular logic.

We had some issues come up where users would set up two Data Actions that a single participant would qualify for at the same time, causing their information to change back and forth over and over infinitely.

We have added a warning when we detect this state, and we now will only process the first Data Action change we see for a participant to prevent the system from locking up by trying to keep changing the data back and forth.

Data Issues are now included in the Export/Import of Race Files.

Notably, this will include the Data Action Logs so that you can investigate changes made to Participants by Data Actions even if you export/import the race to another computer.

Adjusted RunSignup Team Results for Team Scoring Methods that do not have a depth value.

We now will not show the “Finisher 1, Finisher 2, Finisher 3” etc… columns in the RunSignup Team Results Tab when publishing Team Finisher List Reports to RunSignup for events that do not have a depth value in their Team Scoring setup.

Adjusted RunSignup Team Results for Lap Aggregate Team Scoring.

We now will show proper data fields in the RunSignup Team Results for Lap Aggregate scored events. We used to show the total time and total distance of the first member of the team in the Team standings for that team. We now show the total distance or average distance and total/average time based on the Team Scoring configuration.

Added the ability to delete Stream timeshifts when renewing a Race.

This is on by default so we will not carry over out of date time shifts from the previous year.

Bug Fixes

Fixed a bug causing RunSignup Results publishing errors when importing a Setup Only export file from another Race or a previous year of a Race.

Corrected an issue with Reports when Team Types become invalid for a Report.

For example, if a Team Type’s Team Scoring rules are cleared, but is already included in a Report, we will warn the user that they need to update the report to remove the no longer valid Team Type from it instead of getting a hard error.


6/13/2024 – RaceDay Scoring v4.0.48

Bug Fixes

Corrected a bug when importing a spreadsheet of changes that would cause the first name mapping to fail.

Added a clear button to time entry fields.

Previously there was an issue if you partially filled out a time entry field then removed the data from it, where it would not allow you to save the page with a warning that the field was not filled correctly. Now a button will show that will allow you to clear the field.

Corrected an issue causing Raw Read edits to not save.

Corrected a bug causing Team Aggregate Reports for Lap Races to not work properly.

This would impact Team Summary Reports as well as when publishing Team Finisher List Reports to RunSignup.


6/7/2024 – RaceDay Scoring v4.0.47 Hotfix

Bug Fixes

Corrected a bug when renewing a scoring file for a Race that had auto-saves.


6/6/2024 – RaceDay Scoring v4.0.46

Feature Updates

Implemented Result Set Management Functionality.

Found under Reports > Result Set Management, this page will list out any RunSignup Result Sets, allow you to change the order of the result sets, and change most of the settings about Result Sets that are available to you on RunSignup, besides editing the email address, which can still be done when creating the result set in the Auto-Save Settings.

New features include making the Result Set Private or Public, marking the results as preliminary, hiding Splits in Results, hiding Event Names, deleting the Result Set, and clearing the results within a result set. We also show a count of the current number of finishers in each Result Set and provide a link to view each Result Set.

Refactored our Report code to prevent cases where RunSignup Results would stop publishing.

Added Phone Number as a field that can be added to Reports.

Bug Fixes

Fixed a bug causing Result Set changes at RunSignup to not be retained after saving the Auto-Save Settings for an existing Result Set within RaceDay Scoring.

This would cause customizations to a result set that we previously could not control to be wiped out if you needed to save Auto-Save Settings.

Corrected a bug causing reads to not become used after being forced to be used under very specific circumstances.

What would happen was that a non-start backup read would still be skipped over in favor of another later read that’s within the gap factor and from a main stream, despite it being marked as ignored.

Fixed a bug causing the “Used” column data to be incorrect when exporting Raw Reads.

Corrected a bug that would allow you to re-select a deleted Result Set if you delete an Auto-Save then immediately add one back again.

Prevented a crash that could occur when copying Segments between Events if no target Event was selected.


5/30/2024 – RaceDay Scoring v4.0.45

Feature Updates

Support Not Answered (null) state for Yes/No Custom Questions Type.

The Yes/No RunSignup Custom Question may have not been given an answer during registration or values were not provided by import use cases. If there is NOT an actual response provided RaceDay Scoring will show the response of Not Answered for that question. That response can also be used to send back a null response to RunSignup if needed.

Improved import participant support for update only use cases by matching id.

Updates to RaceDay Scoring participants via the import action now do NOT require event, first and last name when doing updates only by registration_id, raceday scoring id or external reference id.

Raw Read views now show timeshifted values if time shifts are applied to stream settings.

Previously timeshifts on streams only showed the affects on the scored reads shown in the participant view and in reporting. Now timeshifted reads will show in raw read views.

Bug Fixes

Fixed processing of Min Finish Time and Max Time Offset values for more complicated multiple occurrence finish setups.

Read processing will now work correctly in all scored event setups with multiple segments when using the Min Finish Time and Max Time Offset values on the overall scored event.

Fixed generate read testing when creating large numbers of reads for a given timing location.


5/23/2024 – RaceDay Scoring v4.0.44

Feature Updates

Added an Estimated Finish Time of Day Report Field.

This is the first of a few features we have coming related to estimated finish times. For now, you can add a column in Reports that will give you a guess of when we think a Participant will finish based on the last completed split’s pace. Please note that this will only fill in for events that have multiple segments.

In the future, we will be added a summary level view of estimated finish times on the Dashboard, so that you will be able to quickly check to see when the first and last finish of each of your events are expected to arrive at the finish. Then in a future update, we will send this data to the Timer Dashboard and eventually Race Dashboard, so that your organization can check in on the Race progress remotely.

Implemented the ability for the Chip2 field to be automatically filled in based on the bib number as you are typing in a bib number while adding or editing a Participant.

Previously, only Chip1 would be automatically pulled in from the Bib/Chip Cross-reference.

Removed the Default Min. Lap Time Setting if not using the Default Lap.

If you are not using the Default Lap, this setting would not do anything, but it was still shown to the user, causing confusion. Now we will hide this setting if you are not using the Default Lap feature.

Added more helpful error information if a report fails to build.

Now if you have an issue with a report, the error message will tell you which report needs to be corrected, and will give you instructions to review the scoring options, filters, and sorts, which should help resolve the issue.

Bug Fixes

Corrected an issue when publishing results to RunSignup from a report that is sending Gender Place as a whole number and has participants in the report that are marked as DNQ.

We will now send DNQ as an arbitrarily high number to prevent RSU from rejecting the “DNQ” flag in the gender place column. This makes it so that Gender Place at RunSignup can still be sorted, and those marked as DNQ will show at the bottom of the list.


5/15/2024 – RaceDay Scoring v4.0.43

Feature Updates

Added the ability to collect reads from the same folder on more than one File Stream.

Added validation on all duration fields to prevent users from partially filling out duration time fields like Gap Factors, Min Finish Times, etc…

Added the ability to select Super-Events in the Registration Event Dropdown in the Participant Filters area of the Corral Member Assignment Rules feature.

Before this change, you could not set up a Corral Member Assignment Rule to automatically move participants into a Corral based on their original Registration Event if they were a part of the Scored Event based on a Super/Sub Event relationship. Now you will see all related Registration Events when selecting the Registration Event field in the Participant Filters area of the Corral Member Assignment tool.

Bug Fixes

Corrected an issue causing the connector to not bring in new reads from a file if the user changed the Stream’s file location while the connector was running.

To install the update, click the button below to install and restart the application.


5/9/2024 – RaceDay Scoring v4.0.42

Bug Fixes

Corrected an issue causing a tooltip to not display when hovering over the “Catch-All” Corral Setting.

Corrected two issues that would cause results to not be correct after making changes to participant data without saving the Scored Events page after making the change.

The two things that could cause this were manually swapping bibs between two participants, and changing the gender of a participant.


5/2/2024 – RaceDay Scoring v4.0.41

Feature Updates

Implemented Impinj-Speedway Direct and File Streaming support.

Added additional time filter data to the Dashboard Stats view.

We used to only show the main timing location time filter information on the Dashboard stats. Now we will show all additional time filters you have added here as well.

Bug Fixes

Fixed an issue with the Timestamp field in the Announcer display causing it to show in UTC time instead of local time.

Fixed an issue causing the unknown reads count to not decrement after ignoring an unknown read.

Fixed an issue that would allow users to enter an invalid IP address into the Stream Setup forms.


4/19/2024 – RaceDay Scoring v4.0.40 Hotfix

Bug Fixes

Corrected a bug causing an issue viewing Participants in a non-RunSignup integrated Race if they were imported from a spreadsheet.


4/17/2024 – RaceDay Scoring v4.0.39

Feature Updates

Performance Updates.

We have implemented significant optimizations to the processing and calculation of result data in this update. As a result, the scoring process is now approximately 2x faster for most events, with an even greater impact on races with numerous teams and/or scored events.

This should reduce the amount of time you may experience the application to slow down or freeze up while collecting reads for events with lots data.

In a future update, we plan to separate the scoring and syncing processes from the user interface processes. This means that if the scoring and/or syncing processes take a long time to complete, the user interface will not be affected, ensuring a smoother experience.

Added Local Super/Sub Event Settings.

You can now use Super/Sub Events with local Races as well as with RunSignup Races. This is useful for scenarios where you want one registration to be distibuted into more than one event, like a combo or challenge where participants can compete in multiple events in a day or weekend.

You can find these settings in the Event Settings when adding a new Race.

You can also use the Local Super/Sub Event Settings for RunSignup integrated Races as well. This is handy if you don’t want to adjust the RunSignup settings, as these Super/Sub Event settings will not update the settings at RunSignup.

You can access these via the “Edit Race” button under Sync Settings, which has been made available for RunSignup Races as well as local Races.

Bug Fixes

Corrected a bug causing the sortable column headers to only sort in one direction.

To install the update, click the button below to install and restart the application.


4/11/2024 – RaceDay Scoring v4.0.38

Feature Updates

Added support for the “Number to Show” setting in Reports when publishing results to RunSignup.

Previously, all data would be sent to RunSignup even if the report was customized to only show the top X results.

Added a warning when setting up a Scored Event that would result in participants being duplicated due to Super/Sub Event Settings.

Added a warning when we detect that Super/Sub Event Settings have changed at RunSignup.

This may impact your existing Scored Event “Included Events” choices, so if you see this message we suggest reviewing your Scored Events setup and the RunSignup Super/Sub Events setup to ensure you don’t end up having duplicated participants because of the new settings.

Bug Fixes

Fixed a bug causing an error when trying to submit a help ticket from a Race that is greater than 10 megabytes.

Fixed a bug causing column label customizations to not show in the Report Builder and Report Template Builder.

Fixed incorrect Super/Sub Event tooltip messages.

Corrected an issue for some users who could not start or stop the connector process.

Fixed an issue that could occur when creating a backup file from a Race whose filterer had crashed.

We have also added more logging to identify reasons for filterer crashes.

4/3/2024 – RaceDay Scoring v4.0.37

Bug Fixes

Corrected an issue that could cause errors when attempting to connect to an Announcer Kiosk Window.

Fixed a bug causing auto-saves to pause after making changes to a report.

Fixed a bug causing Date of Birth to always be invalid when importing Participants from a CSV.

Corrected an issue causing Participants to be marked as Did not Start after setting a Corral Start Time.

Added more protection around the Import from Cloud screen to prevent users from clicking import again while it’s still processing.

We found that this could cause the system to load two copies of the same race file on that computer, which can cause database issues.


3/28/2024 – RaceDay Scoring v4.0.36

Feature Updates

Added a Minimum Segment Time Feature in the Segment Setup.

You can now define a minimum Segment Time when building your Segments. This is particularly useful for situations like a Triathlon with multiple distance options that use the same readers for transition. This will let you say that the Sprint bike leg must be no faster than 20 minutes, but the Olympic no faster than 1 hour, for example.

This should cut down on the need to set up multiple locations just to be able to use different time filters for different events.

Added a Clear function to the RaceDay Hub Announcer Kiosk Window.

This will let you clear all the currently displayed data on the window.

Changed the RaceDay Hub Announcer Kiosk Window to not show every read for each Participant.

We now will only show the amount of occurrences that the Timing Location is set up to accept. We use the Gap Factor on the Timing Location to determine how long to wait before showing another read for that same Participant.

We have also updated the Announcer Timing Location settings so that you will be able to define a max occurrence count on this Timing Location Type, as well as a Gap Factor.

Lap Timing Locations will display as many reads as are seen as there is no limit to the number of occurrences in Lap Timing Locations, but we still will use the Gap Factor on that Timing Location to determine the min time between reads that we display in the Announcer Window.

Implemented Read Cutoff Time for Relay Team Entities.

Bug Fixes

Fixed a bug that would not allow you to log out if your Race list was empty.


3/22/2024 – RaceDay Scoring v4.0.35

Feature Updates

Added MyLaps Cloud Streaming Integration Beta.

This is a new Direct Stream Type for MyLaps timers who have access to the beta of MyLaps’ new Cloud reader management software.

Updated default RACE RESULT gunshot trigger value from 99999 to -1

We have discovered from RACE RESULT timers that this default changed from 99999 to -1 at some point on the RACE RESULT side.

Added more graceful handling of the connector shutdown if the application crashes or shuts down without the connector being made aware of it.

Before this change, if the app crashed or shut down before the connector did, the connector would stay running in the background which could cause problems when trying to start up the application again. Now the Connector will automatically shut down if it detects that RaceDay Scoring is not running.

Removed Division Placements for athletes in progress.

Before this change, we would send a Division Place to RunSignup for athletes who have not yet finished. This would cause a significant increase in the amount of data and API requests that we would have to make for each result push. For larger races that have many splits on course, this could significantly impact the performance of results publishing and cause issues where it takes a long time for division placements to appear at RunSignup, or in the worst case, having the Division placements disappear completely. With this change, you should see an improvement in publishing performance for races with many splits and participants.

Added a warning when publishing a Report to RunSignup that does not have an Age Place column included.

If you don’t include this column, Divisions will not be created/populated at RunSignup. This warning will now tell you that when you try to publish a report to RunSignup that does not have this column.

Bug Fixes

Corrected an issue causing RunSignup Results to be cleared and rebuilt with every result push.

This could cause slow result processing for larger events.

Made File Extension required in the setup form for RFID File Streams.

This was required in order to accept reads, but the form would allow you to create an RFID File Stream without setting a File Extension.

Corrected a bug with the Participant import process that would cause times to not properly import into time-formatted custom fields or custom questions.


3/13/2024 – RaceDay Scoring v4.0.34

Feature Updates

Added Total Rest Time for Lap Events.

A new column Total Rest Time is available for lap reporting for lap events that support rest segments. In addition, the lap details for a given participant will show the rest time per lap based on the rest time in each rest segment of a given lap. These rest times are then accumulated in a Total Rest Time column for reporting.

Improved Shutdown Experience.

In order to ensure the integrity of the database, users will not be able to shutdown RaceDay Scoring if a race deletion is underway. In addition, the overall shutdown prompts will appear as required no matter the user actions on the screen.

Bug Fixes

Fixed Segment Editing of attributes like “Is Rest Segment”.

The ability to select the different checkboxes on Segment Detail form is fixed.

Fix delete of place when participant record changes and using the “Send as Whole Number” setting with RunSignup.

The ability to remove the place for a participant due to read or status changes is now supported when also using the setting “Send as Whole Number” on the RunSignup autosave settings.

To install the update, click the button below to install and restart the application.


3/7/2024 – RaceDay Scoring v4.0.33

Feature Updates

Added Distance and Time Adjustment functionality to Lap Races.

Participants and Teams for Lap Races can now have an adjustment added. If you add a distance adjustment to a Lap Participant, the system will add an additional lap for that participant with the distance you entered into the adjustments area. If you include a time adjustment, that will be added to the additional lap.

All adjustments for Lap Races are added to the end of the race. This is typically done to add on a partial lap at the end of the event for those who were unable to complete a lap within the cutoff time. The race organizers want to give them partial credit.

Added Read Cutoff Time Field to Adjustments.

You can now enter the time of day to stop considering reads for a participant on the Scoring view. This feature is particularly useful for “Last Man Standing” events, where you need to forcibly stop collecting reads for someone for the remainder of the event.

Please note that this feature is currently only available for Individual Participants, but it will be added to Relay Teams in the next update.

Added more Lap Race fields for Leaderboard and Race Progress use cases.

We have recently added some useful data fields to reports for Lap Races. These fields include the name of the last lap completed, the time of the last lap completed, and the time of day that the last lap was completed.

These data fields can be used to create leaderboard display reports for lap events. You can sort the results based on the time of day that the last lap was completed (so the most recent passing shows first) and show the time of the last lap completed, along with any other relevant information.

Once you create the reports, you can use the HTML Auto-Save functionality and display them on a monitor connected to your scoring computer, or save them to a Dropbox folder and view them on another device connected to the internet. This way, you can have a fully customizable Lap Race leaderboard display.

It would be helpful to include some of these fields in the online results for events that aim to provide real-time progress tracking for spectators as well. For example, including the time of day of the last lap was completed for each participant would be very useful for those who are tracking their friends and family members participating in long lap events.

Added warning to the user when starting up RaceDay Scoring with less than 1gb of hard drive space available.

If hard drive space runs out while scoring an event it can cause a corruption of the database. We now alert the user when they have less than 1gb of space left, suggesting that they start thinking about cleaning up their hard drive before they end up running out of space and corrupting their database.

Bug Fixes

Corrected an issue with recalculating reads when the incoming chip codes case and the chip code in the cross-reference case do not match.

For example, if the chip code from the reader was lx1111 but the chip code in the system was LX1111, we had a bug that would cause scoring to not work correctly after manually recalculating reads.

Corrected an issue with the Super/Sub Event Panel where we would not show all sub-events for a Super Event underneath the Event Name.

Added more logging to help us track down an issue that has been reported where results would stop publishing to RunSignup periodically, forcing the user to save auto-save settings.


2/27/2024 – RaceDay Scoring v4.0.32

Bug Fixes

Fixed an issue with our system logging system causing system crashes.

Fixed a typo on the chip cross reference maintenance screen.


2/22/2024 – RaceDay Scoring v4.0.31

Feature Updates

Made Rest Segments Optional in Lap Races.

There is a new setting in the Scored Event setup for Lap Races that is on by default which makes it so that Rest Segments within a Lap are not required for that Lap to be considered completed.

This helps in scenarios like stair climbs where you do not expect the athletes to cross back over the starting mats after their final descent. With this setting on, their Laps are considered complete at the top of the stairs.

Added Lap Fields to the Report Filtering Area.

We have added a few new fields that can be used to filter reports for Lap Races.

-Num. Laps Finished

-Total Lap Distance

-Total Lap Time

For example, these fields will allow you to create reports that are filtered to show only those participants over or under a certain lap count.

Removed the Report Title/Section Header from CSV and TXT Report Exports and Auto-Saves.

This is a setting found when exporting a Report and setting up an auto-save on a report that is CSV or TXT that will allow you to decide whether or not you’d like Report Section Headers included as a row in the data or not. By default, these Section Headers are no longer included.

Bug Fixes

Corrected an issue when trying to ignore a very long chipcode.

Fixed an issue causing a crash when trying to send results to RunSignup with a column header that has a very long name.


2/15/2024 – RaceDay Scoring v4.0.30

Bug Fixes

Corrected an issue that could cause columns to be associated with the wrong data in RunSignup Results.

Fixed a bug that would cause Participants to remain “In Progress” after their reads have been deleted.


RaceDay Scoring v4.0.29

Feature Updates

Added support for RunSignup’s [EST_FINSH_TIME] Result Notification Tag.

If you customize your Split Notifications and include this tag, the TXT/Email alerts to participants and spectators will include an estimate of their finish time if they continue at the pace they are currently averaging.

This feature is found on RunSignup under RaceDay Tools > Results > Show More > Customize Results Notifications.

Bug Fixes

Corrected a critical issue that would cause problems loading a Race that had over 32,667 participants, or 16,334 if they all had bib and chip numbers.

Fixed a bug causing the Race List to not display the correct number of pages when filtered to only show races that have passed.

Fixed an issue causing Corral Assignments made via a Data Check Report to not save to the Participant record.

Corrected an issue with RunSignup Split Results not displaying in the correct order after re-ording Segments in RaceDay Scoring.

Fixed a bug causing Data Actions to not import correctly when importing a Race file.

Addressed Issue when scoring a Race that crosses over Daylight Savings Time.

If a Race is being scored and crosses over the Daylight Savings Time change, there will be a set of times that will be ambiguous. We will not be able to determine accurate times for races that are crossing over DST because of this. The recommended workaround would be to change the race date to another day and adjust your stream read dates accordingly.


RaceDay Scoring v4.0.28 Hotfix

Bug Fixes

Corrected a critical issue that would cause problems loading a Race that had over 32,766 reads.


1/18/2024 – RaceDay Scoring v4.0.27

Bug Fixes

Adjusted how we set and get Age Group Placements in order to avoid situations where the Age Group Place would appear blank for all participants in RunSignup Results.

Improved performance by reducing the amount of read data to recalculate when participant data changes.

We have reduced which fields will trigger reads to recalculate, and made it so that we will only recalculate reads for participants that have had some data changed about them that would impact scoring. This will help with performance and with participant edit screens updating as you are editing them when reads from other participants come in.


1/12/2024 – RaceDay Scoring v4.0.26 Hotfix

Fixed a critical bug causing reads to be marked as manually ignored for all Races on a computer when resolving an unknown read that had no bib associated with it.

It should not be possible to have a read without a bib number, but we found that you could add one via the Add Raw Reads function. We have fixed the ignore reads function if it is used on an unknown read without a bib, and we have updated the Add Raw Reads function to prevent this from occurring going forward. We also found that it is possible to import a CSV of Scored Reads that have no bib numbers associated with them, so we have made a change to prevent that import as well.


1/11/2024 – RaceDay Scoring v4.0.25

Bug Fixes

Fixed a bug causing the Min. Finish Time setting to not work properly for Events that use multiple occurrences.

Corrected an issue causing Time Formatting settings to not apply until you saved Scored Events after making the change.

Made a correction to the rounding rule used for TFRRS Reports to match their requirements.


1/4/2024 – RaceDay Scoring v4.0.23

Feature Updates

Added “Min Finish Time Allowed” and “Max Chip Start Time Offset” settings on the Scored Event level.

These new settings will simplify the setup and execution of scoring for many races. Instead of relying on time of day filtering at the Timing Location level, you can now define a minimum accepted finish time for each Scored Event.

For example, if you have a 5k and a 10k that use the same start/finish location and start at 9am, you no longer need to create two Timing Locations. You can use the same Timing Location for both Scored Events and specify the minimum finish time for each event, such as 14 minutes for the 5k and 30 minutes for the 10k.

This new feature will also make things easier on race day if your start time changes. Previously, you had to adjust the time of day for each Timing Location. Now, the filtering will adjust automatically when the start times change.

In addition, there is a new “Max Chip Start Time Offset” setting, which is similar to the Min Finish Time but for start times. This setting selects chip start reads for participants within a certain amount of time since the start time, which you can specify based on the expected time for all participants to cross the start mats for the given Scored Event. For example, it could be a minute or two for a small 5k or 30 minutes for a large wave start event.

Note: You will still need to set a time for the accept times starting/until settings in the Timing Location, but these new settings will override them. So, if you want to just rely on the Scored Event Min. Finish Time Allowed/Max Chip Start Time Offset settings, you would want to set the accept start times until setting to something very late and the time to start considering finish times very early to ensure that you never need to adjust them if your start time shifts.

Added Corral Member Counts to the Corral List View.

Now when you navigate to the Corrals page, we show a total count of Members in each Corral so you can quickly check in on the numbers to ensure that your assignment rules are working as expected, and so that you can easily verify the number of participants you expect to see in each wave start.

These counts include both individual participants and relay teams.

Updated Timing Location Settings View for Announcer Mode.

We have changed the setup for Timing Locations when you enable to Announcer Timing Location mode so that you no longer have to enter the irrelevant time filter and occurrence settings as they do not apply to the Announcer functionality.

We have also updated the Timing Location Type selection to include the Announcer Timing Location setting. This means that you can now choose between four different Timing Location Types: Finish/Split, Start & Finish/Split, Start Times Only, or Announcer. The Announcer option is no longer a checkbox, which should help eliminate any confusion about which Timing Location Type to select when using the Announcer Setting.

Updated Announcer Window Initialization to Require that the user selects the Timing Locations they would like to include in this window instead of requiring that they remove the ones they do not want to include

We found that most of the time users would typically want to only include a single Timing Location. This should make setup easier especially if you are working with a lot of different Timing Locations.

Added the ability to Ignore Unknown Reads.

You can now choose to ignore a read in the Unknown Reads view, which can be useful if you want to exclude it from the dashboard count. This feature will come in handy for those who have a test chip that they don’t want to be counted in the dashboard statistics.

Added setting to Ignore Chips that are not included in the Cross-Reference.

If you are utilizing a Bib/Chip Cross-Reference, you can use this new setting in the Unknown Reads View to exclude any chips that are not a part of the reference list from the Unknown Reads Count. This will help in eliminating any erroneous reads that may have originated from invalid sources.

Added Connecting/Disconnecting Status to Reads Indicator.

When starting or stopping the collection of reads, the indicator will now be yellow until the process has successfully started or stopped. This will help make the status of the connector process more clear.

Bug Fixes

Fixed a bug causing results to not update automatically after a Raw Read is deleted for that Participant.


RaceDay Scoring v4.0.22

Bug Fixes

Fixed an issue causing users to not be able to close the Pending Sync Queue dialog.

Corrected a bug that caused the app to crash when changing Events in the Team Type list.

Prevented additional errors occurring when sync fails.

Fixed a bug causing backup reads to be selected over primary reads for Start locations.


RaceDay Scoring v4.0.21

Feature Updates

Added a “Clock Pace” field that will include the pace for the Entire Race Segment that this Report is for based on each Participant’s gun start time instead of their chip start time.

Bug Fixes

Improved RunSignup Results syncing to only clear and resend Division placements if a change in the division standings was detected.

We are working on a number of changes to the RunSignup Results sync code to address reports of Divison placements being cleared at RunSignup and not coming back, or taking a long time to repopulate. This change should help a bit by reducing the amount of times we clear Division placements to a minimum, but we have also added logging to help us investigate this issue further if it continues.

We also plan on a few more improvements to this area over the next couple of weeks.

Corrected an issue causing certain links to be invalid in the app when followed in a certain order.

Corrected an issue with Timing Locations > Scored Reads view where the Segment name each read completes would not be correct in some cases.

This would also impact the Recent Reads by location full screen views.


RaceDay Scoring v4.0.20

Feature Updates

Improved the application startup process to detect if the Connector is already running, then automatically shut down that process before starting the application.

We found that users could get into a bad state where they are unable to start the connector if the app shut down before the connector shut down. This should prevent issues if this happens again going forward.

Bug Fixes

Fixed a bug causing Essay Responses at RunSignup to be cleared.


RaceDay Scoring v4.0.19

Feature Updates

Added a count to the Sync Queue Button in the Sync Settings Area.

This will help make it more clear if you have a stuck item in your sync queue that needs to be deleted.

Updated Currently Pending Sync Queue Page.

We have added a Sync Status field to each pending Sync Queue item that will either be “Error” or “Pending”. We will now mark Sync Queue items as an Error if they will not sync to RunSignup, and Pending if they will on the next sync cycle. Any items that are an Error should be deleted in order to stop continuous sync errors.

Added link to Sync Queue from Participant Sync Failed Pop Up Message.

Added a Merge Duplicate Participants function to Participants > Actions.

If you have two participants with identical names, ages or dates of birth, and genders in the same event, you will encounter a sync error as RunSignup does not permit such occurrences. Typically, the solution is to remove the duplicate record after transferring any necessary data from it. With the new update, you can view all the duplicated records and decide which information to keep from each entry during the merge process. The process will automatically remove the duplicate participant that you choose not to keep.

Bug Fixes

Fixed a critical bug that would cause Age Group Placements to not show up at RunSignup due to old Divisions at RunSignup.

It is possible for old Divisions to cause issues if they were created and renewed in the RunSignup renewal process, but not by RaceDay Scoring or The Race Director, or if they were created by RaceDay Scoring or Race Director before April 2022. This is because the source of the Division was not being sent to RunSignup to determine what software created it.

To avoid such issues going forward, we will automatically remove any Divisions that were not created by RaceDay Scoring or The Race Director since April 2022.

Fixed a bug that would warn users when removing a bib assignment from a participant that this bib is already in use if someone else in this Race also does not have a bib assigned.

Fixed a bug that could allow Participants to be added without an Event, which would cause a Sync Error.

Corrected a bug causing Corral Changes to not sync to RunSignup.

Corrected a bug causing a sync error when no Corral Start Time was provided when creating a new Corral in RaceDay Scoring.

Fixed a bug that would cause an infinite loop of failed syncs due to a duplicated participant being created under certain circumstances.

Added a check to the installer to try to detect and prevent installing an older version on top of an existing installation of RaceDay Scoring.

This could cause database corruption issues.


11/16/2023 – RaceDay Scoring v4.0.18

Feature Updates

Changed the RunSignup Corral Integration to no longer update the Corral Start Time at RunSignup with the actual start time in RaceDay Scoring.

We used to update RunSignup with the Corral Start time that was set in RaceDay Scoring.

Since this is used to hold the scheduled start time, or even sometimes something like “5 minutes after the first wave”, this would cause problems when the race renewed, as registration coordinators would typically want to change it back to the scheduled start time after renewal, instead of it showing the exact time of day that the Corral started the previous year.

We will now no longer update the Corral Start Time at RunSignup with the actual Corral Start Time in RaceDay Scoring.

Bug Fixes

Corrected a major issue causing Question Response data loss at RunSignup after renewal if a new Custom Question had been added since the previous year.

We found that if a Race adds a new custom question to RunSignup after renewing, when the Timer renews the scoring file, the responses for the participants in the new version of the Race will have their responses cleared. This has been corrected going forward.

Prevented sync errors when deleting participants who have not yet been synced to RunSignup.

We found a condition where you could get into a cycle of sync errors if you add participants while offline then delete the same participants, or if you quickly add and delete the same participants before they were synced to RunSignup. This would cause a bad reference to a participant when we try to sync the pending adds and deletes in a row. We now will update the list of pending sync items internally before the sync goes up to RunSignup.

Corrected a few bugs with the installer which could cause the shortcut to not appear.

Fixed an issue with Timing Location Bib filters when using a crossreference file.

We used to always look at the raw bib on the read itself when determining whether a read meets the bib filter conditions, but we will now look at the cross reference and base the filtering on the bib the participant the read is associated with is wearing, instead of the raw bib value. This is important if you’re re-assigning bibchip codes.

Fixed an issue causing the participant view count and page values to not reflect participants in events that are not being synced.


11/9/2023 – RaceDay Scoring v4.0.17

Feature Updates

Added Unknown Reads Count and shortcut to RaceDashboard.

You will now find an Unknown Reads count on the Dashboard just below the Raw Reads count. This will display a count of unique bib numbers that are unknown, and if you click it it will bring you to the Unknown Reads Resolution area where you can create a new participant record or associate the read with an existing record. This will make it easier to tell if you have unknown reads and makes it faster to resolve them.

Added Crossreference Bib to Raw Reads View when encountering an unknown Chip read.

Added Unassigned Bibs Report to Participants > Actions > Unassigned Bibs

This will display a list of bib ranges that are not assigned in this Race.

Reduced RaceDay Hub Kiosk Report Refresh Interval.

RaceDay Hub Kiosks used to have a hardcoded 15 second refresh interval. We have reduced this to 1s to match the fastest speed that is available for RaceDay Hub Auto-saves. This will make the RaceDay Hub Result windows display results much more quickly.

The warning about the start time not being set has been updated to stop displaying after each auto-save cycle.

We have also updated the logic to only display to the user if the system time is after the estimated start time.

Bug Fixes

Prevented a crash when a Report contains columns that were invalid for the Report Type.

We now warn the user about this instead of crashing.

Fixed a bug causing the Assign Corrals function to not overwrite existing Corral Assignments

Corrected a bug causing the filterer to crash due to an infinite loop when using the Ambiguous Reads selection area.

Prevented a bug with Top Finisher Categories by removing “Scored Event” as an available field in the Participant Filters area.

Since Top Finisher Categories are always associated with a single Scored Event, the ability to filter Top Finisher Categories by Scored Event is not needed. You can use Registration Event to filter by if you want to only score Participants in one of the Registration Events included in this Scored Event.


10/26/2023 – RaceDay Scoring v4.0.16

Feature Updates

Added Super/Sub Event Note Panel and Tooltips.

For Races that use Super/Sub Events enabled at RunSignup, we now show to the user a notes panel on the Scored Events page, as well as show tooltips over the registration event selection components, that tell you which events this event is related to.

Removed “Default Scored Event” Functionality.

This feature was set by accident or used incorrectly 99% of the time. It would make it so that Participants in all Registration Events that are not included in other Scored Events would show up in this Scored Event. Since this was essentially a shortcut to checking each box individually, and just caused confusion as to what it did, we have removed it.

Bug Fixes

Fixed a bug that caused Backup Stream Reads to be selected over Main Stream Reads.

Fixed a bug that caused participants to appear in both their initial event’s results and their new event’s results after switching events following the posting of their results. .

Fixed an issue when using the Timing Location > Add Reads > Enter Clock Times.

When selecting which start time you will be providing a race time based on, we did not dismiss the pop up, so it looked like nothing was happening when you clicked a time. Now when you click a time here, the dialog dismisses itself.

Corrected a bug causing the Scored Reads by Location Search to not work.

Fixed a crash caused by entering in an invalid date when adding a raw read.

Updated Lap Race Scoring so that Participants who missed their Chip Start will now fall back to use the Gun Start to calculate their first lap.

Fixed a Race Import bug that could happen if you had a Report using “All” Scored Events that was referencing a no longer existing Scored Event.

Fixed a bug when importing a Setup Only Export into an existing Race Dashboard if that original Race had RunSignup Race Memberships.


10/19/2023 – RaceDay Scoring v4.0.15

Feature Updates

Implemented “Events to Sync” Functionality.

Under the Participant Sync tab, you will now be able to select/de-select Registration Events to sync in this Race by opening up the “Events to Sync” Panel at the top of the page, and adding/removing them as needed.

Removing an Event here will make it so that the software will not include that Registration Event anywhere in the setup, nor will it include any of the Participants that are registered for that Event.

A simple use case for this feature would be to choose to not include a Registration Event set up for Virtual Runners that you are not going to score on race day. Just go into the Events to Sync Panel and remove the Virtual Event and you won’t have to see that additional data.

This will be especially useful for Races that are set up as a series, with each Event being a different day. What you could do is set up a scoring file for “Week 1” by removing all but the “Week 1” Registration Event from the “Events to Sync” Panel, and your interface will be much more focused, and if you are using RunSignup Super/Sub Events, you won’t have to worry about multiple versions of raw reads for Super Event records, as you will only be referencing the Registration Events that you are scoring today.

Note: We do not allow you to remove Registration Events from this Panel that are currently used in a Scored Event. If you would like to remove a Registration Event, you must first remove it from the Scored Event it is currently being used for.

Updated Aggregate Team Reports to sort incomplete teams by number of finishers.

Bug Fixes

Fixed an issue causing Scored Read Counts to not show when scoring a Race that includes Gunshot Markers.

Corrected an issue that could cause the Team Type “Applicable Events” selection to get out of sync with RunSignup, which could potentially cause sync errors.

Corrected a bug where tooltips would remain on screen as you scroll away from a multi-select box that already had at least one selection made.

Corrected a bug that could cause errors when publishing results after changing Scored Event Team Scoring Rules after Auto-saves had been set up.

Corrected a bug that could cause incorrect reads to be selected when using a single Stream for two Locations with similar filtering rules, so that both reads could be valid at the same time.

Fixed a bug with Races that use more than one Start Location within a Segment Setup.


10/11/2023 – RaceDay Scoring v4.0.14

Feature Updates

Implemented Tier-2 Cross Country Scoring

Please note that this feature is exclusively available for Cross Country. It enables you to automatically divide a team into two versions, “Tier 1” and “Tier 2”, based on the finish order of the members. This is commonly used to create Varsity and JV teams from a single school’s results, automatically.

For example, you could have members 1-7 count as the Tier 1 version of the team, and 8-14 count as an entirely separate team. When you enable this setting you must provide the position to start from (8 is the default), and the numbers to score through and displace through for the second tier.

When you have Tier 2 Scoring enabled, you will be prompted when setting up reports to decide which tiers you would like to include in this report.

Added Dual Meet Team Summary Report Section.

This is similar to the Dual Meet Team Detail Report Section, but does not show the member details, giving you a much more condensed report.

Added the ability to make Ghosted Runner times equal to the time of the last runner in the event instead of their team.

This is now the deafult, but we left the option to make it based on the team if needed.

Added the ability to include Unattached Runners in the Team Rosters Report Section.

You can enable this setting in Filters & Sorts > Allow Unnattached Runners. This will create a section for all runners that are not a part of a team.

Added a Scored Event Filter to the Raw Reads View.

Improved Participant/Team Import flow when creating a Team Type in the import process.

Now if you create a single Team Type while importing Participants and Teams, we will preselect the new Team Type for each incoming team so you don’t have to select each one individually.

Added Team Name to the Participant > Export to CSV function.

Added functionality to prevent setup issues when converting from separate start/finish to common start/finish Timing Locations.

We now will automatically set the finish occurrence to 2 if you convert a Timing Location that is a Finish type to a Start/Finish type for any Scored Events that used this Location as a Finish.

We also will prevent users from saving the Scored Events page if they have a Scored Event that uses a common start/finish location and is saying that they will finish on occurrence 1 as this is not a valid setup.

Bug Fixes

Corrected a bug with Lap Races when using chip starts and overlapping start/finish times causing reads to not be turned into Laps.

Corrected an issue where the Ignored Reason code used would not help to identify the real issue.

We made “Not a Scored Event” ignored raw read reason always the highest priority so that it is clear when you are seeing reads for versions of participants that are not included in a scored event in this setup. You can use the new feature to filter by scored event to hide participants not included in a scored event.

Corrected an issue with Races that use Start Locations as mid-point splits for other events.

This would cause the system to select the last start time seen for each participant across all start locations in the segment setup. We have fixed this so we now look for the last time seen for each start location within a segment setup individually.

Updated MileSplit Report Export to ensure compatibility with their submission requirements.

Corrected TFRRS setup form to default in race distances from Scored Events setup.

Updated TFRRS setup form to not default in a gender.

We do not have the ability to set this based on the report data, so we have removed the default of setting this to “Male” for all races.

Corrected an issue when adding a Participant that would prevent you from being able to associate the Participant with an existing Team.


10/6/2023 – RaceDay Scoring v4.0.13 Hotfix

Bug Fixes

Corrected a bug with Lap Races when using chip starts and overlapping start/finish times causing reads to not be turned into Laps.


RaceDay Scoring v4.0.12

Feature Updates

Updated print formatting to fit more results on a page and to make text more legible.

Bug Fixes

Fixed an issue that could cause the first page of a PDF export to show up blank.

Fixed an issue causing Events to not be selectable in Corrals > Applicable Events for Local Races.

Fixed an issue causing users to not be able to change a Participant’s Event to a Corral that was not synced with RunSignup.

Fixed an issue to make sure that the “Print Spooling” pop up will be dismissed when the print job is complete.

With this change, we also added the ability to close the “Print Spooling” pop up in case it stays up for some reason we haven’t accounted for.

Fixed an issue causing the Swap Raw Reads functionality to not work.

Fixed an issue causing Team Relay results to not process correctly when team members shared a bib.

Fixed an issue causing the Participant level setting to allow pre-gun times to always be hidden.


RaceDay Scoring v4.0.11

Feature Updates

Updated RaceDay Hub Announcer Kiosk Window to show settings immediately after launching.

We’ve noticed that people often forget to adjust the Timing Locations displayed in the announcer window until after reads have already been displayed in the window. To address this, we now display the settings screen upon launching so you can customize the window immediately.

Updated the Participant CSV Export to not include empty columns of data.

Updated the Participant Import flow to make it more clear which ID field you are using to update based on, and whether you are adding records, updating records, or both.

We now provide two checkboxes when mapping an ID field, allowing you to choose whether the import should be processed as adds, updates, or both.

Added a Close All button to all pop up messages.

Updated Print Status Reporting.

We have resolved some problems and enhanced the printing experience by providing more detailed updates to the user regarding the current print job status. Although printing large reports may still require some time, we will now display the progress more effectively.

Updated Raw Reads View to show all instances of a Raw Read.

When a Race has a single Stream mapped to multiple locations, the reads are copied and subjected to each location’s filters to determine if they are accepted or ignored. However, we only displayed the ignored reason for one of these reads, which can be problematic if it doesn’t provide the necessary information for the user. To address this issue, we now show if there are multiple reads generated from a single read and display all the reasons why it was ignored at each possible location it could be valid for. This is done for clarity and to make it easier for users to understand that one read that can be utilized at multiple locations.

Note: If a Race uses a Stream connected to multiple locations, the raw read count will be inflated to account for each instance of a possible read. However, the Scored Read counts will remain unchanged.

Updated Raw Reads Table Display for better readability

We now highlight and bolden Raw Read rows as you hover over them, making it easier to see the data you are focusing on.

Bug Fixes

Fixed an issue causing the “Disregard Every Other Lap” setting to not work for Lap Races.

Fixed an issue when adding participants in the RaceDay Hub Participant Kiosk.

Fixed an issue where super-event Participants in Lap Races were not getting their DNF flags removed.

Fixed an issue when using == operator for open ended fields that happened to have numbers.

Corrected an issue where columns marked as hidden in RaceDay Scoring would not be hidden at RunSignup, but removed completely.

Fixed an issue where the raw reads view would display the hardware name in lowercase.


RaceDay Scoring v4.0.10 Hotfix

**Fixed an issue where saving Scored Events could have caused participants to have DNF status and drop out of reports.**


RaceDay Scoring v4.0.9

Feature Updates

When adding a Scored Event, we now use the default Race Date instead of the current date for the approximate start time of day date.

Added a restriction so that it is only possible to include one dual meet report section per report.

Having multiple dual meet sections was found to cause a significant slowdown due to the number of sections that could potentially be generated, so we decided to restrict reports to only allow users to add a single dual meet section per report.

Improved Trident streaming to ignore non-read messages.

We found that Trident included system status messages that we did not need to be getting, so we no longer will try to parse these records any more.

Bug Fixes

Fixed a few bugs that could cause reports to not get deleted properly when Scored Events have changed.

Before this update, if you had a Lap Scored Event set up then deleted it, we would not delete the associated reports. Then if you tried to back the race up to the cloud or export it, we would show a warning that some reports may not be imported.

In addition, we found that the default report cleanup process would not go through all Scored Events, which could result in other instances of reports existing without their original reference.

Fixed a bug with non-RunSigup Races that would clear out the Event association from Teams if race settings changed after the initial setup.

This would cause problems with reports not showing any results if it is a team report.

Fixed an issue in Participants > Actions > Fix Unknown Reads which would cause the page picker to show more pages available than actually existed.

Fixed a bug causing Team Name to not populate in the RaceDay Hub Announcer Kiosk Window.

Fixed an issue when editing Marker Read Occurrences that would cause them to not change in the user interface (even though the underlying data has changed).

Corrected an issue with Race Director exports if the timezone data was missing that could cause the race that is built in RaceDay Scoring from a Race Director export to not have the appropriate time zone applied.

Corrected an issue with missing Participant Data fields that could cause reads to be ignored.


RaceDay Scoring v4.0.8

Feature Updates

Added Dual Meet Report Type.

You can now add a Report Section that will automatically generate Dual Meet scoring, where each team is scored against each other team, head to head.

Each pair of teams will have it’s own section with a header like “Team A vs. Team B”. Within each section, we will show a Team Detail section, which shows all of the members of that team, with details like their Score, times, name, etc…

Added the ability to Swap Positions in Raw Reads.

You can now select two Raw Reads and click the button to Swap Position. This will swap the read times between the two participants/teams that you have selected.

This is a very helpful feature if you need to quickly swap the positions of two runners after you have verified their finish order, and it does not agree with your chip read positions. By swapping the times, it effectively swaps their positions.

Added Checkboxes to the Raw Reads view to only show “Ignored” and “Locked” Reads.

You can now check the “Locked” or “Ignored” checkboxes in the Raw Reads view if you’d like to filter the Raw Reads list to only show “Locked” or “Ignored” reads, respectively.

Manually added reads will now be locked automatically.

Replaced PDF export with Print to PDF functionality.

The old PDF export did not have great formatting, so we have replaced it with a shortcut to print to PDF. This also now opens up the Print Preview screen, where you can customize things like whether the PDF should be landscape or portrait, and whether or not you want to insert page breaks between sections.

Added the ability to transfer the Scoring Stats for a Race to the current Time Account being used if this Race currently is sending Scoring Stats to a different Timer Account.

The Scoring Stats, which include registration and finisher counts, are sent automatically to the Timer Dashboard. You can find them under Races > Scoring Stats on the dashboard. If you are logged into a different Timer account and load a race that has already posted stats to that account, you will now have the option to update the destination of the Scoring Stats to the Timer Account you are currently using.

Updated Spreadsheet Selection functionality to default the Windows service to only display CSV and TXT files.

Since we do not support other file types like XLS, XLSX, etc… we have set the defaults so that these kinds of files are not shown to the user. If needed, it is possible to change this filter in the Windows File Browser window that displays when picking a file to import.

Bug Fixes

Fixed a bug when using a Registration Event filter on a Team Report Section.

Any reports using a Registration Event filter on a Team Report Section will need to be removed and re-added for this fix to be applied.

Fixed a crash when generating test reads when entering “0” for the “Reads per second” value.


RaceDay Scoring v4.0.7

Feature Updates

Splits w/ Place column on reports will now publish to RunSignup using the RunSignup Results Split Place field.

Reports that publish results to RunSignup and use the Splits w/ Place column will see a split place field in the results at RunSignup. This is supported for all types of overall and team finisher report types.

Bug Fixes

Fixed issue for setting common bib for all relay participant records if using chip cross references.

Fixed issue where team event ids were being blanked when editing a Local non-published race.


RaceDay Scoring v4.0.6 Hotfix

Bug Fixes

Corrected an issue that would clear reads from other Races that used the same Stream.

Previously, a bug caused Raw Reads to be cleared for other Races when reads were cleared for a different Race, as long as they used the same Stream. However, this issue has now been fixed. If any reads were lost as a result of this bug, they will be restored once the update has been run.

Corrected an issue with importing a full backup from the cloud.

We fixed a bug that caused duplicate participants when importing a full cloud backup on top of an existing Race.

Fixed an issue with incremental results not pushing to RunSignup.

Results for races with multiple segments were not updating in real-time on RunSignup as Participants completed segments. Auto-saving had to be stopped and started or the report had to be rebuilt for updates to take effect.

Fixed an issue when importing a setup only import where reads would not automatically be replayed.

Fixed an issue causing participants who get reads that are in an event that is not included in a scored event to be marked as unknown.

Their reads will now be ignored with the message “Not in Scored Event”.


RaceDay Scoring v4.0.5 Hotfix

Fixed an issue when importing older Race exports (prior to 2022)

Fixed a bug where we would show an error if you have a report that includes participants/teams with no reads (non-starters) and has one of the Last Completed Segment columns.

Temporarily disabled Full Race Cloud Import feature while inside of a Race.

We have discovered a bug that occurs when utilizing the Full Race cloud backup import feature within a Race. As a temporary solution, we have disabled this feature until the issue is resolved. However, you may still use the Setup Only import option from within a Race or the Full import option from the main Race Import area. Please note that in order to use the Full import option from the Race List, you must first delete your current Race.


RaceDay Scoring v4.0.4 Hotfix

Corrected the outdated previous release notes link.

Fixed an issue causing Raw Reads to be ignored when no time filters have been set up on the default Timing Locations.

It is still important to set up time filters even when using the default Timing Locations.

Fixed a bug causing the print status to not be reported to the application.

Fixed an issue with the system not overwriting processed read records properly when they changed from the “used” state to “unused”.

Fixed an issue causing Corral Assignments that originated from a Participant Import that is processing updates to not be pushed to RunSignup.

Fixed a bug with read processing if the user had imported teams without bib numbers from a spreadsheet.

Improved the connector shutdown process.

Fixed an issue causing invalid reads from showing up in Races from an old database.

Fixed an issue causing Scored Read Counts to not be correct when viewing a Timing Locations Scored Reads.

Fixed an issue causing Raw Read counts to not the same on the Dashboard compared to when you view the Raw Reads list.

Fixed an issue causing Corral ID to show in Data Actions list instead of Corral Name.

Fixed an issue causing the filterer to crash related to deleting participants when using super/sub events.


8/22/23 – RaceDay Scoring v4.0.3 Hotfix

Fixed an issue causing a slowdown when viewing Scored Reads.

Fixed an issue causing a crash when adding Scored Reads.

Fixed an issue when adding participant data causing the bib number field to jump to bib number while typing in other fields.

Fixed a crash when setting the Auto-Save interval to “None”.


8/21/23 – RaceDay Scoring v4.0.2

Feature Updates

Raw Reads/Filtering/Scoring Updates

Major upgrades to Read Filtering to significantly improve performance.

Previously, Scored Reads were copies of Raw Reads selected by the system for scoring. When scoring settings changed, Scored Reads were deleted and recalculated, which was time-consuming for large events. With the update, Raw Reads marked as scored are used for scoring, eliminating the need to regenerate Scored Reads and reducing data writing. Scoring changes are now applied automatically, and the filtering code was migrated to a different language (Rust) that prioritizes the speed of data access and memory efficiency, improving the speed of processing raw reads.

Removed the requirement to recalculate Raw Reads whenever start times/time filters, etc change.

This was mentioned above, but it’s worth emphasizing. This change eliminates the need to recalculate raw reads after scoring changes, such as start time or time location filters. The reads are automatically updated and re-scored.

Added the ability to mark selected Raw Reads as “Ignored”.

This feature allows you to mark reads as ignored and not scored, without deleting them. You can ignore or un-ignore selected reads using the “Toggle Ignore Reads” button, which changes their status to or from “Ignored”.

Added the ability to “Force Selected Reads”

You can select and score one or multiple reads for a participant at a specific timing location by using this feature. To do this, filter the Raw Reads view to only show reads for one entity at one timing location. Once filtered, the “Force Selected Reads” button will become enabled, allowing you to select and score specific reads for that entity at that location. All other reads for that participant at this location will be marked as ignored.

Added the ability to edit a Raw Read’s time and bib/chip information.

You can edit a Raw Read by clicking the green pencil icon on the right side of each row in the View Raw Reads table. You can change the date/time and bib/chip that was recorded. Use this feature to make adjustments to existing reads instead of adding new ones. Also, update invalid bib numbers for reads with “0” as the bib number, as many backup timers will do to indicate an unknown athlete.

Added Timing Location column to Raw Reads View.

You can now view the Timing Location that each Raw Read is associated with in the Raw Reads view.

By default, all reads before the assigned Gun Start Time will be ignored. If the Event is collecting Chip Start times, all reads before that Chip Start time will also be ignored by default.

Replaced “Filter Reads Before Start Read” setting with “Require Chip Start Time setting.

Now that we are always ignoring any chip reads that occur before the assigned start or a chip start time, we have changed this setting to now allow you to require a Chip Start Time for all Participants in this Scored Event. When this is enabled, it means that the system will ignore all reads for all Participants who do not have a Chip Start Time recorded. It is only recommended that you use this setting if you effectively want to disqualify anyone who is missing a chip start time. This setting is only available for Scored Events that are collecting Start Times.

Renamed “Filter Previous Segments…” setting in the Segment Setup view.

We have updated the phrasing of this setting to be more easily understood.

For the “Entire Race Segment”, this setting has been renamed to “Ignore Chip Start Reads that occur after the Finish Read.”. This is a recommended setting if you have a risk of Participants being read at the Start location after they have finished, and your Start times filter is still set to allow later start times. For example, in a time trial event where there are starts throughout the day, and you expect some athletes who have finished may come back to the start and get picked up again. This setting would prevent the later start read because the athlete has already finished.

The risk of this setting would be the inverse of the situation described above. If someone happened to get a read at the finish location that is within your acceptable finish time range, but before their chip start time, we would ignore their actual Chip Start time because we think they have already finished.

For other Segments, we have changed the name of this setting to “Once this Segment has been completed, do not use later reads to complete earlier Segments.”

This is a very useful setting for long events that have an out-and-back type course, where athletes may miss some of the reads going out, but get them on the way back. Without this setting enabled, if someone were to have missed a read at one of the “out” locations, but got a read on the way back, we would think that the “back” read was really the “out” read, which would result in a negative split time for this person. Enabling this setting will make it so that the system will keep track of which Segments have been completed, and by using the Cumulative Distance of each Segment, prevent earlier Segments from being completed by later times. This will prevent negative split times from showing in results, and instead, those splits will be blank.

Participant Add/Edit Updates

Added tabs to Participant View to go between viewing Scoring Data and Registration data.

By default when you tap a link to a name, we will bring you to the Scoring Data view for a Participant so that you can more quickly check on results and reads for Participants as the race is ongoing, and prevent accidental registration data changes from occurring. If you need to edit registration data for a participant, you will need to select the “Registration” tab and update from there.

The Scoring Data view includes the Results panel, the Status Panel (where you can set the status fields like Did Not Start/Finish, Drop, DQ, DNQ.), and adjustments.

The Registration View includes all other data fields that you can change for this participant.

Added Registration Event Selection control for Scoring Data/Registration Views.

On both tabs of the Participant View, you can now change the context of which version of the participant you are changing data for, if the participant you are working on is included in other Registration Events. This is critical if the participant you are working on is included in a Super Event at RunSignup, and you need to make a data change to one of its Sub Event registrations, but not others.

Moved Registration Event selection to the Participant Information toolbar.

In Participant Add mode, the Registration Event field will be selected by default, unless that field is being set by the system automatically.

This field can be set automatically if there is only one Registration Event in the Race, or if you have configured the “Race Default Participant Information” section in Participant > Settings to make a chosen Registration Event the default one.

If the Registration Event is set by default when adding a new Participant, the bib number will be the first field selected.

Changed Participant Quick Mode Add to always hide the Registration/Scoring Data tab bar, as it is unnecessary when adding new participants.

Other Updates

Added an External Reference ID field to hold external identifiers that can be used to update records with new data from a spreadsheet.

You can use this feature to store IDs from other registration providers, which can then be imported and used to update participant information. For instance, if you are importing data from a non-RunSignup registration source and have a spreadsheet with participant IDs, you can import another spreadsheet with updates or new registrations that include the same IDs. By mapping the ID field, RaceDay Scoring will update any changes for existing participants and add new registrations for those who don’t yet exist.

Added RaceDay Suite License Serial Number expiration notices.

On the main landing page, you can now hover over your RaceDay Suite License Serial Number and it will tell you when it will expire. When you are within 10 days of expiration, we will show a pop-up that lets you know you are close to expiring, and give you a link to renew. The serial number will turn yellow when this happens. If your serial number has expired, we will also show a popup with a link to renew, and the serial number will be red.

Updated Main Landing Page, Race List, and Kiosk Views to use more available width for content.

Before this change, these screens were off-center, with unnecessary white space on the left side of the screen. This has been removed to better accommodate smaller screen sizes and to be consistent with other screens.

Bugs Fixed

Fixed a bug causing Data Check Reports to not be included when importing a setup-only Cloud Backup.

Fixed a bug causing spreadsheet imports that include adds and changes to only process the changes and ignore the adds.

Fixed a bug causing the Award Winners display at RunSignup to display the incorrect time when the Top Finisher Category is scored by Clock but the race by Chip, and vice-versa.

Fixed an issue causing Data Actions to not fire on Participants that are not included in a Scored Event.

Now you will be able to use Data Actions on Participants in Registration Events that aren’t being scored to move them into another Registration Event that is being scored, for example.

Corrected an issue that can occur when you have an individual and a relay team that share the same bib number, but the team is not in a Registration Event that is not included in a Scored Event in this Race.

This would cause the reads to show up for the team instead of the individual.

Fixed a bug that would cause “Chip 2” to not save in the participant edit form.

Corrected an issue causing the Adjustments > Count field to be too small to see the values under some circumstances.

Corrected an issue with File Streaming that would cause the system to look through sub-folders within the folder that it is pointing to.

This would cause issues if users were pointing to a folder that had a sub-folder that contained non-timing data files, or times from other Races that should not have been referenced.

Corrected an issue with the Last Segment Completed Field if a Participant got extra reads that were not valid for their Event.


8/3/23 – RaceDay Scoring v3.3.49

Feature Updates

Added a Download button to the Cloud Backup List.

When Importing a Cloud Backup, you now have the option to download a .zip version of any of the available Cloud Backups. This may be useful if you like to keep a local archive of scoring backup files.

Scored Event page position is now retained after exiting the Team Scoring dialog.

This should make it less confusing when setting up a Race with many Scored Events that has Team Scoring for each Scored Event. Prior to this update, after leaving the Team Scoring dialog, it would jump back up to the top of the Page so it was easy to lose track of where you left off. Now the page position is retained when exiting this dialog.

Updated default USAT Submission File Name to include Report Name.

The default used to include the Race Name and the USAT Category. This will now include the Report Name so it’s easier to distinguish multiple files if you need to generate multiple instances of a single USAT Category within the same Race, for example, if you have multiple Scored Events, each of which needs to have an Age Group submission created.

Bugs Fixed

Fixed a bug causing Timing Location Occurrence fields to not be included in Report Filters in the Race Export and Backup to Cloud functions.

This would cause reports that use this data to filter on to not work unless you re-map these fields after importing a backup.


7/26/23 – RaceDay Scoring v3.3.48

Feature Updates

Added a Last Completed Segment Time of Day Field.

This field displays the most recent time of day when each participant successfully completed a Segment. This real-time information allows you to monitor participant progress more accurately and make informed decisions during the event.

Improved “Last Completed Segment” Handling for final Segments.

This field used to list the “Entire Race” Segment name as the Last Completed Segment, even if there was another individual Segment that finished at the same Location/Occurrence combination. Now, we will show the name of the last individual Segment instead of the Entire Race Segment.

Let’s consider a Triathlon event with the following Segment setup: Swim > T1 > Bike > T2 > Run. In this scenario, when a participant finishes their race, they are completing both the “Run” Segment and the “Triathlon Entire Race” Segment, because both Segments finish on the first occurrence at the “Finish” location. With this change, the “Last Completed Segment” will now display the individual Segment name “Run” instead of the more generic “Triathlon Entire Race.”.

This improvement ensures that the “Last Completed Segment” field reflects the specific stage of the race at which the participants finished, offering a more detailed and precise overview of the event progress. We think that this enhancement will prove valuable, especially for events with multi-stage setups, such as Triathlons and Ultramarathons, where it’s essential to track participants’ progress accurately.

Scoring Renewal: Clear Bib/Chip Cross-References.

When renewing a scoring file, we have added a checkbox that is enabled by default. This checkbox allows you to clear out the chip assignments from the previous year’s scoring setup. By doing so, you can start with a clean slate for the new season or event.

When you initiate the renewal process for your scoring file, you will encounter the new checkbox labeled “Clear Bib/Chip Cross-Reference.” This checkbox is checked by default, ensuring that chip assignments from the previous year are automatically cleared when you proceed with the renewal. Should you wish to retain the chip assignments from the previous year’s setup, simply uncheck the box before confirming the renewal.

Added Non-Adjusted Time Fields

To provide greater flexibility in your reporting and analysis, we have introduced Non-Adjusted Time Fields for all Segments in a Race, covering both Clock and Chip Times. Previously, adjustments were automatically applied to the actual time fields associated with the Segment being adjusted, making it challenging to view the original times without adjustments.

Now, with the addition of Non-Adjusted Time Fields, you have the option to display both the adjusted and non-adjusted times, enabling easy comparison when required.

Bugs Fixed

Fixed a bug causing Adjustments to not apply to Chip Time fields.


7/20/23 – RaceDay Scoring v3.3.47

Feature Updates

Corral Management screen position is maintained.

When working in events with a large number of corrals, the current screen scroll position is maintained when exiting a given corral edit.

Added Last Completed Segment Cumulative Clock Time field for reports.

You can now display the last completed segment’s cumulative clock time in reports – the total clock time from the event start to the time the participant completed their last segment.

Bugs Fixed

Fixed Manage Team Types on existing Report Sections.

We fixed the ability to adjust the team types for report sections with the new drag and drop design of report sections.

Fixed the last segment completed logic to ensure reads are sorted correctly.

Last completed segment data is now correct based on the passing read datetime sorting.


7/12/23 – RaceDay Scoring v3.3.46 Hotfix

Bugs Fixed

Corrected an issue with CSV exports causing the name field to not be formatted correctly.


7/12/23 – RaceDay Scoring v3.3.45

Feature Updates

Implemented Drag and Drop functionality for Corrals.

We have introduced a new feature that allows you to conveniently re-arrange corrals by simply dragging and dropping them. To enhance usability, we have redesigned the screen to resemble the functionality of segments. The panels can now be collapsed, making it easier to navigate, particularly when dealing with a large number of corrals. Additionally, we have incorporated the Corral Start Time data into the header, providing a quick and convenient way to double-check this critical information at a glance

Bugs Fixed

Fixed a bug causing Participant Data Actions to fail if they encountered a Team entity, and Team Data Actions to fail if they encountered a Participant entity.

If you require updates to both Team entities and Participant entities, you will need to set up separate Data Actions. In the ‘Data to Change’ area, instead of the default Participant option, select the Entity Type > Team dropdown.

Fixed a bug causing Custom Fields/Questions to not properly save their values when changed by a Data Action, which would cause them to show up blank in Reports.

Fixed a bug when using the Scored Events > Quick Setup feature causing the default occurrence to be set to 2 for Scored Events that did not have start or finish locations automatically mapped.

This would happen if there are more that one option for start and finish locations available, so the system wouldn’t know which location to use for each Scored Event.

Fixed an issue causing hidden columns to have their data included in CSV exports, but not the header, causing the data to be incorrect.


7/6/23 – RaceDay Scoring v3.3.44

Feature Updates

Added a Save button to the top of Corrals Setup page.

Added Collapse All function to Report Builder Sections List, and made it so that Report Section Panels can only be dragged and dropped if they are closed.

Bugs Fixed

Fixed a crash when using a Data Check Report without any filters applied.

Fixed a bug causing Bib/Chip Cross Reference Records to be added when resolving an unknown Raw Read for Races that did not have a Bib/Chip Cross Reference set up, causing all other Participants to become Unknown.


6/29/23 – RaceDay Scoring v3.3.43

Feature Updates

Added Login/Out and RunSignup Timer Selection functionality to the main Dashboard and Race List pages.

You can now view and change which RunSignup User account and Timer Account you are using before logging into a Race. This will help with situations where you don’t realize which account you are using and end up opening a Race that you may not have access to, which would cause sync errors. Now you can see which account you’re logged into up front, and change it if needed.

Added an option when editing a Splits field in the Report Builder to easily hide all cumulative times and paces.

For Triathlons it’s typically to only want to show Segment times. By default the Splits field will include Segment and Cumulative times, so most people will choose to hide all Cumulative Times by editing the Report, opening up the Edit Columns section, then clicking the edit icon on the Splits field and checking the boxes to hide the Cumulative Times and Paces. Now you can quickly hide them all in one checkbox instead of having to do this for each and every Segment you have.

When using the setting to Hide all Cumulative Times, the RunSignup Auto-Save will now automatically disable the setting to send Cumulative Times.

This setting is found in the Auto-Save Setting for any Report with a Splits field that is set up for any Scored Event that has Segments setup. It allows you to decide which kind of times should be sent to RunSignup Splits. You have to choose between sending Cumulative or Segment Times – it is not possible to send both. This setting will now default to not send cumulative times if you use the above setting to hide all cumulative times/paces, and instead will send Segment times.

Bugs Fixed

Corrected an issue causing Participants in Registration Events that are not in Scored Events to not show up in Data Check Reports.

Corrected a potential bug when importing Bib/Chip Cross-reference files


6/22/23 – RaceDay Scoring v3.3.42

Bugs Fixed

Fixed an issue that could allow races to be loaded more than one time on the same computer which can cause database problems.

Fixed an issue causing Report Name to not be available in the Custom Section Header Replacement Tags area.


6/15/23 – RaceDay Scoring v3.3.41

Feature Updates

Made non-HTML custom headers centered in print and print preview exports.

Bugs Fixed

Fixed an issue with publishing Relay Team Results to RunSignup which would cause duplicate records to show for Teams.

Corrected ControlServer errors for IPICO/Trident Direct that could occur when a TCP/IP connection does not disconnect gracefully.

Fixed a bug when switching a Participant’s Team association from their Participant edit form which would cause their Aggregate Team Results scoring to not update appropriately.

Fixed an issue causing Scored Reads to not be automatically recalculated for a Participant when Raw Reads are deleted for them.


6/7/23 – RaceDay Scoring v3.3.40

Feature Updates

Added Last Completed Segment Time and Cumulative Time Fields.

These will be especially useful for events with many segments as an easy way to track progress using a single field. This in combination with the Last Completed Segment column could be used as a way to easily see the last point a participant was seen at, along with their total time at the point, and the time of the last segment itself.

Added Automatic Field Delimiter Detection for Spreadsheet Imports.

The system will now automatically accept either tabs or commas as a delimiter by default when processing a file import of data. If necessary, you can disable this setting to force the system to use only commas or tabs (or other delimiters like semicolons if necessary).

Updated error system so that we can mark some errors as warnings that should be avoided during the setup of Races, but not prevent an import of the Race.

Updated help text in the Import Adjustments area.

Bugs Fixed

Fixed an issue causing negative values to not show correctly in the import adjustments review screen.

Corrected an issue causing Segment Occurrence fields to be missing from Data Check Reports after exporting/importing a Race.

Fixed an issue with MyLaps TCP/IP Streaming that could cause the system to disconnect.

We are now recommending that users always enable the setting in Timing & Scoring to “Send Ping” for all TCP/IP exports to ensure that the connection between Timing & Scoring and RaceDay Scoring is not dropped.

Improved FinishLynx File Streaming when handling times that are in seconds.

Fixed an issue causing Progress Report links to not work if the name of the report included certain characters like “&”

Fixed an issue when using the Did Not Start field in filtering, where the system would ask for a number instead of Yes/No.

Resolved an issue that could cause an undefined error while processing reads.Fixed an issue causing a crash when using the “IN” Operator without any options selected.

Fixed an issue when changing a Scored Event Team Scoring Type to “None”

We found that the system would not offer a way to clear Team Types that are associated with this Scored Event when you are setting the scoring rules to “None”. This would result in Team Types that still have relay/aggregate rules, even though the Scored Event is not set up for Team Scoring, causing a variety of potential issues.

Fixed an issue causing a warning that the connector was not installed correctly.

This would happen under a very specific scenario – if you used the login popup to authorize with RunSignup, then close down RaceDay Scoring, then use the button in RunSignup to authenticate, which would launch RaceDay Scoring from the browser. We found that when the browser launched RaceDay Scoring, we were not looking in the right directory for where the connector is stored, causing an error.


5/31/2023 – RaceDay Scoring v3.3.39

Feature Updates

Added a notification if an Event has been deleted at RunSignup.

This can cause issues if you are publishing results for a deleted event, so we recommend removing any registration events that have been deleted at RunSignup from use in any of your Scored Events, or contacting RunSignup support to have events restored if this was an accident.

Bugs Fixed

Fixed an issue causing FinishLynx times to not be processed correctly if they were under 10 minutes from the gun time in the file.

Corrected the automatic creation of a display field when you create a custom computed field that is in milliseconds.

This was not working as expected before, but we also have updated the fields that are created, so the initial one will automatically have ” (ms)” appended to the field label, and the secondary field that is created for you in a standard time format will have the original field name.

Fixed an issue causing date/time fields used in filtering to not display values to the user, making it seem like the values were not saved.


RaceDay Scoring v3.3.38

Feature Updates

Added support for importing State Names in the Participant import.

Prior to this change, we would only import 2 digit State codes, or the full State and Country name. Now you can just use State name without having to include Country name as well.

Improved Connector to better handle situations where connection to a device through a direct TCP/IP port has been lost.

Added the ability to use the “Is Null” and “Is Not Null” Operations when filtering by a custom question response.

This will make it easier to do things like selecting all participants who did not respond to a question at all.

Bugs Fixed

Corrected an issue with the Prediction Run settings that would not allow you to select a Time question type in the Scored Event setup.

Fixed an issue causing a report error when viewing a report that had a Segment Place column that was a part of a Race that was renewed.

Fixed a potential crash when viewing Scored Reads.

Fixed an issue with the Race Day Hub Announcer Kiosk read processing causing it to not handle lowercase chip codes.


5/11/2023 – RaceDay Scoring v3.3.37

Bugs Fixed

Further adjusted green Race toolbar to better accommodate long Race/Timer/User names.

Fixed an issue causing top finisher category priority to not be respected causing incorrect placements.

Corrected an issue causing Timer account selection to be lost after closing the app if you have multiple Timer accounts.

Corrected an issue causing Participants in non-relay Scored Events that have a Team assignment from being scored properly.

Fixed a bug causing Lap scoring settings tooltips to not show.

Added better validation when adding field delimiters and file extensions in the Stream settings.

Before this, a user could enter invalid characters into this field, like spaces, which would cause the stream to not process reads correctly or at all.

Fixed a bug causing the Boston Qualifier Summary counts to include participants who have dropped or were disqualified.

Fixed a bug when resolving an unknown raw read causing the bib number to not be included in the unknown raw read resolution form, causing the reads to not get associated with the target participant unless you remembered to enter in the bib manually.

Removed unneeded additional Gender and Team Type name appending when auto-saving a Team report to RunSignup.

This would cause result set names that looked like: “Team Summary-5-Person Relay School-5-Person Relay School” when they should be “Team Summary-5-Person Relay School”

Prevented an issue causing an error when publishing results to RunSignup with too long of a Result Set name.


5/5/2023 – RaceDay Scoring v3.3.36 – Hotfix

Bugs Fixed

Fixed an issue with Team Name search in Raw Reads not showing all related members

Corrected an issue with read selection when recalculating raw reads when reads came in out of order.

For example, if you imported start reads after finish reads, and used the setting to require a start read before a finish, recalculating would not work as expected.


4/28/2023 – RaceDay Scoring v3.3.35 – Hotfix

Bugs Fixed

Fixed an issue with the Race toolbar causing dropdowns to not work properly.


4/27/2023 – RaceDay Scoring v3.3.34

Feature Updates

Added Custom Section Header in Report Builder.

You will now be able to add a custom header to any Report Section in a Report. You can add variable fields like Race Name, Race Location, Race Date, Timer name/URL as well as any text you like.

We also support custom HTML in the field if you have some specific formatting or colors that you prefer.

In the future we will make this available to use in Report Templates if you want to have a standard custom header for all reports you create.

Added Built-in Predicted Time/Pace Reports

You can now mark a Scored Event as a Prediction Run. This will allow you to select a Custom Question/Field that is tracking the predicted time or pace for each participant. After doing this, you will have the ability to create a new report that includes a Prediction Time/Pace Section, which will rank participants based on how close they were to their predicted time or pace.

You also have the ability to say that all Predicted Time/Pace sections created for this Scored Event should be broken out by gender. This will make it so that when you add this kind of Report Section for this Scored Event, it will generate a section that is automatically filtered to only show the genders that you have selected. So if you select Male and Female, when you add a Predicted Time/Pace Report Section, two will drop into the Report (one filtered to only show males, and another filtered to only show females).

Added Time Formatting when using Filters.

Added time formatting to filtering when a time field is selected. Now you will be more easily able to create a filter that is something like “All participants who ran faster than 19:30.000”. Prior to this change you would have to figure out how many milliseconds are in the time you are filtering on.

Added more default dates.

Now whenever a date field shows up in the app it will default to the default race date.

Added Pace (Not Rounded) field to Report Builder.

The default Pace values are rounded up to the nearest second. We use the not rounded version when calculating predicted pace reports, so we have made this field generally available if you prefer to show Paces that are more precise.

Added RFID Direct Stream Support

We have added an RFID Direct Stream option, which will allow you to create a Stream that will connect directly to a single RFID reader by using it’s IP Address and Port.

Added a way to define Aggregate Team “Must Have Gender/Age” settings so that you can require some amount of members per Gender AND some number of those must be over some age.

This will allow you to do a scoring setup such as:

Score through 8 total members. 4 must be male, 1 of those 4 males must be over 40 years old, 4 must be female, and 1 of those 4 females must be over 40 years old.

Bug Fixes

Fixed a bug causing City/State to not automatically populate when entering in a zipcode.

Fixed a bug causing Relay Summary Reports for Races with multiple Segments to not sort non-finishers properly.

Fixed a bug when exporting Reports that include the Team & Members column to CSV, TXT, and PDF that would cause HTML formatting to show in the export.

Fixed user interface issue where the cloud backup/restore buttons could be hidden if the Race name was very long.

Better handling of network errors that occur when connectivity is insufficient.

Corrected issue with IPICO Gunshot Marker processing.

Fixed a bug causing a crash when saving “Must Have X” per Gender settings at the Team Type level under certain situations.


4/18/2023 – RaceDay Scoring v3.3.33

Feature Updates

Implemented improved RunSignup Login functionality (Oauth2).

This login will be saved for up to a month, so you will no longer need to periodically log in to RunSignup.

You also will now be able to remotely revoke access from your RunSignup profile if necessary via the “Oauth2 Authorizations” link. https://runsignup.com/Profile/OAuth2

The login will now ask that you use RunSignup to authenticate, which will open up a browser window where you will need to login to RunSignup and click a button to authorize RaceDay Scoring.

Added Minimum Age by Gender Settings to Aggregate Team Scoring Rules.

You can now say that you must have some number of participants on a Team that are of a certain gender and over a certain age to count towards their Team Score using this feature.

It is possible to use the min age settings by themselves to say all participants of that gender must be over a certain age by leaving the gender count field blank.

Added a column to Aggregate Team Detail Report Sections that will indicate which members of each Team contributed to the Team Score.

This makes it easier to tell how the Team Score is calculated.


3/30/2023 – RaceDay Scoring v3.3.31

Feature Updates

Improved the warnings when saving scored events and the selected registration event distances do not match.

In addition the selection of the “Use this as the default scored event” will now correctly change the list of selected registration events for the given scored event.

Bugs Fixed

Fixed announcer screen ability to change columns selected and for default setup Gender/Age column to work with no changes.

Removed the ability for auto-saves to automatically update when changes occur to related settings because it was causing issues with Splits columns clearing data in RunSignup Results. Now you must go into Auto-Save Settings and save them whenever you make a change to a Report in order for changes to be applied.

Corrected database issue


3/8/2023 – RaceDay Scoring v3.3.30

Feature Updates

Changed Total Time for lap races field so that it shows as empty instead of null for those who do not have any times recorded.

Added “Splits – Times Only” Field

You can now include this field if you do not want to show paces along with times for all of your splits.

Added Boston Qualifier Report Section Type

You can now create a Report with a Boston Qualifier section in it, which will show you who has qualified in this Race for the Boston Marathon, based on the times posted at https://www.baa.org/races/boston-marathon/qualify

In addition, we will show a summary of how many participants in this Scored Event have qualified, with a percentage of finishers that were Boston Qualifiers.

You can only use this report section on a Scored Event that is exactly 26.2 miles, and when you decide to add the section you will need to select which year of the Boston Marathon you would like to run the report for, and what class you are running the report on. The class selection is typically used for paralympic categories.

There is a setting that will allow you to only show Boston Qualifiers, otherwise all participants will show in the report.

Any participants without birthdays or genders in the database will show a message in the field indicating what they are missing.

Once you have a Boston Qualifier Report, you will be able to use Export > BAA Submission to produce a CSV that should be acceptable for submission to BAA.

Bugs Fixed

Fixed a bug with the auto-import functionality when creating bib/chip cross-reference files

Fixed an issue causing you to not be able to access Corral Member Assignment Rules directly after creating a new Corral.

Fixed an issue causing Timing Location Occurrence Time of Day Fields used in Data Actions to not be imported properly.

Improved performance for events with many Aggregate Team Detail Results.


3/2/2023 – RaceDay Scoring v3.3.29

Bugs Fixed

Fixed a bug with printing.

Fixed a problem causing “Custom Field X is using Invalid Segment ID” errors.

Fixed a problem causing a “Top Finisher X Jumping Rules is not a map” error when importing a Race export.


2/23/2023 – RaceDay Scoring v3.3.28

Feature Updates

Added Total Time (ms) as a field that can be sorted on.

It is now possible to use the Total Time field in the Sort functionality in reports. The Total Time field is used to hold the Total Time completed in Lap Races.

Added Time Back Fields

Time back from gender winner: The difference between this participant’s time and the fastest participant of the same gender’s time. Labeled as “Time Back”.

Time back from overall winner: The difference between this participant’s time and fastest participant for the overall listing of the report section. Labeled as “Overall Time Back”.

Time back from last finisher: The difference between this participant’s time and the participant one spot ahead of this participant’s time. Labeled as “Time Back from Previous”.

All 3 fields are available based on both chip and clock time, and only work for standard (non Lap) results at this time.

Made Timer Contact Email the default Race Contact Email when creating a Race on RunSignup through RaceDay Scoring.

Updated underlying components throughout the application to ensure compatibility and stability.

Added support for p, P, and B records for Summit Timers.

These kinds of records are from Impulse or Photocell recording devices.

Added Channel Filter for Summit Timer Streams.

You can now specify which channel this Stream will pull reads in from. This will allow you to say that you only want to use reads from a specified channel for a given Stream. It will also allow you to set up multiple Streams referencing the same file, but have the reads split to different Streams based on the channel they were recorded on. If no channel is set, reads from all channels will be processed.

Bugs Fixed

Fixed an issue causing Participant search terms to stick after changing races.

Fixed an issue causing Membership Setting ID is not valid after renewing the scoring file for a RunSignup Race that has Memberships enabled.

Fixed an issue causing some settings to save on Timing Locations when cancel button is used.


2/8/2023 – RaceDay Scoring v3.3.27

Bugs Fixed

Fixed an issue causing RunSignup Custom Question Responses to not sync under certain circumstances.

Fixed an issue causing a crash when importing a Race that included a Report that uses the new “Last Completed Segment” column.

Fixed an issue with Progress Reports not displaying correctly if the Scored Event name included a “+” character.


2/2/2023 – RaceDay Scoring v3.3.26

Feature Updates

Added RSU Participant Data Reset Function

This is only necessary under specific scenarios where you need to clear and reimport all participant data from RunSignup. The one scenario that this is useful for would be if the RunSignup registration has updated their Super/Sub Event Settings since the first time you synced participants. When this happens, the old sub event records will be retained in your RDS database, potentially causing issues with scoring or confusion. This is found by using the gear icon in the top right with a race loaded.

Added a View Report button to the Report Builder.

This will allow you to quickly save and view a report to more quickly see the changes you have made.

Added an Edit Report button on the Report View.

Now you can edit a report right from the Report View.

Added a Refresh button on the Report View.

This will allow you to update the Report you’re currently viewing if a race is in progress.

Bugs Fixed

Fixed an issue causing the Show Award Winners Only filter to not show on Lap Age Group Reports.

Fixed an issue causing “Scoring entity ID is not valid” errors when exporting/importing race files.

Fixed an issue causing “Scored Event ID is not valid” errors when exporting/importing race files.

Fixed an issue causing Data Actions to be duplicated when restoring a cloud backup.


1/19/2023 – RaceDay Scoring v3.3.25

Feature Updates

Auto-Save Timer Info Fields now will pull from RunSignup Timer Account Info.

The Questions Contact Email, Results Timer Name, Results Timer URL, and Questions Contact URL will now be prefilled with the data that you have set up on your Timer Dashboard under Settings > Timer Info. You can change these values as you like if you want something different for a particular race.

Added a Number of Segments Completed Field to Reports.

This will show a count of how many segments each participant has completed so far.

Added a Race Progress Field to Reports.

This will show whether a Participant is a finisher or still in progress as a field in your report.

Added Last Completed Segment Field to Reports.

This will show the name of the last completed segment for each finisher as a column in reports. This could be nice information to add for long events like Ultramarathons where you want to see the last checkpoint each athlete was seen at, without having to scroll over to see all the split data.

Added “Age Place Only” and “Age Group Desc.” Fields to Reports.

These can be used if you ever need to break out the placement fields from the label fields for the existing “Age Place” field. This will include Top Finisher Categories as well as Age Groups.

Added a pop up message when trying to renew the scoring file for a Race at RunSignup that has not yet renewed it’s registration page yet.

In order to renew a scoring file, you first must renew the registration page.

Bugs Fixed

Fixed issue causing Paces reported in Minutes per KM to not show properly at RunSignup.

Fixed an issue causing a crash when setting up invalid band jumping rules.

Corrected a database upgrade bug that affected users who had upgraded from a version before 3.1.32 to any version after 3.2.2, without installing any version in between.

The gap between versions would have been between November 11th 2021 through March 24th 2022, and could cause app crashes periodically when looking at Raw/Scored Reads. After installing this update, recalculating Raw Reads will fix any of these app crashes.


1/11/2023 – RaceDay Scoring v3.3.24

Feature Updates

Updates to RaceDay Hub Announcer Window

  • Added the ability to customize what fields are shown, and in what order.
  • Added a Custom Splash Message field on the Participant Record that will display in the Announcer “Message” field when they are read.
  • Added Gender/Age combo field.
  • Added Team Name and Grade fields.
  • Added State and Country fields.
  • Changed default fields in the display to [Bib, Name, City, Gender/Age, Age Group, Event, Message, Location].

Added the name of the currently selected Scored Event to the Team Type list.

Made Chip and Chip 2 fields available in Report Builder.

Updated Separate Report Section by Gender feature so that it will update existing default reports if changes are made after initial setup.

Added the ability to update teams in the participant import without needing to provide Team Type.

Bugs Fixed

Fixed an issue with IPICO Gun Trigger processing.

Fixed a potential issue causing runaway “uncaught exception in the filterer” notifications.


12/23/2022 – RaceDay Scoring v3.3.23

Feature Updates

Updated Top Finisher Category Duplicate function to clear Short Description as well as Description.

Updated “Separate Report Sections by Gender” feature to allow you to select which Genders should have separate report sections created.

Prior to having this, the system would create separate sections for Male, Female, and Non-Binary whenever a Report is created for this Scored Event. Now you can choose which of these three options you would like to be automatically created. By default, just Male and Female are selected.

Added the ability to create a Pre Race Report Section when All Scored Events are selected.

This will combine registrations from all events into a single Report Section and will be sorted alphabetically.

Added Currently Selected Event to Age Groups, Participants, and Teams views.

This should make it more clear that these views are Event specific, and that the counts apply to the currently selected Event.

Added warning message when backing up to the cloud if there is an issue with the Race that could prevent it from being imported.

Sometimes there is an issue with a Race configuration that can cause it to not be able to be loaded onto another computer. Now you will get a warning with details about what is wrong with the setup so you can correct the issue and back it up again.

Bugs Fixed

Fixed an issue causing FinishLynx files to not properly reference the start time of the event if the name of the Race contained quotation marks or commas.


12/15/2022 – RaceDay Scoring v3.3.22

Feature Updates

Added “Duplicate” and “Copy to Other Events” functions to Top Finisher Categories.

You can now duplicate single bands within an Event when setting up Top Finisher Categories if you need to quickly copy the same settings to another band, as well as copy all bands from the currently selected Event to other Scored Events. When copying to other Events, you are given the option to select some or all Events.

Added note to error about RunSignup account being locked due to too many failed attempts that will direct you to our support team.

Added explanation tooltip to Registration Events selection in Scored Events.

This note reminds you that in order to combine Registration Events together, they must be the exact same distance, and instructs you how to update that if necessary.

Added the ability to delete Unknown Raw Reads.

Changed “Age Place” column to always use the Short Description from Top Finisher Categories.

Prior to this change, we would always use the Long Description in the Top Finisher labels for this column.

Bugs Fixed

Fixed a bug causing laps to not be calculated correctly for Lap Races when mid lap reads are processed before start/finish reads are.

Fixed a bug causing the participant level setting to accept Pre-Gun Reads to not work.

Fixed a bug saving Streams when editing an existing File Stream and making it a Direct Stream in some circumstances.

Changed ignored reason priority to always mark an unknown read as unknown even if it would have been filtered for other reasons.


12/01/2022 – RaceDay Scoring v3.3.21

Bugs Fixed

Fixed an issue in Lap Races that caused reads that are being ignored due to them being “Within Gap Factor” to display as being ignored due to “Occurrence Not Defined”

Fixed an issue with Progress Reports showing incorrectly.

Updated import/export to automatically correct races with duplicate reports/report sections.

Fixed an issue causing bib numbers to not be cleared in RaceDay Scoring if you are using a bib/chip cross-reference and the bib was cleared at RunSignup or in the CheckIn App.

Fixed an issue causing comparison operators (==, <, >, etc…) to not work for open ended fields.


11/22/2022 – RaceDay Scoring v3.3.20

Bugs Fixed

Fixed a bug causing the Event selection to be disabled when adding Participants via Quick Mode.

Fixed an issue causing an error when submitting results o RunSignup that include Custom Fields with column headers that exceed 64 characters.

We will now automatically trim to 64 characters and let the user know that which column headers we have trimmed.

Removed unneeded error from notifications when setting up RaceDay Hub.


11/18/2022 – RaceDay Scoring v3.3.19

Bugs Fixed

Fixed default report regeneration.


11/17/2022 – RaceDay Scoring v3.3.18

Feature Updates

Updated Progress Report to remove participants that did not start, have been dropped, or have been disqualified from the “Out of” counts.

We have changed the counts so that they will automatically be adjusted for participants that you don’t actually expect to finish. Prior to this change, it would look like you still had some on course if you had participants that were dropped, for instance.

Added Connection Indicator to Announcer Kiosk Display, and added the ability to auto reconnect.

This will now give you the ability to view the connection status of the Announcer Kiosk Display to your RaceDay Hub Server. If at any time connection is lost, the indicator will go red and the system will automatically try to reconnect once the server is back up, or connection to it has been restored.

Added warning to the Folder Path field in the File Stream setup.

We have added a warning to this area when selecting a folder that files will be placed into, reminding the user to never include any files in the folder besides actual timing files. Including other files in the folder you are pointing to can cause system instability.

Bugs Fixed

Fixed a bug causing newly added participants in RaceDay Scoring to fail when syncing to RunSignup.

Fixed an issue causing Bulk Updates using Registration ID to fail.

Fixed “Native filterer error while updating devices.” error.

Fixed a bug causing Corral assignments that were made from a Member Assignment Rule were not causing their Corral Assignment to not be updated at RunSignup.


11/10/2022 – RaceDay Scoring v3.3.17

Feature Updates

Added the ability to mark a Location as an Announcer.

This setting removes the need to set up a Segment that uses this location in order for reads collected on it to show up in the RaceDay Hub Announcer Kiosk.

Prior to this change, you would have to have a Segment set up for each Event that you expect to have passings for at your announcer location. Now all you need to do is set up one announcer location, mark it as an announcer, and all reads for all events will show up on the RaceDay Hub Announcer Kiosk.

Added an option to include empty Age Group bands in Age Group Report Sections.

Locked the switching of Registration Events for Participants that are a Sub Event Participant.

These Participants are “copies” of the Super Event Participant. It’s not possible to change only one of the sub-event Participants Registration Events without affecting the others, so we now prevent you from changing the Sub-Event Participant’s Event. If you need to change the event for all, you can do so by changing the Super Event Participant’s Event.

Bugs Fixed

Fixed an issue causing Age Groups that were added one by one to not have their award winners number saved properly, causing those bands to not be included when using the option to show award winners only in Age Group Reports.

Fixed an issue when using the “Contains” operator on an open ended field in a filter.

Fixed an issue causing TFRRS Publish Settings to not show for Reports including more than one TFRRS Report Section.

Fixed an issue causing Auto-Save buttons to not show for reports that include a single Team Summary Report Section.

Fixed an issue causing the Live Results link to not show for Reports with multiple Report Sections.

Fixed an issue when changing the event of a Participant that is a part of a Super Event causing duplicate participants to show in RaceDay Scoring.


11/3/2022 – RaceDay Scoring v3.3.16

Feature Updates

Updated Score, Team Score, and Team Place labels to show as “UNA” for unattached runners.

Added support for including unattached runners in TFRRS Reports.

Updated Ignored Raw Reason Codes to show reads that occur after an accepted occurrence as “Occurrence Not Defined” if the system is not expecting any more occurrences on any Segment for this Location.

We will now only ever use “Better Read Selected” for start reads for participants that have a later valid start read.

All finish/split reads after the one selected will be marked as “Occurrence not defined”, unless they are collecting multiple occurrences, in which case they will be marked as “Within Gap Factor” if they are too close to the previously recorded time.

Bugs Fixed

Fixed an issue causing unsaved changes to Corral to get cleared when the next sync occurs.

Fixed an issue causing Corrals deleted at RunSignup to not be removed from RaceDay Scoring.

Fixed a bug causing a label to not show in the Lap Summary Filtering area.

Fixed an issue causing segment updates to not apply to RunSignup Results Splits.

Fixed an issue causing a Websocket client disconnection error whenever a kiosk was disconnected from RaceDay Hub.


10/27/2022 – RaceDay Scoring v3.3.15

Feature Updates

Added the ability to send Cumulative times and places instead of Segment times and places when setting up RunSignup Auto-Saves to include Split data.

Typically, Segment times/places will be used for Triathlons where you want to report the individual segment times, and Cumulative times/places will be used for running races where you want to show the total time it took to get to the end of that segment from the very beginning of the Race.

Added DQ’d runners to Athletic.net export.

Added support for sending properly formatted “Yes/No” responses in results to RunSignup.

Prior to this change they would upload as “1” or null.

Added a new Ignored Raw Read Reason code for times that are ignored because they are within the Gap Factor from the previous read at that location.

Added the ability to access File Auto-Saves for Age Group Reports

This opens up the ability to create HTML Scroll Auto-Saves for Age Group Reports.

Bugs Fixed

Fixed issue for Races using the “All” genders option for Age Groups when importing/exporting the Race.

Fixed an issue with importing/exporting Races that have a Report that was set up using the “All” Scored Events option.

Fixed test reads being generated in the wrong timezone.

Improved import error warnings.


10/20/2022 – RaceDay Scoring v3.3.14

Feature Updates

Added Qualifiers to Aggregate Team Scoring Setup.

You can now configure a new Team Qualifier option when setting up Team Scoring. These settings allow you to say how many teams and individuals should be marked as qualifiers. By default, individuals are marked as qualifiers if they are not a part of a team that has qualified.

There is another setting to base the individual qualifiers on finish position, which will make it so that individuals must finish within the first X finishers overall, where X is the number you have set in the Individual Qualifiers field. Without this setting enabled, the system will select the first X available, regardless of their finish position.

Note: Enabling these settings does not automatically add the Team Qualifier columns – it must be added manually.

Added Close Finish List Report Sections.

You can now create Close Finish Report Sections for all Scored Event Types besides Relay Team and Lap Events.

This will allow you to set a time value that is considered a close finish, and the report will show pairs of participants within whatever time you have set based on their clock time. We include the time of day of their finish reads by default to assist with checking your camera system to verify finishing order.

This will use either chip time or clock time based on what was being used to score participants in the Scored Event setup at the time the report was created.

Note: The report will not update if a Scored Event changes between chip/clock time scoring – you will need to delete and re-add the close report report if you change the chip/clock time setting after this report has been created.

Made Report Section Headers “Sticky” in Scrolling HTML Files.

Headers will now stick to the top of the page when scrolling through reports. This works for multi-section reports as well.

Added Ability to set Font Size when creating HTML Scroll Files and Auto-Saves.

**Made HTML Scroll Speed consistent regardless of how many rows are in the report. **

Bugs Fixed

Fixed an issue causing finishers to not show in reports after importing a race until you saved Scored Events.

Fixed an issue causing an error when importing lap races.


10/12/2022 – RaceDay Scoring v3.3.13

Feature Updates

Num. Winners will automatically populate when adding individual Age Groups.

It will default to 3, but will follow from values that have been set if you had used “Create Ranges” to set up other Age Groups for that Event.

Updated Corral Assignment Syncing to allow for RSU changes to override RDS changes.

Previously we would not allow a change to a Corral made at RunSignup to override a change made in RaceDay Scoring. This was to prevent RSU from constantly reverting changes made to Corral in RaceDay Scoring when we used to not be able to update RunSignup’s Corral Assignments.

Now we are syncing like other data points, where the last change made always wins, regardless of whether it’s made on RunSignup or in RaceDay Scoring.

Added the ability to set up a RunSignup Partner Token so that Races you create in RaceDay Scoring and upload to RunSignup can automatically be associated with your RunSignup Partner Account.

This is set in the App Settings (gear in upper right) below the serial number entry, and will be applied by default to all new Races you publish to RunSignup. It can be edited when publishing if you for some reason need to make one Race not associated with your Partnership.

Added a check to prevent using the same Result Set for multiple Reports or Auto-Saves within the same Race.

This can cause issues, and should never be necessary to do, so we now prevent it.

Added the ability to map all participants in an import that are missing an Event to a specified Event in RaceDay Scoring.

You can now import spreadsheets that do not have an event included at all, and we will allow you to say that all participants should be placed into a specified Event. Alternatively, you can also decide on a case by case basis which participants should go into which Event as well.

Added the ability to run Data Actions on Teams

Bugs Fixed

Fixed an error – Native Filterer error while updating entities


10/06/2022 – RaceDay Scoring v3.3.12

Feature Updates

Updated Top Finisher Category Links in Reports to use Top Finisher Category Label.

Prior to this change, the labels for custom top finisher categories would not use the custom label, and would instead just say “Top Male” or “Top Female”.

Added the ability to filter “All” Scored Event Team Rosters Report Sections by Registration Event.

Bugs Fixed

Fixed issue causing status flags to not be properly controlled by read data if a Timing Location name had been changed and Scored Events had not been saved after that change.

Fixed an issue causing an infinite loop of Team Sync Failures.

Removed the ability to filter “All” Scored Event Team Rosters Report Sections by Scored Event.

This would cause reports to not work properly, so we removed this ability and enabled the ability to filter by Registration Event as noted above.


9/28/2022 – RaceDay Scoring v3.3.11

Feature Updates

Added the ability to fully sync Corrals with RunSignup

Prior to this change, we could only pull down Corral information from RunSignup. We were not able to add or edit any Corral information. Now with this change we are fully syncing the Corral structure and assignments with RunSignup, so if you add a Corral in RaceDay Scoring it will show up in RunSignup, and vice versa.

Please note that Corrals added to RunSignup after a Race has been set up in RaceDay Scoring will not show up until you go to Participant Sync and click Save Sync Settings to force a refresh of the Race settings.

Added the ability to create Team Rosters Report for All Scored Events

Now when adding a Report Section you will be able to select the Team Rosters Report after using the “All” Scored Event selection option. This will create a Report that shows team rosters broken out by Team, but includes participants from all Scored Events within each Team section.

Added new Ignore Raw Read Reason Code: “Prior to Assigned Start Time”

Reads in this state used to be ignored due to them being “Filtered by Time”. This should help when troubleshooting ignored Raw Reads, especially if you accidentally set your start times incorrectly.

Made a change to the TFRRS Report and Upload to also send Participants that have not started.

Made Team Names Clickable Throughout the App.

Added RunSignup Login/Logout Buttons to Green Race Toolbar.

Optimized Scored Event Setup for Lap Races and Races with lots of Registration Events.

We saw performance issues with Races that have many Scored Events set up for Lap Scoring, as well as Races that have a lot of Registration Events. We will now show checkboxes for all available Registration Events only if there are less than 10 Registration Events in the Race. If there are more than that, we will display the selection as a multi-select (similar to what is used when associating a Stream to a Timing Location).

Added the ability to include Custom Questions in Report Templates.

We discovered that using a Report Template with a Custom Question in it causes issues after creating a Report for another Race using that template. We now support this, and allow you to map a new question in the Race that you are using the Report Template for.

Added the currently selected Scored Event to the Segments Setup View.

This should make it more clear what Segments you are currently looking at/editing.

Bugs Fixed

Fixed issue causing Custom Question Reponses for “Yes/No” Type Questions to show as blank when included as a column in a Report.

Fixed an issue when transferring participants if also changing some other part of that participant’s information at the same time.

Fixed an issue for XC races that were previously scored with Race Director that were renewed and scored with RaceDay Scoring this year, that would cause an error with Divisions when publishing results.

Made a change to the Raw Reads display so that times are correctly adjusted for timezone when viewing the race on a computer in a different timezone than the one it was scored in.


9/15/2022 – RaceDay Scoring v3.3.10

Feature Updates

Updated Duration Input to auto-advance after entering two characters in the hours position.

Now you won’t have to press the tab key after entering in two digits into the duration fields, but it does restrict you from entering anything more than 2 digits. If you need to enter in an hour value over 99 hours into a duration input (we think this is very rare), you can copy and paste the value into the hours field.

Reports with invalid configurations can now be edited and fixed.

Sometimes Reports can become unusable if something that they are relying on in the setup has been deleted. For instance, if you have team reports that rely on a team type that you’ve since deleted, that Report will no longer work properly.

Before this update, if you tried to edit or delete the Report that was not working, it would open up the Report Builder with no data in it – as if you were creating a new Report entirely. Now, when you are in this state, you will be able to edit the bad report and update the Team Type that it’s using to fix it up instead of having to delete all reports and rebuild them manually.


9/8/2022 – RaceDay Scoring v3.3.9

Feature Updates

Added MileSplit Report Section Type and Export Function.

You can now create MileSplit Exports from Reports that have MileSplit Report Sections added to them. So if you need to generate a MileSplit Export, first you need to create a Report that includes MileSplit Report Sections for each Event you have in your Race, then export that Report using the new MIleSplit Export Option.

It’s important to not change the order of the Report Sections that are generated for each Scored Event when you add them to the Report. They must be grouped together by Scored Event in order to meet MileSplit’s required formatting.

Bugs Fixed

Fixed issue causing log files to grow too large.

Fixed an issue causing Corral Changes to not automatically update existing read selection status.

Fixed an issue causing times in the Lap Details views to be displayed in an incorrect time zone when not in EST.

Fixed an issue causing multiple instances of the same Segment to show up when opening up a Segment Panel for Lap Events.

Added more specific error messages when reports fail to rebuild automatically.

Usually this is due to some part of the setup that this report relied on no longer being present – like a deleted Team Type, for instance.


9/2/2022 – RaceDay Scoring v3.3.8 Hotfix

Bugs Fixed

Fixed issue causing some systems to crash when installing the 3.3.7 update.

Those who currently have this error will need to download the installer from your RunSignup Timer Dashboard > Software page.

Fixed issue causing an error that would show for Race Result streaming.


8/31/2022 – RaceDay Scoring v3.3.7

Feature Updates

Added Raw Read Announcer Kiosk

On the main app landing page there’s a new button to set up an Announcer Kiosk. This uses the RaceDay Hub to send a stream of all raw read data to an announcer feed that includes participant info like name, timing location of the read, event, age group, city, bib/chip and time of day of the read. We also show a message for users whose birthdays are within +/- 7 days.

This will create a new window that you can display on a separate monitor or any kind of display that you can connect to your computer. It also can be set up on a separate computer that is connected to the same local network as your main scoring computer.

Through the settings menu you can control the text size and which Timing Locations should be included in the announcer feed (by default it’s all).

This leaderboard is much faster than the previous implementation, as we do not have to wait for the raw reads to be processed into Scored Reads. This means that the data will display in these leaderboards in less than 5ms from the time that the Connector sees them, instead of around 5 seconds.

Added the ability to import a spreadsheet of participants with Team names without having to provide a Team Type or set any up in advance.

It’s typical for XC races to start from a simple spreadsheet without any Team Type info. This new feature allows you to create a single Team Type that all teams will be associated with during the import. This should reduce the amount of back and forth you have to do when setting up simple Team scoring Races where there’s only one Team Type.

Added the ability to process changes to Teams by importing a CSV that includes the Reg Group ID.

This works similar to the Participant Import, where if you include an ID it will process the import as an update instead of an add. This could be useful if you ever need to make bulk changes to teams.

Updated “No Event for Bib” Ignored Raw Read Reason Message

This message shows when the Event associated with the bib that is associated with the read encountered is not found in the list of valid events for the given Timing Location/Occurrence count. The system looks through all Segments for the Event and if it can’t find any Segments that use this Timing Location/Occurrence combination for the given Event, it will ignore the read for this reason.

We have updated this message to be more descriptive – “Location is Not in any Segment in this Scored Event.”, hopefully pointing timers to the right place to fix the problem, which is either in Segment Setup or Scored Event. It typically means that the Segment Setup isn’t correct, or the wrong Location was used on the Scored Event.

Added Quick Report Links to Multi-Section Reports

In a previous update we added quick links to Age Group sections from the top of an Age Group Report. We have applied this same functionality to work the same way for any Report that has multiple sections within it.

Bugs Fixed

Fixed an issue causing changes being made to participant data to be lost if reads come in while you are editing.

Made changes to prevent unnecessary RunSignup Participant updates to fire when reads cause a change in the Participant Status.

This should reduce the amount of data used while scoring, and improve performance in locations with poor internet reception.

Fixed an issue with Report Templates that would cause you to not be able to add new columns to a Report that was created from a Template.

Fixed an issue causing the setting to allow pre gun times for a Participant to be reset at the next sync.

Fixed an issue that would allow you to save a Custom Computed Field without anything selected, causing errors.

Fixed an issue that would allow you to try to publish results to RunSignup for Local Races that do not have a RunSignup Race to publish to.


8/18/2022 – RaceDay Scoring v3.3.6

Feature Updates

Added FinishLynx Report Section and Auto-Save option

You can now create a Report that includes a FinishLynx Report Section when you select “All” Events that will give you the ability to set up a FinishLynx Auto-Save. This Auto-Save will export .evt, .ppl, and .sch files automatically as a race is ongoing, so that you can update your FinishLynx software with up to date participant information.

Added HTML Scroll Report Export

This is available for any Report under the Export menu > HTML Scroll. You can set a scroll speed, and the report will automatically return to the top once it has scrolled through all rows.

This is compatible with the File Auto-Save system, so you could create a scrolling HTML file, then auto-save to it to use as a Race is ongoing to present on a leaderboard or large monitor display system either connected to your scoring computer, or on another computer using Dropbox/Google Drive to host the file.

Added Time Entry Field Helper Text to Time of Day Fields and Duration Fields.

We have added a label telling the user that the formatting is in HH:MM:SS.sss format for both time of day and duration entry fields.

Bugs Fixed

Fixed a bug causing check-ins made via Data Check Reports to not save.


8/11/2022 – RaceDay Scoring v3.3.5

Feature Updates

Updated USAT Export to include Participants missing state or zip codes.

This would cause some international participants to not show in exports if they did not have a state or zip code provided. This will allow these participants to be included in the export data.

Updated Race List sort functionality so that it is retained when closing the app and starting it again.

Updated Results and Participant Sync to always stay synchronized with eachother.

Syncing of Participant data and Result data will now always run on the same interval – every 30 seconds. This change was made to reduce issues where we could cause RunSignup Results to lock up due to syncs happening to participant records and result records for a participant at the same time.

Bugs Fixed

Fixed an issue that could cause the app to crash after clearing chip cross reference.

Fixed an issue causing Actual Start Times and Corral Start Times to not be cleared when renewing a Race.

Fixed an issue causing reads from Backup Streams to be selected even if a time was available on a Main Stream.

Fixed an issue with Custom Computed Fields causing race exports/backups to not be able to be imported on another computer.

Fixed an issue with multi-segment aggregate team scored events which would cause teams to not properly show as incomplete.

Fixed an issue causing Corral assignment imports to not work properly when Corral names were numbers.


8/4/2022 – RaceDay Scoring v3.3.4

Feature Updates

Added the ability to save Data Check Reports.

You can now create and save Data Check Reports to reference later. These reports will stick around when exporting/importing a Race.

Added more options for filtering the Race List.

Prior to this change you could only update the filter to not show passed Races. Now you can show all, just those in the future, just those that have passed, or just those within X number of days.

These settings persist when you exit the app now, so you can keep the same filtering applied whenever you start the app up.

Added PC Timer/Mobile Timing App File Stream

This is a new File Stream format that you can use to import backup timing files created by PC Timer or the Mobile Timing App.

Added the ability to type TAB into the field delimiter area when setting up a custom File Stream.

Added the ability to accept Pre-Gun Chip Start Times for a specific Participant.

Prior to this update, you could only set this on the Scored Event level. Now if you had someone with an early chip start time that you want to use (normally these would be ignored if they happened before the start time of day), then you can go to their participant record and change this setting so that the system will take their early chip start time into consideration.

Added Scored Event Name to Entire Race Segment Labels.

This will help in identifying which entire race segment you are using when adding to reports or setting up custom computed fields. Now they will show as “5k Entire Race Segment”, for instance. This will be applied after saving Scored Events after getting the update.

Updated Participant Quick Mode Entry to allow including Custom Questions.

Prior to this update, you could not include RunSignup Questions when limiting what fields are displayed when using Quick Mode.

Updated duration inputs for Gap Factor and Time Custom Question Responses to make it easier to enter the correct format.

We now show the colons and decimal so that you will no longer mistake hours for minutes, for example.

Added Age Group Shortcut Links at the top of the Age Group Report.

Now you can easily navigate to a specific age band or top finisher category when viewing the Age Group Report. This is applied to both HTML exports and the Report view in the app.

Bugs Fixed

Fixed an issue causing Auto-Save “Plus” buttons to be displayed to the side of the icon instead of beneath.

Fixed a bug causing chip codes to not be saved if you are adding a participant and include the chip code as you are adding them.


7/20/2022 – RaceDay Scoring v3.3.3

Feature Updates

Updated Result Set Selection when Publishing Results to RunSignup.

If you are adding an Auto-save and no results exist for that Event on RunSignup yet, we will default the Auto-save to create a new Result Set.

If there is a single Result Set available, we will automatically select that Result Set in the dropdown, and will let you know via a pop up message that it has been selected and will overwrite any existing results in it.

If there are multiple Result Sets for the Event at RunSignup, you will be prompted to select which Result Set to use manually from the dropdown, or you can select to create a new Result Set.

Added the ability to import a Cloud Backup within a Race.

You can now import a Cloud Backup while working on a Race without having to exit the Race, delete it, and import from a new backup. You have the option to import just the setup or the entire race. The setup only option will not overwrite existing reads, while the full import will replace the reads with any from the backup you are importing.

Added more fields to the Data Check Report.

The following fields have been added as field options to display on the data check report:

Clock Start Time of Day Chip Start Time of Day Finish Time of Day, Chip time, Clock time, Scored Event, Age Grade.

We have also updated the default column set that is included in the Data Check Report:

Name, Gender, Age, Scored Event, Bib, Clock Start Time of Day, Chip Start Time of Day, Finish Time of Day, Chip Time, Clock Time.

This will help you be able to quickly identify participants who have missed a start read, but were read at the finish, for instance.

Updated Data Check Report to show all Super/Sub Event Participants.

We used to filter the results so we would not show duplicate participants, but now we will show all instances of each Participant so you can take action on any “version” of Participants who are in multiple Scored Events via a Super/Sub Event setup on RunSignup.

Updated Corrals to Prevent Setting Syncing Confusion.

Currently, RunSignup does not allow adding, editing, or deleting of Corrals remotely. This means that we can only get updates from RunSignup about Corrals, and not push changes back to RunSignup.

We have made some changes that prevent you from editing RunSignup Corral information, which would be overwritten the next time the sync was saved anyway, and have prevented the deletion of RunSignup Corrals, as they would repopulate the next time the sync was saved as well. This should help avoid confusion if you happen to save sync settings and see your changes to RunSignup Corrals disappear in your Corral setup.

Added Unattached Runner support for Cross Country events.

This is a Report Section level setting found in the Filters & Sorts area. By default, runners without a team association will now be included in Team Finisher List Report Sections, but they will not have a score or Team listed. They will not affect the scores of the other participants in the list. If you do not want to include unattached runners, you can update the setting found in the Report under the Filters & Sorts section.

Bugs Fixed

Fixed an issue causing exports/imports to fail after adjusting Scored Events and/or Segments.

Fixed an issue causing reads to not map to participants after changing a bib number that was used by a team to an individual participant.

Fixed an issue causing RunSignup to not properly display column order when Splits and Divisions are included in Result Sets.

Fixed an issue that would cause custom fields published to RunSignup to display twice.

Fixed an issue with how RSU will display Splits Time of Day fields.

Fixed an issue impacting Lap Races that have multiple Lap options and include Non-Timed Starts in the setup.

Fixed an issue impacting Lap Races that have a maximum of one Lap, and are set to finish immediately, that will some Participants to not have their DNF flag lifted as it should be.


7/7/2022 – RaceDay Scoring v3.3.2

Feature Updates

Change “Splits Time of Day” Field so that it can be published to native RunSignup Splits.

We publish this field in military time format so that it can be used in conjunction with RunSignup Video Results for Races that have multiple start times per Event.

Changed Report Search so that search terms do not go away after loading or editing a Report.

Bugs Fixed

Fixed an issue causing exports/imports to fail after adjusting Scored Events and/or Segments.

Fixed an issue that would allow you to try to add a Scored Read without having a Stream attached to the Location that you are adding the read for.

Fixed an issue causing Custom Questions/Fields that are in “Time” format to display in RunSignup Results in milliseconds instead of standard time format.

Fixed a bug causing the Resolve Unknown Reads view to not properly display the bib number of the read from the cross-reference file.

Fixed an issue causing some time of day timestamps to show in the wrong time zone.

Fixed an issue with USAT Export causing Segments to not display in the correct order.

Note: We use the Segment Order in the setup and select the first 5 Segments to place into the 5 available Segment Time “slots” that USAT accepts.

Fixed an issue causing USAT Exports to not include USAT Membership IDs if the Race had USAT Memberships set up to be Event specific instead of just at the Race level.


6/30/2022 – RaceDay Scoring v3.3.1

Updated database to improve stability and prevent missing/invalid ID errors.

This version includes a major update to the database to fix some issues we have been seeing for a long time that would cause you to have to save Scored Events or rebuild Reports to fix them.

Please note that this installation may take longer than normal to update as we upgrade your local database of Races.

Additionally, any computers that update to this version will not be able to revert back to an older version of scoring after the database upgrade is complete. We do backup databases between updates so it’s possible to recover if necessary – contact raceday@runsignup.com for instructions on reverting if needed.

Races created on older versions of scoring will be compatible with this version, but races created or loaded on this new version of scoring will not be compatible with older versions of scoring. Keep this in mind if you have many computers sharing backups – it is critical that you have all of your computers on either this updated 3.3.1 version or all on 3.2.X versions.

Finally, because of some changes to the way Auto-Saves are configured, any Auto-Saves created on older versions of the software need to be saved before unpausing them. Before saving the custom fields and splits will not populate at RunSignup – all you need to do is to save them and it will correct itself.

Feature Updates

Add functionality to look up existing result sets when deciding if you would like to publish a new one or overwrite an existing one.

You can now select existing Result Sets at RunSignup if you would like to reuse them instead of adding a new one when setting up a new auto-save.

Added support for sending new Custom Fields to Existing Result Set.

You can now include newly added columns in a report to an existing RunSignup Auto-save instead of having to delete it.

Added pop up when making changes to Reports and Segments to remind users that they must save any existing auto-saves in order to apply the recent changes to RunSignup Results.

All you need to do to update the auto-save is to click “Auto-Save” on a Report, then click save settings. There is no need to click the pencil icon to update the individual auto-save streams.

Additional columns in Reports now default to send to RunSignup as Arbitrary Text.

When setting up the Auto-Save you will now see all of the additional columns without having to open up the “Advanced Settings” area, and they will default to send as Arbitrary Text. You can always change what format they will send if you like.

Added support for sending “Splits Time of Day” and “Splits w/ Place” fields to RunSignup Results.

Updated Auto-Save setup on Reports with multiple sections.

We now show the auto-save settings for all sections that will be uploaded up front instead of only having one settings area that gets duplicated to the other auto-save settings panels after the setup is complete. This was confusing, as users would not understand that multiple result sets were going to be created.

Bugs Fixed

Fixed an issue causing imports to fail in a specific scenario.

Fixed an issue causing Corral changes made by a Data Action to not display correctly when viewing the Corral Members list.


6/22/2022 – RaceDay Scoring v3.2.19

Feature Updates

Added an option in the Segment Setup to Hide a Segment from Report Columns.

This will make it so that any Segments that have this setting enabled will not be included in any of the “Splits” type columns that include all Segments. In addition, these Segments will not be pushed to RunSignup Results. This is useful if you need to create a Segment for an announcer that you don’t want to include in reports, or if you have other Segments that you use for checkpoints that you don’t want to show in results. This is also useful for any Rest Segments that you have that you may not want to include in results.

You can always add individual Segment fields for Segments even if they are hidden from the “Splits” columns.

Added an option when setting up Custom Computed Fields to automatically create a “display” version of a calculated time.

Now you don’t have to manually create a new field based on the one you just made that just has a “ms2time” transformation applied in order to display a custom computed field in a standard time format.

Made minor adjustment to Team Type selection dialog to better accommodate long Team Type Names.

Added the ability to manually mark Data Issues as Resolved.

Bugs Fixed

Updated Race list with better paging, and will automatically switch to page one if updating filters.

Fixed an issue with Segment specific adjustments that would cause an adjustment to one Segment to apply to others.

Fixed an issue that would show a warning for reports including more than one section when it should not.

Fixed an issue causing Data Issues to not resolve when the thing that caused them had been fixed.


6/15/2022 – RaceDay Scoring v3.2.18

Feature Updates

USAT Export Option for Reports

We have added a USAT Export option from the Export dropdown on a Report. This will produce a spreadsheet that is in the format the USAT expects. You must have separate filtered Reports for each USAT Category, as we require you to tell the system the type of participants within the Report you’re exporting.

The categories are: Age Group, Open, Elite, Clydesdale/Athena, Para, and Relay.

Added Scored Event Option to Filter Reads Before Start Reads

This setting with ignore all times for a Participant until they record a chip start time. Once they record a chip start, we will ignore all reads prior to it, and accept any reads after it.

Bugs Fixed

Fixed an issue when creating Custom Computed Fields based on other Custom Computed Fields that would make some previously created fields not available in the existing field dropdown

Fixed an issue causing Splits fields to not respect the Timing Precision set on the Dashboard

Now if you display times out through the millisecond, the time values in the “Splits” field will also show out through the millisecond, for instance.

Fixed an issue causing “Splits w/ Place” field to not populate Split Places for Relay Team Reports

Made a change to prevent inaccurate warning for reports containing multiple sections.

Fixed an issue causing a failure to import with an improperly formatted bib/chip cross-reference file

Fixed an issue that could cause database corruption if you deleted a Race, then closed RaceDay Scoring before a Race had time to finish deleting it

Fixed an issue causing Reports to not include Corral filters correctly after export/import


6/10/2022 – RaceDay Scoring v3.2.17 Hotfix

Bugs Fixed

Fixed an issue when setting up Top Finisher Categories using the “By Rule” Band Jumping option.

Fixed an issue causing Backups to Cloud not working within a Race if that Race had not been backed up in the past.


6/8/2022 – RaceDay Scoring v3.2.16

Feature Updates

Report Template Import/Export Support

You can now import and export report template packages between computers. This is helpful if you have a set of templates that you typically use that you want to move over to another computer.

Added the Ability to Renew a Scoring Setup.

There is a new option in the Race List to renew a Race. This allows you to keep all of your scoring setup but pull down all the new event year registration information from RunSignup.

Items like Timing Locations, Streams, Segments, Reports, Age Groups, Top Finishers, Reports, etc… will all be copied to the new year. Reads will be removed, and Participants replaced with the new Participant data.

We do require you to map any variable fields that could change year over year. Specifically, things like Corrals, Team Types, Custom Questions are things that typically can change when a Race renews, so you must map what is used in the old setup with what is in the new year version of the Race. This is critical if you use RunSignup Custom Question Responses to drive Top Finisher Categories or Report Filters.

Added the Ability to Name Race Backups When Creating a Cloud Backup of a Race.

Now you have the option to include a name when you create a Cloud Backup. This will make it easier to identify different versions of a setup.

Added the Ability to Create a Cloud Backup With a Race Loaded.

In the green toolbar near the Force Sync button, you can now quickly create a Cloud Backup. You no longer need to exit a Race to back it up to the Cloud.

Added Entire Race Gun/Corral Start Time of Day Field to Custom Computer Field Builder.

You can now use the Entire Race Gun/Corral Start Time of Day Field when building calculated fields. This could be used as a way to build a “Chip Difference” field to show how long after the actual start time a participant crossed the start line.

Changed IPICO default Stream Settings to show ActiveTiming Streams.

Since ActiveTiming users use IPICO hardware, it made sense to allow those who set their default system to IPICO to be able to add an ActiveTiming Stream.

Added RDS Participant ID to Participant View/Edit

Bugs Fixed

Fixed issue with import setup only races under certain circumstances

Fixed an issue causing Super Event Participants’ Results Panel in View/Edit Participants to not wrap Sub Event Names in the Event Selection area.

Fixed issue causing Team Name search to not work properly in reports

Fixed an issue causing the shutdown prompt to show beneath other full-screen dialogs.


5/25/2022 – RaceDay Scoring v3.2.15

Feature Updates

Added the ability to customize Aggregate Team Detail Report Filters to only show those that scored.

This is found in Team Detail Report Sections when building Reports under the “Filters & Sorts” section.

This will hide all participant’s who weren’t used towards counting the group’s aggregate placement. Participants who were not originally scored, but were used as Tie-Breakers, will not be included in the shown list.

Added the ability to import adjustments to specific segments.

This is found under Participants > Actions.

This will allow you import Segment adjustment times for a specified participant. Prior to this change you could only import adjustments to the “Entire Race Segment” field. You will need to create a spreadsheet with a column for a reference to the participant (RunSignup Registration ID or RDGO Participant ID), and each Segment that needs to be adjusted. The name of the headers besides the ID will need to match the Segment name in RDS exactly.

Added “Aggregate Custom Field” options when creating Custom Computed Fields.

This is found under Scoring > Computed Fields > Add/Edit Custom Fields.

This will allow you to build custom computed fields that are based on the average, minimum, or maximum of any number of other fields. This can be used to produce a single field that holds the minimum time over three different segments, for instance.

You could create a millisecond version of this field to sort by, then create a readable time to display, then create a report that sorts by and displays this custom field if you needed to score a race based on the min. time over some selection of segments.

Bugs Fixed

Change Participant Export so that Sub-Event Participants have their event name replaced with their Sub-Event name instead of their Super-Event name.

So instead of “Bundle” it would show “5k”, “10k” for each sub-event version of the super-event participant.

Fixed An Issue when entering Time formatted Custom Fields.

Fixed An Issue with manual Marker Reads.

Removed unneeded database version log message from notifications.


5/12/2022 – RaceDay Scoring v3.2.14 Hotfix

Bugs Fixed

Corrected an issue causing the in app updater to stall at 100%

v3.2.12 introduced a bug with the updater that would cause the app to stall at 100% when installing an update. It’s entirely safe to force close the app once it has reached 100%, and the update will be installed properly.

This fix will apply the next time an update is available, so you will still have to force close after installing this update.

For now, if you notice that the installer is stuck at 100% you can use CTRL + ALT + DELETE and force close the app without fear of harming anything.


5/11/2022 – RaceDay Scoring v3.2.13

Feature Updates

Added warning when saving MyLaps Readlite File Streams and Chronotrack File Streams if you do not have the date override set.

These two systems do not include date in the passing data, and our default is to use the current system date when bringing reads it. This can cause problems if you are ever collecting reads not on the actual race date, so we are now forcing you to select a date override when saving. Generally you would want to use the “Set to Race Date” feature so that all incoming reads will use the date of the Race.

Note: If you are scoring a multi-day event with one of these stream types, set the date override to the first day, as we have found that these systems will export data over 24 hours by counting up the hours further (25 hours) instead of resetting to 1 hour times on the next day.

Added Gender Labels to Top Finisher Category Names in Reports.

Now if you have a Top Finisher Category called “Overall”, we will show the gender label in the “Age Place” column. For example Male and Female “Overall” winners will now show like this: “1: M Overall” or “1: F Overall”, whereas before this change both would show as “1: Overall”.


Bugs Fixed

Fixed an issue causing times to not display in RSU Announcer Links.

RSU will now display the time of day that the read occurred at the location for these links.

Fixed an issue causing reports with individual Segment Place fields to not run.

Fixed an issue causing Data Actions to not fire on Super Event Participants.


5/5/2022 – RaceDay Scoring v3.2.12

Feature Updates

Added Option to Create a Cloud Backup when Exiting the App or Switching Races.

For any Races that have had Cloud Backups created for them, we will now present the option to create a Cloud Backup when you exit the software or switch races. This will be helpful on site so that Timers in the field will remember to back things up once they’ve finished scoring the Race.


Bugs Fixed

Fixed an issue when importing Setup Only Export files.

Added better error messaging when report is in a bad state and needs to be re-saved.

Fixed an issue causing segments in the Splits column to not be displayed in the order you have set up in the Segment setup.

Fixed an issue that allowed users to create multiple Streams with the same Hardware Name, which could cause reads to not be selected properly.

Fixed a few issues with Ambiguous Read Pair selection.

Fixed an issue when importing adjustment times with a CSV.

Removed Incompatible Sort Fields

Some sort fields that are not necessary have been removed like Segment Places and Team Aggregate fields. To sort by the fastest Segment, just select the Segment Time field instead of using Place, and it will give you the same result.


4/28/2022 RaceDay Scoring v3.2.10

Feature Updates

Added Data Check Function to Data Actions

This is the first version of a new function in RaceDay Scoring that will allow you to search for Participants who meet some conditions (for instance, all of those who missed their start read but have a finish read, or all of those who have an age grade over 90), then manually apply a change to them, with the option to select all, or pick and chose which ones you would like to update.

When you search for Participants, it will present a table of all participants who match the filtering you have set up, and there will be a checkbox in each row. You can then apply any changes you like to the Participants in the Data to Change section by using the “Update Selected Rows” button.

You could make any change you like to them. For instance, you could disqualify all those who missed their chip start but have a finish read, or you could update a Custom Field that you have set up that you use to indicate suspicious participants that have an Age Grade value over 90.

We will be adding more features and options to this function in the future, including things like preset Data Check Reports for common use cases, the ability to save and reference Data Check Reports later (right now the search fields and settings go away after you close the report), and the ability to include additional fields to display like chip read times of day for each Participant.

Note: In order to use this function on an existing Race, you should save the Scored Events page before using, as some new fields will not be available until you save Scored Events after the update is applied.

Updated the Participants > Actions > Fix Unknown Reads Feature To Only Show One Instance Per Participant.

We used to show every instance of an unknown in this area – now we will only show one so it’s much easier to manage resolving unknown reads.

Made a change to how restrictive we are with Auto-Saves when Participant Sync is disabled.

We used to restrict all auto-save types if Participant Sync was disabled and you had pending items in the Sync Queue. Now we only restrict RunSignup Auto-Saves, meaning that you no longer need to have Participant Sync enabled to use RaceDay Hub Kiosk Auto-Saves.

Added Option to Delete Associated RunSignup Results When Deleting All Reports.

Bugs Fixed

Fixed an issue causing errors when using RunSignup Announcer Links with Relay Teams.

Fixed an issue when adding local Relay Team Types that could cause you to not be able to build Reports combining Team Types.

Fixed an issue causing Report Section Type description tooltips to not show when hovering over the button to add them to a Report.


4/22/2022 – RaceDay Scoring v3.2.9 Hotfix


A bug was introduced in v3.2.8 that causes an issue when manually adding Raw Reads and recalculating. If you plan on manually adding Raw Reads and are currently on v3.2.8 we highly recommend you apply this hotfix.


4/20/2022 – RaceDay Scoring v3.2.8

Feature Updates

Removed Age Place column for Default Age Group Reports

Since the Place column and Age Place column would be the same for Age Group Report Sections, we removed this.

Updated terminology from Team Classification to Team Type throughout the app.

We were inconsistent by using Team Type and Team Classification to describe the same thing in a few spots. We have changed this to always refer to them as Team Types throughout the app.

Show bib number from crossreference when encountering unknown chip read.

Now it will be easier to figure out unknown reads when using a chip cross reference. Before you would have to look up the chip code in the crossreference to figure out the bib number it was related to, now we show the bib number in the Raw Reads view.

Updated Timing Location Max. Occur. Count Label for Lap Race Timing Locations.

All Timing Locations marked as a Lap Timing Location allow for unlimited occurrences. We have updated the label on the Timing Locations List to show this.


Bugs Fixed

Fixed an issue causing the Team Type Count to not display in the Team Types List.

Fixed an issue causing custom fields that are Radio or Dropdown type to not be selectable when setting up a Data Action to change their selection.

Fixed an issue causing Raw Reads to not show as locked in some circumstances.

Fixed an issue with importing Age Groups.

Subscribe to Our Blog

Customize Lists...
Loading